Integration · from $6,500
Two to three weeks for a supported system. QuickBooks Desktop starts at $9,500 because it is genuinely three times the work.
Services
Implementation pricing in this industry is opaque by design: a day rate, an estimate, and a change-order relationship. We publish the numbers and the formula behind them, which is possible because the formula is simple and defensible.
Tell us the scope and we will give you a fixed price, usually within two days.
The situation
Starting prices for fixed scope. Complex cases are quoted after a short paid discovery rather than estimated.
Two to three weeks for a supported system. QuickBooks Desktop starts at $9,500 because it is genuinely three times the work.
Full deployment with migration, configuration, and training. Multi-entity and complex revenue arrangements scope higher.
Quoted at API cost times five with a $5,000 floor, after a free scoping session. Hosting $250 to $1,000 a month.
Most of which is the evaluation set rather than the agent. Hosting is included in your subscription.
Health check $4,500. Process design $8,000–$18,000. ERP selection $12,000. All fixed, all credited against later work.
Stalled implementations, quoted after a paid assessment. We will not quote a rescue without looking first — nobody honestly can.
We build with Claude, which means the marginal cost of an engagement is largely measurable: the API cost of the work. Our price is that cost times five, with a floor.
The multiple covers scoping, review, testing, deployment, warranty, and the engagements that go wrong. It is not a margin we are hiding — it is published because a customer who understands the pricing basis argues about scope rather than about rate, and scope is the conversation worth having.
A day rate rewards taking longer. Every consultancy will tell you their incentives are aligned with yours, and the billing model says otherwise — a project that runs over is a better outcome for the vendor than one that lands early.
Fixed price on defined scope reverses that. If we do it faster we keep the difference, if we misjudge we absorb it, and either way you know the number before you commit. That only works if scoping is done properly, which is why discovery is a real phase rather than a sales call.
Two cases. A system nobody has integrated before, where a paid discovery of $1,500 to $3,000 establishes feasibility and produces the fixed quote. And a stalled implementation, where the state of the existing work is unknown and quoting blind would be dishonest.
In both, the discovery is short, priced, and produces a written deliverable you keep whether or not you proceed.
Rare, and by design. Scope is written down before work starts, including what is excluded, which is the part most proposals leave vague. A change order happens when you ask for something outside that, not when we discover something we should have found in scoping.
That distinction is written into the engagement. Discovery failures are ours; new requirements are yours.
Scoping sessions. Connector maintenance and API version changes. Bug fixes. Training that did not land. Support that turns out to be a defect. None of those are change requests and billing for them is how a vendor relationship turns adversarial.
Where to start
Free, sixty to ninety minutes. What you need, what you run, what is in scope and explicitly what is not.
Inclusions, exclusions, assumptions, and dependencies on your side. The exclusions section is the one worth reading closely.
Usually within two days. Where a paid discovery is needed first, we say so rather than quoting a number we cannot stand behind.
Change orders only for genuinely new requirements. Anything we should have found in scoping is ours to absorb.
Questions
Fixed price usually within two days — or an honest answer about why we need to look first.