The work that's slowing your team down.
Most teams I work with are losing hours to the same handful of things:
- Copying the same data between tools by hand, every project.
- Updating the same drawings, models, or data manually after every change.
- Fighting off-the-shelf software that doesn't work the way you do.
- Having a great technical process but it's slow and manual.
- Knowing it could be faster, with no one in-house to build the fix.
If any of that sounds like your team, here's how I help.
Three ways I help.
Strategy, training, or custom development for small to medium AEC teams.
Not sure which fits? Chat with me →
What working together looks like.
The full picture of how a project runs, from the first call through to ongoing support.
Intro
A quick call to discuss the problem and see how I can help.
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.
Handover
We hand over everything, the tool, the docs and any relevant info to your team.
Support
A 60-day warranty once the build passes its tests, plus optional ongoing support.
Questions.
How much does it cost?
All custom development is done on a fixed-price. I scope the work first and we agree on the price before anything ever starts. I never take payment before we know the way forward.
How long does it take?
Tools can take from weeks to months, depending on complexity. I'll give you a realistic timeline once I understand the workflow better. Generally, Revit plugins take ~1 month and standalone programs take ~2 months.
Who owns the tool and the code?
You do. You get the tool, the source code, the documentation, everything. It's yours to keep, run, and change if you need to.
What if it breaks, or we need changes later?
We test things as we build and define criteria that the tool must pass. Every tool also comes with a warranty. Beyond that, changes are quoted as small follow-on pieces, or you can keep me on a light retainer to maintain and extend it.
Will it work with our software?
Almost certainly. I build around the tools your team already uses: Revit, Rhino, AutoCAD, Civil 3D, Excel, anything. If there's a real technical blocker, I'll tell you early on, not after you've committed.
What if we're not sure it's even worth automating?
Then we start with a call first. Part of my job is telling you what's worth automating and what isn't. Sometimes the honest answer is "don't." You won't get a pitch for something you don't need.
Ready to turn a workflow into a tool?
Book a short call and we'll work out whether it's worth building, and what it'd take.