Building-level backup workforce network that guarantees vetted house help when regular maids or instant apps fail.
Instant house-help apps have proven demand, but April reporting showed that supply collapses exactly when households need them most. Families still rely on informal maids for daily continuity, then scramble across WhatsApp groups, local agencies, and consumer apps when that help disappears.
Generated 2026-04-26 · Run 20260426084306
Overall rating3.3/ 5.0
2
Market
Narrow $73M India wedge growing 18-22% annually, but four credible rivals mean the beachhead is focused rather than expansive.
4
Differentiation
Building-level reserve capacity, access workflows, and absenteeism data create a real wedge, though large apps or ERPs could copy parts over time.
3
Execution
Milestones are crisp and unit economics look healthy at 6.8x LTV/CAC with 7.3-month payback, but four model flags and early cash burn temper confidence.
5
Timeliness
Late-April funding, supply crunch, and safety coverage all land in the same month, making continuity infrastructure unusually timely.
Why now
Capital is validating that households will pay for formalized backup home-help services at scale.
Recent migrant-worker departures exposed continuity, not discovery, as the most painful failure mode for urban households.
Because service happens inside private homes, any winner needs building-grade trust, access, and incident workflows rather than just matching.
Verified workers, training, insurance, and digital payouts have made a managed reserve workforce operationally feasible.
Catalyst.Late-April news showed simultaneous investor conviction in instant house help and acute service failure during migrant-worker departures, making continuity infrastructure newly urgent and budgetable.
The idea
ReserveGrid would sell apartment communities a guaranteed backup labor layer rather than a household marketplace. The product would maintain a neighborhood-level reserve pool of trained, background-checked workers who are pre-approved for each building's entry, resident preferences, and safety protocols. Community managers would see predicted gap days, reserve coverage windows, live worker ETAs, digital check-in and check-out, and incident escalation from one dashboard. Residents would book only through their building, which concentrates demand and makes standby staffing economical. Over time, the company becomes the labor continuity and trust layer for residential communities, not just a booking tool.
Beachhead
Premium gated communities in Gurugram with 500+ occupied units that see repeated maid absenteeism and already coordinate resident issues through a facility office or community app
Wedge
A subscription backup house-help grid for residential communities with pre-cleared float workers, building-specific access workflows, reserve capacity planning, and incident tracking
Non-obvious insight
The durable wedge is not another faster consumer booking app. Consumer apps have already trained households to pay for verified backup help, but the real unmet need is continuity at the building level, where pooled demand can support a reserved labor bench, tighter safety controls, and predictable unit economics.
Venture-scale path
Start with backup domestic help for dense apartment communities, then expand into the operating system for managed residential labor across cooks, nannies, eldercare aides, and overflow staffing for large home-service platforms.
Community backup labor grid
flowchart LR
Buyer[Property manager] --> Pain[Resident complaints from maid no-shows]
Pain --> Product[Backup house-help grid]
Product --> Outcome[Guaranteed trusted coverage]
Market
Sizing
TAM
$73MBottom-up: start with 8.8M gross managed homes/families across Mygate (4.0M) and NoBrokerHood (4.8M), remove an estimated 30% overlap to ~6.2M unique homes, filter 25% for large gated communities where a reserve bench is economically plausible (= ~1.55M homes), then apply an estimated blended annual revenue of ₹4,000 per home. Result ≈ ₹6.2B, or roughly $73M.
SAM
$5.1MApply a 7% Gurugram / premium-NCR share to the 1.55M-addressable-home proxy, informed by Gurugram’s 59% share of NCR launches and 51% share of NCR sales in H1 2024, yielding ~108k homes. At ₹4,000 per home-year, SAM is ≈ ₹434M, or about $5.1M.
SOM
$0.9MYear-3 reachable case: 25 communities × 800 occupied units per community × ₹4,000 blended annual revenue per home ≈ ₹80M, or about $0.9M. This assumes disciplined concentration in a few Gurugram corridors rather than citywide sprawl.
Executive takeaways
The evidence supports a real pain point, but the investable wedge is much narrower than the headline home-services market: continuity for dense premium communities, not another generic maid app.
Supply reliability and trust are the real bottlenecks. Customer demand already exists; what breaks during shocks is trained labor density, access approval, and incident handling.
Urban Company, Snabbit, and Pronto are validating consumer demand, but they are optimizing household acquisition and micromarket density rather than building-level reserve SLAs.
Gurugram is a credible beachhead because premium apartment supply is dense, community software is already entrenched, and NCR is a core demand cluster for instant house help.
The market remains early and operationally hard: online penetration is still tiny, the leading players are subsidy-heavy, and worker onboarding lags demand growth.
Any winning product must look as much like security/compliance infrastructure as labor dispatch: verification, data governance, access logs, and safety escalation are central, not ancillary.
Urgency vs workflow control in house-help alternatives
quadrantChart
title Market map
x-axis Low workflow control --> High workflow control
y-axis Low urgency --> High urgency
UrbanCompany: [0.55, 0.82]
Snabbit: [0.70, 0.90]
Pronto: [0.72, 0.92]
Broomees: [0.48, 0.52]
ReserveGrid: [0.90, 0.86]
Competition
Competitor
Stage
Wedge
Weakness vs. us
Urban Company InstaHelp
incumbent
Full-stack home-services platform extending into instant housekeeping.
Optimized for B2C demand capture, not building-level reserve capacity or RWA workflows; instant vertical is still investment-heavy and reputationally scrutinized.
Snabbit
scale-up
Instant household chores via a dense, women-only managed workforce and full-stack operations.
Household-led acquisition model still has to win one home at a time and does not solve community-level standby planning or shared access workflows.
Pronto
scale-up
Gurugram-born 10-minute house-help platform with high repeat use and dense local hubs.
Demand still outpaces onboarding, and the model remains household-centric instead of selling continuity to a community operator.
Broomees
scale-up
Verified domestic-help and placement service with both monthly-wage and on-demand options.
More agency-like and less software-native; weaker on live density planning, community integrations, and rapid shared-service economics inside towers.
Why incumbents do not win by default
Consumer marketplaces.Urban Company, Snabbit, and Pronto win household demand, but they do not own the building-level SLA, reserve bench, or resident-governance workflow that matters when multiple apartments fail at once.
Society ERPs and gate apps.Mygate and NoBrokerHood already own visitor, billing, and staff-entry workflows, but they do not guarantee labor supply; that makes them better channels or integration surfaces than default winners.
Traditional agencies and local networks.Agencies and resident WhatsApp groups offer breadth and replacement promises, but they are slower, less auditable, and weak on live capacity planning or standardized access control.
In-house community staffing.RWAs can try to hire float staff directly, but recruitment, verification, absenteeism management, and utilization become an HR problem most communities are not equipped to run.
Business plan
ReserveGrid targets a specific failure mode in India's fast-growing house-help category: when regular maids disappear, premium apartment communities have no trusted building-level fallback. Same-month reporting on Snabbit, Pronto, and Urban Company shows consumer demand is real, but supply collapses during migration shocks and safety expectations rise because workers enter private homes. The plan is to start in 500+ occupied-unit gated communities in Gurugram and sell property operators a backup labor SLA, not another household marketplace. The MVP is a community ops product that combines a pre-cleared reserve bench, building-specific access workflows, digital check-in and check-out, and incident handling. Go-to-market starts with regional property managers that control multiple towers, because one contract can unlock dense demand and shorten procurement versus selling one RWA at a time. The narrow market sizing from research is modest for the first wedge — about $73M TAM, $5.1M SAM, and $0.9M year-3 SOM — so the venture case depends on proving expansion into adjacent managed residential labor categories and overflow infrastructure. The biggest disconfirming risks are whether communities will fund continuity from shared budgets and whether reserve staffing can hold >90% fill rates at morning and evening peaks without breaking margins. Until those are validated in paid Gurugram pilots, budget ownership and partner willingness should be treated as assumptions rather than facts.
Beachhead
Premium gated communities in Gurugram with 500+ occupied units, sold first through property management firms that already control multiple towers.
Wedge rationale
This entry point creates faster proof than a broad household app because one buyer unlocks repeated demand, a shared operations workflow, and enough density to test standby labor utilization. It also aligns the budget owner, complaint owner, and security owner in the same sales motion.
Sequencing
Start with a concierge-heavy product and a narrow service scope so the company can first prove buyer willingness to pay, peak fill-rate reliability, and safe gate operations. Only after those metrics stabilize should the company deepen ERP integrations, automate resident booking, and expand labor categories or geography.
Not yet
Standalone direct-to-consumer app for individual households outside contracted communities · Expansion into cooks, nannies, eldercare, or live-in placement before backup cleaning and chores hit repeatable margins · Multi-city rollout before two Gurugram corridors show repeatable pilot-to-production conversion and worker utilization
Milestones
0–12 months
Close 3 paid pilots with Gurugram operator-controlled communities
Sustain >90% fill rate in contracted windows for at least one full absenteeism cycle
Convert at least 2 pilots into annual contracts
Launch one live workflow integration or reliable manual sync with a society ERP or gate system
Reach 5-8 contracted communities in two Gurugram corridors
12–24 months
Expand to 12-15 contracted communities with at least 2 multi-tower operator accounts
Prove corridor-level workforce planning with repeatable gross margin improvement
Launch one adjacent labor category in the strongest corridor only
24–36 months
Reach roughly 25 contracted communities consistent with the year-3 SOM case
Convert operator dashboards and incident logs into a premium reporting module
Decide whether to enter a second NCR cluster or deepen Gurugram density based on retention and utilization data
Test overflow supply partnerships with at least one larger platform or managed-living operator
Strategy map
flowchart LR
Wedge[Sell continuity pilots to multi-tower Gurugram operators] --> MVP[Reserve bench + dispatch + gate workflow MVP]
MVP --> Proof[Prove fill rate, complaint reduction, and safe operations]
Proof --> Expansion[Expand to more towers, more categories, and overflow partnerships]
Investor verdict
Call
Meet / investigate further
Why believe
A real pain point, visible category demand, and a clear building-level wedge create a plausible path to early proof that incumbents are not directly optimizing for.
Why doubt
The initial wedge is narrow and the two hardest questions — shared-budget willingness to pay and peak-hour unit economics — are still assumptions.
Next diligence
Secure 3 paid Gurugram pilots with one multi-tower operator and show 8 weeks of >90% fill rate plus measurable complaint reduction.
Financial model
3-year totals
Year 1 revenue
$91KEBITDA $-579K · Cash EOP $-479K
Year 2 revenue
$425KEBITDA $-368K · Cash EOP $-848K
Year 3 revenue
$845KEBITDA $-199K · Cash EOP $-1.05M
Unit economics
ARPU (annual)
$42K
Gross margin
70%
CAC
$18KPayback 7.3 months
LTV / CAC
6.8xLTV $123K
Funding ask
Round
pre-seed · $2.2M
Runway
24 months
Milestone
Reach 12-15 contracted communities, 2 multi-tower operator accounts, >90% fill rates in contracted windows, and one adjacent-category test with corridor-level gross-margin improvement.
Model sanity
Revenue engine. Base-case revenue comes from scaling contracted communities from 6 in Y1 to 26 by Q4Y3 at about $42K annual revenue per community.
Must go right. The model needs pilot-to-annual conversion and >90% fill rates to hold, because those two levers drive both community growth and gross-margin improvement.
Model breaks if. The biggest cash risk is a slower sales cycle plus sub-64% gross margin, which drives the downside cash low point to roughly -$1.45M.
Next-round proof. The next round is justified once the company shows 12-15 communities, two multi-tower operators, and corridor-level margin improvement on the Gurugram wedge.
Revenue, cash, and EBITDA — 12-month Y1 + 8-quarter Y2/Y3
Revenue (line, area)
Cash EOP (dashed)
EBITDA (bars, gray = loss)
Use of funds — $2.2M pre-seed
Headcount build by role — peak 19 FTE
Founder/CEO
Engineering
City ops
Sales
Training/compliance
Ops coordinators
Customer success
Finance/admin
Year-3 scenarios — base / downside / upside
Y3 revenue
Y3 EBITDA
Cash low point
Description
Downside
$590K
-$420K
-$1.45M
Slower operator approvals and weaker corridor density hold the company to 18 communities by Q4Y3.
Base
$845K
-$199K
-$1.05M
Gurugram wedge works as planned, ending Y3 at 26 communities with improving but still sub-target reported margins.
Upside
$1.08M
-$40K
-$860K
Faster multi-tower expansions and better reserve-bench utilization push the business close to breakeven by Q4Y3.
Sensitivity — Y3 cash and revenue impact, sorted by magnitude
Variable
Downside
Upside
Cash impact
Revenue impact
hiring pace
Ops and GTM hires are pulled forward 2 quarters ahead of revenue.
Hiring stays one quarter behind plan without missing SLAs.
-$180K
-$20K
sales cycle
Pilot-to-annual cycle stretches to about 6 months.
Strong proof shortens cycle to about 3 months.
-$170K
-$120K
gross margin
Reported margin exits Y3 at 64%.
Reported margin exits Y3 at 69%.
-$150K
$0K
CAC
CAC rises to $24K because enterprise diligence takes longer.
CAC falls to $14K with operator referrals and ERP partnerships.
-$140K
$0K
churn
Monthly churn rises to 3.0% after pilots convert.
Monthly churn improves to 1.5%.
-$130K
-$90K
ARPU
Blended annual revenue per community slips to $38K.
Blended annual revenue per community rises to $46K.
Flags: Base case runs below zero cash by M3 if no financing closes, so the raise must happen before pilots are fully underway. · Reported gross margin reaches only 66% in Y3, so reserve-bench utilization still needs to improve to meet the 70% target. · Revenue per FTE is low because this is an ops-heavy continuity service, not a pure software model. · Customer concentration remains meaningful until at least two multi-tower operator accounts are live and renewing.
BBC News. You can hire house help in 15 minutes in India. But is the system fair? · Sun Apr 05 2026 00:00:00 GMT+0000 (Coordinated Universal Time) · https://www.bbc.com/news/articles/c98megy6r1mo