Latest / B2B SaaS Talks with Fexingo: Enterprise Software, Sales Cycles, and Procurement / Why Enterprise Software Vendors Need a Customer Zero
Transcript
- Lucas: Luna, I want to talk about a concept that's quietly reshaping how enterprise software vendors get their first real customer — it's called 'Customer Zero'. Luna: Customer Zero — that sounds like a bug report. What is it exactly? Lucas: It's actually the opposite of a bug. A Customer Zero is a design partner — a real enterprise buyer who signs up to use the product before it's fully built, often at a steep discount, in exchange for giving the vendor constant, unfiltered feedback. Luna: So it's not a beta program. It's more like a co-creation arrangement. Lucas: Exactly. A beta program is usually about testing for bugs — you give a nearly finished product to a few users and say, 'tell us what breaks.' Customer Zero is about testing for value. You give a half-finished product to a real buyer and say, 'tell us what matters.' Luna: And that buyer is paying you — even if it's a fraction of list price. That changes the dynamic. Lucas: It does. The best example I know is Snowflake. Before they went public, before they had a polished product, they recruited a handful of design partners. Companies like Adobe and Netflix, actually. Those early customers used a version of the platform that was nowhere near what Snowflake is today. Luna: And they shaped the core architecture — the separation of compute and storage, the pricing model, all of it. Lucas: Right. One of Snowflake's co-founders, Benoit Dageville, has said in interviews that those early conversations were brutal. Customers would tell them, 'Your query engine is too slow,' or 'Your pricing doesn't make sense for my workload.' And Snowflake would rebuild. Luna: That level of feedback is rare if you're just selling a finished product. Most enterprise buyers won't bother telling you what's wrong — they'll just not buy. Lucas: That's the whole point. With a Customer Zero, the buyer is invested. They've already committed budget and internal mindshare. They want the product to work, so they give you the kind of specific, actionable feedback that product managers dream about. Luna: But how do you find the right Customer Zero? It can't be just any company that says yes. Lucas: You're right. The wrong Customer Zero is dangerous. If you pick a company that has a really weird workflow, you might end up building a product that only works for them. Then you launch to the broader market and nobody else wants it. Luna: So what's the filter? How do you know if a prospect is the right fit? Lucas: I think there are three criteria. First, their problem has to be common — not a one-off. If their pain is shared by at least 20 other companies in your target segment, you're safe. Second, they need to have a genuine tolerance for unfinished products. Some enterprise buyers will freak out if the UI is ugly or a feature is missing. Luna: And third? Lucas: They need to have a champion who can push back internally. Because the Customer Zero relationship means the product will have outages, it will have rough edges. The champion has to be able to tell their own boss, 'No, this is worth it — we're helping build this thing.' Luna: That's a lot to ask. What do you give them in return besides a discount? Lucas: Influence. The Customer Zero gets a seat at the table. They can request features that matter to them, and they know the vendor is listening. There's also status — Snowflake's early design partners are often mentioned in case studies, and they get access to the CEO. That has real value inside a large company. Luna: It also compresses the sales cycle. Normally an enterprise deal can take nine to twelve months. But if you're selling a Customer Zero arrangement, it's more like a partnership discussion than a procurement process. Lucas: Exactly. I've seen deals close in 30 to 60 days when they're structured as Customer Zero. Because you're not asking for a big budget — you're asking for a small, experimental budget. And the legal review is lighter because the contract explicitly says the product isn't finished yet. Luna: That's a huge advantage. But I imagine there's a flip side. Once you graduate from Customer Zero and start selling to mainstream buyers, you have to manage the expectations of those original partners. Lucas: Absolutely. The classic risk is that your Customer Zero gets upset when the product becomes more generic. They loved being special. Now you're saying, 'We can't build that feature just for you anymore.' Some vendors handle this by creating a customer advisory board, so the Customer Zero companies still have a voice, just not a veto. Luna: That makes sense. So Customer Zero is a strategy for the first two to five deals. Not a long-term program. Lucas: Exactly. I'd say the window is roughly the first six to twelve months of a product's life. After that, you should have enough feedback to build a general-purpose product. Then you start selling to the early majority, and the Customer Zero relationship ends — or evolves into a standard enterprise account. Luna: What about pricing? Do you keep the discount forever? Lucas: Typically no. The contract has a sunset clause. After 12 or 18 months, the price steps up to a negotiated rate — still lower than list, because they helped build the product, but not the steep 80 percent discount they got initially. That transition needs to be handled delicately, because the relationship is now a real commercial one. Luna: I can see why this is appealing for startups. But what about established vendors launching a new product? Could Salesforce do a Customer Zero for a new AI feature? Lucas: They could, and some do. Though the challenge for a big vendor is that the Customer Zero gets lost in the noise. The feedback loop has to be direct to the product team, not filtered through account managers. That's harder to maintain at scale. Luna: So the best fit is probably a Series A or B SaaS company with a clear target segment and a product that's not quite ready for prime time. Lucas: I think so. And there's a specific metric I like to look at: time to first value. For a Customer Zero, you want that to be under 30 days. If they can't get value in a month, they'll lose interest internally, and the feedback will dry up. Luna: That's a good discipline. It forces the product team to focus on the core use case instead of building bells and whistles. Lucas: Right. And it also forces the sales team to be honest about what the product can do. You can't oversell a Customer Zero — they'll find out in week two. Luna: There's a parallel here to something I've been thinking about regarding the ad-free nature of our show. We don't run ads, and that's a deliberate choice. It keeps the conversation honest, but it also means the show relies on listener support. Lucas: That's a good point. We're essentially doing a Customer Zero model with our audience — we give you unfiltered conversations, and in return, we ask for feedback and, if you find value, a contribution at buy me a coffee dot com slash fexingo. Luna: Exactly. It keeps us accountable to you, not to advertisers. And it lets us dive into niche topics like this one without worrying about mass appeal. Lucas: Anyway, back to Customer Zero. Another thing I want to touch on is how you measure success. The obvious metric is product adoption, but I think the real metric is the number of features that originated from Customer Zero feedback that later became top-used features in the general product. Luna: So you're tracking the feedback to feature pipeline. Lucas: Yes. I've seen one company that had a board in their office — a literal whiteboard — where they listed every piece of feedback from their two Customer Zero accounts. They'd mark it as 'shipped,' 'planned,' or 'won't do.' That transparency built enormous trust. Luna: That's smart. But it also creates a lot of noise. Not every piece of feedback is strategic. Lucas: Agreed. The product team has to filter. The rule of thumb I've heard is: if two out of three Customer Zero accounts ask for the same thing, it's probably a legitimate need. If only one asks, it might be specific to their workflow. Luna: What about the emotional side? Customer Zero relationships are intense. The vendor's team is in near-daily contact with the buyer's team. That can lead to burnout. Lucas: It can. And it's often overlooked. I recommend that the vendor assign a dedicated customer success person to the Customer Zero — someone who can buffer the product team from the daily noise. The product team should get a weekly summary, not a firehose of Slack messages. Luna: So structure matters. You can't just wing it. Lucas: Right. And you need to set expectations from day one. Write a joint success plan that says: this is what we're building, this is when you'll see it, and this is how we'll communicate. Otherwise, the buyer feels ignored and the vendor feels overwhelmed. Luna: I want to ask about the legal side. Do you need a special contract for Customer Zero? Lucas: Yes, ideally. The standard enterprise software license agreement assumes the product is finished. You need a design partner agreement that explicitly states the product is in development, that uptime SLAs don't apply, and that the buyer gets a right to terminate early if the product isn't meeting their needs. Otherwise, procurement will kill the deal. Luna: And what about IP ownership? Does the Customer Zero own the features they suggest? Lucas: No, the vendor retains all IP. But the contract should grant the Customer Zero a non-exclusive, royalty-free license to use any features developed from their feedback. That's standard and fair. Luna: Good. So to wrap it up, Customer Zero is a deliberate, structured way to compress the learning loop for a new enterprise product. It's not just a discount — it's a relationship with a buyer who helps you build the right thing. Lucas: Exactly. And the best part is, when you get it right, those Customer Zero accounts often become your biggest advocates. They'll speak at your conferences, they'll give you testimonials, and they'll buy more when you launch the full product. Luna: So it's a high-risk, high-reward strategy. But for a startup with a clear vision and a lot of listening skills, it might be the fastest path to product-market fit. Lucas: I'd say it is. And if you're a founder listening, think about the one enterprise customer you'd love to co-build with. That's your Customer Zero.