Loading
Pricing
Most firms in this space will not put a price on a page. That is a sales tactic, and it wastes the time of anyone whose budget was never going to reach. Here is what things cost.
Start here
$3,500
fixed fee · 2 weeks
The main thing
$4,000 – $75,000
fixed scope · fixed price · milestone billing
Ranges are driven by document variety, how cooperative your existing software is, and whether the process is already well defined. The assessment turns a range into a number.
Running costs
$50 – $800/mo
Hosting and AI usage, billed at cost directly to your accounts. No markup.
Support retainer
$1,200 – $3,500/mo
Optional. Monitoring, small changes, and someone to call. Plenty of clients skip it.
Hourly
$175/hr
Small changes to systems we already built. Not how we price new work.
What is never in the invoice
Any of these numbers is only meaningful next to what the manual process is costing you now. The calculator does that in about a minute, and it is deliberately conservative.
Because the alternative wastes both our time. If your budget is $3,000 and the work costs $15,000, we should both find that out today rather than after two discovery calls and a proposal. Hidden pricing exists to keep you on the phone long enough to be sold to.
For a defined scope, yes. If we underestimated the work, that is our problem and we absorb it. If you change the scope mid-build, we price the change and you decide whether to proceed. Nothing gets added quietly and invoiced later.
Hosting and AI usage, billed at cost to your own accounts — typically $50 to $600 a month. Phone agents run higher because telephony has real per-minute costs. We do not mark up infrastructure.
Rarely, and only for small changes to something we already built, at $175 an hour. Hourly billing on a new build misaligns the incentives — it pays us to be slow, and it moves all the estimation risk onto you.
Available after launch for support and small changes, typically $1,200 to $3,500 a month depending on the system. Genuinely optional. Plenty of clients launch, hand it to their own IT people, and never take one.
No. It complicates a straightforward relationship and it tends to end badly for the smaller party — which, in that arrangement, is usually us.
A 30-minute call where we work out whether there is anything here worth building. If there is not, we will say so — that is a useful outcome too.