Skip to main content

Pricing

Published bands, and a written quote before anything is built. If you leave this page not knowing roughly what your project costs, we have failed at the thing this page is for.

Our build cost is dominated by the compute our agent team consumes, not billable human hours — so what you pay tracks what your project actually took to build, and the bands below are honest ranges rather than padded day-rate math.

Internal Tools & Line-of-Business Apps

$4,000 – $15,000 typical range

You get a quoted range in the statement of work before the build starts. The final price is settled at delivery from the actual compute the build consumed — what moves it: number of distinct workflows, integrations with other systems, and how many people use it at once. About 20% is paid up front; the balance at handoff.

Most internal tools ship in 1–3 weeks from an approved statement of work.

API & Integration Work

$2,500 – $10,000 typical range

Quoted up front, settled at delivery from the compute the build actually consumed. Driven by the number of systems, whether data flows one way or both, and how well-documented the vendor APIs are. Poorly documented vendor APIs are our problem to figure out, but they honestly cost more.

Single-direction, two-system integrations typically ship in under a week. Multi-system or bidirectional work: 1–3 weeks.

Rescue & Modernization

Assessment $1,500 · rescue builds $8,000 – $30,000 typical range

Rescue pricing depends on how much behavior must be preserved exactly, the state of the data, and whether the old system can be read or must be reverse-engineered from its outputs. Rescues of this size are paid about 20% up front with the rest at agreed checkpoints, and the final number is settled at delivery from the compute the rescue actually consumed. The assessment exists so the quote is grounded in evidence, not hope.

Assessment: about a week. Rescue builds: 2–6 weeks depending on scope, stated precisely in the statement of work.

Fixed-Scope Prototype

$2,000 – $5,000 typical range

The band reflects scope, and scope is one workflow — quoted up front, settled at delivery from what the build actually consumed. If the idea needs three workflows to prove itself, that is either a bigger prototype (quoted honestly) or — more often — a sign the scope needs cutting, which we will say.

One week or less from approved scope, fixed.

How pricing works

  1. 1.Your project brief and a scoping call produce a written statement of work with a quoted range from the bands above.
  2. 2.You pay roughly 20% up front to start the build. On larger projects, the rest is paid at agreed checkpoints as working software is delivered; on smaller ones, at handoff.
  3. 3.The final price is settled at the end of the project, based on the compute the build actually consumed — within the quoted range. You pay for what your project took, not for a padded worst case.
  4. 4.Scope changes are new, separately quoted change orders. The original quote never quietly grows.

Why not one fixed number? Because our cost is the inference our agent team burns, and on larger projects that genuinely cannot be predicted to the dollar before the work starts. Rather than pad a “fixed” price to cover the uncertainty, we quote a range, show our working, and settle on the real number at delivery.

What never costs extra

  • Source code ownership — the repository is yours, always, at every price point
  • The automated test suite and the handoff documentation
  • Defect fixes against the statement of work for 30 days after handoff
  • Honesty during scoping — if you don’t need custom software, we say so before you spend anything

Get your number

The brief takes about five minutes and includes a budget-band question — so the first conversation starts from reality on both sides.

Start a project brief