PRICING

Two ways to start. Scope decides what comes next.

The starting price is public. The written scope still matters, because a planning decision and a production release are not the same engagement.

From US$1,000

Product Blueprint

A bounded planning engagement that turns one product or technical question into an evidence-based scope and next decision.

Founders who need to test feasibility, define one workflow, review an existing prototype or prepare a build brief before committing to implementation.

What the starting scope can include

  • Problem and user outcome defined in writing
  • One core workflow, prototype or technical risk reviewed
  • Scope boundaries, assumptions and dependencies recorded
  • Recommended next step with the important unknowns left visible

A Product Blueprint is not a complete application build. The exact output is agreed before work begins.

From US$2,500

Launch Sprint

End-to-end technical execution for one tightly scoped first release or core workflow, from planning through launch.

Founders with a defined problem who need one team to own the technical path from scope and UX direction through implementation, testing and deployment.

What the starting scope can include

  • Scope definition and technical planning
  • UX direction for the agreed workflow
  • Implementation and review in a buyer-accessible repository
  • Testing against agreed acceptance checks
  • Deployment of the agreed release and technical handover

Authentication, billing, mobile applications, advanced AI, multiple integrations, data migration, compliance requirements and extensive administration can increase the quote.

WHAT CHANGES THE QUOTE

The boundary is part of the product decision

A price is useful only when the buyer can see the assumption behind it. We define the first release, its acceptance checks and its dependencies before implementation begins.

  • The written proposal defines the release, acceptance checks and what is outside scope.
  • Third-party subscriptions, hosting usage, domains and app-store fees are paid directly by the client unless the proposal says otherwise.
  • Ongoing maintenance, support and later product phases are separate from the first engagement unless they are explicitly included.

START WITH THE PROBLEM

We will tell you which starting point fits

Describe the user, the workflow and what must be true after the first engagement. If the scope does not fit either starting offer, we will explain why before proposing a larger phase.

Send project detailsBook a discovery call