02Custom Software Build
Built in your accounts. If we walked away tomorrow, it would still run.
We build the systems an audit prescribes — in your tools, under your logins, with the documentation for someone else to take over. That's the whole test, and most of what follows is us showing our working.
What you own
The test is whether it survives us.
Plenty of software gets built in a way that quietly depends on the people who built it — their accounts, their subscriptions, their access, their undocumented decisions. It works beautifully right up until the relationship ends.
It's worth asking anyone you hire, including us: whose account is this being built in, and what happens to it if we stop working together?
Your accounts, your logins
The system runs on infrastructure you control and pay for directly. Not resold through us, not sitting inside a subscription we hold.
Your data stays yours
It lives where your business already keeps things. Nothing gets routed through a platform of ours that you'd have to extract it from later.
Handoff docs with every build
What it does, how to tell it's working, what to do when it isn't. Written so another developer could pick it up without calling us.
One accountable contact
Including when a vetted partner does some of the building. You get one person to hold responsible, not a chain to chase.
What gets built
Two sizes, and the audit tells you which.
A single workflow
One process, automated end to end. A thing that currently eats a morning every week, doing itself instead. Scoped tightly, shipped, documented, done.
Usually a quick win on the matrixAn agent system
Several workflows that share context and hand off to each other — the shape you need when the problem spans your whole client lifecycle rather than one step of it.
Usually a big swingWhich one you need isn't a question you should have to answer before buying. That's what the audit is for.
How it's built
Not a no-code tool shuttling data between boxes.
Most of what gets sold as automation moves information from one app to another and calls it finished. That's fine for the simple cases, and where it's the right answer we'll tell you to use it rather than pay us.
The work worth paying for is the part that needs to actually remember and understand context — a client's history, what was said last session, what's changed since. That's the difference between a system that files things and one that notices them.
Cost
There's no price on this page, and that's deliberate.
Any number here would be invented. What a build costs — and how long it takes — depends on what it has to do, what it has to connect to, and what already exists in your business. We don't know any of that yet, and we'd rather tell you nothing than tell you something we'd have to take back on the first call.
We don't take on build projects under $1,500.
How it starts
The first session is where it gets pinned down.
What's being built, what it connects to, what already exists. That session is $200, and you come out of it with a real scope and a real number for the build itself.
Not sure you need a build yet? Start with the audit instead.
Examples
What a roadmap typically prescribes.
Examples, not a menu. What actually gets built depends on what the audit finds in your business.
Payment chaser
Watches for late and failed payments and drafts the follow-up in your voice.
No-show rebooker
Catches a missed session the moment it happens and drafts a personal rebooking message.
Check-in digest
One short summary of who needs your attention this week, instead of reading everything by hand.
Lead follow-up catcher
Qualifies and follows up with every enquiry, so interest doesn't quietly disappear.
Session-to-content repurposer
Turns one recorded session into a month of content in your own voice.
Already deployed
Every system below is running, and you can look inside it.
Not mockups and not diagrams of what we could do. Open any one to see the architecture that's actually in production.
Afterwards
Then it needs keeping alive.
Systems that get shipped once and left alone are the ones that quietly fail. Tools change their APIs, models get replaced, and your business stops working the way it did when we mapped it. A retainer covers keeping what's running current as all that moves.
It's optional, and it's optional in a way that means something — you own the system, so stopping the retainer doesn't stop the software. That's rather the point of building it this way.
Questions
What people ask before booking.
How much does a custom AI build cost?
It depends entirely on scope, which is why there's no number on this page. The $200 scoping session exists to turn that into a real figure. We don't take on build projects under $1,500.
How long does a build take?
Same answer, same reason — it comes out of scoping. A single workflow and a multi-step agent system are very different jobs, and quoting a duration before we know which one you need would be guessing.
Who owns the system when it's finished?
You do. It runs in your accounts on infrastructure you pay for directly, your data stays where your business already keeps it, and handoff docs ship with every build so another developer could take it over.
What happens if we stop working together?
The system keeps running. That's the test this whole page is built around — nothing we build is designed to make leaving expensive.
Can you build with the tools we already use?
Wherever possible, yes, and we'll push for it. Fewer new subscriptions and fewer new logins means less to maintain and less for your team to learn.
Do we have to do the audit first?
It's the usual route, because building the wrong thing well is the expensive mistake. But if you already know what you want built, the scoping session is the faster path.
See where you stand.
A few questions about how your business runs, and you get a score and a written breakdown back. If a build is the right next step, you'll get a link to book a 20-minute call.
See where you stand