WAYS TO WORK TOGETHER
A delivery format for each product stage
Start with discovery, deliver a defined project or continue with regular product development. Team composition, capacity and commercial terms are confirmed in a proposal.
CHOOSE YOUR NEXT STEP
From a first idea to ongoing delivery
01↗
Product discovery
For an idea whose requirements, priorities and scope are still unclear. We turn the business goal into a plan that can be estimated and delivered.
Explore format ↗02↗
Defined-scope project
For a clear outcome: a website, application, portal or focused integration. We agree on deliverables before starting and release the solution in defined stages.
Explore format ↗03↗
First release / MVP
Test an idea through a working product. We choose one useful journey and defer features that are unnecessary for understanding demand and user behaviour.
Explore format ↗04↗
Product development
For a live product needing new capabilities, better quality or increased capacity. We review its condition and plan a sequence of changes.
Explore format ↗05↗
Dedicated team
For sustained development with changing priorities. We agree on roles and capacity for the product and organise work with your responsible stakeholder and a shared backlog.
Explore format ↗06↗
Maintenance
For a launched product needing a clear process for errors, updates and smaller changes. We first define the supported systems and responsibilities.
Explore format ↗A QUICK COMPARISON
Match the format to your situation
| Format | When it helps | Planning and budget |
|---|---|---|
| Product discovery | Useful for a new service, a complex integration or a rethink of an existing product, especially when stakeholders have different expectations or mistakes would be costly. | An agreed discovery scope is a separate paid phase. The development estimate is refined once journeys and constraints are understood. |
| Defined-scope project | A fit when you need a specific result with a manageable scope and want delivery coordination handled by the development partner. | Price and milestone payments are set out in the proposal. New capabilities are estimated separately before joining the scope. |
| First release / MVP | A fit for a new SaaS product, service, application or internal tool when validating value matters more than delivering every planned capability at once. | The first-release scope and budget are agreed separately. Later phases are estimated after launch and updated priorities. |
| Product development | Useful when people already rely on the service, a backlog exists and working journeys need to remain stable during improvements. | Delivery can be planned in phases or an agreed capacity for a period. Time tracking and budget adjustments are defined in the proposal. |
| Dedicated team | Useful for regular product releases, several connected development streams or reinforcing an internal team. Composition depends on the work and specialist availability. | Pricing follows an agreed capacity and period. Rates, time tracking, substitutions and team changes are discussed before work begins. |
| Maintenance | Useful for a website or service requiring regular technical attention while support tasks need to be distinguished from major new development. | A time allowance or another maintenance scope is set out in the proposal. Major capabilities and external costs are estimated separately. |
NOT SURE YET?
Describe the goal first
A brief is enough to discuss the next step. You do not need to choose a team size or prepare a detailed specification.
