CodedConstructs

Turn repetitive workflows into custom tools.

I help small to medium AEC teams turn repetitive workflows into custom tools they actually keep using.

by Braden Koh Braden Koh
Discuss a workflow See past outcomes

AEC's best workflows are too manual and locked inside documents, spreadsheets, and individual experts.

Leadership knows the work could be far more efficient.

But three things stand in the way:

  • Internal IT teams can't build custom tools.

  • Hiring and resourcing a dedicated dev team is hard to justify.

  • Off-the-shelf software doesn't reflect how you actually work.

The result: slow delivery, high cost, and a fragile process.

A new model for creating tools in AEC.

Most automation comes from software people who don't know delivery, or delivery people who can't build.

CodedConstructs sits in between.

More about me →

Built from experience, not just ideas

Every tool comes from years of real computational delivery work, not just theories about how AEC should work.

Understand first, then deliver

The workflow is understood and clarified before anything is built, so the tool solves the real problem.

Tools that work with you, not the other way around

Built around how your team already works, so no one has to bend their process to fit new software.

Capability without the overhead

You get tools built without worrying about salary, management, or utilisation of a full-time developer.

What working together looks like.

In my experience, one big commitment upfront is overwhelming. Together, these stages help us understand the value of what we're building before committing to it. They give you and me the clarity to ensure we're building the right thing.

01

Intro

A quick call to discuss the problem and see how I can help.

02

Scope & Build

We scope the work (with an optional discovery phase if too complex), agree on a fee, then build, test, and document the tool.

03

Handover

We hand over everything, the tool, the docs and any relevant info to your team.

04

Support

A 60-day warranty once the build passes its tests, plus optional ongoing support.

Discuss a workflow See the full process

Should we work together?

Best for small to medium AEC teams who face the same technical work repeatedly, without the time or capability to handle it in-house.

Good fit when

The same work keeps coming back, project after project

Your team loses hours entering or moving data between tools

You don’t have anyone in-house to build the tools you need

You know technology could help, but not how to apply it

You’d rather have a tool shaped around your workflow than cobble together a few off-the-shelf ones

Probably not a fit when

Your day-to-day is hands-on and barely touches software

You’re not open to bringing new tools into your process

There’s no settled workflow to improve yet

You want the problems gone without changing how you work

You need a full-time hire for support not someone to make you a custom tool

Not sure if this is right for you?

Discuss a workflow
Braden Koh, founder of CodedConstructs

Hi, I'm Braden.

I've spent most of my career inside structural engineering consultancies, building the tools, scripts, and workflows that real projects ran on.

Now I do that for other teams, turning the workflows you repeat into custom tools your team actually keeps using.

The way I make that happen is to understand the problem first, then build something that fits how you really deliver.

The best tools work with your team, not the other way around.

That's what CodedConstructs is here to build, turning your best workflows into tools for more efficient delivery.

Discuss a workflow