When you need it
You need a product in front of customers soon, but you do not want an MVP that must be rebuilt before it can grow, or one that fails the first customer security review.
What sets the quote
- 4 weeks: up to 12 screens, 5 user journeys, 2 user roles and 2 integrations, such as a payment provider and email.
- 12 weeks: up to 40 screens, 20 user journeys, 5 user roles and 6 integrations, such as an ERP, a CRM or supplier APIs.
- Three environments are included (development, test and production). Each extra environment adds to the quote.
- Compliance needs, such as data residency, audit logs, retention rules or card payments under PCI DSS, are agreed up front and included in the quote.
- Larger products are sized in a discovery and built in phases, each with its own fixed quote.
What changes
- You own a working product in your own cloud, with the code and infrastructure in your Git.
- Every change passes review, tests and security scans before it reaches production.
- The first release runs in production with logging, monitoring and alerts in place.
- The architecture and pipeline carry the next releases, not only the first demo.
What you get
- Web app and API for the agreed first release, with automated tests
- Sign-in through a managed identity service, such as Amazon Cognito, Microsoft Entra External ID or Google Cloud Identity Platform, with access rules per user role
- The integrations agreed for the first release, such as payments with the provider you choose
- Hosting on a managed runtime, such as Amazon ECS on AWS Fargate, Azure Container Apps or Cloud Run
- Infrastructure as code (Terraform by default) for development, test and production
- CI/CD pipeline with tests, security scans and an approval gate, deploying without stored cloud keys
- Logging, monitoring and alerts for production
- Handover documentation, runbooks and a walkthrough with your team
We built our own B2B and B2C travel commerce platform: web and admin apps, a mobile app and payments. If the first release is not yet defined, start with a product and architecture discovery. After launch, application support keeps the product patched, with 24/7 on-call as an option.
Not included
- Mobile apps (quoted separately)
- Brand and visual design (we build from your designs or a standard UI component library)
- Content writing, translation and the marketing website
- Penetration testing (we can refer you to a certified partner)
- Running the product after launch (available as application support, with optional 24/7 on-call)
- Compliance certification, audit opinions or legal advice
What we need from you
- A product owner who makes scope decisions within two working days and joins a review every two weeks.
- A repository in your GitHub, GitLab or Azure DevOps organisation, with admin rights on it during the build.
- AWS: an account per environment, with AdministratorAccess through IAM Identity Center during the build.
- Azure: a subscription or resource group per environment, with Contributor and Role Based Access Control Administrator during the build.
- Google Cloud: a project per environment, with the Owner role during the build.
How it works
A discovery or a free 30-minute call, then a written fixed quote for the first release.
A senior architect leads every engagement; vetted specialists join when the scope needs them. You see working software every two weeks.
Every change is reviewed as a pull request and ships through the pipeline.
Launch with monitoring in place, then handover. Build access is removed, and your team holds every credential.
At a glance
- Duration
- 4–12 weeks
- Price
- Fixed quote after a free 30-minute call
- Delivered by
- Our lead architect and developers
Related services
Product and architecture discovery
A discovery of 1–2 weeks that turns a product idea into a first-release scope, an architecture, a build estimate and a delivery plan, before you commit budget to the build.
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.