Services
Three situations, three ways in.
Teams reach us in one of three states: a roadmap with nobody to build it, a team that is one or two engineers short, or a system whose owners have all left. All three run on the same paperwork — EU entity, MSA and SOW, 30 days' notice either way — and the same three-month minimum.
Two ways to add engineers
What separates these two is who the engineers report to and who owns the backlog; the contract is the same either way. Both ramp in 10–15 business days, both carry a three-month minimum, and both staff against the same ten technologies — Java/Spring, Go, TypeScript, React, Python, PostgreSQL, Kafka, AWS, Kubernetes, Terraform. There are 21 engineers here and 6 active clients, so the start date is a real constraint, not a formality: the honest answer on a first call is sometimes a date five or six weeks out.
Ramp-up, reporting, exitDedicated teams
2–6 engineers with a named technical lead, working in your repositories, your review process, and your sprint cadence. The team is not shared with another client and is not rotated off to cover someone else's gap. Ramped in 10–15 business days; if an engineer leaves, their replacement overlaps with them for three weeks before taking the work.
Staff augmentation
One to three senior engineers inside a team you already run, reporting to your engineering manager and taking work from your backlog rather than ours. English is B2+ for engineers, C1 for team leads. Minimum three months, no trial shorter than four weeks.
One way to hand a system back
A takeover is the one engagement we plan to end. Discovery runs two weeks and is paid; it produces a written account of what the system does, what it costs to keep running, and what will break first. The handover date is fixed in those two weeks and everything after it is measured against that date. The larger engagement is priced against that document rather than against an estimate made before anyone had read the code.
A handover, start to exitWhat we don't do
A mismatched engagement costs both sides more than a declined one, so these five are settled before a proposal is written rather than in month four.
- No engagements shorter than three months. Ramp-up alone runs 10–15 business days. Below three months you are paying mostly for the ramp.
- No fixed price against an undefined scope. We quote a fixed price only where the scope is written down and signed; otherwise the engagement runs monthly on 30 days' notice.
- No mobile application development. The ten technologies above are the whole list we staff against, and none of them ships an app store build. We would be hiring for the work after signing it.
- No single-engineer trials shorter than four weeks. One engineer needs roughly four weeks to get through your onboarding and produce something worth judging. A two-week trial measures onboarding.
- No engagement without a named technical counterpart on your side. Someone has to accept pull requests and settle priority. Without that, a team of four stalls in week two and bills for it.
That is the whole list. Work that sits inside the ten technologies, runs three months or longer, and has someone on your side to answer to, we will quote. Anything else you will hear about on the first call rather than three weeks later in a proposal.
Tell us which of the three this is.
A dedicated team, one to three augmented engineers, or a takeover that ends on a handover date. Whichever it is, five kinds of work get a no on that call instead of a proposal three weeks later.