Services
Engineering help, sized to the problem
From a two-week discovery to a long-term delivery squad — with the same senior people either way.
Product engineering
Discovery, design and build for products that need to work on day one and still work at ten times the volume.
Cloud & platform
Environments, pipelines and observability set up so your team can deploy without asking permission.
Data & AI
Warehousing, reporting and applied models — starting with the decisions you want to make faster.
Support & maintenance
Monitoring, patching and small improvements on a rolling agreement, with a named engineer.
Engagement models
Pick the shape that fits your decision
You can move between models as the work becomes clearer. Nothing here is a twelve-month lock-in.
|
Model
|
Best for
|
Typical length
|
Team
|
|---|---|---|---|
|
Discovery
|
New products, unclear scope, board approval
|
2 weeks
|
2 people
|
|
Delivery squad
|
A committed roadmap and budget
|
3–9 months
|
3–6 people
|
|
Embedded specialists
|
An in-house team missing one skill
|
Rolling
|
1–2 people
|
|
Support retainer
|
Live systems that need care
|
Rolling
|
1–2 people
|
Typical engagement shapes — all figures indicative.
On fixed-price work
We quote fixed price when the problem is genuinely well understood. When it is not, we will say so rather than pad the number.
Questions we get asked
The practical stuff
How quickly can you start?
Usually within three to four weeks for a full squad, and inside a week for a discovery.
Do you work with our in-house team?
Most of the time, yes. We embed alongside your engineers and hand work over continuously rather than in one lump at the end.
Who owns the code?
You do, from the first commit. It lives in your repositories under your accounts.
What if we want to stop?
Thirty days’ notice on retainers, and a handover pack is part of every engagement — not an upsell.
How we work
The same four stages, whatever the model
Discover
Understand the business case before the technology.
1–2 weeks
Shape
Scope, sequence, cost and risks in one document.
1 week
Build
Fortnightly releases with real users in the loop.
8–20 weeks
Support
Care through launch, then a clean handover.
Ongoing
Not sure which model fits?
Describe the problem in a paragraph. We will tell you what we would do and roughly what it costs — no charge for the answer.