A whole team, scoped to an outcome, with one person accountable
When you need a system built, migrated or integrated and do not want to manage the team yourself, we deliver it under a statement of work. You agree the scope and acceptance criteria. Our delivery lead answers for the result.
Scope is settled before build starts
Before any work starts, we agree in writing what you will provide, what we will deliver and how each deliverable will be accepted. That covers access, stakeholders, data, constraints and acceptance criteria. Questions about scope get resolved at this stage, not halfway through the build.
Payment follows accepted work
Each payment is tied to a defined milestone and your formal acceptance of it. Any change to scope goes through a written change request with its effect on cost and timeline, and nothing changes until you approve it.
- Fixed price for well-defined work with a firm deadline
- Time and materials with milestones for work that will change as it goes
- Dedicated team for longer programmes where you want a stable group under our lead
You see progress every week
Governance is part of the contract. Your delivery lead and programme director are named in the statement of work, and escalation paths are agreed before work begins.
- Weekly status: milestones, blockers, open risks and change requests
- Monthly delivery review: progress against plan, quality and spend against budget
- Quarterly review with your executive sponsor and ours
At the end, the system is yours
Each engagement closes with source code, infrastructure as code, integration specifications, architecture records, runbooks and test evidence handed to your team. The test we apply: can your people run, extend and troubleshoot the system without calling us back?
How it works
Discovery call
A 30-minute call. You walk us through your systems, vendors and where delivery is stuck. We tell you honestly whether we are a fit.
Delivery assessment
Senior engineers map your environment, find the integration gaps, compliance risks and vendor overlap, and write up a scope and approach.
Engagement design
Together we define scope, milestones, acceptance criteria, team structure, service levels, governance and handover terms. This becomes the statement of work.
Governed execution
The team delivers milestone by milestone. No phase starts until the previous one is accepted, and you get weekly reporting throughout.
Handover
We transfer code, documentation and operational knowledge to your team, or move the system into a managed operations agreement if you want us to keep running it.
Common questions
When should I choose a managed team over staff augmentation?
Choose a managed team when the scope is defined and you want one party accountable for delivering it. Choose staff augmentation when you know what to build and want extra people working under your own leads.
What if the scope changes during delivery?
We log the change, assess its effect on cost and timeline, and send you a change request. Nothing changes until you approve it in writing.
Who owns the code and documentation?
You do. Ownership of the source code, infrastructure definitions and documentation transfers to you as agreed in the statement of work.
Can a managed team use your India delivery centre?
Yes. Many teams combine a US-based delivery lead and client-facing roles with engineers in our Gurgaon delivery centre. We agree the mix with you during engagement design.