I Tried to Build for Every Small Business

My first description of Kashi's customer was "small businesses."

That seemed specific enough. Shops needed to track sales, inventory, customers, and money. I thought one flexible platform could serve most of them.

Then I spent time with businesses that were all "small" and had almost nothing else in common.

A flower shop handled custom orders and delivery dates. A hardware store dealt with large inventories and supplier pricing. A café needed quick service. A pet grooming business relied on appointments and repeat visits. A grocery store cared about fast checkout.

Their needs overlapped on a feature list. Their days did not.

The broad audience showed up in the product

I tried to give everyone something useful. That produced more screens, more configuration, and a homepage that had to promise everything at once.

"Manage your business in one place" was true enough to describe Kashi. It didn't tell a florist why they should stop using their existing process today.

The same problem affected distribution. Where do small-business owners spend time online? There isn't one answer. A florist may follow event-planning communities. A hardware store owner may know suppliers and trade groups. The channels, language, and buying triggers change by business.

I'd made the addressable audience large on paper and difficult to reach in practice.

What I'd do differently

I'd start with one business category and one painful workflow.

I would visit owners, watch how they do the task today, and ask about actual failures: a missed order, an inventory mistake, a late quote, or a customer they failed to follow up with.

I'd look for problems that recur, cost money or time, and are already being solved awkwardly. I'd build a narrow tool around one of those problems and see whether people come back.

I'd still want the option to expand. But I'd rather earn it by solving one job well than start with a platform broad enough to fit everyone and specific enough for nobody.