One formula.
Published.
Priced from the scope itself. Complexity is a fixed multiplier driven by your constraints, and every driver behind your number is printed on the estimate. No quote-on-request, no discretionary discounting, no sales override.
These figures are indicative. The formula and the way complexity is derived are settled and will not change on you mid-engagement. The rates themselves are still being finalised, so treat anything the calculator returns as an order of magnitude rather than a quote. Your actual number comes from an intake conversation, and it is the one written into the statement of work.
base = derived from your scope priced = base × complexity (1.0 | 1.25 | 1.5) monthly = priced + addOns effective = monthly × term (monthly 1.0 | yearly 0.8) dueToday = effective × termMonths + deposit
The base is computed from what you are building and how big it is. You do not estimate it, and there is no headcount to guess at. Every multiplier applied on top of it is published on this page, and every one that fired on your quote is printed on your estimate.
Change a constraint. Watch the reason change.
This runs the production engine. The panel underneath shows the API call your configuration maps to.
Not listed? Describe it at intake, the agents scope from the problem, not from a menu.
- HIPAA compliance constraints detected
- onprem deployment target
- Real-time latency requirement
- 40 concurrent video streams
{"billing": "YEARLY""addOns": ["PRIORITY_SUPPORT"]}
No amount field, and no headcount field. The server computes both from the requirements it extracted.
Indicative. Your contract price is issued after intake by the same engine, computed server-side from the requirements the agents extracted, not from anything entered on this page.
The whole table, in the open.
Every signal that can move your price, and by how much. Sum the weights: 0-1 is LOW, 2-4 MEDIUM, 5 or more HIGH.
Publishing this is deliberate. A buyer who can predict their own quote does not need a pre-sales call to get one.
The same formula, two different briefs.
Both quotes below were produced by the production engine from the transcripts shown. The difference is not a sales judgement. It is four compliance and deployment signals, each listed against the price it moved. The figures are indicative; the mechanism is not.
“A small assistant over our public FAQ pages, hosted on AWS. No personal data.”
- PII compliance constraints detected
“We run a hospital network. 40 CCTV cameras across four plants need patient-fall detection. It must be real-time and stay on-premise, air-gapped. Patient data is involved.”
- HIPAA compliance constraints detected
- onprem deployment target
- Real-time latency requirement
- 40 concurrent video streams
(agents × $199) × complexity(1.0 | 1.25 | 1.5) + add-ons × term(1.0 | 0.8)Brief us like thisThe cost is not only the invoice.
Weigh it against what shipping the same system costs you today, which is rarely a line item anyone tracks.
Finding the people
No search, no agency fees, no three-month notice periods. The capability is there the day you decide.
Standing up a team
No onboarding, no context transfer, no waiting for someone to learn your systems before they are useful.
The coordination
No standups, no handoffs, no dependency on another team’s sprint. Work does not queue behind whoever is busy.
The calendar
Scoped and priced in minutes instead of weeks of discovery, proposals and procurement. Delivery starts when payment clears.
We are not going to put a currency figure on that. Your loaded cost per engineer and your cost of a quarter's delay are numbers you already have and we do not. Put ours next to them.
Every engagement, whatever the size.
The ones that actually get asked.
How is the base derived?
From the scope itself, what you are building, how many systems or surfaces it spans, and the volume it has to handle. You do not estimate it and there is no headcount to guess at. The three agents are not a pricing unit; they are who does the work.
Why is the base not published as a rate card?
Because a rate card invites you to price your own project wrongly and then argue about it. Every multiplier that can move your number is published above, and the calculator below runs the production engine, so you can see the figure before you speak to anyone.
Who decides the complexity tier?
The weights above, summed. Score 0-1 is LOW, 2-4 is MEDIUM, 5+ is HIGH. There is no discretionary adjustment and no sales override, the drivers behind your tier are printed on your estimate with the requirement each came from.
Why does HIPAA cost more than GDPR?
Protected health data pulls in a business associate agreement, an audit trail and retention controls that materially change the build. General PII and GDPR handling weigh less because more of that work is baseline for every engagement.
Is the number on this page the number I pay?
It is an indicative quote from the same formula. Your contract price is computed server-side from stored requirements, because a figure on a signed document cannot originate in a browser. The API has no field for a client-supplied amount.
When is payment taken?
After signature, before delivery. Kickoff is blocked in code until the contract is SIGNED and payment is SUCCEEDED, both confirmed by provider webhook. Card, ACH, wire and purchase-order flows are supported.
What happens when scope changes?
A written change order re-runs the estimate. The multiplier may move if the new requirements change the drivers. Work continues on the existing scope until you approve the revised figure.
Get the real number.
An intake conversation produces your actual scope, price and contract terms , before you commit to anything.