0:00 Here’s a quote that’s been stuck in my head all week: "Most commercialization failures are not created at launch.0:07 They are merely revealed there." Oof.0:10 Yeah.0:10 That lands.0:11 That’s from that Knox Institute paper, right?0:14 It feels like it should be tattooed on the inside of every founder’s eyelids.0:19 Exactly.0:19 And it’s the perfect bridge from our conversation last week about brutal pivots.0:25 We talked about the aftermath of a failed plan, but today I wanna talk about the moment before the pivot—the launch that forces your hand.0:34 The one that was dead on arrival and you just didn't know it yet.0:38 Oh, I know the one you mean.0:40 You’re talking about Fetch.0:42 The company that’s now processing, what, 13 million receipts a day?0:46 Thirteen million a day.0:48 A reported seven-hundred-million-dollar gross revenue run rate.0:52 Profitable.0:53 They are a monster.0:54 But their first product was a complete, total, catastrophic failure.0:59 And that's what makes it such a good story.1:01 Because they didn't just stumble.1:04 They built this incredibly complicated, elegant, and fundamentally doomed machine.1:09 They called it the "three-legged stool." Which is already a red flag.1:14 Anytime your business model needs three different, independent groups to all do something perfectly in sync… you’re in trouble.1:22 So break it down.1:23 What were the three legs?1:25 Okay, so leg one: the shopper.1:27 They go to the grocery store, they want rewards.1:30 Simple enough.1:31 Leg two: Fetch, the company providing the rewards platform.1:35 Fine.1:35 Leg three… this was the killer.1:38 The grocery retailer itself.1:39 Ah.1:40 So they needed the store’s permission.1:42 Permission, integration, everything.1:45 The original idea was a checkout-based system.1:48 It had to plug directly into the retailer’s point-of-sale software.1:52 So to launch in ANY city, the Fetch sales team had to go store by store, chain by chain, and convince them to install their software and train their cashiers.2:03 Oh, that’s a nightmare.2:04 That’s not a tech company, that’s a door-to-door sales company with a cripplingly long sales cycle.2:11 I mean, can you imagine the pitch?2:13 "Hi, we’re a no-name startup.2:15 Please inject our code into the single most critical piece of technology in your entire business—the thing that takes the money." Right?2:24 "And then train your entire, very-high-turnover staff on how to use it.2:29 For free!" It’s insane in retrospect.2:31 But you can see how they got there, right?2:34 It feels more… legitimate.2:36 More defensible.2:37 A deeper moat.2:38 It feels like a 'real' business partnership.2:41 But you’re not building a product, you’re building a series of one-off consulting gigs.2:47 Your growth is capped by the number of salespeople you can hire and how many flights they can take.2:53 It’s the opposite of scalable.2:55 And that’s what the data shows.2:57 CB Insights says 42% of startups fail because of no market demand.3:02 But a quote I saw from Userpilot reframed it.3:05 They said often the market need wasn’t absent, it was just… misunderstood.3:10 People did want easier savings.3:12 Fetch’s CEO, Wes Schroll, even said that.3:14 He said, "The first thing to fail… was not the premise that people wanted easier savings.3:20 It was the route to them." The route to them.3:23 That’s it.3:24 They put a mountain range between the customer and the value.3:28 And every single grocery store was another mountain they had to convince to let them pass.3:34 So what does that feel like, inside the company?3:37 You’ve raised money, you’ve hired people.3:40 You’re all in on this vision of this beautiful, integrated system.3:44 But the numbers aren’t moving.3:46 It’s denial, at first.3:48 You know?3:49 You blame the execution.3:50 "Oh, we just need better salespeople." Or, "This one retailer is just slow, the next one will be faster." You look for any reason other than the core assumption being wrong.4:02 And the core assumption here was that retailers would be willing partners in this.4:07 That the value for them was clear enough to overcome the massive friction of implementation.4:13 Which it never is.4:14 What was the value prop for the retailer?4:17 Vague promises of customer loyalty?4:20 More data?4:20 They already have loyalty programs.4:23 You’re asking them to do all the work for a benefit they probably feel they can get themselves.4:29 So you’re burning cash.4:30 The second biggest reason startups fail, right?4:34 82% fail because of cash flow problems.4:36 And Fetch is spending all this money on sales teams, on custom integration work… and they’re getting, what, a handful of stores live?4:45 It’s a leaky bucket.4:46 A firehose, really.4:48 And the whole time, the clock is ticking.4:50 You can just feel the runway getting shorter and shorter.4:54 And the conversations in the boardroom must have been brutal.4:58 The investors are looking at the burn rate versus the adoption rate and the math just isn't mathing.5:05 Right.5:05 And this is where that Knox Institute quote comes back in.5:09 The failure was baked in months, maybe years, before launch day.5:14 It was baked in the moment the whiteboard diagram had "Retailer POS Integration" as a required box.5:20 The launch just held a mirror up to the bad decision.5:24 So then what happens?5:25 The moment of truth.5:26 Do you double down, or do you find what they called "the escape hatch"?5:31 The escape hatch.5:32 I love that phrasing.5:34 It wasn’t a "pivot." It was an emergency exit.5:37 And it was so brilliantly simple.5:39 They asked: what is the one thing that EVERY shopper gets from EVERY store, that requires zero permission and zero integration?5:47 A paper receipt.5:49 A paper receipt.5:50 A little trail of data that the store just gives away.5:53 So they scrapped the entire three-legged stool.5:56 They threw out the point-of-sale integration, fired the sales team probably, and built an app with one function: take a picture of your receipt.6:06 And in that one move, they took back all the power.6:09 They no longer had to ask for permission.6:12 Their growth was no longer tied to a retailer’s IT department schedule.6:17 It was only tied to how many people they could convince to download an app and take a picture.6:23 A waaaay easier problem to solve.6:25 A marketing problem, not an impossible sales and engineering problem.6:30 And look what happened.6:31 13 million receipts a day.6:33 They found a way to get the data they needed without ever setting foot in the store.6:39 There’s a quote from the analysis that just nails it.6:42 "The winning product did less at checkout and learned more after it." Say that again.6:48 That’s the whole lesson.6:50 "The winning product did less at checkout and learned more after it." Their first product tried to do everything at the point of sale.6:59 It was complex, it was integrated, it was a heavy lift.7:02 The winning product did literally nothing at checkout.7:06 It was invisible.7:07 The work happened later, on the user's couch, in five seconds.7:11 And that’s what this means if you’re a founder listening to this.7:15 You have to ask: where is the friction in my model?7:19 Who has to say 'yes' for me to grow?7:21 If the answer is a long list of people who are not your customer, your model is probably broken.7:28 You have to find the path of least resistance.7:31 Fetch leveraged a behavior that already existed—people get receipts.7:35 They didn't have to teach anyone anything new.7:38 They just attached a reward to a thing people were already doing.7:43 So let's pinpoint the moment of failure.7:45 It wasn't when the first grocery store said no.7:48 It wasn't when they missed their first quarter's target.7:52 No.7:52 The moment of failure was on day ONE.7:55 Before they wrote a line of code.7:57 It was the moment someone stood at a whiteboard and drew a box that said "Integrate with Retailer" and everyone in the room nodded.8:06 Yes!8:06 That's it.8:07 That was the original sin.8:09 It was the untested, unvalidated assumption that this was a feasible path to scale.8:14 Everything that came after—the slow growth, the cash burn, the painful sales cycles—it was all just a symptom of that one, core, flawed belief.8:24 And it's so seductive.8:25 As a founder, you fall in love with the elegant, complex solution.8:29 It feels more defensible, harder to copy.8:32 You think a complex problem needs a complex answer.8:36 But the market almost always rewards the simple answer.8:39 The one that removes a step, not the one that adds three.8:43 The first Fetch product added steps for the retailer, for the cashier, for everyone.8:49 The second Fetch product removed the need for all of them.8:53 It put the user in complete control.8:55 Scan or don’t scan.8:56 The business's success or failure rested entirely on the value proposition to that one person, not on a delicate negotiation between three different parties.9:07 So the lesson here is almost painfully simple.9:10 Don't build a business that relies on other people's permission to grow.9:15 Find the "paper receipt" in your industry.9:17 Find that trail of data or that existing customer behavior that you can latch onto without needing to ask for a key to the building.9:26 And you have to be brutal about your assumptions.9:30 What is the one single belief that, if wrong, will sink your entire company?9:35 For Fetch, it was the belief that retailers would be willing partners.9:39 And they were wrong.9:41 They were catastrophically wrong.9:43 But they were smart enough to realize it and find the escape hatch before the plane hit the ground.9:49 A lot of founders aren't.9:51 They just keep flying, insisting the runway will appear.9:55 They ride the bad assumption all the way down.9:58 Because they’ve tied their ego to it.10:00 They’ve told their investors it’s the right plan.10:04 Admitting it’s wrong feels like admitting they were wrong.10:07 Which they were!10:09 And that’s okay!10:10 I mean, that’s the whole point of this show, right?10:13 Being wrong is part of the process.10:15 The winners are just the ones who admit it fastest.10:19 Okay, so let's bring this home for the founder who's maybe feeling a little queasy right now, listening to this.10:26 Maybe their whiteboard drawing has a few too many "three-legged stool" components.10:32 Yeah, they're looking at their own beautiful, complex machine and starting to sweat.10:37 What’s the first thing you do?10:39 If you suspect your core assumption might be flawed, what is the action you take tomorrow morning?10:46 You have to design the cheapest, fastest possible test for that one assumption.10:51 Forget the full product.10:53 Forget the elegant UI.10:54 What is the absolute minimum thing you can do to prove or disprove that belief?11:00 For Fetch, they could have literally just gone to a mall and offered people five bucks to show them their receipts.11:07 Like, a concierge MVP.11:09 Just you, a human, faking the entire backend of the system.11:13 Exactly.11:13 Before you build a single line of integration code, can you manually prove that retailers are even willing to have a conversation?11:22 Can you get ten of them on the phone?11:24 If you can't get ten on the phone, you are not going to get a thousand to install your software.11:31 It’s about de-risking the single biggest point of failure.11:35 And I think founders, especially technical founders, often miss this.11:39 They de-risk the tech.11:41 "Can we build it?" Yes, you can almost always build it.11:44 That's not the question.11:46 The question is, "Should we build it?" And even more, "If we build it, who has to give us permission for anyone to even use it?" Mm-hm.11:55 And the Fetch story is the perfect example of the stakes.11:59 They had the right idea—people want rewards.12:02 They had the right market—grocery shoppers.12:05 They had the wrong mechanism.12:06 And that one detail was the difference between bankruptcy and a company with a seven-hundred-million-dollar revenue run rate.12:15 It's staggering when you put it like that.12:18 The entire outcome of the company hinged on changing the method of data collection from "ask permission" to "leverage what's already there." It all goes back to that Knox quote.12:29 The failure was there all along.12:32 The launch just made it impossible to ignore.12:35 The market is the ultimate truth-teller.12:37 It doesn't care how cool your tech is or how smart your team is.12:42 It just cares if you solve a problem with the least amount of friction possible.12:47 So the final thought for anyone listening is this: look at your business model.12:52 Find the friction.12:53 Find the person you’re depending on who isn’t your customer.12:57 That’s your point of failure.12:59 And your job isn’t to convince them.13:02 Your job is to design a new model that makes them completely irrelevant.
