Starting out in Guidewire DevTrails, I expected to work on just another problem statement. But this one made me pause and think deeper.
We looked at gig workers—especially delivery partners—and how unpredictable their income can be. A normal day for most of us can mean zero earnings for them, just because of rain, pollution, or extreme weather.
What struck me wasn’t just the problem—it was how common it is. This isn’t a rare situation. It happens frequently, and yet there’s no proper system that supports them when it does.
Initially, I thought insurance could solve it. But when I explored how current insurance systems work, it didn’t really fit.
They are designed for major, occasional risks—not something that affects people almost every day. The idea of filing claims repeatedly and waiting for approvals clearly doesn’t match the pace at which gig workers operate.
That’s when our thinking shifted.
Instead of relying on traditional claim-based systems, we explored a model where the system itself reacts automatically to real-world conditions. If certain thresholds—like heavy rain or poor air quality—are met, the system can trigger support without the worker needing to take action.
Another interesting idea was pricing. Rather than keeping it fixed, we considered making it flexible—changing based on how risky the upcoming days are expected to be. That way, it stays practical for both users and the platform.
What I found most valuable in this experience was not just the solution, but the mindset shift.
It made me realize that sometimes the right approach is not improving an existing system, but rethinking it completely based on how people actually live and work today.
This is my first step into sharing what I build and learn. Looking forward to exploring more problems like this and documenting the journey. 🚀
Top comments (4)
Good job❤️‍🔥
Great work ✨
Keep going ✨
Amazing idea!!