ENGINEERS AI TOOL

OPTIMISING ENGINEERS WORKFLOW

Meet Scottie and his roof calculator

Working with an engineering firm to optimise their workflow:

Built a live tool that pulled values straight off a structural 3D model and ran a full set of complex calculations, saving one of their specialist engineers around two hours every fortnight.

Right now we're running a workflow audit, mapping out where the real bottlenecks sit. That's how we find the areas with the biggest impact and build out from there. You need the big picture of the business before you get granular, not the other way around. Human connection and listening come first, that's how we pull out what actually matters before we implement anything.

Here's how we got there:

I listened first. Before I started, I got him to walk me through how he currently works, what the two hours a fortnight was going towards, and what would save him time.

I broke it down with him, step by step. Instead of simply handing him a finished black box, I broke down the problem in pieces he already recognised from his own process.

I showed him the how, not just the what. I sat him in front of VS Code and built it with him watching. He saw exactly where AI slotted into his existing process and where his own judgement still mattered.

I got him to verify it. Once it ran, Scottie checked the output against what he already knew as a structural engineer, and confirmed it was right.

An hour later, we'd built it. The other engineers all had their own subscriptions by the end of the day, nobody told them to, they just watched what Scottie did and and wanted in.

ENGINEERS AI TOOL

OPTIMISING STRUCTURE
ENGINEERS WORKFLOW

Meet Scottie and his roof calculator

Working with an engineering firm to optimise their workflow:

Built a live tool that pulled values straight off a structural 3D model and ran a full set of complex calculations, saving one of their specialist engineers around two hours every fortnight.

Right now we're running a workflow audit, mapping out where the real bottlenecks sit. That's how we find the areas with the biggest impact and build out from there. You need the big picture of the business before you get granular, not the other way around. Human connection and listening come first, that's how we pull out what actually matters before we implement anything.

Here's how we got there:

I listened first. Before I started, I got him to walk me through how he currently works, what the two hours a fortnight was going towards, and what would save him time.

I broke it down with him, step by step. Instead of simply handing him a finished black box, I broke down the problem in pieces he already recognised from his own process.

I showed him the how, not just the what. I sat him in front of VS Code and built it with him watching. He saw exactly where AI slotted into his existing process and where his own judgement still mattered.

I got him to verify it. Once it ran, Scottie checked the output against what he already knew as a structural engineer, and confirmed it was right.

An hour later, we'd built it. The other engineers all had their own subscriptions by the end of the day, nobody told them to, they just watched what Scottie did and and wanted in.

ENGINEERS AI TOOL

OPTIMISING STRUCTURE
ENGINEERS WORKFLOW

Meet Scottie and his roof calculator

Working with an engineering firm to optimise their workflow:

Built a live tool that pulled values straight off a structural 3D model and ran a full set of complex calculations, saving one of their specialist engineers around two hours every fortnight.

Right now we're running a workflow audit, mapping out where the real bottlenecks sit. That's how we find the areas with the biggest impact and build out from there. You need the big picture of the business before you get granular, not the other way around. Human connection and listening come first, that's how we pull out what actually matters before we implement anything.

Here's how we got there:

I listened first. Before I started, I got him to walk me through how he currently works, what the two hours a fortnight was going towards, and what would save him time.

I broke it down with him, step by step. Instead of simply handing him a finished black box, I broke down the problem in pieces he already recognised from his own process.

I showed him the how, not just the what. I sat him in front of VS Code and built it with him watching. He saw exactly where AI slotted into his existing process and where his own judgement still mattered.

I got him to verify it. Once it ran, Scottie checked the output against what he already knew as a structural engineer, and confirmed it was right.

An hour later, we'd built it. The other engineers all had their own subscriptions by the end of the day, nobody told them to, they just watched what Scottie did and and wanted in.