Pricing

A useful budget starts with a clear scope.

Use these ranges to plan a conversation. Your proposal defines the deliverables, assumptions, exclusions, and milestones for the work you approve.

Fixed-scope projects

Progress you can see.
Payments that follow it.

30%Kickoff40%Working demo30%Handoff
Milestones and acceptance criteria are agreed before the build begins.

Planning ranges.

The project workbench

A view of the investment.

Start with what you want to make possible. Pick a project to explore.

From possibility to a planConcept sketch

Connect the dots.

  1. Your systems
  2. One workflow
  3. Connected work

Your project, at a glance

Internal tool or integration

Planning budget · USD
$8k–$25k
Build time
3–6 weeks
The scope

A focused workflow and agreed system connections.

Discuss this project

Planning ranges, not fixed quotes. The audit has a fixed fee; repairs are quoted separately. Build time starts at the agreed kickoff. Compare all scopes in the table below.

Software services — build time begins at the agreed kickoff
ServiceTypical scopeBuild timeBudget range
Internal tool or integrationA focused workflow and agreed system connections.3–6 weeks$8k–$25k
Customer application or portalDefined customer tasks, roles, and integrations.6–18 weeks$25k–$75k
Rapid prototypeOne core flow for user feedback; production work separately scoped.1–2 weeks$3k–$8k
Application auditFindings and a prioritized repair or rebuild plan.1–2 weeks$2.5k
Application repairRemediation agreed after an audit; quoted separately.2–8 weeks$8k–$40k

Ranges are estimates, not a fixed quote. Discovery comes before build kickoff. Migration volume, system access, third-party approvals, and requirements can change the scope and schedule.

Before the build

Discovery and the fixed quote.

The initial scoping call is free. Before deeper discovery begins, we confirm its deliverables, timing, and any fee in writing. You decide whether to proceed.

For a clearly bounded project, we aim to deliver a fixed proposal within 10 business days after discovery is agreed and the required information and access are available. Larger or uncertain scopes get a discovery schedule first.

What helps us quote accurately

  • A walkthrough of the current workflow.
  • The users and tasks the first release must support.
  • The systems we need to connect and available access.
  • Examples of data, with sensitive details removed.
  • Your target date and how you will judge success.

Choose an engagement that fits.

Defined outcome

Fixed scope

An agreed deliverable, price, and acceptance criteria. Delivery overruns within the agreed scope are ours; requested changes are priced before work begins.

30% kickoff · 40% working demo · 30% handoff

Evolving product

Two-week sprints

Agree a prioritized set of work and a price for each sprint. Review the result before deciding on the next one.

Per-sprint pricing agreed in advance

Included in a production build.

  • Agreed architecture and implementation.
  • Code review, testing, and security review.
  • Deployment, handoff documentation, and training.
  • 30-day defect coverage on fixed-scope production work.

Scoped or billed separately.

  • Discovery fees, if any, agreed before discovery starts.
  • Hosting, domains, and third-party software fees.
  • Data migration, specialist assessments, or media outside the agreed scope.
  • New features and ongoing maintenance after handoff.

Find out what a sensible first release could cost.

Book a free scoping call or email a short description of the workflow you want to improve.

Discuss your project