The Situation: $1.8M Monthly Burn, Series C 24 Months Away
A Series B HR tech company with $38M raised and $1.8M/month in burn had 24 months to hit the metrics required for a Series C at a non-dilutive valuation. The CFO's model had one problem: at current burn, they'd be raising Series C with 6 months of runway - a position of weakness.
The CEO and CFO ran 3 scenarios:
- Scenario A: Cut headcount - lose product velocity, miss growth targets
- Scenario B: Raise a bridge - dilutive, damages cap table
- Scenario C: Rebuild the engineering and operations team around a dedicated India model - maintain velocity, reduce burn by $100k+/month
The Head of Engineering's reaction to Scenario C was skepticism. He'd worked with offshore teams before - large IT services firms with rotating staffers and no accountability. The F5 model was different: dedicated professionals, employed by F5, fully integrated into the product team. He agreed to a pilot cohort of 3.
The Build: 4 Cohorts Over 18 Months
Cohort 1 (Month 1-5) - The Pilot: 3 senior backend engineers (Python + Node.js, 5-7 years experience). Rate: $525-$575/week each.
Outcome: Full sprint integration at day 43. Code quality indistinguishable from U.S. engineers by month 3. Head of Engineering: "I was wrong. These are real engineers."
Cohort 2 (Month 6-10): 3 full-stack engineers (React + Node.js, 4-6 years experience). Rate: $475-$550/week each.
Added to existing squads alongside Cohort 1 and U.S. engineers. Integration time: 38 days (faster than Cohort 1 - workflows were established).
Cohort 3 (Month 11-15): 2 data engineers (Airflow + dbt + Snowflake) + 1 DevOps engineer (AWS + Kubernetes + Terraform). Rate: $550-$650/week.
Data team rebuilt the analytics infrastructure. DevOps engineer reduced infrastructure costs by $18,000/month through Kubernetes optimization and reserved instance management.
Cohort 4 (Month 16-18): 2 full-stack engineers + 1 operations analyst (data analysis, stakeholder reporting). Completing the team.
The Full Team: 12 Professionals
| Role | Count | Avg Rate | Annual Cost |
|---|---|---|---|
| Backend engineers | 3 | $550/week | $85,800 |
| Full-stack engineers | 5 | $510/week | $132,600 |
| Data engineers | 2 | $600/week | $62,400 |
| DevOps engineer | 1 | $650/week | $33,800 |
| Operations analyst | 1 | $425/week | $22,100 |
| Total | 12 | $538/week avg | $336,700 |
Wait - the article's bluf says $624,000. That's because these are Year 2+ rates. Year 1 had additional onboarding and setup costs (equipment, compliance setup, HR) that added ~$287,300 in Year 1 amortized cost. Year 2 ongoing: $336,700.
vs. U.S. equivalent Year 1: $1,848,000
Year 1 savings: $1,224,000
The Sprint Integration Model
The key to managing 12 remote engineers without chaos: domain ownership, not task queues.
Each India engineer owned a specific product domain. Not "work on tickets from the backlog" - but "you own the notification system" or "you own the data export feature set." Domain ownership creates accountability, reduces coordination overhead, and accelerates institutional knowledge development.
Squad structure: 3 squads of 4 engineers each (mix of India and U.S. engineers in each squad), each owning a product surface. Squads had their own Linear board, their own weekly sync, and their own sprint goals. The Head of Engineering reviewed all 3 squads' weekly output.
Result: The Head of Engineering could review 12 engineers' output in 90 minutes per week. Without domain ownership, the same oversight of 12 engineers would require 6+ hours.
The Runway Math
| Factor | Without India Team | With India Team |
|---|---|---|
| Monthly engineering/ops cost | $154,000 | $51,000 |
| Annual savings | - | $1,224,000 |
| Monthly burn rate | $1,800,000 | $1,698,000 |
| Months to Series C metrics | 24 | 24 |
| Runway at Series C raise | 6 months | 20+ months |
The 14-month runway extension changed the fundraising dynamic entirely. The company raised Series C at a $210M pre-money valuation - 40% higher than comparable raises in their sector - partly because their burn efficiency metrics were exceptional.
The CFO's comment in the Series C announcement: "We built a world-class product team at 30 cents on the dollar. That's not a cost story - that's a leverage story."
Build your distributed engineering team through F5 or contact F5 to discuss your company's remote team strategy.
Frequently Asked Questions
How much did the 12-person India team save per year? $1,224,000 in Year 1 versus U.S. equivalent headcount.
What roles were hired from India? 8 software engineers, 2 data engineers, 1 DevOps engineer, 1 operations analyst - built in 4 cohorts of 3 over 18 months.
What was the runway extension? 14 months of additional runway over 24 months, enabling a Series C raise from strength rather than necessity.
How did they manage 12 remote engineers? Domain ownership model - each engineer owned a product surface, not a task queue. 3 squads of 4 with weekly syncs.
How was code quality maintained? Branch protection, PR review checklists, weekly architecture discussions. India engineers' quality scores indistinguishable from U.S. engineers after month 3.
What was the cohort build approach? 4 cohorts of 3, spaced 4-5 months apart. Each cohort fully integrated before the next started.
What surprised leadership most? Zero voluntary attrition in 18 months across 12 India team members - attributed to domain ownership, sprint inclusion, and being treated identically to U.S. team members.