The "you only have one customer" question

We hear this on basically every sales call. It deserves a real answer, so here's the honest one.

Yes. We have one paying customer.

A weekly farmers market in San Diego. They've been our customer since the day we shipped the first version of VIBEPro 13 months ago.

That's it. One customer. One market.

When prospective customers find this out, the reaction usually falls into one of three buckets:

1. "Cool, talk to me." (About a third.)
2. "Hmm, interesting, let me think about it." (About half.)
3. "I need a more proven tool." (The rest.)

We respect all three reactions. But for the second and third buckets, we want to make a case for why the math here might not be what you think.

What "one customer" means in our case

In most early-stage SaaS, "one customer" is a synonym for "untested." It usually means a few weeks of usage, a handful of test workflows, a founder who's mostly building rather than running real production, and a product that hasn't been stress-tested under real failure conditions.

That's not what one customer means here. Here's what 13 months of "one customer" actually produced:

• Days in production — 400+
• Market days run — 57, every Sunday, no missed weeks
• Space requests handled — 11,547
• Vendors onboarded — 556
• Active vendors in last 90 days — 324
• Messages delivered — 46,673 at 99.4% delivery rate
• Documents tracked with expiration alerts — 365
• Collection rate — 92%

If you spread those numbers across 5 customers instead of 1, every metric would still be impressive. We just happen to have run all of it through one market.

This is the version of "one customer" where the customer has stress-tested every code path, every edge case, every weird vendor situation, every fee model, every Saturday-morning emergency, every billing dispute, every insurance lapse, every weather cancellation, every "oh god the system is down at 5am on market day" moment, for over a year, with real money at stake.

We've shipped 5+ major releases (1.5 → 1.9) in response to actual production pain points. We've debugged real customer issues at 6am on a Sunday. We've handled real billing disputes. We've fixed real bugs that only showed up at scale. We're not a demo. We're a working system that has just only been deployed in one place.

Why we waited to start selling

This is the part that usually surprises people. We could have started selling VIBEPro a year ago. We chose not to. For 13 months, we deliberately avoided marketing, sales, growth — all of it. We focused exclusively on making one market work. Here's why.

Reason 1: Software for a niche profession is impossible to design without a customer.

Farmers market software written by people who haven't run a farmers market is bad software. The only way to build the right thing was to spend a year embedded with people running a real market — and that meant not letting other customers distract us.

Reason 2: A bug at 5am on market day is a fireable offense.

Until we were absolutely sure the system would not fail at the worst possible moment, we couldn't ethically take on customers who would depend on it. 13 months of zero downtime on market days is not nothing.

Reason 3: We wanted to know what we were selling before we sold it.

The pricing tiers we publish today, the feature priorities, the positioning — none of it could have been honestly written until we'd watched someone actually use the product for a year. The cost of this approach is that we're behind on revenue. The benefit is that we know exactly what we built, who it works for, and where it doesn't.

What "more proven" actually buys you

When a prospective customer says "I need a more proven tool," what they usually mean is some combination of: the assurance of social proof, the knowledge it won't break, somebody being there if there's a problem, and confidence the vendor will still exist in two years. Let's go through these honestly.

Social proof. We don't have a logo wall yet. That's a real downside if logo walls drive your buying. We do have receipts: 13 months of operational data, 57 market days run without a missed Saturday, real metrics, a real case study, the founder available to talk. We think that's better information than logos for an evaluation. We get that it doesn't feel the same.

Stability. Zero downtime on market days in 13 months. Other downtime has been brief and outside production hours. The system has been stress-tested by real operations. Our stability story is better than most early-stage SaaS, not worse.

Support. This is the one where we win against most of the category. Every customer talks to the founder directly. Every email gets a same-day reply. Every Saturday morning emergency gets handled in real time. We are unambiguously the most-supportive option in our category, because we have the time. (At 25 customers, we'll have to evolve this. At 1, we have it dialed.)

Long-term existence. VIBEPro is owned by Blargo LLC, a real legal entity. The product is generating revenue. We're not VC-funded so we're not at risk of being killed by an investor pivot. Keith has a 25-year career in software and isn't going anywhere. The biggest risk to us isn't "we run out of money" — it's "we don't grow fast enough to justify being a full-time company forever." We're working on that. One way is by writing posts like this and being honest.

The trade you're making

If you become VIBEPro customer #2, here's what you're trading.

You give up: the comfort of joining a 1,000-customer roster, the reassurance of seeing your peers' logos on the homepage, the certainty of an established brand name.

You get: a tool that genuinely fits the way real markets run, public simple pricing, direct access to the founder who built it, real production data instead of marketing copy, the ability to influence the product roadmap directly (because there are 2 of you), flexible fee rules — flat booth fees, sales-based percentages, or both in the same workflow — and a 13-month track record of zero downtime on market days, with 92% collection rate as your starting point, not your goal.

Some of you will make this trade. Some of you won't. Both are reasonable.

Who should NOT become customer #2

We're going to be the ones to say this, because if we don't, someone else will.

You should probably wait if your job depends on picking a "safe" software vendor that nobody at your nonprofit board can second-guess; if you don't have the time or appetite to give product feedback (we'll absolutely listen, which means we'll absolutely ask); if you're allergic to early-stage anything; or if you can't afford to take a small risk on a tool still establishing its market.

You should probably talk to us if you're tired of every other tool being almost-right; if you want flexibility in how you bill vendors instead of being locked into one fee model; if you'd genuinely prefer founder-direct support to a ticket queue; or if you want to be proud of being one of the first 10 customers when you tell the story later.