Staff augmentation
Vetted engineers, on your team.
Add one to four senior engineers into your workflow. They use your tools, your rituals, your repo — and they stay long enough to matter.
- Ramp
- < 2 weeks
- Commitment
- 3–12 months
- Seniority
- 7+ yrs avg.
Services
Three shapes.
One standard.
We staff teams in three shapes — and one of those shapes will fit. Inside any of them you get the same standard: senior engineers, a written plan, working software at every review.
§ 01 — How we plug in
How we plug in.
Each shape has a different ramp, commitment, and mode of working. Pick the one that maps to what you actually need; we'll tell you if you've picked wrong.
Embedded squad
A team that plugs in, not in the way.
Design, engineering and delivery, working alongside yours. Same standup, same roadmap, one shared backlog — we close out the sprints nobody else will.
- Squad size
- 4–9 people
- Typical term
- 6–18 months
- Includes
- PM + Eng + Design
End-to-end build
We lead it. You ship it.
For greenfield products or a rescue mission. We own discovery, architecture, build, launch — then hand the keys, documented and tested, to your team.
- Shape
- Fixed-outcome
- Timeline
- 8–24 weeks
- Handover
- Code + runbooks
§ 02 — What we do
Six things we're known for.
Not exhaustive — but if your work touches one of these, we have shipped the same shape before.
01 / 06
Product discovery, paid by the week.
We don't write decks. We read your code, ride along with your support tickets, talk to your power users, and write back a plan a senior engineer can actually execute against — with the risks priced in and the un-decided things flagged.
Deliverables
- A 10-15 page written plan you keep regardless of fit
- Architecture sketch + data model walkthrough
- Risk register with mitigations
- A staffing recommendation we can deliver against
Typical
Tech we tend to reach for
02 / 06
Platform & cloud that outlasts us.
Cloud infrastructure, CI/CD, observability, and cost controls — built so a team that has never met us can keep operating it. We document everything as we go and avoid bespoke tooling unless the constraint genuinely warrants it.
Deliverables
- IaC (Terraform / Pulumi / CDK) with module boundaries
- CI/CD pipelines with environment promotion
- Logging, tracing, and metric dashboards
- Cost budget + alerting
- Runbooks for the top 10 incidents we can imagine
Typical
Tech we tend to reach for
03 / 06
Web & product apps, typed and tested.
Customer-facing apps, internal tools, and admin consoles. Defaults: TypeScript end-to-end, Postgres for the source of truth, React + a sensible meta-framework on the front. We deviate when the work demands it, not for novelty.
Deliverables
- Architectural decision records for every meaningful fork
- Component library with documentation
- Test pyramid: unit + integration + a small set of e2e
- Performance budget enforced in CI
- Accessibility audit report
Typical
Tech we tend to reach for
04 / 06
Mobile apps that feel native.
Native iOS, native Android, or React Native — picked from the actual constraints, not from familiarity. Either way you get apps that survive App Store / Play Store review on the first submission, with a release pipeline your team can run.
Deliverables
- iOS + Android apps in lockstep
- Submission to both stores, including review responses
- CI builds + TestFlight / internal track distribution
- Crash + analytics instrumentation
- Handover to your team with a working release runbook
Typical
Tech we tend to reach for
05 / 06
AI integration that pulls weight.
LLMs in real product workflows: extracting data, drafting copy, summarising support, recommending actions. We treat AI features like any other production system — with evals, cost caps, fallbacks, and a way to roll back. No demos that don't survive contact with real users.
Deliverables
- Eval harness with regression tracking
- Cost dashboards + per-feature budget caps
- Fallback behaviour for every model call
- A safety/abuse review and prompt-injection threat model
- Documentation that lets your team tune without our help
Typical
Tech we tend to reach for
06 / 06
Codebase rescue without freezing the business.
Inherited a codebase that's slow to change, expensive to run, or just a little haunted? We stabilise the bleeding first, then re-shape — adding tests around the parts you can't break, replacing what's structurally beyond repair, and documenting what we found.
Deliverables
- Audit report with ranked risks and a sequenced plan
- Test scaffolding around the highest-risk modules
- Targeted refactors with measurable outcomes
- Onboarding guide for the next engineer
- A list of the things we did NOT touch and why
Typical
Tech we tend to reach for
§ — Logistics
The practical stuff.
Questions clients ask before signing the first SOW. If yours isn't here, send it over — short answers tend to be the honest kind.
How fast can we start?
Two weeks from contract for a small engagement. Three to four for a full squad — we won't ramp someone in less than that without warning you.
Where are you located?
Engineers are in Europe (London, Lisbon, Berlin) and the Middle East. Standups happen between 09:00 and 18:00 CET.
Do you do fixed-price?
End-to-end builds, yes — once the discovery is done. Staff aug and embedded squads are time-and-materials, monthly invoiced. We don't do fixed-price for things we haven't scoped.
Will you sign our NDA / DPA / vendor forms?
Yes. We have standard forms ready, and we can sign yours. Compliance reviews (SOC2 / ISO27001 vendor questionnaires) are no problem.
What if we want to hire one of your engineers full-time?
Talk to us. We won't punish either of you for that conversation — it's a sign we did the work right.
How do you bill?
Monthly, net 14, in EUR or USD. Wire transfer or SEPA. No retainer required for engagements over 12 weeks.
◇ Currently booking
Have a thing that
needs shipping?
Tell us the shape of the problem. We'll write back within a working day with an honest read — fit, no fit, or a second question.