Four Ways to Work With Us — Chosen to Fit the Work
The commercial model should follow the nature of the project. Fixed scope where the requirement is clear, capacity where it will evolve, and a phased structure for early-stage products.
Fixed Cost
A defined scope, a defined price, a defined date.
Best where the requirement is well understood and the outcome can be described precisely before work starts. You get budget certainty; we take the delivery risk within the agreed scope.
Project control and communication
You review and sign off at each milestone. A named project manager runs a weekly written update and a scheduled call, and the working environment is available to you throughout.
Suitable for
- A clearly definable deliverable — a website, a defined module, a migration, an integration
- Budget approval that requires a firm number in advance
- Projects with a hard external deadline
- Organisations that prefer a single accountable supplier commitment
Main benefits
- Budget certainty from the outset
- Clear acceptance criteria for every milestone
- Delivery risk within scope sits with us
- Straightforward internal approval
How it works
Discovery and specification
A short paid discovery produces the documented scope the price is based on.
Fixed proposal
Scope, assumptions, exclusions, milestones and payment schedule set out in writing.
Milestone delivery
Work delivered against agreed milestones, each reviewed and signed off.
Change control
Anything outside scope is quoted separately before it is started — never absorbed silently or billed by surprise.
Recommended project type
Well-specified projects: websites, defined modules, integrations, migrations and discrete phases of a larger programme.
When it is the wrong fit
Fixed cost works badly for exploratory work. If the requirement is likely to change as you learn, a capacity-based model will cost you less and frustrate you less.
Staff Augmentation
Specific skills added to your team, under your process.
You direct the work; we supply vetted engineers, designers, QA specialists or DevOps capacity who work inside your existing team, tools and ceremonies.
Project control and communication
Complete. Your leads assign the work, run the reviews and set the standards. We stay available for escalation, cover and performance management.
Suitable for
- An existing team that needs specific skills or extra capacity
- A hiring gap that must be covered now rather than in six months
- Short-term surges around a release or a migration
- Organisations with their own delivery management in place
Main benefits
- Capacity without a permanent hire
- You keep full control of priorities and process
- Scale up or down with agreed notice
- Access to specialist skills you do not need full-time
How it works
Role definition
Skills, seniority, time zone overlap and expected duration agreed.
Selection
Candidate profiles proposed and interviewed by you. You decide who joins.
Onboarding
People join your tools, your stand-ups and your process, working to your standards.
Ongoing management
We handle employment, equipment, cover and performance; you direct the day-to-day work.
Recommended project type
Established engineering teams needing depth in a specific area — mobile, QA automation, DevOps, data or front-end — without a permanent headcount decision.
When it is the wrong fit
This model assumes you have delivery management capacity. If you need outcomes rather than hands, a dedicated team is usually the better fit.
Dedicated Development Team
A standing team that holds the context and owns delivery with you.
A cross-functional team assigned to your product — engineering, QA, design and delivery management — working to a shared roadmap at a predictable monthly cost.
Project control and communication
Shared and explicit. You own the roadmap and priorities; we own delivery mechanics and technical quality. Sprint demos, a live backlog and a monthly written report keep it visible.
Suitable for
- Products and platforms with continuous development, not a single end date
- Organisations that want outcomes rather than task execution
- Programmes where domain knowledge takes time to build and is expensive to lose
- Roadmaps that will change as customers respond
Main benefits
- Retained context compounds over time
- Predictable monthly capacity and cost
- One accountable team across design, build and QA
- Technical health managed alongside features
How it works
Team design
Composition and size shaped to the product, with named people you meet before they start.
Onboarding
A ramp-up period building domain and codebase understanding, planned into the schedule.
Delivery cadence
Sprints, demos, retrospectives and a visible backlog, with regular releases.
Quarterly review
Roadmap, metrics, technical health and team composition reviewed together.
Recommended project type
SaaS products, long-running platforms and multi-phase transformation programmes.
When it is the wrong fit
It needs commitment on both sides. Teams reach full productivity after the ramp-up period, so very short engagements do not get the benefit.
Startup Partnership
A phased structure for early-stage products with real potential.
A staged engagement designed around how early-stage companies actually fund development: a small validated first phase, then commercial terms structured around the milestones that follow.
Project control and communication
You own the product, the code and the direction. We provide technical leadership, delivery and candid advice — including when the evidence suggests stopping.
Suitable for
- Founders with a defined problem, early customer evidence and limited runway
- Products that need a credible MVP before a funding conversation
- Teams without in-house engineering leadership
- Businesses where speed to a first release genuinely matters
Main benefits
- Investment staged rather than committed up front
- Technical leadership without a founding CTO hire
- A product engineered to survive success
- An honest recommendation at each decision point
How it works
Product discovery
A short fixed-price phase producing scope, prototype and a realistic build plan.
MVP phase
A focused first release built to reach real users, engineered so it can be extended.
Structured terms
A phased commercial arrangement agreed in writing, shaped around your funding position.
Post-launch
Measurement, iteration and a decision point: continue, pivot or pause, taken on evidence.
Recommended project type
Founders and corporate innovation teams taking a first product to market.
When it is the wrong fit
We take on a limited number of these and we are selective, because the model depends on genuine commitment from both sides. Terms are agreed case by case.
Not sure which model fits?
Send us the outline and we will recommend an approach, with the reasoning and the trade-offs stated.