When you need it
You have a product or a major feature to build, and the estimates you have are far apart. Nobody has written down what the first release must do, which systems it connects to, how it will run in the cloud, or what it will cost to build and run.
What sets the quote
- One product, or one major feature of an existing product, per discovery.
- One week: up to 3 user roles, 10 user journeys, 3 integrations and 3 workshops of two hours.
- Two weeks: up to 6 user roles, 20 user journeys, 8 integrations and 6 workshops of two hours.
- Each compliance need you name, such as data residency, audit logging or card payments under PCI DSS, becomes a written requirement and adds review time.
- Larger products are split into phases, or quoted after the free call.
What changes
- You know what the first release includes, and what can wait.
- The biggest risks, such as integrations, data migration and compliance needs, are known before the build starts.
- You can check any vendor's quote, or your own team's plan, against a written estimate.
- You own the plan and can take it to any team, including your own.
What you get
- First-release scope: user roles, prioritised user journeys and what waits for later
- Architecture document with diagrams and architecture decision records
- Integration map with each external system, its API limits, failure modes and owner
- Hosting, security and CI/CD approach for your cloud (AWS, Azure or Google Cloud)
- Build effort estimate per milestone, and a monthly running-cost estimate from your cloud's pricing calculator
- Delivery plan with milestones and the skills the build needs
- Risk list with an owner and a mitigation for each risk
- A 90-minute readout with your product owner and technical leads
Discovery stands on its own. If we then build with you, it sets the scope of the fixed quote for a cloud-native web app or an API and integration platform, so the build starts without a second round of questions.
Not included
- Building the product (quoted separately, often as a cloud-native web app or an API and integration platform)
- Visual design, clickable prototypes and research with your end users
- Legal or compliance opinions (we turn the requirements you give us into design decisions)
What we need from you
- Your product owner at every workshop and review, about one day a week, with authority to make scope decisions.
- Your technical lead, if you have one, for the integration and hosting workshops.
- Existing material, such as product notes, designs, API documentation and written compliance requirements.
- If the product extends an existing system: read access to its repositories, and read-only cloud access (AWS ViewOnlyAccess, Azure Reader or Google Cloud Viewer).
How it works
Free 30-minute call, then a written fixed quote.
Workshops led by a senior architect with your product owner and technical leads: goals, users, journeys, integrations and constraints.
Draft scope and architecture, reviewed with you in short sessions.
Build and running-cost estimates, split into milestones.
Readout of the plan, the risks and the next decision.
At a glance
- Duration
- 1–2 weeks
- Price
- Fixed quote after a free 30-minute call
- Delivered by
- Our lead architect
Related services
Cloud-native web app or MVP
A web app or MVP with its API, built in your own AWS, Azure or Google Cloud environment in 4 to 12 weeks, with infrastructure as code, CI/CD and security gates from the first commit.
API and integration platform
Tested integrations with your suppliers, partners and payment providers that handle timeouts, retries and duplicate messages, so one slow partner cannot stall your product. Built in 2 to 8 weeks.
Legacy app modernisation
Older applications, including .NET and IIS apps, moved into containers on Amazon ECS on AWS Fargate, Azure Container Apps or Cloud Run, with CI/CD and a tested rollback for every release.