अनुलिपि 🔗
WEBVTT
1
00:00:00.240 --> 00:00:05.639
Every single day, thousands of incredibly smart, capable people just
2
00:00:05.790 --> 00:00:07.690
quietly empty their savings accounts.
3
00:00:07.769 --> 00:00:09.089
Yeah, happens all the time. Right.
4
00:00:09.230 --> 00:00:10.970
And they do it to build a product that literally
5
00:00:11.029 --> 00:00:13.689
no one asked for. I mean, they sit in coffee shops,
6
00:00:13.830 --> 00:00:17.670
they sketch out logos, they hire developers to build these
7
00:00:17.829 --> 00:00:18.850
slick applications.
8
00:00:19.309 --> 00:00:21.550
And they plan these massive launch days.
9
00:00:21.730 --> 00:00:24.230
Exactly. And then when they finally push that button to
10
00:00:24.250 --> 00:00:27.949
go live to the world, there is just absolute deafening silence.
11
00:00:28.129 --> 00:00:28.660
It's brutal.
12
00:00:29.000 --> 00:00:32.520
It really is. So today we're going to deconstruct exactly
13
00:00:32.560 --> 00:00:35.500
why that happens. But more importantly, we are going out
14
00:00:35.539 --> 00:00:36.399
on a rescue mission.
15
00:00:36.740 --> 00:00:38.689
I love that. A rescue mission.
16
00:00:38.909 --> 00:00:42.189
Because whether you were an aspiring founder with a notebook
17
00:00:42.229 --> 00:00:44.630
full of dreams or maybe just someone staring at the
18
00:00:44.670 --> 00:00:48.429
ceiling at 3 a.m. convinced you have a billion dollar concept,
19
00:00:49.070 --> 00:00:50.969
our mission today is to save you from the single
20
00:00:51.049 --> 00:00:53.549
most expensive trap in entrepreneurship.
21
00:00:53.880 --> 00:00:57.310
And it is a trap. One that is particularly vicious
22
00:00:57.350 --> 00:00:59.219
because when you're caught in it, you actually feel like
23
00:00:59.229 --> 00:01:00.100
you're doing everything right.
24
00:01:00.380 --> 00:01:01.700
You feel super productive, right?
25
00:01:01.799 --> 00:01:04.879
Exactly. You're checking boxes off a list, but you are
26
00:01:04.920 --> 00:01:08.640
just building a beautifully designed mirage. Okay.
27
00:01:09.060 --> 00:01:13.010
Let's unpack this because to actually build a business, we
28
00:01:13.030 --> 00:01:16.170
have to fundamentally pivot away from that romance of the
29
00:01:16.750 --> 00:01:19.730
light bulb moment and just stare directly into the very
30
00:01:19.890 --> 00:01:21.930
unromantic reality of customer psychology.
31
00:01:22.250 --> 00:01:22.810
We really do.
32
00:01:23.680 --> 00:01:26.500
Today, we're basing our deep dive on a really tactical
33
00:01:26.540 --> 00:01:30.230
business guide called the business code from business idea to
34
00:01:30.269 --> 00:01:33.069
first customer. And I want to start by looking at
35
00:01:33.090 --> 00:01:34.709
what we'll call the idea phase.
36
00:01:34.969 --> 00:01:35.989
Right. The danger zone.
37
00:01:36.290 --> 00:01:39.590
Yeah. Why is it that the moment a concept pops
38
00:01:39.629 --> 00:01:42.870
into our heads, our first instinct is to
Load full transcript
like design
39
00:01:42.890 --> 00:01:46.019
the logo rather than just ask a stranger if they
40
00:01:46.060 --> 00:01:46.560
even care?
41
00:01:46.890 --> 00:01:49.680
Well, because the vacuum of your own mind is a
42
00:01:49.780 --> 00:01:51.819
remarkably safe space, you know?
43
00:01:52.219 --> 00:01:52.599
Oh, for sure.
44
00:01:52.980 --> 00:01:56.219
When you originate an idea, you implicitly know all the
45
00:01:56.280 --> 00:01:58.620
context behind it. Like, you know exactly what you mean
46
00:01:58.670 --> 00:02:02.629
by it. In your head, this hypothetical app has zero bugs.
47
00:02:02.890 --> 00:02:03.609
It never crashes.
48
00:02:03.709 --> 00:02:06.689
Right. It never crashes. It has no direct competitors. And
49
00:02:06.730 --> 00:02:10.870
a million people instantly understand the value proposition. You essentially
50
00:02:10.889 --> 00:02:13.310
fall in love with your own cognitive creation.
51
00:02:13.509 --> 00:02:14.569
It's intoxicating.
52
00:02:14.830 --> 00:02:16.830
It's intoxicating. It's an addictive game.
53
00:02:16.849 --> 00:02:20.750
I mean, you're basically playing a business simulator in your brain.
54
00:02:21.090 --> 00:02:23.919
Precisely. But you're playing it on easy mode with absolutely
55
00:02:24.099 --> 00:02:28.099
no external variables. The psychological disconnect happens because the founder
56
00:02:28.159 --> 00:02:33.069
assumes their internal context is universally shared. You think, well,
57
00:02:33.090 --> 00:02:35.229
I see how brilliant this is, so obviously a customer
58
00:02:35.250 --> 00:02:35.729
will see it too.
59
00:02:36.030 --> 00:02:38.110
But they don't have that context.
60
00:02:38.270 --> 00:02:41.030
No. A customer doesn't have your internal context at all.
61
00:02:41.569 --> 00:02:44.490
They are operating in a noisy, chaotic world where your
62
00:02:44.550 --> 00:02:47.819
idea is competing against thousands of other demands on their
63
00:02:47.840 --> 00:02:48.979
attention and their wallet.
64
00:02:49.360 --> 00:02:51.569
Which puts... It brings us to the harshest reality check
65
00:02:51.680 --> 00:02:55.280
any entrepreneur has to face, which is outcomes over ideas.
66
00:02:55.419 --> 00:02:57.360
Yes. The fundamental truth.
67
00:02:57.780 --> 00:03:00.360
The fundamental truth we have to operate from today is
68
00:03:00.400 --> 00:03:03.419
that customers do not buy the idea inside your head.
69
00:03:03.439 --> 00:03:06.729
I mean, they do not care about your visionary status.
70
00:03:07.349 --> 00:03:08.389
They buy a result.
71
00:03:09.370 --> 00:03:11.129
Customers are ruthlessly pragmatic.
72
00:03:11.169 --> 00:03:11.409
They are.
73
00:03:11.650 --> 00:03:14.069
They are inherently self-interested when it comes to parting with
74
00:03:14.090 --> 00:03:15.069
their capital. Right.
75
00:03:15.129 --> 00:03:18.000
They're not funding a charity for your ego. Exactly. Right.
76
00:03:18.419 --> 00:03:20.800
They are not funding your dream. They
are purchasing a
77
00:03:20.860 --> 00:03:25.370
specific relief or a specific enhancement for their own daily existence. Yeah.
78
00:03:25.689 --> 00:03:28.110
If your beautiful idea does not translate into one of
79
00:03:28.150 --> 00:03:31.250
those tangible outcomes, it is economically worthless.
80
00:03:31.569 --> 00:03:34.689
So let's get incredibly specific about what those outcomes actually are.
81
00:03:35.069 --> 00:03:38.430
We're going to dive into seven specific results that customers
82
00:03:38.629 --> 00:03:41.500
actually open their wallets for, according to the source material.
83
00:03:41.840 --> 00:03:42.960
And this list is crucial.
84
00:03:43.219 --> 00:03:46.360
It really is. If a concept doesn't demonstrably deliver at
85
00:03:46.400 --> 00:03:49.009
least one of these, it's a hobby. Not a business.
86
00:03:49.729 --> 00:03:52.849
So the first one is less stress. Now, I want
87
00:03:52.879 --> 00:03:56.680
to push on this because stress feels somewhat, you know, nebulous.
88
00:03:56.860 --> 00:03:59.199
Are we talking about selling yoga mats here or does
89
00:03:59.240 --> 00:04:01.219
this apply to B2B software?
90
00:04:01.639 --> 00:04:05.159
It applies heavily to B2B software. Actually, think of stress
91
00:04:05.240 --> 00:04:08.780
not just as emotional anxiety, but as cognitive load.
92
00:04:09.039 --> 00:04:09.879
Oh, cognitive load.
93
00:04:09.919 --> 00:04:13.580
Yeah. Okay. Decision fatigue. The mental weight of managing a
94
00:04:13.620 --> 00:04:16.879
chaotic process. When a massive company buys an enterprise resource
95
00:04:16.920 --> 00:04:20.050
planning software, They are essentially buying less stress.
96
00:04:20.269 --> 00:04:21.370
They're buying brain space.
97
00:04:21.689 --> 00:04:24.829
Right. They are paying a massive premium to offload the
98
00:04:24.870 --> 00:04:29.649
cognitive burden of, say, tracking inventory and payroll across 50
99
00:04:29.649 --> 00:04:30.410
different spreadsheets.
100
00:04:30.470 --> 00:04:31.189
That makes a lot of sense.
101
00:04:31.410 --> 00:04:34.269
If a product can tangibly reduce the number of variables
102
00:04:34.430 --> 00:04:36.810
a human being has to worry about on a Tuesday afternoon,
103
00:04:37.180 --> 00:04:39.149
that is a highly saleable result.
104
00:04:39.500 --> 00:04:41.600
So you're selling peace of mind in the form of
105
00:04:41.860 --> 00:04:45.540
operational efficiency. And that connects directly to the second result,
106
00:04:45.699 --> 00:04:47.199
which is saved time.
107
00:04:47.649 --> 00:04:51.519
Time is the ultimate non-renewable resource, right? But it's important
108
00:04:51.560 --> 00:04:54.560
to understand the actual mechanics of selling time.
109
00:04:54.800 --> 00:04:55.180
What do you mean?
110
00:04:55.759 --> 00:04:58.800
Well, you aren't just selling speed. You are selling the
111
00:04:58.920 --> 00:04:59.879
opportunity cost.
112
00:05:00.220 --> 00:05:01.259
Okay, give me an example.
113
00:05:01.939 --> 00:05:05.579
Say a meal delivery service saves a working parent 90
114
00:05:05.579 --> 00:05:08.680
minutes of grocery shopping and cooking. They aren't just buying food.
115
00:05:09.180 --> 00:05:10.800
They are buying an hour and a half to read
116
00:05:10.819 --> 00:05:13.290
to their kids. Or, honestly, an hour and a half
117
00:05:13.310 --> 00:05:15.209
to just sit in silence.
118
00:05:14.850 --> 00:05:16.870
On the couch. Yeah, that's incredibly valuable.
119
00:05:17.300 --> 00:05:20.439
The deeper the emotional value of the recovered time, the
120
00:05:20.459 --> 00:05:21.720
higher the premium you can charge.
121
00:05:22.199 --> 00:05:25.300
That makes perfect sense. You're basically buying your life back.
122
00:05:26.319 --> 00:05:30.569
So the third result is lower cost. This one feels
123
00:05:30.610 --> 00:05:32.790
a bit obvious, you know, just be cheaper than the
124
00:05:32.829 --> 00:05:36.009
other guy. But is competing purely on price just a
125
00:05:36.189 --> 00:05:36.930
race to the bottom?
126
00:05:37.410 --> 00:05:40.470
It can be. Competing on price is a dangerous game
127
00:05:40.529 --> 00:05:43.329
if your underlying cost structure is exactly the same as
128
00:05:43.370 --> 00:05:44.009
your competitors.
129
00:05:44.170 --> 00:05:46.610
Because then you just destroy your margins. Exactly.
130
00:05:47.339 --> 00:05:50.740
But if you have achieved a technological or operational breakthrough
131
00:05:50.779 --> 00:05:53.839
that allows you to deliver the exact same baseline result
132
00:05:53.879 --> 00:05:57.759
with radically lower overhead, then lower cost becomes a massive
133
00:05:57.800 --> 00:05:58.540
disruptive force.
134
00:05:58.839 --> 00:05:59.199
Like what?
135
00:05:59.720 --> 00:06:03.399
Look at early cloud computing versus maintaining on-premise servers. It
136
00:06:03.439 --> 00:06:07.550
wasn't just slightly cheaper. It fundamentally altered the financial pressure
137
00:06:07.579 --> 00:06:11.589
on startups. The customer is buying the relief of financial constraint.
138
00:06:11.990 --> 00:06:15.329
Okay, here's where it gets really interesting for me. The
139
00:06:15.350 --> 00:06:19.269
fourth result is better performance. This feels different from the
140
00:06:19.310 --> 00:06:22.759
first three. It is different. Because less stress, save time,
141
00:06:22.819 --> 00:06:27.040
lower cost. Those were all about minimizing negatives. Better performance
142
00:06:27.100 --> 00:06:29.220
is about maximizing a positive, right?
143
00:06:29.459 --> 00:06:32.860
You're tapping into the human desire for optimization and status.
144
00:06:33.379 --> 00:06:35.779
Better performance isn't about fixing something that is broken. It
145
00:06:35.980 --> 00:06:39.550
is about taking an existing capability and making it exceptional.
146
00:06:39.829 --> 00:06:41.129
Like a professional athlete.
147
00:06:41.329 --> 00:06:45.519
Exactly. This is why professional athletes
spend thousands on customized footwear.
148
00:06:46.000 --> 00:06:49.040
Or why a day trader buys a terminal that executes trades,
149
00:06:49.420 --> 00:06:51.079
you know, just milliseconds faster.
150
00:06:51.319 --> 00:06:53.439
They are purchasing a competitive advantage.
151
00:06:53.660 --> 00:06:57.329
Right. They are buying an upgraded version of their own output.
152
00:06:57.649 --> 00:07:01.050
Okay, let's look at the fifth result, which is convenience. Now,
153
00:07:01.110 --> 00:07:04.689
I want to challenge this one because isn't convenience just
154
00:07:04.750 --> 00:07:08.319
a repackaged version of save time or less stress? Do
155
00:07:08.339 --> 00:07:10.040
we really need a whole separate category for it?
156
00:07:10.379 --> 00:07:14.540
We do, actually, because the mechanism is different. Convenience is
157
00:07:14.620 --> 00:07:17.560
strictly about the removal of friction in the user journey.
158
00:07:18.100 --> 00:07:19.000
Friction. Yeah.
159
00:07:19.360 --> 00:07:21.579
You might have plenty of time to walk three blocks
160
00:07:21.620 --> 00:07:23.959
to pick up a pizza, and the walk might not
161
00:07:24.000 --> 00:07:24.879
stress you out at all.
162
00:07:25.240 --> 00:07:26.519
True. Might be a nice walk.
163
00:07:27.319 --> 00:07:29.600
But having it dropped at your door with a single
164
00:07:29.639 --> 00:07:33.040
swipe on your phone, that is convenient. Let's look at
165
00:07:33.060 --> 00:07:36.870
the modern API economy. Stripe didn't necessarily save a developer
166
00:07:36.910 --> 00:07:40.310
time in the grand scheme of a multi-year project, but
167
00:07:40.360 --> 00:07:44.040
it removed the immense friction of negotiating with banks and
168
00:07:44.120 --> 00:07:48.579
building payment gateways from scratch. People pay exorbitant premiums simply
169
00:07:48.620 --> 00:07:51.660
to reduce the number of steps between their desire and
170
00:07:51.680 --> 00:07:53.060
the fulfillment of that desire.
171
00:07:53.639 --> 00:07:57.519
So convenience is literally just the elimination of steps. I
172
00:07:57.540 --> 00:08:01.560
see that. OK, the sixth result is confidence. This is
173
00:08:01.620 --> 00:08:06.009
fascinating because it's deeply psychological. How do you package and
174
00:08:06.269 --> 00:08:07.379
sell confidence?
175
00:08:08.120 --> 00:08:11.980
You sell confidence when your customer is navigating high-stakes uncertainty.
176
00:08:12.420 --> 00:08:13.240
Okay, like when?
177
00:08:13.879 --> 00:08:17.079
Well, why do Fortune 500 companies hire management consulting firms
178
00:08:17.100 --> 00:08:20.800
like McKinsey? Is it because McKinsey has some secret spreadsheet
179
00:08:20.860 --> 00:08:21.899
formula nobody else has?
180
00:08:22.730 --> 00:08:23.389
Probably not.
181
00:08:24.189 --> 00:08:27.350
No, the CEO is buying a psychological safety net. They
182
00:08:27.389 --> 00:08:30.269
are buying the ability to tell their board of directors, hey,
183
00:08:30.529 --> 00:08:33.610
the most prestigious firm in the world vetted this strategy. Oh, wow.
184
00:08:34.100 --> 00:08:39.330
So it's CYA, cover your assets. Precisely.
185
00:08:39.759 --> 00:08:43.129
People buy premium brands, extensive warranties, and elite consultants because
186
00:08:43.149 --> 00:08:45.929
it provides the feeling of knowing they made the safe,
187
00:08:46.049 --> 00:08:46.850
defensible choice.
188
00:08:47.250 --> 00:08:49.870
They are buying an insurance policy against their own doubt.
189
00:08:50.889 --> 00:08:55.250
That's powerful. And the final of the seven results is enjoyment.
190
00:08:55.830 --> 00:09:00.750
Yeah, this is pure, unadulterated, positive experience. Entertainment, luxury, hobbies, art.
191
00:09:01.080 --> 00:09:01.820
Things we just like.
192
00:09:02.190 --> 00:09:04.929
Right. Here, the customer is not solving a negative pain
193
00:09:04.970 --> 00:09:08.009
point in the traditional sense. They are actively purchasing a
194
00:09:08.149 --> 00:09:09.370
positive emotional state.
195
00:09:10.090 --> 00:09:16.950
So we have less stress, save time, lower cost, better performance, convenience, confidence,
196
00:09:17.429 --> 00:09:23.250
and enjoyment. If I can synthesize this, falling in love
197
00:09:23.289 --> 00:09:24.909
with a business idea is kind of like falling in
198
00:09:24.929 --> 00:09:28.840
love with a highly complex architectural blueprint for a house.
199
00:09:29.039 --> 00:09:29.960
I like this analogy.
200
00:09:29.980 --> 00:09:34.309
Right. As the founder... You are staring at this blueprint
201
00:09:34.350 --> 00:09:36.970
in your office. You're obsessing over the elegant sweep of
202
00:09:37.009 --> 00:09:39.879
the staircase, the precise angle of the roof line, the
203
00:09:40.320 --> 00:09:42.340
negative space in the floor plan. You think it's an
204
00:09:42.519 --> 00:09:43.419
absolute masterpiece.
205
00:09:43.500 --> 00:09:43.919
Naturally.
206
00:09:44.620 --> 00:09:47.759
But the customer, the customer is just standing outside in
207
00:09:47.799 --> 00:09:50.960
a thunderstorm looking for a roof that doesn't leak. They
208
00:09:50.980 --> 00:09:54.490
just want the result, less stress, convenience, keeping dry. They
209
00:09:54.509 --> 00:09:57.090
do not care about the elegance of your blueprint.
210
00:09:57.990 --> 00:10:00.960
The blueprint is your internal map. Mm-hmm. The dry room
211
00:10:01.000 --> 00:10:03.259
is the customer's outcome. If you force the customer to
212
00:10:03.320 --> 00:10:05.799
care about the blueprint, they will literally walk down the
213
00:10:05.830 --> 00:10:08.129
street to someone who simply offers them an umbrella.
214
00:10:08.529 --> 00:10:11.049
So how does a founder force themselves to step away
215
00:10:11.090 --> 00:10:14.049
from the blueprint? I mean, when you are so deep
216
00:10:14.169 --> 00:10:16.250
in the vision, how do you snap out of it
217
00:10:16.309 --> 00:10:17.620
and realize it's
raining outside?
218
00:10:18.590 --> 00:10:21.850
Stepping away requires a structural change in how you interrogate
219
00:10:21.870 --> 00:10:25.149
the world. The natural instinct is to seek inward validation.
220
00:10:25.509 --> 00:10:26.429
Like asking your mom.
221
00:10:26.610 --> 00:10:29.730
Right. The founder asks themselves or their spouse, hey, is
222
00:10:29.750 --> 00:10:32.440
this a good idea? But answering that question only builds
223
00:10:32.519 --> 00:10:35.620
the mirage higher. You have to move from inward validation
224
00:10:35.700 --> 00:10:38.700
to an outward, somewhat ruthless investigation of the market.
225
00:10:38.980 --> 00:10:40.879
Which means we need to talk about the four pillars
226
00:10:40.919 --> 00:10:44.500
of problem investigation from the source material. We have to
227
00:10:44.539 --> 00:10:48.480
completely stop asking, is my idea good? and replace it
228
00:10:48.519 --> 00:10:51.730
with four critical sequential diagnostic questions.
229
00:10:52.190 --> 00:10:55.690
Yes, and treating them as a sequential diagnostic tool is vital.
230
00:10:56.230 --> 00:10:59.070
These questions are designed to dismantle your assumptions and force
231
00:10:59.090 --> 00:11:01.669
you to anchor your concept to a tangible reality.
232
00:11:01.970 --> 00:11:06.120
Let's interrogate these four pillars. Question number one, who has
233
00:11:06.159 --> 00:11:06.700
this problem?
234
00:11:07.059 --> 00:11:10.240
Notice the phrasing there. It does not ask who would
235
00:11:10.279 --> 00:11:11.159
like my product.
236
00:11:11.299 --> 00:11:12.299
Right, it's about the problem.
237
00:11:12.600 --> 00:11:16.720
It demands you identify the actual victim of the inefficiency
238
00:11:16.759 --> 00:11:20.309
you are trying to solve. If you cannot vividly, granularly
239
00:11:20.389 --> 00:11:24.080
describe the specific person or demographic that is currently suffering
240
00:11:24.279 --> 00:11:27.080
because this problem exists, the people standing in the rain,
241
00:11:27.120 --> 00:11:30.639
to use your analogy, then your entire foundation is imaginary.
242
00:11:31.019 --> 00:11:32.860
So you start by literally hunting for a victim.
243
00:11:33.120 --> 00:11:33.340
Yes.
244
00:11:33.759 --> 00:11:35.539
And once you find them, you move to the second
245
00:11:35.580 --> 00:11:38.919
diagnostic question, which is, how are they solving it today?
246
00:11:39.320 --> 00:11:42.700
This is the ultimate reality check because it forces you
247
00:11:42.740 --> 00:11:45.639
to confront the status quo. And here is a secret
248
00:11:45.720 --> 00:11:47.120
that surprises a lot of founders.
249
00:11:47.399 --> 00:11:47.679
What's that?
250
00:11:47.870 --> 00:11:52.070
Your biggest competitor is rarely a well-funded startup. Your biggest
251
00:11:52.110 --> 00:11:55.789
competitor is a hacked-together spreadsheet. It's an intern doing manual
252
00:11:55.809 --> 00:11:58.970
data entry. It's a roll of literal duct tape.
253
00:11:59.149 --> 00:12:00.090
Does the total work around?
254
00:12:00.450 --> 00:12:03.350
Exactly. If a problem is truly painful, the customer is
255
00:12:03.690 --> 00:12:05.129
already trying to solve it somehow.
256
00:12:05.649 --> 00:12:07.769
But wait, if they already have a duct tape solution,
257
00:12:07.820 --> 00:12:10.600
doesn't that mean the market is saturated? Like, shouldn't I
258
00:12:10.620 --> 00:12:12.299
look for a problem that nobody has ever tried to
259
00:12:12.340 --> 00:12:12.799
solve before?
260
00:12:13.440 --> 00:12:16.490
No, that is a very dangerous assumption. If nobody has
261
00:12:16.610 --> 00:12:18.850
ever tried to solve it, it usually means the problem
262
00:12:18.909 --> 00:12:21.549
isn't actually painful enough to warrant human effort.
263
00:12:21.789 --> 00:12:22.669
Oh, so they just don't care.
264
00:12:23.009 --> 00:12:26.450
Right. The existence of the duct tape solution is your
265
00:12:26.529 --> 00:12:28.700
proof of life. It proves the pain exists.
266
00:12:28.980 --> 00:12:29.580
Okay, I see.
267
00:12:30.340 --> 00:12:33.240
If a small business owner is staying up until 2 a.m.
268
00:12:33.679 --> 00:12:36.740
every Friday night, you know, manually copying and pasting customer
269
00:12:36.759 --> 00:12:39.759
data between two different software platforms because they don't integrate,
270
00:12:40.159 --> 00:12:41.919
that manual labor is the duct tape.
271
00:12:42.110 --> 00:12:42.610
Sounds awful.
272
00:12:43.129 --> 00:12:46.350
It's inefficient. It's miserable. But they are doing it because
273
00:12:46.389 --> 00:12:50.250
the underlying result is necessary. Your job isn't to invent
274
00:12:50.320 --> 00:12:52.759
a new problem. It's to replace the duct tape with
275
00:12:52.820 --> 00:12:53.600
a proper bridge.
276
00:12:53.840 --> 00:12:56.860
That makes a lot of sense. The hacked-together solution is
277
00:12:56.899 --> 00:13:00.139
the beacon. And that leads us to the third diagnostic question.
278
00:13:00.779 --> 00:13:04.149
What does the problem cost them in money, time, or frustration?
279
00:13:04.610 --> 00:13:08.129
You must quantify the bleeding before you can successfully sell
280
00:13:08.210 --> 00:13:13.830
the bandage. Is this disconnected software costing the business $ 10, 000
281
00:13:12.230 --> 00:13:13.309
a month in lost sales?
282
00:13:13.690 --> 00:13:15.820
Or costing the founder three hours of sleep every night?
283
00:13:16.009 --> 00:13:18.419
Exactly. You have to assign a metric to the pain.
284
00:13:18.799 --> 00:13:22.580
So what does this all mean for the concept of frustration?
285
00:13:22.600 --> 00:13:25.440
Because I really want to push back on this. I
286
00:13:25.460 --> 00:13:30.019
look at this list, money, time, frustration. If I'm an
287
00:13:30.039 --> 00:13:33.100
investor or just a founder looking at my own dwindling
288
00:13:33.139 --> 00:13:36.929
bank account, I understand the math of lost money. I
289
00:13:36.950 --> 00:13:41.490
understand the math of lost time. Sure. But frustration feels
290
00:13:41.529 --> 00:13:45.440
incredibly subjective. It feels squishy. Can you really quantify a
291
00:13:45.500 --> 00:13:48.309
bad mood enough to build a reliable business model around it?
292
00:13:49.259 --> 00:13:51.320
It is a fair pushback, but you have to look
293
00:13:51.360 --> 00:13:55.299
at the downstream effects of human psychology. Frustration in a
294
00:13:55.330 --> 00:13:59.250
vacuum is a feeling, yes. But in the theater of commerce,
295
00:13:59.769 --> 00:14:05.110
sustained frustration almost always metamorphoses into lost time or lost money.
296
00:14:05.470 --> 00:14:07.009
Okay, walk me through the mechanics of that.
297
00:14:07.340 --> 00:14:11.269
Consider a piece of highly frustrating inventory software. The interface
298
00:14:11.309 --> 00:14:14.230
is cluttered, it crashes constantly, the search function doesn't work.
299
00:14:14.809 --> 00:14:18.429
The immediate, surface-level cost is just employee frustration.
300
00:14:18.649 --> 00:14:19.830
They're just annoyed. Right.
301
00:14:20.289 --> 00:14:23.129
But what is the secondary cost? The employee slows down
302
00:14:23.169 --> 00:14:27.000
to avoid triggering a crash. They start double-checking inventory manually
303
00:14:27.059 --> 00:14:30.320
because they just don't trust the system. Morale drops, which
304
00:14:30.399 --> 00:14:31.700
leads to higher turnover.
305
00:14:31.720 --> 00:14:33.899
Oh, and replacing employees is expensive.
306
00:14:34.360 --> 00:14:39.399
Very expensive. Now that initial squishy frustration has directly translated
307
00:14:39.470 --> 00:14:43.350
into measurable lost time, lost productivity, and the hard financial
308
00:14:43.370 --> 00:14:45.450
cost of hiring and training new staff. Wow.
309
00:14:45.809 --> 00:14:46.070
Okay.
310
00:14:46.490 --> 00:14:50.649
Frustration is merely the early warning system. It's the smoke
311
00:14:50.710 --> 00:14:54.850
before the fire. If you can identify and eliminate severe frustration,
312
00:14:55.049 --> 00:14:58.190
you are inherently delivering the tangible results of less stress
313
00:14:58.350 --> 00:15:00.029
and better performance that people will pay for.
314
00:15:00.490 --> 00:15:03.929
Okay. I definitely see the causality there. The frustration creates
315
00:15:04.009 --> 00:15:07.409
the friction. And the friction creates the financial loss.
316
00:15:07.820 --> 00:15:11.019
Precisely. Which brings us to the fourth and final pillar
317
00:15:11.120 --> 00:15:14.580
of the investigation. Why might they choose a different solution?
318
00:15:14.600 --> 00:15:16.299
The tipping point. This is the.
319
00:15:16.259 --> 00:15:19.580
Catalyst for change. Even if you identify the victim, even
320
00:15:19.620 --> 00:15:21.950
if you see their duct tape solution, and even if
321
00:15:21.990 --> 00:15:24.690
you know it's costing them time and frustration, you have
322
00:15:24.710 --> 00:15:28.830
to remember that human beings have a profound gravitational pull
323
00:15:28.870 --> 00:15:29.809
toward the status quo.
324
00:15:29.929 --> 00:15:31.090
Yeah, change requires energy.
325
00:15:31.850 --> 00:15:33.809
Exactly. The devil you know is better than the devil
326
00:15:33.830 --> 00:15:34.509
you don't. Right.
327
00:15:34.879 --> 00:15:37.559
So you have to determine what specific trigger would finally
328
00:15:37.600 --> 00:15:40.279
push them over the edge to adopt your new solution.
329
00:15:40.799 --> 00:15:43.700
Is it a specific price point? Is it a sudden
330
00:15:44.000 --> 00:15:46.000
integration with a tool they already use?
331
00:15:46.639 --> 00:15:48.970
Or is it a regulatory change that forces their hand?
332
00:15:49.470 --> 00:15:52.470
You have to understand the activation energy required to break
333
00:15:52.509 --> 00:15:53.289
their current habits.
334
00:15:53.990 --> 00:15:57.110
So when we look at this entire sequence, who has
335
00:15:57.149 --> 00:15:59.809
the problem? How are they solving it today? What does
336
00:15:59.850 --> 00:16:03.080
it cost them? Why might they change? it becomes really
337
00:16:03.149 --> 00:16:06.120
clear that starting a business based on a problem is
338
00:16:06.539 --> 00:16:09.879
architecturally superior to starting based on a product description.
339
00:16:10.360 --> 00:16:12.379
It is the difference between hunting and farming.
340
00:16:12.399 --> 00:16:14.220
Ooh, I like that.
341
00:16:14.860 --> 00:16:17.039
If you start with a product description, say a beautifully
342
00:16:17.080 --> 00:16:20.399
coded app with five specific features, you have to go
343
00:16:20.460 --> 00:16:22.519
out into the wild and hunt for people who happen
344
00:16:22.559 --> 00:16:26.960
to want that exact arbitrary combination of features. It's incredibly inefficient.
345
00:16:27.320 --> 00:16:28.240
Yeah, sounds exhausting.
346
00:16:28.559 --> 00:16:31.970
But if you start problem first, You are identifying a
347
00:16:32.070 --> 00:16:34.710
unified demographic of people who are all suffering from the
348
00:16:34.830 --> 00:16:38.950
same specific pain. You understand their habits, you understand their budgets,
349
00:16:39.129 --> 00:16:43.240
and you understand their triggers. The problem organically cultivates the audience.
350
00:16:43.500 --> 00:16:45.740
Your eventual product is just the harvest.
351
00:16:46.340 --> 00:16:48.740
It's like finding a line of 50 people shivering outside
352
00:16:48.779 --> 00:16:51.299
a concert venue in the snow and then deciding to
353
00:16:51.480 --> 00:16:54.340
sell hot coffee. Rather than brewing a massive vat of
354
00:16:54.580 --> 00:16:57.899
obscure experimental herbal tea in your basement and wandering the
355
00:16:57.940 --> 00:17:00.120
streets hoping someone magically has a craving for it.
356
00:17:00.429 --> 00:17:02.549
The demand must precede the supply.
357
00:17:02.970 -->
00:17:07.039
Always. But answering these four questions is impossible to do
358
00:17:07.079 --> 00:17:09.799
in isolation. You can't just sit in a dark room
359
00:17:09.839 --> 00:17:11.960
with a whiteboard and guess who has the problem and
360
00:17:11.980 --> 00:17:14.839
what it costs them. To get these answers, you have
361
00:17:14.859 --> 00:17:15.660
to leave the vacuum.
362
00:17:16.079 --> 00:17:18.839
You have to find flesh and blood human beings. Right.
363
00:17:19.220 --> 00:17:21.849
And this is the exact moment where 90% of aspiring
364
00:17:21.880 --> 00:17:25.490
founders freeze. They would rather spend six months writing code
365
00:17:25.549 --> 00:17:28.809
than spend six minutes having an awkward conversation with a stranger.
366
00:17:29.500 --> 00:17:33.019
Which brings us to the absolute necessity of the micro-targeted customer.
367
00:17:33.660 --> 00:17:36.470
There's a massive pitfall here from the text that traps
368
00:17:36.569 --> 00:17:39.710
almost everyone. And that's the urge to sell to everybody.
369
00:17:40.130 --> 00:17:42.329
The fear of missing out drives founders to define their
370
00:17:42.369 --> 00:17:46.210
target audience as broadly as possible. They think, you know,
371
00:17:46.259 --> 00:17:48.619
if I narrow my focus, I'm leaving money on the table.
372
00:17:48.900 --> 00:17:50.140
No, that makes sense intuitively.
373
00:17:50.339 --> 00:17:53.880
But it is a fundamental misunderstanding of how initial traction works.
374
00:17:54.369 --> 00:17:57.369
Let's dissect a real example to show why broad targeting
375
00:17:57.549 --> 00:18:01.690
is a disaster. Let's say I've built a generic social
376
00:18:01.730 --> 00:18:05.859
media scheduling tool. I decide my target audience is small businesses.
377
00:18:06.539 --> 00:18:07.559
Why is that a terrible idea?
378
00:18:07.900 --> 00:18:11.960
Because a small business is an IRS tax designation, not
379
00:18:12.019 --> 00:18:13.859
a psychological profile. Oh, wow.
380
00:18:14.720 --> 00:18:15.380
That's a great point.
381
00:18:15.980 --> 00:18:18.849
A freelance wedding photographer in Austin is a small business.
382
00:18:19.509 --> 00:18:22.910
A steel manufacturing plant in Ohio with 40 employees is
383
00:18:22.950 --> 00:18:26.539
a small business. A local family-owned bakery is a small business.
384
00:18:26.559 --> 00:18:27.640
Right. They have nothing in common.
385
00:18:27.920 --> 00:18:31.859
They have entirely different cash flows, different tech literacy levels,
386
00:18:31.920 --> 00:18:36.680
different operational bottlenecks, and they speak completely different professional languages.
387
00:18:37.440 --> 00:18:39.640
If you try to craft a marketing message that appeals
388
00:18:39.700 --> 00:18:43.200
to the photographer, the factory owner, and the baker simultaneously,
389
00:18:43.720 --> 00:18:47.400
your message will become so diluted, so tragically generic, that
390
00:18:47.420 --> 00:18:49.460
it resonates with absolutely no one.
391
00:18:50.059 --> 00:18:53.470
You're trying to write a horoscope. It applies to everyone,
392
00:18:53.509 --> 00:18:54.170
so it means nothing.
393
00:18:54.470 --> 00:18:58.970
Exactly. Consider the alternative. What if instead of small businesses,
394
00:18:59.069 --> 00:19:04.150
you hyper-target your audience to independent, single-location cafes that struggle
395
00:19:04.190 --> 00:19:06.119
to create Instagram content every week?
396
00:19:06.440 --> 00:19:09.380
Okay, let's play this out. Because if I'm targeting those cafes,
397
00:19:09.759 --> 00:19:14.140
isn't my total addressable market tiny? Aren't I artificially capping
398
00:19:14.160 --> 00:19:16.400
my growth before I even start? If I just target
399
00:19:16.440 --> 00:19:19.630
cafes in my city, how does this ever become a
400
00:19:19.640 --> 00:19:20.069
real company?
401
00:19:20.619 --> 00:19:23.319
You are confusing the starting line with the finish line.
402
00:19:23.920 --> 00:19:27.480
Amazon did not start by selling everything from cloud computing
403
00:19:27.619 --> 00:19:31.380
infrastructure to groceries. They started by selling books to people
404
00:19:31.420 --> 00:19:32.240
who read books.
405
00:19:33.119 --> 00:19:35.430
And Facebook started with just Harvard undergrads.
406
00:19:35.589 --> 00:19:40.130
Exactly. Narrowing the focus at the beginning is a tactical superpower.
407
00:19:40.450 --> 00:19:44.349
It makes the abstract problem highly tangible. You know exactly
408
00:19:44.410 --> 00:19:47.269
where these cafe owners physically exist. You can walk into
409
00:19:47.309 --> 00:19:47.809
their shops.
410
00:19:48.309 --> 00:19:50.880
You can look at their Instagram feeds and immediately... diagnose
411
00:19:50.920 --> 00:19:52.039
if they have the problem.
412
00:19:52.559 --> 00:19:58.130
Right. By being hyper-specific, you can adopt their exact vocabulary.
413
00:19:58.589 --> 00:20:02.390
You understand their specific margin pressures. And your solution feels
414
00:20:02.430 --> 00:20:05.950
custom-built for their reality, not like some generic software tool
415
00:20:05.990 --> 00:20:08.069
they have to force-fit into their workflows.
416
00:20:08.640 --> 00:20:11.920
You become a specialist instead of a general practitioner. And
417
00:20:12.180 --> 00:20:13.480
people pay more for specialists.
418
00:20:13.819 --> 00:20:14.460
They really do.
419
00:20:15.400 --> 00:20:18.440
So once we have this micro-targeted profile, the cafe owner,
420
00:20:19.279 --> 00:20:23.119
we have to employ a strategy of interrogation. We need
421
00:20:23.140 --> 00:20:26.220
to find five to ten of these exact people and
422
00:20:26.259 --> 00:20:29.980
have conversations with them. But these aren't casual chats over coffee.
423
00:20:30.079 --> 00:20:31.279
No, not at all.
424
00:20:31.819 --> 00:20:34.759
The text gives us four specific interview questions that are
425
00:20:34.819 --> 00:20:38.220
engineered to bypass standard
human behavior. Let's break these down
426
00:20:38.279 --> 00:20:40.400
because this is where the real data lives.
427
00:20:40.559 --> 00:20:43.119
The design of these questions is crucial because humans are
428
00:20:43.160 --> 00:20:46.420
incredibly unreliable narrators of their own future behavior.
429
00:20:46.640 --> 00:20:47.960
Yeah, we lie to ourselves all the time.
430
00:20:47.980 --> 00:20:50.440
We do. So the first question you ask the coffee
431
00:20:50.500 --> 00:20:53.509
owner is, tell me about the last time this problem happened.
432
00:20:54.190 --> 00:20:56.369
Now, why are we focusing on the last time? Why
433
00:20:56.410 --> 00:20:59.349
not just ask a direct, simple question like, hey, is
434
00:20:59.390 --> 00:21:00.829
managing social media a problem for you?
435
00:21:01.470 --> 00:21:05.690
Because asking, is this a problem, invites a hypothetical, generalized,
436
00:21:05.809 --> 00:21:08.750
often polite answer. They will sigh and say, oh, yeah,
437
00:21:09.049 --> 00:21:10.490
social media is a real headache.
438
00:21:10.930 --> 00:21:11.730
Which gives you nothing.
439
00:21:12.170 --> 00:21:15.980
Absolutely zero usable data. By anchoring the question with the
440
00:21:16.059 --> 00:21:20.380
last time, you force their brain to retrieve a specific, concrete,
441
00:21:20.539 --> 00:21:23.579
episodic memory. You move the conversation out of the realm
442
00:21:23.640 --> 00:21:26.359
of vague feelings and into forensic reality.
443
00:21:26.779 --> 00:21:29.819
You're forcing them to testify about an event. Like, where
444
00:21:29.859 --> 00:21:31.440
were you on the night of the 14th when you
445
00:21:31.460 --> 00:21:32.500
tried to post to Instagram?
446
00:21:32.700 --> 00:21:36.240
Exactly. You want the details. And the second question immediately follows.
447
00:21:36.900 --> 00:21:37.950
What did you do to solve it?
448
00:21:38.519 --> 00:21:39.960
We are hunting for the duct tape again.
449
00:21:40.200 --> 00:21:43.970
We are looking for evidence of kinetic energy. If you
450
00:21:44.069 --> 00:21:46.269
ask what they did to solve it and they reply, well,
451
00:21:46.430 --> 00:21:48.529
I got overwhelmed so I just didn't post anything for
452
00:21:48.569 --> 00:21:51.630
two weeks, that is a massive red flag for your
453
00:21:51.650 --> 00:21:52.269
business idea.
454
00:21:52.750 --> 00:21:53.890
Because it means they don't care enough.
455
00:21:54.309 --> 00:21:57.250
It tells you that while the problem is annoying, it
456
00:21:57.309 --> 00:22:00.630
is not painful enough to prompt action. But if they say,
457
00:22:01.369 --> 00:22:04.130
I stayed after closing, bought a subscription to Canva, and
458
00:22:04.170 --> 00:22:07.559
spent four hours trying to design a promo graphic. You
459
00:22:07.619 --> 00:22:11.059
now have undeniable proof of severe friction and effort.
460
00:22:11.279 --> 00:22:14.000
Proof of life. So then we ask the third question.
461
00:22:14.680 --> 00:22:17.359
What was frustrating or expensive about that process?
462
00:22:18.000 --> 00:22:20.980
You are handing them a microphone to complain, and you
463
00:22:21.039 --> 00:22:24.400
are mining their response for your future marketing copy. You
464
00:22:24.440 --> 00:22:27.559
need to capture the exact vernacular they used to describe
465
00:22:27.579 --> 00:22:28.079
their suffering.
466
00:22:28.579 --> 00:22:30.549
Ah, so you can use their own words back to
467
00:22:30.589 --> 00:22:30.960
them later.
468
00:22:31.289 --> 00:22:35.230
Exactly. If they say, it took four hours that I
469
00:22:35.250 --> 00:22:38.109
should have spent reconciling the register, and the graphics still
470
00:22:38.130 --> 00:22:42.440
looked amateur, you write that down verbatim. You're extracting the
471
00:22:42.539 --> 00:22:46.759
quantified cost, in this case four hours and damaged brand perception,
472
00:22:47.160 --> 00:22:48.299
directly from the source.
473
00:22:48.859 --> 00:22:52.240
And the final diagnostic question is the acid test. Have
474
00:22:52.259 --> 00:22:53.759
you paid for a solution before?
475
00:22:54.579 --> 00:22:59.009
This separates the minor inconveniences from the commercial opportunities. If
476
00:22:59.029 --> 00:23:00.930
they have paid for a solution in the past, even
477
00:23:00.990 --> 00:23:03.769
if it was a catastrophic failure, like paying a local
478
00:23:03.829 --> 00:23:07.589
college kid $ 500 a month who ended up posting inappropriate memes,
479
00:23:08.190 --> 00:23:11.849
it proves that there is actual capital allocated in their
480
00:23:11.869 --> 00:23:13.170
brain to solve this pain.
481
00:23:13.710 --> 00:23:14.769
It proves the wallet can open.
482
00:23:15.410 --> 00:23:17.730
What's fascinating here is that it relies on the most
483
00:23:18.039 --> 00:23:22.119
fundamental principle of behavioral economics, which is that past behavior
484
00:23:22.519 --> 00:23:24.819
is the only reliable predictor of future behavior.
485
00:23:25.180 --> 00:23:26.960
We have to talk about why this is so critical.
486
00:23:27.549 --> 00:23:31.009
because it touches on the psychology of polite validation. I
487
00:23:31.029 --> 00:23:33.799
think this is a concept often called the mom test.
488
00:23:34.480 --> 00:23:39.019
It completely blindsides founders. We have a natural human inclination
489
00:23:39.079 --> 00:23:39.880
to be empathetic.
490
00:23:40.059 --> 00:23:43.859
We do. We are socially conditioned to avoid conflict. We
491
00:23:43.880 --> 00:23:46.509
don't like telling people their babies are ugly, and we
492
00:23:46.549 --> 00:23:50.150
don't like telling excited founders their ideas are terrible. Right.
493
00:23:50.549 --> 00:23:52.430
If I burst into a coffee shop, run up to
494
00:23:52.450 --> 00:23:55.150
a stranger and say, Hey, I've quit my job to
495
00:23:55.190 --> 00:23:58.029
build this revolutionary app that uses AI to schedule your tweets.
496
00:23:58.970 --> 00:24:01.809
Isn't that amazing? They are going to look at my
497
00:24:01.869 --> 00:24:06.509
crazy eyes and say, wow, yeah, that sounds awesome. I'd
498
00:24:06.569 --> 00:24:07.250
totally use that.
499
00:24:07.529 --> 00:24:11.579
And you will take that polite, conflict-avoidant validation, go home,
500
00:24:12.059 --> 00:24:14.539
and spend $ 50, 000 building the app.
501
00:24:14.940 --> 00:24:15.720
And no one buys it.
502
00:24:15.940 --> 00:24:18.660
When you launch, that stranger will absolutely not buy it.
503
00:24:19.470 --> 00:24:23.670
Polite validation is functionally worse than useless. It is actively
504
00:24:23.730 --> 00:24:26.910
destructive data. A promise to buy something in the future
505
00:24:27.009 --> 00:24:30.210
is a polite fiction. A detailed description of how they
506
00:24:30.250 --> 00:24:33.069
spent money last Tuesday to fix a problem is hard,
507
00:24:33.190 --> 00:24:34.390
empirical fact.
508
00:24:34.759 --> 00:24:36.759
But I need to challenge the mechanics of this interview
509
00:24:36.799 --> 00:24:39.640
process for a second. We're talking about interviewing five to
510
00:24:39.700 --> 00:24:43.079
ten people. Let's put our statistician hats on.
511
00:24:43.259 --> 00:24:43.519
Okay.
512
00:24:44.019 --> 00:24:47.279
If I'm going to risk my livelihood... max out credit
513
00:24:47.299 --> 00:24:49.920
cards and dedicate years of my life to a project,
514
00:24:50.839 --> 00:24:54.849
is a sample size of five people statistically significant? Shouldn't
515
00:24:54.869 --> 00:24:58.549
I be running like a quantitative survey with thousands of
516
00:24:58.609 --> 00:25:00.329
respondents to find a true market trend?
517
00:25:00.650 --> 00:25:02.950
It's a natural fear, but you have to understand the
518
00:25:02.990 --> 00:25:07.910
difference between quantitative validation and qualitative discovery. The goal at
519
00:25:07.950 --> 00:25:12.089
this fragile stage is not to achieve statistical perfection. You
520
00:25:12.119 --> 00:25:15.170
are not writing a peer-reviewed paper on macroeconomic trends. You
521
00:25:15.430 --> 00:25:17.630
are trying to establish a binary baseline.
522
00:25:18.210 --> 00:25:20.089
Does any organic demand exist?
523
00:25:20.450 --> 00:25:23.430
Demand, yes or no. Look at the depth of the data.
524
00:25:23.890 --> 00:25:26.039
If you blast a survey to 1,000 people, you get
525
00:25:26.190 --> 00:25:29.700
shallow hypothetical clicks. But if you sit down with 10
526
00:25:29.700 --> 00:25:34.039
highly targeted identical cafe owners and 8 of them describe
527
00:25:34.059 --> 00:25:38.799
the exact same pain point using the identical frustrated vocabulary,
528
00:25:39.119 --> 00:25:41.339
and three of them confessed they recently wasted money on
529
00:25:41.359 --> 00:25:45.660
a terrible agency. That is a profoundly dense cluster of signal.
530
00:25:45.980 --> 00:25:48.069
It's like a localized heat map of demand.
531
00:25:48.240 --> 00:25:52.210
Exactly. Conversely, if you have five deep conversations and discover
532
00:25:52.230 --> 00:25:54.430
that none of them actually care about social media, you
533
00:25:54.450 --> 00:25:58.049
just saved yourself a year of wasted engineering. Five deep
534
00:25:58.289 --> 00:26:02.470
behavioral interrogations are vastly superior to a thousand shallow survey
535
00:26:02.529 --> 00:26:05.619
responses because you can probe the why behind their actions
536
00:26:05.650 --> 00:26:08.279
in real time. You can Ask follow-up questions. You can
537
00:26:08.380 --> 00:26:10.579
observe their body language when they talk about the pain.
538
00:26:11.099 --> 00:26:13.680
You're not looking for a guarantee of a billion-dollar market yet.
539
00:26:14.049 --> 00:26:16.680
You're just checking to make sure you aren't completely hallucinating.
540
00:26:16.849 --> 00:26:18.430
You are avoiding total blindness.
541
00:26:19.250 --> 00:26:22.230
Okay, let's say I've done the scary part. I've pounded
542
00:26:22.250 --> 00:26:25.430
the pavement. I've had the five conversations. I've verified the
543
00:26:25.470 --> 00:26:28.210
problem exists. The pain is real, and they have budget
544
00:26:28.230 --> 00:26:32.250
for it. The immediate overwhelming instinct for any visionary founder
545
00:26:32.269 --> 00:26:34.589
at this point is to sprint back to the safety
546
00:26:34.609 --> 00:26:37.420
of the blueprints. Lock the door and spend six months
547
00:26:37.460 --> 00:26:40.980
building the ultimate fully featured software platform to save these
548
00:26:41.039 --> 00:26:41.720
cafe owners.
549
00:26:42.140 --> 00:26:45.819
Which would be the second fatal mistake of the entrepreneurial journey.
550
00:26:46.500 --> 00:26:49.119
Because the rule is you do not build the final product.
551
00:26:49.640 --> 00:26:51.980
You build a test. We are entering the realm of
552
00:26:52.039 --> 00:26:53.869
the minimum viable offer.
553
00:26:54.220 --> 00:26:57.970
Yes. The architecture of a small test requires an entirely
554
00:26:58.009 --> 00:27:01.410
different mindset than a business launch. The rule is draconian.
555
00:27:01.779 --> 00:27:05.039
Your first version does not need every feature. It does
556
00:27:05.140 --> 00:27:07.740
not need to scale. It only needs to deliver one
557
00:27:08.019 --> 00:27:11.720
specific useful outcome to one specific type of customer.
558
00:27:12.019 --> 00:27:14.980
I can feel the collective blood pressure of every visionary
559
00:27:15.059 --> 00:27:16.259
listening right now spiking.
560
00:27:16.460 --> 00:27:17.160
I know, it's hard.
561
00:27:17.519 --> 00:27:19.960
It is agonizing to be told to build something tiny
562
00:27:20.000 --> 00:27:22.720
when you see the grand vision. You want to unveil
563
00:27:22.759 --> 00:27:25.779
the Sistine Chapel, and this process is telling you to
564
00:27:25.839 --> 00:27:28.039
just paint a stick figure on a napkin to see
565
00:27:28.059 --> 00:27:29.099
if people like the
color blue.
566
00:27:29.569 --> 00:27:30.869
It attacks the ego directly.
567
00:27:31.130 --> 00:27:33.720
But the test is purely diagnostic. You are just trying
568
00:27:33.740 --> 00:27:36.099
to prove they want to take the first step. Let's
569
00:27:36.140 --> 00:27:39.019
explore the five specific formats these small tests can take.
570
00:27:39.619 --> 00:27:42.900
Because visualizing these really helps bridge the gap between theory
571
00:27:42.940 --> 00:27:45.619
and reality. The first one from the text was a
572
00:27:45.789 --> 00:27:46.960
one-week service pilot.
573
00:27:47.349 --> 00:27:52.730
Right. Imagine you've developed a comprehensive 12-month corporate training methodology
574
00:27:52.769 --> 00:27:54.890
that you want to sell to HR departments for $ 50, 000.
575
00:27:54.769 --> 00:27:55.190
A big-ticket item.
576
00:27:55.210 --> 00:27:55.329
Huge.
577
00:27:58.339 --> 00:28:00.720
You do not start by trying to sell the 12-month contract.
578
00:28:01.279 --> 00:28:03.900
You offer to take one single team for five days
579
00:28:04.319 --> 00:28:07.890
and solve one specific communication bottleneck for a fraction of
580
00:28:07.910 --> 00:28:10.970
the cost. It radically lowers the risk for the buyer,
581
00:28:11.109 --> 00:28:14.250
but more importantly, it proves to you if your methodology
582
00:28:14.430 --> 00:28:16.230
actually survives contact with the real world.
583
00:28:16.529 --> 00:28:19.390
Okay, the second test format is a simple landing page
584
00:28:19.410 --> 00:28:20.150
with a booking form.
585
00:28:21.079 --> 00:28:24.519
This is the purest test of value proposition. Before you
586
00:28:24.539 --> 00:28:28.609
spend thousands on complex, automated scheduling and routing software for
587
00:28:28.640 --> 00:28:31.289
a new service, you just build a single web page.
588
00:28:31.609 --> 00:28:34.210
It clearly states what you do, who it's for, and
589
00:28:34.230 --> 00:28:36.509
the price. And there is a button that says Book Now.
590
00:28:36.970 --> 00:28:37.670
And if they click it?
591
00:28:38.029 --> 00:28:40.210
If someone clicks it, the request just goes to your
592
00:28:40.269 --> 00:28:43.720
personal email inbox, and you manually call them to schedule it.
593
00:28:44.019 --> 00:28:48.059
You're just faking the backend. Which ties into the third example,
594
00:28:48.380 --> 00:28:49.420
a sample product.
595
00:28:50.700 --> 00:28:53.660
If you are in the physical grid space... Let's say
596
00:28:53.700 --> 00:28:57.529
you've designed a revolutionary ergonomic computer mouse. You do not
597
00:28:57.569 --> 00:29:00.789
go to a manufacturer in Shenzhen and order 10,000 units
598
00:29:00.890 --> 00:29:01.829
to get a bulk discount.
599
00:29:02.250 --> 00:29:04.049
No, you'd be stuck with a garage full of mice.
600
00:29:04.549 --> 00:29:08.009
Right. You go to a local makerspace. You 3D print
601
00:29:08.170 --> 00:29:11.509
five prototypes. You handwire the components. And you see if
602
00:29:11.630 --> 00:29:14.390
anyone at a local co-working space will actually hand you
603
00:29:14.410 --> 00:29:17.390
cash for the ugly prototype because the ergonomics are just
604
00:29:17.410 --> 00:29:18.329
that good. Nope.
605
00:29:18.740 --> 00:29:20.480
The fourth example is the one I want to spend
606
00:29:20.519 --> 00:29:22.880
significant time on because I think it is the most
607
00:29:22.940 --> 00:29:27.240
conceptually difficult for tech founders to grasp. The manual version
608
00:29:27.440 --> 00:29:31.990
of a digital service. How does a founder manually simulate
609
00:29:32.170 --> 00:29:34.430
what a massive software stack might eventually do?
610
00:29:35.410 --> 00:29:38.410
This is the ultimate crucible for testing value over features.
611
00:29:39.329 --> 00:29:42.640
Let's role play this. scenario. Let's say your grand vision
612
00:29:42.880 --> 00:29:47.440
is a sophisticated AI driven application. Users scan their grocery
613
00:29:47.480 --> 00:29:51.089
store receipts. The AI cross references the items against local
614
00:29:51.130 --> 00:29:56.190
supermarket weekly sales data and instantly generates a highly optimized
615
00:29:56.369 --> 00:29:58.450
budget friendly meal plan for a family of four.
616
00:29:59.079 --> 00:30:03.349
Okay, that sounds like a legitimate venture-backed startup. Building that
617
00:30:03.390 --> 00:30:07.890
requires machine learning engineers, optical character recognition for the receipts,
618
00:30:08.529 --> 00:30:11.470
API integrations with hundreds of grocery chains. I mean, we're
619
00:30:11.490 --> 00:30:13.849
talking about a million-dollar seed round and nine months of
620
00:30:13.890 --> 00:30:15.079
development just to build a beta.
621
00:30:15.339 --> 00:30:20.079
Exactly. It's a massive, heavy, risky lift. So how do
622
00:30:20.099 --> 00:30:23.400
we build a manual test? Right. How? You do not
623
00:30:23.440 --> 00:30:26.099
write a single line of code. You build a landing
624
00:30:26.119 --> 00:30:28.890
page that makes the promise... Upload a photo of your
625
00:30:28.930 --> 00:30:31.930
grocery receipt, and within 24 hours, I will email you
626
00:30:31.970 --> 00:30:35.069
a custom, budget-friendly meal plan for $ 5.
627
00:30:34.769 --> 00:30:38.410
Okay, so a customer pays the $ 5 and uploads the photo.
628
00:30:38.799 --> 00:30:39.690
What happens on the back end?
629
00:30:40.170 --> 00:30:40.779
Nothing happens.
630
00:30:41.200 --> 00:30:41.440
Nothing?
631
00:30:42.039 --> 00:30:45.039
There is no AI. There is no algorithm. There is
632
00:30:45.079 --> 00:30:47.940
just you, the founder, sitting at your kitchen table at
633
00:30:47.940 --> 00:30:51.500
2 a.m. in your sweatpants. You receive the email with
634
00:30:51.519 --> 00:30:54.380
the photo of the receipt. You open a blank Google spreadsheet.
635
00:30:55.130 --> 00:30:58.160
You manually search the local grocery store flyers online, use
636
00:30:58.200 -->
00:31:01.940
a calculator. You spend 45 minutes manually typing out a
637
00:31:01.960 --> 00:31:04.200
meal plan, and you email it back to the customer.
638
00:31:04.680 --> 00:31:09.430
Wow. I am literally the supercomputer. I am simulating the
639
00:31:09.549 --> 00:31:11.529
AI with sheer brute force human labor.
640
00:31:11.730 --> 00:31:16.230
You are the algorithm. Because remember, the absolute core rule,
641
00:31:16.869 --> 00:31:19.109
the customer does not care about your tech stack.
642
00:31:19.170 --> 00:31:19.650
They really don't.
643
00:31:19.869 --> 00:31:22.279
They do not care if a neural network or a
644
00:31:22.319 --> 00:31:25.630
human in sweatpants generated the meal plan. They only care
645
00:31:25.670 --> 00:31:27.990
about the result. Did you save them time, lower their
646
00:31:28.009 --> 00:31:29.630
grocery cost, and reduce their stress?
647
00:31:29.769 --> 00:31:32.390
Here's where it gets really interesting for me. Think about
648
00:31:32.410 --> 00:31:34.990
the implications of this. It's kind of like testing a
649
00:31:35.049 --> 00:31:38.390
pharmaceutical drug, you know? You don't secure loans to build
650
00:31:38.430 --> 00:31:41.950
a massive $ 500 million manufacturing plant to mass produce a
651
00:31:41.970 --> 00:31:44.799
pill before you even know if the chemical compound cures
652
00:31:44.839 --> 00:31:46.599
the disease in a tiny Petri dish.
653
00:31:46.730 --> 00:31:47.700
That's a great way to look at it.
654
00:31:48.119 --> 00:31:51.099
The manual kitchen table service is the Petri dish. You're
655
00:31:51.119 --> 00:31:52.440
just dipping a toe in the water.
656
00:31:52.920 --> 00:31:57.450
That is the perfect... mechanism to understand it. If you
657
00:31:57.490 --> 00:31:59.829
launch the landing page and not a single person is
658
00:31:59.869 --> 00:32:02.630
willing to pay $ 5 for the manual meal plan, you
659
00:32:02.670 --> 00:32:05.589
have just saved yourself a million dollars in wasted engineering.
660
00:32:05.849 --> 00:32:07.609
The underlying demand does not exist.
661
00:32:07.849 --> 00:32:09.329
But if they do want it.
662
00:32:09.349 --> 00:32:12.289
But if you suddenly have 50 people a day sending
663
00:32:12.309 --> 00:32:15.230
you receipts and you are drowning in manual labor and
664
00:32:15.329 --> 00:32:17.359
crying at your kitchen table because you can't keep up,
665
00:32:17.950 --> 00:32:20.460
now you have proven the demand. Now you have the
666
00:32:20.500 --> 00:32:23.039
hard data to justify raising capital to build the software
667
00:32:23.059 --> 00:32:26.390
to automate the process. Automate success, you don't build software to.
668
00:32:26.390 --> 00:32:31.150
Guess at it. That is simultaneously incredibly liberating and deeply
669
00:32:31.190 --> 00:32:35.230
terrifying for a founder. Which leads to the final test format,
670
00:32:35.549 --> 00:32:37.230
a small paid workshop.
671
00:32:38.170 --> 00:32:40.619
Instead of isolating yourself for a year to write a
672
00:32:40.630 --> 00:32:45.119
300-page book or record a highly produced 50-hour online masterclass,
673
00:32:45.660 --> 00:32:48.700
you charge $ 20 for a live two-hour Zoom call where
674
00:32:48.720 --> 00:32:51.299
you teach the core thesis. If no one buys a
675
00:32:51.299 --> 00:32:53.730
ticket to the Zoom call... You know the topic isn't
676
00:32:53.789 --> 00:32:55.250
compelling enough to sustain a book.
677
00:32:55.950 --> 00:32:59.670
So we have the formats for the tests. But the
678
00:32:59.710 --> 00:33:02.940
text says we have to set strict, non-negotiable boundaries on
679
00:33:02.960 --> 00:33:07.680
these experiments. A test needs a short deadline, a small budget,
680
00:33:08.220 --> 00:33:11.619
and exactly one result to measure. Why are these constraints
681
00:33:11.640 --> 00:33:12.099
so vital?
682
00:33:12.960 --> 00:33:16.329
The rationale is operational discipline. The goal of this phase
683
00:33:16.390 --> 00:33:19.990
is not to look like a large, established, sophisticated company.
684
00:33:20.490 --> 00:33:23.670
The goal is purely diagnostic. If you don't enforce a
685
00:33:23.710 --> 00:33:28.240
short deadline, say seven days, a simple test will inevitably
686
00:33:28.319 --> 00:33:31.059
succumb to scope creep and bleed into a six-month project.
687
00:33:31.240 --> 00:33:32.980
Right, you'll just keep tinkering with it. Exactly.
688
00:33:33.599 --> 00:33:36.779
If you don't set a microscopic budget, you risk financial
689
00:33:36.819 --> 00:33:41.019
ruin on an unproven concept. And crucially, if you don't
690
00:33:41.160 --> 00:33:44.390
isolate exactly one result to measure, like did they click
691
00:33:44.410 --> 00:33:47.549
the buy button, the data becomes muddy. If you change
692
00:33:47.630 --> 00:33:50.549
the price, the packaging, and the target audience all at once,
693
00:33:50.690 --> 00:33:52.950
and the test fails... You won't know why it failed.
694
00:33:53.630 --> 00:33:55.890
We need to talk about the human element here, the
695
00:33:55.970 --> 00:33:59.599
psychology of the founder executing this. How does someone suppress
696
00:33:59.619 --> 00:34:02.920
their ego enough to present a messy, manual Wizard of
697
00:34:03.039 --> 00:34:06.019
Oz version to the public? If I view myself as
698
00:34:06.059 --> 00:34:09.159
the next Steve Jobs, putting out an ugly landing page
699
00:34:09.219 --> 00:34:14.579
where I'm manually typing spreadsheets feels incredibly vulnerable. It feels amateurish.
700
00:34:14.900 --> 00:34:19.070
It is deeply vulnerable. It is a direct assault on
701
00:34:19.090 --> 00:34:22.860
the founder's ego. The ego desperately wants to be perceived
702
00:34:22.920 --> 00:34:27.699
as professional, polished, and infallible. Running a manual test requires
703
00:34:27.739 --> 00:34:31.500
you to be scrappy, transparent, and willing to be judged
704
00:34:31.599 --> 00:34:34.800
on a rudimentary, unpolished version of your
grand vision.
705
00:34:35.199 --> 00:34:38.150
So how do you actually override that ego? Because knowing
706
00:34:38.190 --> 00:34:40.070
you should do it and actually doing it are very
707
00:34:40.130 --> 00:34:40.650
different things.
708
00:34:41.369 --> 00:34:44.449
You have to fundamentally realign your internal metric for what
709
00:34:44.489 --> 00:34:45.289
constitutes a win.
710
00:34:45.389 --> 00:34:45.829
Okay, how?
711
00:34:46.730 --> 00:34:48.989
If your definition of a win is, strangers on the
712
00:34:49.030 --> 00:34:51.469
internet think I am a genius and my brand aesthetic
713
00:34:51.510 --> 00:34:54.730
is flawless, you will never launch the test. But if
714
00:34:54.750 --> 00:34:58.389
you shift your definition of a win to, I acquired accurate,
715
00:34:58.530 --> 00:35:02.269
hard behavioral data about customer demand for the lowest possible cost,
716
00:35:02.829 --> 00:35:05.800
then running a scrappy manual test becomes a point of
717
00:35:05.929 --> 00:35:09.260
immense pride. You are no longer failing to look professional.
718
00:35:09.420 --> 00:35:13.019
You are succeeding at being an intelligent, risk-mitigating scientist.
719
00:35:13.519 --> 00:35:17.059
You transition your identity from a showman... to an investigator.
720
00:35:18.039 --> 00:35:21.380
But even as an investigator, your communication has to be clear,
721
00:35:21.920 --> 00:35:25.400
which is why we need to discuss crafting the irresistible proposition.
722
00:35:26.539 --> 00:35:29.280
Having a brilliant small test is entirely useless if you
723
00:35:29.300 --> 00:35:31.239
cannot articulate it to the customer in a way that
724
00:35:31.260 --> 00:35:31.960
makes them care.
725
00:35:32.699 --> 00:35:35.460
If the offer is confusing, the customer will simply walk away.
726
00:35:35.880 --> 00:35:38.099
And the tragedy is you won't know if they rejected
727
00:35:38.139 --> 00:35:41.000
your core idea or if they just didn't understand your pitch.
728
00:35:41.440 --> 00:35:43.079
Ambiguity corrupts the data.
729
00:35:43.860 --> 00:35:47.030
Let's look at the framework for clarity. A useful offer
730
00:35:47.070 --> 00:35:51.329
must answer four very specific questions immediately. One, who is
731
00:35:51.369 --> 00:35:56.159
it for? Two, what problem does it solve? Three, what
732
00:35:56.199 --> 00:35:59.460
result does the customer get? And four, what should the
733
00:35:59.500 --> 00:36:00.280
customer do next?
734
00:36:01.019 --> 00:36:03.719
If your pitch is missing even one of those four elements,
735
00:36:03.960 --> 00:36:06.500
a cognitive gap opens up and the customer will fall
736
00:36:06.559 --> 00:36:07.380
through that gap.
737
00:36:08.460 --> 00:36:11.590
To ensure no one falls through, the source material gives
738
00:36:11.650 --> 00:36:16.070
us a highly specific fill-in-the-blank syntax. I love this formula
739
00:36:16.090 --> 00:36:19.989
because it violently strips away all the flowery, meaningless marketing jargon.
740
00:36:20.789 --> 00:36:26.530
The formula is, I help blank achieve blank without blank.
741
00:36:27.349 --> 00:36:29.030
It's so simple, but so effective.
742
00:36:29.750 --> 00:36:32.710
Let's bring back our cafe owner and deeply deconstruct the
743
00:36:32.730 --> 00:36:36.150
pitch through this lens. The pitch is, I help independent
744
00:36:36.170 --> 00:36:39.469
cafes plan a week of social media posts in one
745
00:36:39.489 --> 00:36:41.780
hour without hiring a full-time marketer.
746
00:36:42.519 --> 00:36:46.449
That single sentence is an absolute masterclass in psychological alignment.
747
00:36:47.010 --> 00:36:50.750
Let's break down why it is so effective. First, I
748
00:36:50.829 --> 00:36:54.170
help independent cafes. That answers the who is it for
749
00:36:54.230 --> 00:36:57.349
question instantly. If I own a hardware store, I stop reading.
750
00:36:57.610 --> 00:37:00.829
If I own an independent cafe, my reticular activating system
751
00:37:00.949 --> 00:37:04.510
fires and my ears perk up. You have captured targeted attention.
752
00:37:05.269 --> 00:37:08.989
Next part is the result. Plan a week of social
753
00:37:09.030 --> 00:37:10.469
media posts in one hour.
754
00:37:11.309 --> 00:37:14.110
This is the specific result. And notice how it maps
755
00:37:14.150 --> 00:37:16.550
directly back to the seven core outcomes we discussed at
756
00:37:16.570 --> 00:37:19.760
the very beginning. What are they actually buying here? They
757
00:37:19.800 --> 00:37:23.340
are buying saved time, compressing a week of anxiety into
758
00:37:23.380 --> 00:37:27.019
one hour. And they are buying less stress. The chronic
759
00:37:27.099 --> 00:37:30.340
nagging worry of what to post is eliminated. It is
760
00:37:30.400 --> 00:37:32.519
a highly tangible, measurable outcome.
761
00:37:33.199 --> 00:37:36.019
And the final clause, without hiring a full-time marketer.
762
00:37:36.599 --> 00:37:39.300
This is where you address the common frustration or the
763
00:37:39.360 --> 00:37:43.570
fear to alternative cost. It directly attacks the duct tape solution.
764
00:37:44.070 --> 00:37:46.869
The cafe owner knows they need social media presence, but
765
00:37:46.909 --> 00:37:50.989
they dread the financial and operational complexity of hiring an employee.
766
00:37:51.849 --> 00:37:55.699
By explicitly stating that your solution bypasses that specific friction,
767
00:37:55.840 --> 00:37:58.539
you are selling lower cost and convenience.
768
00:37:59.199 --> 00:38:01.980
It's all delivered in a single breath. But making the
769
00:38:02.019 --> 00:38:04.820
promise is only half the battle, right? You have to
770
00:38:04.860 --> 00:38:08.360
make the execution of the promise feel safe. There are
771
00:38:08.400 --> 00:38:10.650
rules of engagement to follow this up. You have to
772
00:38:10.710 --> 00:38:16.239
provide relentless clarity about exactly what is included, the exact price,
773
00:38:16.800 -->
00:38:20.039
the timeline, and the specific sequence of events that will
774
00:38:20.079 --> 00:38:21.579
happen the moment they say yes.
775
00:38:22.440 --> 00:38:26.460
This is about managing expectations and systematically removing perceived risk.
776
00:38:27.260 --> 00:38:31.969
If your fill-in-the-blank sentence hooks their attention, this relentless operational
777
00:38:32.010 --> 00:38:35.289
clarity reels them in. You cannot have hidden setup fees.
778
00:38:35.650 --> 00:38:38.449
You cannot have vague delivery windows like sometime next week.
779
00:38:38.829 --> 00:38:39.730
Yeah, that should be concrete.
780
00:38:40.340 --> 00:38:44.420
Very concrete. You must outline the exact choreography. You pay
781
00:38:44.420 --> 00:38:47.460
$ 50 today. You receive a three-question intake form via email.
782
00:38:47.659 --> 00:38:50.579
You fill it out. Exactly 24 hours later, you receive
783
00:38:50.639 --> 00:38:55.130
a PDF with your seven social media posts. Ambiguity kills conversions.
784
00:38:55.489 --> 00:38:59.409
Think about the psychological function of this syntax. When you
785
00:38:59.510 --> 00:39:03.130
force yourself to articulate your entire business as I help
786
00:39:03.289 --> 00:39:06.929
X achieve Y without Z, it acts as a heavy anchor.
787
00:39:07.530 --> 00:39:10.130
It physically prevents you from drifting back up into the
788
00:39:10.170 --> 00:39:11.769
clouds of the idea phase.
789
00:39:12.730 --> 00:39:15.880
If we connect this to the bigger picture, it forces
790
00:39:15.900 --> 00:39:16.679
you to stay grounded.
791
00:39:16.840 --> 00:39:21.519
Yeah. You cannot fit a grandiose, vague vision of revolutionizing
792
00:39:21.659 --> 00:39:26.289
digital synergy into that strict sentence structure. The syntax itself
793
00:39:26.369 --> 00:39:29.639
forces you to remain grounded in the harsh, pragmatic reality
794
00:39:29.679 --> 00:39:31.179
of the customer's immediate needs.
795
00:39:32.159 --> 00:39:34.260
It is a reality check enforced by grammar.
796
00:39:34.519 --> 00:39:38.400
I love that. Okay, having the theory, the psychology, and
797
00:39:38.420 --> 00:39:42.699
the framework is powerful, but knowledge without execution is just entertainment.
798
00:39:43.539 --> 00:39:46.579
Let's move into the operational reality. Let's walk through the
799
00:39:46.639 --> 00:39:50.730
exact seven-day sprint detailed in the book. Let's put ourselves
800
00:39:50.750 --> 00:39:53.449
in the shoes of a founder experiencing the emotional rollercoaster
801
00:39:53.489 --> 00:39:56.750
of this week. Day one, write down the customer group
802
00:39:56.769 --> 00:39:59.949
and the problem. Day two, find 10 real people who
803
00:40:00.010 --> 00:40:01.500
fit that exact profile.
804
00:40:01.820 --> 00:40:03.880
Let's pause on the reality of days one and two
805
00:40:03.960 --> 00:40:09.619
because this requires highly practical, often uncomfortable hustle. Finding 10
806
00:40:09.619 --> 00:40:12.599
specific people is not a passive activity. You cannot just
807
00:40:12.699 --> 00:40:15.079
tweet a link into the void and hope they find you.
808
00:40:15.260 --> 00:40:15.699
No, they won't.
809
00:40:16.250 --> 00:40:19.219
If your target is independent cafe owners, day two means
810
00:40:19.360 --> 00:40:22.219
putting on your shoes, walking down Main Street, buying a
811
00:40:22.380 --> 00:40:26.760
lot of coffee, or systematically scraping local business directories, picking
812
00:40:26.900 --> 00:40:30.889
up the phone, and sending highly personalized direct messages. It
813
00:40:30.929 --> 00:40:32.750
is active manual hunting.
814
00:40:32.869 --> 00:40:33.650
It's detective work.
815
00:40:33.929 --> 00:40:36.369
It's literally knocking on doors.
816
00:40:36.949 --> 00:40:39.539
Then we hit day three and four. Have the five
817
00:40:39.599 --> 00:40:40.699
short customer conversations.
818
00:40:41.639 --> 00:40:44.679
This is the interrogation phase. This is the terrifying part
819
00:40:44.699 --> 00:40:48.150
where you ask about the last time, what they did,
820
00:40:48.610 --> 00:40:51.530
what was frustrating, and if they paid. This is where
821
00:40:51.550 --> 00:40:54.670
you sit in the awkward silence while they think. This
822
00:40:54.750 --> 00:40:58.469
is where you collect the raw, unvarnished vocabulary they used
823
00:40:58.510 --> 00:40:59.400
to describe their pain.
824
00:41:00.059 --> 00:41:02.500
Then we reach the absolute pivot point of the sprint,
825
00:41:03.119 --> 00:41:06.659
day five. Create one small offer based strictly on what
826
00:41:06.679 --> 00:41:09.159
you heard, not what you originally dreamed up.
827
00:41:09.460 --> 00:41:12.250
Strictly is the operative word here. Day five is the
828
00:41:12.329 --> 00:41:15.760
ultimate test of your discipline. You will be overwhelmingly tempted
829
00:41:15.800 --> 00:41:18.219
to look at the interview notes and say, OK, they
830
00:41:18.260 --> 00:41:20.320
said they just want a simple template, but I know
831
00:41:20.360 --> 00:41:24.059
they really need a fully automated AI video generator. So
832
00:41:24.099 --> 00:41:25.440
I'm going to pitch the video generator.
833
00:41:25.860 --> 00:41:27.000
Which ruins the whole experiment.
834
00:41:27.539 --> 00:41:30.860
Completely ruins it. No, you build exactly what the pain dictates.
835
00:41:30.980 --> 00:41:34.000
You build the scrappy manual service or the simple landing
836
00:41:34.039 --> 00:41:36.989
page based purely on the empirical evidence you just gathered.
837
00:41:37.320 --> 00:41:39.730
Day six, you take that offer. You put it in
838
00:41:39.769 --> 00:41:42.449
front of potential customers. And you ask for a concrete
839
00:41:42.510 --> 00:41:45.590
next step. You ask for a preorder, a paid pilot,
840
00:41:45.650 --> 00:41:46.130
or a booking.
841
00:41:46.670 --> 00:41:50.030
You take your perfectly crafted I help X achieve Y pitch.
842
00:41:50.510 --> 00:41:53.010
You lay
out the clear pricing and timeline. You put
843
00:41:53.050 --> 00:41:54.449
it in front of the people you spoke to on
844
00:41:54.469 --> 00:41:57.210
days three and four or lookalikes. And you hold your
845
00:41:57.230 --> 00:41:58.630
breath and ask for the action.
846
00:41:58.969 --> 00:42:02.190
Which brings us to the final day, day seven, the review.
847
00:42:03.070 --> 00:42:05.789
This is where dreams either cross the threshold into reality
848
00:42:06.110 --> 00:42:09.489
or they hit a brick wall. Did anyone book? Did
849
00:42:09.570 --> 00:42:12.739
anyone pay? And here is where I want to focus deeply,
850
00:42:12.780 --> 00:42:16.940
because the emotional weight of day seven is immense. How
851
00:42:16.980 --> 00:42:18.380
do we process a no?
852
00:42:19.070 --> 00:42:22.170
Processing a no requires the hardest emotional reframe a founder
853
00:42:22.210 --> 00:42:25.250
has to make. The immediate biological response to a no
854
00:42:25.429 --> 00:42:28.789
is to interpret it as a personal failure. But analytically,
855
00:42:28.809 --> 00:42:31.489
a no is incredibly rich diagnostic data.
856
00:42:32.110 --> 00:42:34.820
Let's break down the taxonomy of a no. There are
857
00:42:34.840 --> 00:42:38.059
three specific mechanical reasons a no happens. What is the first?
858
00:42:38.769 --> 00:42:42.250
First, a no usually indicates that the problem simply isn't
859
00:42:42.530 --> 00:42:46.449
urgent enough. The customer acknowledges the problem exists. They might
860
00:42:46.489 --> 00:42:49.340
even complain about it. But the pain hasn't reached the
861
00:42:49.360 --> 00:42:52.440
threshold where they are willing to expend capital or energy
862
00:42:52.480 --> 00:42:54.960
to fix it. The duct tape is holding well enough
863
00:42:54.980 --> 00:42:55.300
for today.
864
00:42:55.920 --> 00:42:59.179
So the pain is chronic, but not acute. Okay, what
865
00:42:59.219 --> 00:43:00.039
is the second reason?
866
00:43:00.659 --> 00:43:03.320
Second, your targeting might be off. The customer group is
867
00:43:03.340 --> 00:43:06.429
too broad. Perhaps you pitched the social media planning service
868
00:43:06.449 --> 00:43:09.300
to a bakery owner. And they respond, well, I just
869
00:43:09.320 --> 00:43:11.119
snap a photo of a croissant when it comes out
870
00:43:11.139 --> 00:43:12.599
of the oven. It takes three seconds. I don't need
871
00:43:12.619 --> 00:43:16.139
a planner. The problem was real for the cafe, but
872
00:43:16.179 --> 00:43:16.860
not for the bakery.
873
00:43:17.480 --> 00:43:18.300
And the third reason.
874
00:43:19.059 --> 00:43:23.059
The third reason is operational. The offer wasn't clear. They
875
00:43:23.079 --> 00:43:26.349
have the urgent problem. They are the perfect target demographic.
876
00:43:26.809 --> 00:43:29.449
But your pitch was so convoluted or the mechanism of
877
00:43:29.489 --> 00:43:32.309
delivery was so confusing that they said no simply out
878
00:43:32.329 --> 00:43:34.849
of self-defense because they didn't understand what they were buying.
879
00:43:35.900 --> 00:43:39.019
A day seven no forces you to forensically examine which
880
00:43:39.039 --> 00:43:42.960
of those three variables, urgency, targeting, or clarity, is broken.
881
00:43:43.440 --> 00:43:45.800
But let's step out of the analytical and back into
882
00:43:45.820 --> 00:43:48.179
the human for a second. We are talking about human
883
00:43:48.219 --> 00:43:52.269
beings with hopes and anxieties. You've spent a week hustling.
884
00:43:52.449 --> 00:43:55.050
You've swallowed your pride to build a scrappy test. You've
885
00:43:55.070 --> 00:43:58.750
made yourself incredibly vulnerable by pitching in. And someone looks
886
00:43:58.769 --> 00:44:02.289
you in the eye and says, no thanks. How does
887
00:44:02.369 --> 00:44:06.139
a founder objectively analyze those three variables without taking it
888
00:44:06.260 --> 00:44:10.500
as a devastating rejection of their very identity as an entrepreneur.
889
00:44:10.840 --> 00:44:13.260
This raises an important question, and it cuts to the
890
00:44:13.300 --> 00:44:17.320
core of why this methodology exists. It forces a separation
891
00:44:17.360 --> 00:44:21.710
between measuring action and measuring ego validation. When you tie
892
00:44:21.730 --> 00:44:25.190
your self-worth to your initial idea, when you believe you
893
00:44:25.349 --> 00:44:27.849
are the blueprint, then a rejection of the idea feels
894
00:44:27.869 --> 00:44:30.329
like a rejection of your soul. It feels like they
895
00:44:30.369 --> 00:44:32.150
are saying, you are not good enough.
896
00:44:32.530 --> 00:44:33.369
It's deeply personal.
897
00:44:33.730 --> 00:44:37.849
But, Consider the architecture of the seven-day sprint. You have
898
00:44:37.929 --> 00:44:41.590
deliberately separated your identity from the test. You are not
899
00:44:41.630 --> 00:44:44.750
pitching a grand, sweeping vision of yourself as a visionary
900
00:44:44.829 --> 00:44:48.889
tech CEO. You are pitching a highly specific manual solution
901
00:44:48.949 --> 00:44:52.320
to a highly specific cafe owner's problem. You are a
902
00:44:52.360 --> 00:44:53.980
scientist running an experiment.
903
00:44:54.199 --> 00:44:55.239
Right. You're wearing the lab coat.
904
00:44:55.559 --> 00:44:58.940
Exactly. When an experiment yields a negative result, the scientist
905
00:44:58.960 --> 00:45:02.389
does not have an existential crisis and quits science. The
906
00:45:02.429 --> 00:45:05.610
scientist coolly adjusts the variables and runs a new experiment.
907
00:45:06.559 --> 00:45:09.780
The emotional toll is entirely mitigated by the speed and
908
00:45:09.840 --> 00:45:12.800
cheapness of the sprint itself. It has only been one week.
909
00:45:13.079 --> 00:45:15.199
You haven't spent your life savings. You haven't taken out
910
00:45:15.239 --> 00:45:18.400
a second mortgage. You haven't wasted a year of your life.
911
00:45:19.079
--> 00:45:22.269
You have just spent a few days gathering data. You
912
00:45:22.289 --> 00:45:24.570
survived the no because the no was cheap.
913
00:45:24.949 --> 00:45:27.889
That is the profound realization here. You survived the no
914
00:45:27.929 --> 00:45:30.570
because the no was cheap. That is the entire genius
915
00:45:30.630 --> 00:45:33.789
of this operational framework. It is an emotional and financial
916
00:45:33.829 --> 00:45:34.309
safety net.
917
00:45:34.610 --> 00:45:35.650
It protects you from yourself.
918
00:45:36.949 --> 00:45:39.699
We have covered an immense amount of ground today, completely
919
00:45:39.760 --> 00:45:43.519
unpacking the mechanics of moving from an illusion to a customer.
920
00:45:44.480 --> 00:45:48.199
Let's synthesize this deep dive into four critical takeaways. First,
921
00:45:49.380 --> 00:45:52.500
define a real customer problem. Start with the people standing
922
00:45:52.530 --> 00:45:56.130
in the rain, not the architectural blueprint. Focus relentlessly on
923
00:45:56.170 --> 00:45:59.650
delivering one of those core results. Less stress, save time,
924
00:45:59.750 --> 00:46:01.389
lower cost, or convenience.
925
00:46:02.230 --> 00:46:09.269
Second, interrogate past behavior, ignore future promises. Find your hyper-targeted microgroup,
926
00:46:09.730 --> 00:46:11.730
ask them what they did last Tuesday to solve the pain,
927
00:46:12.289 --> 00:46:15.130
and treat polite validation as the dangerous fiction it is.
928
00:46:15.750 --> 00:46:19.909
Third, test a small offer before you build perfection. Suppress
929
00:46:19.929 --> 00:46:23.730
the ego, embrace the scrappy manual kitchen table test, and
930
00:46:23.769 --> 00:46:27.030
focus on delivering just one useful outcome to prove demand.
931
00:46:27.849 --> 00:46:32.679
And fourth, measure concrete action. A useful offer is ruthlessly clear,
932
00:46:32.980 --> 00:46:35.880
answering who it's for and what result it delivers. The
933
00:46:35.980 --> 00:46:38.780
only metric that matters is whether it generates a booking
934
00:46:38.980 --> 00:46:42.679
or a payment. Treat a no as cheap diagnostic data
935
00:46:42.760 --> 00:46:45.119
to adjust your variables, not as a personal failure.
936
00:46:45.460 --> 00:46:47.920
Which brings us to the final challenge, because all this
937
00:46:47.980 --> 00:46:50.139
knowledge is useless if it just stays in your headphones.
938
00:46:51.179 --> 00:46:54.989
I am directly challenging you, the listener, to execute on
939
00:46:55.030 --> 00:46:58.510
this today. Step out of the safety of the idea phase.
940
00:46:59.110 --> 00:47:05.030
Find five potential customers this week. Use the four interrogation questions. Ask, listen,
941
00:47:05.489 --> 00:47:08.699
and learn before you invest a single dollar of your savings.
942
00:47:09.320 --> 00:47:11.460
And as you prepare to have those conversations, I want
943
00:47:11.500 --> 00:47:14.960
to leave you with a final lingering thought. Look closely
944
00:47:15.019 --> 00:47:17.679
at your current business idea, the one in your notebook,
945
00:47:17.840 --> 00:47:21.730
the one keeping you awake. Ask yourself, what assumption are
946
00:47:21.750 --> 00:47:24.429
you holding onto right now that would completely destroy your
947
00:47:24.449 --> 00:47:26.889
business model if it turned out to be wrong? And
948
00:47:26.909 --> 00:47:30.610
more importantly, what happens if you run this seven-day sprint
949
00:47:31.010 --> 00:47:33.909
and you discover that your foundational assumption is, in fact,
950
00:47:34.349 --> 00:47:35.090
entirely false?
951
00:47:35.710 --> 00:47:37.809
That is a question that should keep you awake, but
952
00:47:37.989 --> 00:47:40.380
for all the right reasons. We are going to skip
953
00:47:40.429 --> 00:47:45.300
our usual sign-off today to honor the highly tactical, action-oriented
954
00:47:45.340 --> 00:47:48.380
nature of what we've discussed. So get out of the building.
955
00:47:49.019 --> 00:47:51.780
Get out there to learn, strategize, and grow.