It would be easy to make Jugaadi's landing page sound like it's available everywhere. It isn't, and that's intentional.
The temptation to go wide
A marketplace feels more credible when it looks big — more cities, more workers, more tasks posted. The problem is that a two-sided marketplace is only as useful as the density of both sides in one place. A hundred workers spread across twenty cities helps nobody; fifty workers in one neighborhood is enough to make the core loop — post, respond, book — actually work for someone today.
What "one city" buys us
A small, dense pilot means verification is a phone call, not a queue. It means when something breaks in the booking flow, we hear about it from a handful of real users instead of debugging silently across a thousand. It means the manual pieces — checking a worker's identity, handling an edge case — stay manageable by one person.
What has to be true before we expand
More cities means more manual verification load, more support surface area, and a real test of whether the core loop holds up without the founder personally knowing most of the early workers. We'd rather prove that in one place first than discover it's broken everywhere at once.
If you're reading this from outside the pilot city: the waitlist on the homepage is exactly for this — we'll reach out when coverage expands to where you are.