How it works
We start with the business problem, then work out the software.
Most people come to us knowing exactly what's broken and not at all what should be built. That second part is our job. Below is how the whole thing works from start to finish, including when you start paying, which most firms leave vague.
Where it usually starts
Three reasons people call us.
Almost every engagement begins as one of these, and often as a combination of the last two.
01
A business problem, no obvious fix
Something is holding the business back and you know the symptoms exactly. The double-bookings, the re-keying, the report that takes two days. What you don't have is a clear picture of which software fixes it, or whether software is even the right answer. That's the conversation we're best at.
02
Software that costs too much
Per-seat licenses that climb every time you hire, platform fees that go up with your volume, or a maintenance contract on a system nobody has improved in years. Over time the bill has crept past what the software is worth to you.
03
Software that delivers too little
You've bent your business around a product and still use a fraction of what it does, working around the parts that don't fit. Often it's both at once. You're paying a lot, getting little back, and can't see a way to change either.
You don't need to arrive with a spec. Plenty of clients come to us describing a problem in plain business terms and leave the first call with a clear idea of what software would fix it, what it would cost, and sometimes that they shouldn't build anything at all.
How we work
Security comes first
Everything we do starts with one question: is this safe to run your business on? Your accounts, your code and your domain are in your name from day one. Your team signs in with their Microsoft 365 accounts, so access is granted and removed in one place. Every change is built and reviewed away from your live system, and a person reviews the code before it goes live. You can read more on our security page.
We use AI tools to build faster, the way an accountant uses a calculator. A good accountant can do the math by hand, but the calculator lets them get through more work, and they're still the one who signs off on the answer. It's the same here. Experienced people on our side design the system, review the code, test it and keep it secure. Where AI runs inside your platform, we use business-grade providers that don't train on your data, and we send it only what the task needs.
The engagement
From the first call to software that keeps improving.
We learn how your business runs
Day oneWe start with a conversation about the business, not a feature list. What you do, what's slowing you down, what it's costing you, who touches each job, and which tools you use today. We also ask what information you handle and who should be able to see it, because that shapes how we build. Afterward we write it up in plain language and you correct anything we got wrong. You don't need to arrive knowing what the software should be. Working that out is our job.
An initial demo
About a week laterRoughly a week after that call you get a working demo rather than a proposal document. It's built from the write-up, so you're correcting something real instead of describing your processes from scratch. If we got it wrong, we find out in week one, when that costs almost nothing.
Reviews every two weeks
Until the first versionFrom there we build in two-week rounds, and every review is a working version you can click through. You steer with real feedback on real screens, so what launches is something your team will want to use.
The first version goes live
Billing starts hereYour system goes live, with your records moved over and the whole thing hosted, secured and monitored. This is also where billing begins, and where the 12-month term starts. You don't pay a monthly fee, and no clock runs, while we're building toward that first release.
A 12-month roadmap
Just after launchWith the first version live and real people using it, we plan the year together. By now we can plan around how your team really uses it, which is never quite what anyone guessed at the start.
Support, security & improvements
Every month afterUpkeep, support and security updates are part of the fee, along with set hours each month for improvements from the roadmap. The software keeps getting better long after launch day.
Why billing starts at launch, and not before
Because the risky part of custom software is getting to a first release that people use, and that risk should sit with us rather than with you. It also keeps us moving. We have every reason to get a working first version in your hands quickly, and none at all to let the planning stage drag on. Plans run from $1,000/mo on a 12-month partnership, and both the first invoice and the 12 months start the day the first version goes live. AI usage (model and token costs) is billed separately at cost, outside the monthly fee.
See what it costs →Questions about the process
What if we don't know what we need built?
Most clients start there, and honestly it's the better place to start. They come to us with a business problem rather than a specification. The schedule falls apart every week, the quoting process takes three days, the software bill keeps climbing. Working out what should be built, and whether it should be built at all, is the part we do before anyone writes code.
Do you ever tell people not to build something?
Regularly. Sometimes the fix is a settings change in software you already own, sometimes it's an off-the-shelf product that fits well, and sometimes the problem is the process rather than the software. We'd rather give you that answer in the first hour than sell you a system you didn't need.
When exactly does billing start?
When the first version goes live and your team is using it for real. You don't pay a monthly fee during scoping, the initial demo, or the rounds of building that lead up to launch. That way we carry the risk of getting to a working launch, which is how it should be. The one exception is an unusually large or older system, where we may recommend a short paid discovery phase first, and we tell you that up front.
When does the 12-month term start?
The 12 months start when version 1.0 goes live, alongside your first invoice. No clock runs while we are building toward that release. It runs from launch because that's when you start getting value out of the software and we start being paid to keep it running well.
How long until the first version is live?
A focused tool is often live in about a month or two. Something that runs a real part of your operation usually takes longer, and a system the whole business depends on can take six months or more. You see a working version every two weeks throughout, so you always know where it stands.
What happens after the 12-month roadmap is set?
Then we build it, a piece at a time, using the hours included in your monthly fee. We revisit the roadmap as the business changes instead of treating it as a contract, so if something more valuable comes up in month three, we build that instead.
Who will we be talking to?
The people building it. No account manager in between, no ticket queue, and no handoff to a team you've never met. We work that way on purpose.
Start with the problem. We'll work out the software.
One hour, no charge, no obligation. Come with what's broken and we'll tell you what would fix it, even when the honest answer is that you shouldn't build anything.
One monthly fee · Built, hosted & improving · You own the custom code