Opportunity BasketStand at a busy market stall on a Saturday morning and it looks like a good business. Produce moving, a queue forming, cash changing hands. Come back at the end of the day and talk to the person behind the table, and a different story comes out. Half a crate of tomatoes went soft and unsold. Three customers walked off because the card reader was down. Last week's rain meant a whole day's stock was thrown away. And somewhere in a notebook is a tally of the day that will take another hour to reconcile tonight.
Farmers markets and street vendors run one of the oldest kinds of business there is, and they carry problems that almost nobody builds tools for. That neglect is exactly what makes them worth a closer look.
The money leaks where nobody is watching
A market vendor's income does not usually fail in one dramatic way. It bleeds out slowly, through several small gaps at once.
Look at each of those gaps and you are looking at a problem someone would pay to close. Spoilage is a demand-forecasting problem: the vendor is guessing how much to bring and guessing wrong. Lost cash-only sales are a payments problem, still real in dozens of countries where card acceptance at a stall is awkward or costly. The wet Saturday is a perishable-inventory problem. The hours of manual tallying are a bookkeeping problem. The forgotten regulars are a retention problem, the same one a corner shop or a coffee chain spends heavily to solve, just without any of the tools.
None of these is glamorous. All of them cost the vendor real money, week after week. That combination, expensive and unglamorous, is where quiet businesses get built, because the flashy problems are crowded and these are wide open.
Why these problems stay unsolved
The obvious question is why, if the pain is this clear, nobody has fixed it. Three reasons, and each one is an opening rather than a wall.
The buyers are hard to reach as a group. A market vendor is not sitting in an office waiting for a sales demo. They are behind a table at dawn. Reaching them takes knowing where they gather, which most software companies never bother to learn.
The margins look small from the outside. A single stall does not spend like an enterprise, so builders assume there is no money here. They miss that a market can hold two hundred stalls, and a regional network of markets many thousands, all with the same problem.
And the people closest to the problem rarely build software. The vendor knows exactly what hurts, but is busy running the stall, not writing code. The person who could build the tool has usually never stood behind the table, so never sees the pain clearly enough to solve it.
That gap between who feels the problem and who could solve it is precisely the gap worth stepping into.
How to turn one of these into a business
Pick a single leak, not all five. Say you choose spoilage. You would spend a few market days with three or four vendors, watching what they throw away and why. You would learn that the guesswork is really about weather, footfall, and which produce turns fastest, and that a simple weekly forecast, even a rough one, would save real money. You would build the smallest version of that, put it in front of those same vendors, and see whether it changes what they bring to market.
That is the whole method, and it works for any of the gaps. Watch closely, solve one thing by hand for a few real people, then make it repeatable once you know it helps. The market vendor is not a small customer. The market vendor is an underserved one, which is a very different thing.
Where to start looking
Vendor and small-trader problems sit inside the agriculture, retail, and payments categories on Opportunity Basket, each one drawn from real complaints and demand rather than invented at a desk. If you want to see what people in these trades are actually struggling with, that is the place to begin. Browse the problems by category.
And if you already have an angle of your own, a specific leak you think you could close, the Idea Lab is being built to take an idea like that and help you shape it into something buildable. For now, the fastest way in is to read a few real problems and let one of them catch you.