How do we ship and keep shipping?
A pod that ships every fortnight, and a pipeline your team still runs after we leave.
Delivery pods, platform engineering, CI/CD and migrations: a fixed monthly team, a release every fortnight, and the pipeline handed over documented and running.
What it is
We put a small, named pod on your backlog — engineers, a delivery lead, and the agents they run — at a fixed monthly rate with a release cadence you can hold us to. Alongside the feature work we build the part teams skip: the environments, the pipeline, and the migration path off whatever is holding the business back. Handover is a running pipeline and a written runbook, because a pod that leaves nothing behind is a rental.
Who it is for
If none of these sound like your situation, this is probably the wrong arc — and we would rather tell you that than sell you a discovery.
- Releases go out on a Saturday night, because that is when someone is free to fix them.
- You have a backlog, a budget, and no way to hire five engineers this quarter.
- The system that runs billing is on a version nobody will patch any more.
- Every environment differs and nobody can say which one matches production.
How the work is shaped
Repeatable shapes, not bespoke proposals. Each one has been run before and has a duration we hold to.
- 01Delivery Pod · 3 months minimumA fixed team of three to five, a quarter at a time: one release every two weeks, a visible burn-up, and a monthly cost report against the plan.
- 02Platform Engineering · 6 weeksEnvironments, pipeline, preview deploys, migrations and rollback — set up, documented, and demonstrated by your engineers running it rather than us.
- 03Migration · 8–14 weeksA live system moved on a defined cutover: parallel run, reconciliation report, and a rollback that has actually been rehearsed.
What it costs
Published, not gated. The assumptions column is the part that matters — a price without them is a guess you discover was wrong in week three.
| Band | From | What it buys | Typical duration | Assumes |
|---|---|---|---|---|
| Delivery Pod | ₹7,50,000 per month | Three engineers and a delivery lead, a release every fortnight, monthly cost and burn-up reporting. | 3 months minimum |
|
| Platform Engineering | ₹9,00,000 | Environments, CI/CD, preview deploys, migration and rollback procedures, handed over with a runbook. | 6 weeks |
|
| Migration | ₹18,00,000 | Cutover of one live system with a parallel run, a reconciliation report, and a rehearsed rollback. | 8–14 weeks |
|
What sits inside it
Delivery pods
A fixed team at a fixed monthly rate, with the release cadence written into the contract.
Platform engineering
Environments, tenancy, secrets and the release path — built once, so feature work stops paying for them.
CI/CD
Every merge tested, previewed and deployable, with rollback rehearsed rather than assumed.
Migration
Live systems moved with a parallel run and a reconciliation report, not a weekend and hope.
What it has produced
Every number here comes from work on this page. Follow it to the story and check it.
- to return a diagnostic report, from three days
- 4 hoursto return a diagnostic report, from three daysSee the story
- from pod start to reports going out without a chase
- 9 weeksfrom pod start to reports going out without a chaseSee the story
- the longest gap between production releases on a pod
- 14 daysthe longest gap between production releases on a pod
- named people in a pod, no substitutions mid-quarter
- 3–5named people in a pod, no substitutions mid-quarter
Is Accelerate what you need?
Tell us what is slow and what it is costing. If the answer is a different arc, or no arc at all, we will say so before anyone writes a proposal.
Size a delivery pod