CodedConstructs

Take repetitive structural work off your team's hands.

I build custom plugins, workflows and automation for structural engineering firms that don't have an in-house digital team. Most projects involve connecting analysis, modelling and documentation.

by Braden Koh Braden Koh
Discuss a workflow See past outcomes

Too much structural work is still repeated by hand.

Engineers and drafters redraw details, rebuild models, and re-enter analysis results for documentation. Then they do it again when the design changes.

Three things usually get in the way:

  • Custom tools for Revit and analysis software sit outside your IT team's usual remit.

  • A full-time developer is hard to justify when you only need them for specific workflows.

  • Off-the-shelf software leaves gaps because every firm models and documents its work differently.

So your team keeps spending project time re-entering data, redrawing work and checking for errors when a computer could be doing it.

I understand the work and can build the tool.

General software developers rarely know the ins and outs of delivering a structural project. The engineers who do rarely have the time or software experience to build the tools properly.

CodedConstructs sits in between.

More about me →

Structural experience built in

I already understand the projects, software and standards behind the workflow, so you don't have to translate structural delivery for a developer.

The right problem gets solved

I work through the workflow before I build, so the tool addresses the part that is costing your team time.

A tool your team can use

I build around your software, standards and way of working, so the tool fits the process your team already knows.

Software capability without a full-time hire

Bring in someone who understands structural delivery and can build the software when there is a clear workflow to improve.

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 agree on the scope and fee, then I 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.

* If the workflow needs more investigation before it can be scoped, we start with a separate discovery phase.

Discuss a workflow See the full process

Should we work together?

This work has the most value when a structural team repeats the same tasks across projects and has no one in-house to automate them.

Good fit when

The same modelling, detailing, or drawing work comes back on every project

Your team keeps moving the same information between analysis and documentation tools

You know the process could be better, but not what to automate

You can already see where the tool would fit into your next project

Probably not a fit when

The work barely touches software

The workflow still changes from project to project

Existing software already handles the problem well enough

You need ongoing day-to-day support or a full-time digital hire

Still unsure?

Book a call
Braden Koh, founder of CodedConstructs

Tools built around the way structural teams actually work.

I'm Braden. For years, I was the digital person inside structural teams, building the tools, scripts and workflows that real projects ran on.

That work included Atlassian HQ, Sydney Metro, Hong Kong International Airport and the National Gallery of Victoria.

Now I do the same for firms without someone in-house, turning repeated project work into tools their engineers and drafters can rely on.

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

CodedConstructs builds tools around the structural workflows your team already relies on, so the repeated work does not have to stay manual.

Discuss a workflow