Skip to content
Project estimator

A real number, before you talk to anyone.

Most agencies make you sit through a discovery call to hear a price. Configure the scope below and the estimate updates as you go — then book a call only if the range works for you.

01

What do you need built?

Select every capability that applies. Most projects use two.

02

What is in scope?

Choose a capability above to see the relevant scope options.

03

Where is this going?

Stage determines the engineering bar, not the feature list.

04

How fast do you need it?

Compressing a timeline means more people in parallel, which costs more.

05

After launch?

Optional. Most teams take handover and add support later.

Live estimate

Select at least one capability and the estimate builds itself as you go.

Fixed starting point
$1,500architecture sprint, 5 days

Credited in full against a build started within 60 days.

How these numbers are built

Each capability carries a base engineering cost; scope modules add to it. Stage and timeline apply multipliers, because production-grade and compressed both cost real money.

What turns this into a commitment

The five-day architecture sprint. It produces a written scope, a risk register, and a price band we hold. It costs $1,500 and credits in full against the build.

When it will be wrong

Legacy systems with undocumented behaviour, hard compliance deadlines, and integrations with partners who have no sandbox. We flag those on the call rather than after signing.

Range looks right? Let us pressure-test it.

Bring the estimate to a fifteen-minute call and we will tell you where it is optimistic, where it is padded, and what we would cut first.

Book an architecture call

Fifteen minutes, no deck. We map your problem to an approach and tell you what a realistic scope and budget look like.

  • A specific technical recommendation
  • A budget band you can plan against
  • An honest answer if we are the wrong fit

Send a written brief

Prefer to write it down? Email us the shape of the problem and we will reply with a first take, usually under 12 hours.

  • Goes straight to an engineer, not a sales inbox
  • We reply with an approach, not a brochure
  • Attach anything: repos, docs, screenshots