We entered this hackathon thinking it would be like any other.
Read the problem.
Plan the features.
Start building.
But within a couple of days, we realized something important.
We were trying to solve the problem too quickly.
The challenge wasn’t about building an app.
It was about understanding a situation.
We’re working on a solution for delivery partners — people whose income depends on factors they can’t control.
A sudden downpour can stop deliveries.
Extreme heat can reduce working hours.
Pollution can make it unsafe to go out.
And when that happens, their income drops instantly.
At first, we looked at these as technical conditions to handle.
But then we asked a better question:
What does this actually feel like for them?
That question slowed us down — in a good way.
We spent time understanding:
When do they lose income
How frequently it happens
What kind of support would truly help
No coding.
Just thinking.
It felt like we were falling behind.
But once we got clarity, everything else moved faster.
We didn’t try to build a “big” solution.
We focused on building a meaningful one:
An AI-driven system that tracks real-world disruptions
and automatically compensates delivery partners for lost working time
No forms.
No waiting.
No manual claims.
From a development side, one rule became very clear:
If we can’t build it properly within our timeline, we don’t include it.
That helped us avoid:
Overengineering
Unnecessary features
Wasted effort
Now we’re nearing our Phase 1 submission.
We’re preparing:
A GitHub repository
A detailed README
A 2-minute demo video
If there’s one takeaway from this hackathon so far, it’s this:
Understanding the problem deeply saves more time than rushing into solutions.
We’re still learning.
Still iterating.
But this already feels like building something that could actually matter.
More updates soon.
Team VisionLogic | Guidewire DEVTrails 2026
Top comments (0)