Quick commerce — the model where groceries, medicine, and daily essentials arrive at your door in under 30 minutes — is no longer a novelty. It's infrastructure. In most Indian metros, it's quietly become as essential as electricity or water for millions of urban households.
But there's a workforce behind every delivery, and that workforce is operating in a financial environment that's genuinely precarious — not because of bad intentions from platforms, but because the entire financial services industry was built for a different era of work.
We spent Phase 1 sitting with that problem. Not rushing to solutions. Just understanding what's actually happening on the ground for delivery partners. What we found was harder to ignore than we expected.
The Income Reality Nobody Talks About
Here's what a delivery partner's earnings week looks like in practice. Monday is fine — steady orders, decent pay. Tuesday it rains. Not just rains, but pours. Orders slow, roads are dangerous, and the partner makes a call to stay home. Wednesday the platform runs a maintenance window from 11am to 2pm. Thursday is normal. Friday there's a surge — but only in certain zones, and this partner isn't in one of them.
Total weekly earnings: unpredictable. Completely.
Not "variable" in the way a commission-based salesperson might experience. Actually unpredictable — governed by weather, platform uptime, demand zones, time of day, city events, and a dozen other factors outside anyone's control.
| Metric | Reality |
|---|---|
| Guaranteed earnings on any given day | ₹0 |
| Disruptions that are weather or platform-related | ~60% |
| Frequency at which income risk resets | Daily |
And yet — rent is monthly. EMIs are monthly. School fees are monthly. The rhythm of expenses doesn't adjust because the rhythm of income is erratic. That mismatch is where the real pressure lives.
Why Traditional Systems Break Down Here
We looked hard at what already exists — insurance products, income protection schemes, government welfare frameworks — and tried to understand why delivery partners either don't use them or can't access them in any meaningful way.
The answer keeps coming back to the same set of structural mismatches:
Eligibility
Most products require proof of stable income. Delivery partners can't provide that in any form that traditional underwriting recognizes. Payslips don't exist. Bank statements show irregular deposits. The system simply says: insufficient data.
Premiums
Fixed monthly premiums don't work when income is variable. On a bad week, a ₹200/month premium can feel impossible. On a good week, the same person might happily pay ₹400. No existing product bends that way.
Claims
The risks that actually hit delivery partners — a bad weather day, a platform outage, a zone with no orders — are frequent, short-lived, and small. Traditional claims processes are built for large, rare, documented events. The math doesn't work for micro-disruptions.
Trust
Many delivery partners have had bad experiences with financial products — hidden charges, complicated terms, rejected claims. The trust deficit is real, and any solution has to earn its way past it, not assume it away.
The problem isn't that delivery partners are uninsurable. It's that every existing product was designed assuming the user has a stable income, a formal employer, and the bandwidth to navigate complex paperwork. Remove those assumptions and almost every product falls apart.
What Phase 2 Is Really About
We're now deep in the design phase — and what that means in practice is less about building features and more about asking hard questions about the right foundations.
- What does "risk" actually look like for this workforce — at the level of a single shift, a single day, a single week?
- How do you think about eligibility when the traditional signals don't exist?
- What does a fair, transparent, and genuinely useful protection product feel like for someone who has good reason to distrust financial services?
We're working through the logic of how coverage could flex with the nature of gig work — responding to the same real-time signals that already govern whether a partner earns or doesn't on a given day. The idea isn't complicated. The execution is.
There are a lot of ways to get this wrong. You can build something technically elegant that nobody trusts. You can build something workers want but that isn't financially viable. You can over-engineer a solution that adds friction at the exact moments people need it most. We're trying to avoid all of those failure modes at once, which means Phase 2 is slower and more deliberate than Phase 1 was.
The Questions We're Still Sitting With
Honest answer: there are a few things we haven't fully resolved yet, and we'd rather say that than paper over it with confident language.
On data: What are the right signals to assess risk in real time without creating a system that feels intrusive or penalizing to the people it's supposed to help? There's a version of "real-time risk assessment" that becomes surveillance. We're not building that version.
On onboarding: The moment someone first encounters this product is critical — especially given the trust deficit we mentioned. Simplicity isn't just a UX preference here, it's a survival requirement for adoption.
On sustainability: We want to build something that actually helps delivery partners, not a product that looks good on paper and quietly extracts value from a vulnerable workforce. Getting the incentive structures right is an ongoing design problem, not a solved one.
What Comes Next
Once the core framework is stress-tested, we move into a pilot phase with a real cohort of delivery partners. The goal isn't just to validate that the product works — it's to find out whether it meaningfully reduces the financial anxiety that's become a constant undercurrent in this workforce. If it doesn't do that, we haven't solved anything.
More details on the pilot as we get closer.
Why We're Writing This at All
The build-in-public instinct for us isn't about marketing. It's accountability. When you say out loud that you're trying to build something fair, useful, and honest for a workforce that's been underserved — you're setting a standard you have to live up to. That's the point.
Q-commerce isn't slowing down. The workforce behind it isn't going away. The gap in financial protection for these workers is real, documented, and solvable. We're working on it.
If you've worked with gig workers, built in fintech or insurtech, or thought hard about alternative data and financial inclusion — we'd genuinely love to hear from you. The problems we're navigating aren't unique to us, and good thinking doesn't have to be either.
Top comments (0)