Not a flat day-rate, and not a number we make up. Where there's an existing process to replace, we quantify what it's actually costing — hours, errors, delays — before we quote anything. Where there isn't one yet, the price comes from the scope itself, not a made-up baseline. Either way, the number is fixed before you commit.
Fixed once scoped. This is the typical range, not a floor or a ceiling — the exact number comes out of the Architecture Blueprint, and it doesn't move after that.
We anchor to something real.
Replacing an existing process, we put a real number on what it costs today — hours, errors, delays. Building something new with no process to measure yet, we price directly from scope instead — see what actually moves the price below.
We price against that, not a guess.
Where there's a cost baseline, the build is priced as a fraction of what it adds up to over a year. Either way, it's never a day-rate multiplied by a guess at how long the work will take.
The number is fixed before you commit.
You see the price in the Architecture Blueprint and sign off before any build work starts — never a moving target once work begins.
The Discovery Sprint itself is a paid engagement. If you move forward into a Build Sprint, that fee is credited against it — you're not paying twice to get to a fixed price. If you don't move forward, you keep the scope document either way; it's yours regardless of what you decide next.
Month to month, no term contract. We keep what we built running, tuned, and supported. Cancel any time — the software is yours to run without us either way, this is only for the ones who'd rather not do that alone.
How many systems it needs to talk to — one clean data source is a different job than three that don't agree with each other.
Whether existing records need to be migrated in, or the system only needs to handle things going forward.
How much of the process needs real AI judgment — reading and extracting from messy input — versus straightforward forms and workflow.
Whether it's a clean new build or has to fit around a system you're already running in production.
How many distinct roles need their own view — a single user is a different job than an org with layered permissions.
Score the shape of your project the way we would in Discovery. This is a guide only — it needs confirming in your first Discovery Sprint before it's a real number.
Toward the simpler end of what we build — a shorter Discovery Sprint, a tighter Blueprint.
This is a guide only — it needs confirming in your first Discovery Sprint. The real price comes from that conversation, not from this tool.
The Discovery Sprint is the only step that turns any of this into an actual quote for your business.