Team Orbitron | Guidewire DEVTrails 2026 — Scale Phase
Picture this.
It's a Tuesday evening in Chennai. Ravi has been on his Swiggy bike since 10 AM. He skipped lunch, took back-to-back orders through the afternoon heat, and now he's three deliveries away from closing out a decent day — enough to cover rent, groceries, and his daughter's school fees.
Then the rain hits. Not a drizzle. The kind of rain that turns Chennai streets into rivers in under twenty minutes.
Roads flood. Signals go dark. His bike stalls at an underpass that's already knee-deep in water. The app keeps pinging him with new orders he physically cannot reach. Then the cancellations start rolling in — one after another, each one a small financial cut.
By 8 PM, Ravi has lost four hours of work. No compensation. No explanation to give his family. No mechanism to recover what the weather took from him. Just a soaked jacket, a drained phone battery, and the quiet stress of doing the math on what this means for the month.
He'll be back on the road tomorrow. Because he has no choice.
This Is Not a Rare Story
We tend to think of disruptions as exceptions. Ravi's situation — and millions like it — tells a different story.
India has one of the fastest-growing gig workforces in the world. Platforms like Zomato, Swiggy, Zepto, and Amazon have built their last-mile delivery networks almost entirely on the backs of independent gig workers. These workers clock in every day with no fixed salary, no employer benefits, and no safety net beyond whatever they earn that shift.
And the disruptions that hit them aren't rare. Floods and waterlogging during monsoon season. Dense fog that shuts down visibility in North India winters. Bandhs and strikes that block entire districts. Election-day curfews. Sudden road closures from accidents or construction. Protests that lock down city centres without warning.
Every single one of these events — none of which the worker caused, none of which they could have predicted — results in the same outcome: lost income with zero recourse.
No platform compensates for this. Traditional health or vehicle insurance doesn't touch it. There's no product in the market today that says "we'll cover you when the city shuts down and you can't work."
The average delivery worker loses an estimated 20–30% of their monthly income to disruption events over the course of a year. For someone earning ₹15,000–₹20,000 a month, that's not a rounding error. That's the difference between stability and debt.
The Question That Started Everything
When Team Orbitron sat down at the beginning of DEVTrails 2026, this was the problem we couldn't stop thinking about.
Not the technology. Not the architecture. Just this one human question:
Why does Ravi have to absorb the cost of a flood?
He didn't cause it. He couldn't avoid it. He was doing his job when it happened. And yet the entire financial burden of that disruption falls entirely on him.
We started asking: what would it look like if that changed? What if there was a system that knew the flood happened, knew Ravi was affected, and just... made him whole? Automatically. Without him having to file anything, prove anything, or fight anyone?
That question became GigShield — an income protection platform built specifically for gig delivery workers in India, designed to pay out when disruptions happen without putting the burden of proof on the worker.
What Building It Actually Looks Like
We're now in Scale phase at DEVTrails 2026, which means we've moved past the "what are we building" stage and deep into the "why is this harder than we thought" stage.
A few things have hit us hard.
Workers don't stop to file claims. Ever.
This sounds obvious in hindsight, but early in our design process we kept thinking about the product from the perspective of someone sitting calmly at a desk. In reality, when a disruption hits, a delivery worker is stressed, possibly in physical danger, watching their income evaporate in real time. They're not opening an app to fill out a form. They're trying to get home safely.
If your product requires the affected person to initiate anything during a crisis, you've already failed them. The system has to detect, validate, and act — on its own. The worker should find out they're covered, not have to ask for it.
That single realisation changed the direction of almost every design decision we've made since.
You're designing for two kinds of trust simultaneously.
A delivery worker needs to trust that when something goes wrong, the platform will pay them fairly and quickly. An insurer needs to trust that claims coming through are legitimate and not being gamed. These two requirements pull in opposite directions if you're not careful.
Make the system too easy to claim from, and you create fraud risk. Make it too rigorous, and you're treating honest workers like suspects — which is both wrong and counterproductive. The entire Scale phase has been about finding that line and building something that sits on the right side of it.
Every time we made a product decision, we asked: does this make an honest worker's life easier, or does it make them feel like they're being interrogated? That question filters out a lot of bad ideas fast.
The "simple" problems turn out to be the deep ones.
Before we started building, we thought the hard problems would be the technical ones. In practice, the hardest questions have been much more fundamental.
How do you know a disruption actually happened in a specific area at a specific time? How do you confirm a worker was genuinely affected and not somewhere else? How do you make sure the same disruption event doesn't get claimed by hundreds of workers who weren't actually impacted? How do you handle a worker who's new to the platform versus one with a long, clean history?
None of these have clean answers. Each one requires a judgment call that has real consequences for real people. Getting them wrong doesn't just create a technical bug — it either fails an honest worker who deserved to be paid, or it erodes the financial sustainability of the whole system.
We've spent more time in Scale phase on these questions than on anything else. And we're better for it.
Why This Matters Beyond the Competition
DEVTrails ends. GigShield — or something like it — shouldn't.
India's gig economy is projected to employ over 23 million workers by 2030. The platforms will keep scaling. The disruptions won't stop. And right now, there is no product, no regulation, no platform policy that adequately protects these workers when external events take their income away.
We're not naive enough to think a hackathon project solves this. But we do think it's possible to prove the concept — to show that automated, affordable income protection for gig workers is technically and financially viable. That it doesn't require workers to jump through hoops. That it can be designed to be fair to workers and sustainable for insurers at the same time.
If Ravi knows that the next flood won't break his month, he goes to work with less fear. He makes better decisions. He focuses on doing his job safely instead of pushing through dangerous conditions because he can't afford not to.
That's what a safety net is supposed to do.
We're still building. Still learning. But we know what we're building for.
And it starts with Ravi.
Team Orbitron — Guidewire DEVTrails 2026
GigShield: Income Protection for India's Gig Delivery Workers
Top comments (0)