CodedConstructs
Services

Custom tools for structural production work.

Most engagements are custom builds for structural engineering firms. That might mean a plugin, a workflow or automation that connects analysis, modelling and documentation.

I also offer strategy consulting and hands-on workshops when your team wants to do more of this in-house.

What each service includes.

Main focus

Custom Builds & Automation

Custom plugins and automated workflows for the structural work your team repeats.

I scope, build, test and document a tool around one clearly defined workflow, shaped around your standards and the software your team already uses.

Useful when

  • A workflow repeats often enough to be worth automating
  • Existing software doesn't support the exact process
  • The team relies on awkward manual steps between tools
  • You need a reliable, reusable tool, not a one-off script

What you get

  • A working tool built around the agreed workflow
  • Testing against clear acceptance criteria
  • Source code and documentation
  • A clean handover and 60-day warranty
Discuss a workflow

Strategy Consulting

Work out where digital tools could help across the firm, which systems need to connect and where to invest first.

I map how information moves between teams and software, find where people are filling the gaps by hand and set out what to tackle first.

Useful when

  • Manual work and duplicated data sit across several teams
  • Digital tools have grown without a clear plan
  • Systems don't connect and people fill the gaps by hand
  • Leadership needs practical priorities before committing budget

What you get

  • A clear map of how information moves between teams and software
  • The gaps, duplicated work and manual handoffs worth addressing
  • A ranked list of what to improve, replace or connect
  • Recommended next steps, with the reasoning behind them
Discuss your systems

Workshops & Coaching

Hands-on training built around the structural work and software your team already knows.

Workshops are typically three-hour sessions, but the format can change depending on what your team needs.

Useful when

  • Your team wants to upskill on automation or computational tools
  • You'd rather build capability in-house than outsource everything
  • People use powerful software but only scratch the surface
  • You want practical, hands-on training, not generic slides

What you get

  • A workshop built around your real workflows
  • Hands-on techniques the team can use immediately
  • Starter scripts or templates to build on
  • A clearer sense of what to automate next
Discuss a workshop

How a custom build works.

Once we know the workflow is worth automating, this is how the work usually runs.

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.

A few practical questions.

How much does it cost?

Custom development is quoted at a fixed price. I scope the work first and we agree on the fee before anything starts. I'll never ask for payment until there's a clear way forward.

How long does it take?

Most tools take weeks rather than days. A Revit plugin often takes around a month, while a standalone program can take around two months. I'll give you a realistic schedule once I understand the workflow.

Who owns the tool and the code?

You do. You receive the tool, source code and documentation. It's yours to keep, run and change if you need to.

What if it breaks or we need changes later?

We agree on acceptance criteria and test the tool against them. Custom builds include a 60-day warranty. Later changes can be quoted separately, or I can maintain and extend the tool through a light retainer.

Will it work with our software?

Usually. I build around tools including Tekla Structures, Revit, Rhino and Grasshopper, RAM Concept, ETABS, SAP2000, AutoCAD, Civil 3D and Excel. If an API or file format creates a real blocker, I'll tell you before you commit.

What if we're not sure it's worth automating?

Start with a call. Part of my job is working out what is worth automating and what should stay manual. Sometimes the answer is ‘don't build it’. You won't get a pitch for something you don't need.

Have a workflow in mind?

Tell me what your team is doing by hand. I'll help you work out whether it is worth automating.

Discuss a workflow See past outcomes