· Mike Maples Jr.

A Playbook for Startups — Mike Maples Jr.

Breakthrough startups force a choice toward a different future built on inflections, run a three-phase breakthrough sequence (insight → product → growth), and recruit early believers as co-conspirators rather than chase conventional customers.

venture-capitalbreakthrough-startupscategory-designcustomer-developmentpivotsfloodgate90% confidence

Why this is in the corpus

Most cited mental-model framework for breakthrough investing — inflections, backcasting, value hypothesis, category design, force-a-choice — from a seed investor with Twitter/Lyft/Twitch/Okta.

Summary for skimmers

Maples lays out the Floodgate operating system: invest in inflections, use backcasting, force a choice, hire to take out biggest risks first, go-for-the-no in customer dev, treat ~90% of exit value as coming from pivots, transition deliberately from value-hacking to growth-hacking, and design the category by building the minimum viable future.

Briefing

What survives the editorial filter

This page should feel like a smart colleague already listened for you and left only the operating logic worth keeping. Not everything said in the episode makes it through.

Trust signal

direct_practitioner_account

Guest type: practitioner.

Best used for

Decision-grade retrieval metadata not yet added for this episode.

Hold lightly

No explicit downgrade reason stored yet for this episode.

Principles

Durable claims that survive beyond the speaker's biography — each with explicit limits, transferability judgment, and evidence.

Principle

Co-conspirators, not investors — founders need believers in the controversial secret

Conventional advice (TAM, cohorts, customer-requirement requests) actively pushes founders toward local-maximum thinking.

“Those founders do not need investors. They need co-conspirators.”Mike Maples

Reframes the investor-founder relationship as ideological alignment.

Principle

Force a choice, not a comparison — startups must offer a different future, not a better banana

When you compete on better, the customer's reference is the incumbent and you lose by their yardstick.

“If everybody is selling bananas, you say I am the world's first apple. The set of people who value apples, 100% of them should flock to your apple.”Mike Maples

Foundational Floodgate framing.

Principle

Risk is something you take, not something you avoid — chase unbounded upside

When success magnitude is uncapped and failure cost is one year + a small check, EV is dominated by the right-tail.

“Failure does not matter, only success matters, as long as the magnitude of upside is big enough.”Vinod Khosla via Mike Maples

Direct Khosla lineage.

Principle

Inflections, not gaps — get out of the present before you think of a startup

Inflections, not market gaps, are the asymmetric weapon that lets a tiny team wage asymmetric war on the present.

“Customer development is get out of the building, insight development is get out of the present.”Mike Maples

Most-quoted Maples mental model.

Frameworks

Reusable systems and operating models — including when they help and when they break.

Framework

Plausible / possible / preposterous — typing your secret determines team and capital structure

Without typing your secret, you over- or under-resource the team and the round.

“Some secrets are plausible, some are possible, and some are preposterous. The team, fundraising, risk profile, the inflections that have to come together — all vary.”Mike Maples

Diagnostic typology preventing the most common Series-A mistake.

Framework

The Breakthrough Sequence — insight → product → growth (gas → liquid → solid)

Stage-mismatched operating mode is the biggest predictable killer of post-PMF startups.

“You transition from being a gas to a liquid to a solid. You are literally becoming something different.”Mike Maples

Structural backbone of the Maples playbook.

Framework

Hire to take out the biggest risk first — startup teams are an Ocean's Eleven, not an org chart

Generic functional hiring spreads scarce capital across non-binding risks while the binding risk goes uncrushed.

“They need people that are different from a traditional org chart. They need people that are going to take out the critical risks.”Mike Maples

Operating implication of the Ocean's Eleven metaphor.

Signals

What appears to be shifting, for whom it matters, and what happens if you ignore it.

Signal

"If most VCs like it, I am worried" — controversiality is the leading indicator of breakthrough

VC consensus is downstream of present-day pattern-matching; consensus-pleasing ideas sit on the comparison axis where startups lose.

“If most VCs like it, now I am worried because it is not controversial enough.”Mike Maples

A counter-intuitive signal that doubles as a self-selection mechanism.

Opportunities

Only included where there is a buyer, a real wedge, and a plausible revenue path — not vague idea theater.

Opportunity

Opportunity: AI-vertical inflection-point investing

Alpha-fund opportunity.

“AI is creating inflection points across verticals.”Maples

Durability: Time-sensitive.

Forward.

Lessons still worth keeping

Useful takeaways that did not fully clear the bar for durable principle status.

Lesson

When a startup fails, blame the experiment, not the founder — back them on the next thing

Most great breakthroughs are second or third experiments by the same operators.

“Odeo was not ever failing. It was a failure because it was not the right idea at the right time.”Mike Maples

Direct Maples-Williams reference — the most expensive lesson given Twitter came from the same team.

Lesson

Pivots drive ~90% of exit value — buy the insight, not the first product

If you underwrite the first product instead of the insight, you sell at the bottom of every pivot.

“90% of our exit profits have come from pivots. What matters is the potential energy of the insight, not the actualized execution.”Mike Maples

Most consequential portfolio statistic disclosed.

Lesson

Always tease out the earned secret — even from founders you pass on

"If their presentation is bad but they are still great, I am the idiot."

“Whenever we pass on a deal that we should have done, I always go back and interview the founder and coax out what the real secret was.”Mike Maples

Process-design lesson born of the Airbnb miss.

The Plays

Try these this week

Verb-first executable actions — each one tied to a stated outcome in the episode.

The Pick-30-Get-10 customer selection play

Outcome: Customer-selection should precede customer-acquisition; if you let the inbound pipeline pick your customers, conventional thinkers will dominate the early customer base and pull the product back to the comparison axis.

“In board meetings, I would have a slide of the 30 customers we chose for this year, of which we want to get 10. We would not even talk to any other customers. We ended up getting 12.”
— Mike Maples

annual list refresh; quarterly conversion review per (proposed)

1
Define future-fit criteria
Write 4-6 attributes that identify customers already living in the different future (early adoption of upstream tech, regulatory permission, internal champion with budget authority, public commitment to outcome the product enables).
2
Build the 30-name target list
List exactly 30 named accounts that match the future-fit criteria. Do not exceed 30. Do not include broad inbound.
3
Lock the focus at the board level
Present the 30 list at every board meeting; commit to not spending time on prospects outside the list. Treat any deviation as a focus failure.
4
Concentrate effort on the 30
All sales, success, and product cycles run against the 30. Target conversion: 10 of 30 in the first year. Track conversion rate quarterly.
5
Convert bellwether wins into category narrative
As wins close, publicize the names — let word-of-mouth among future-fit segment do the second-order acquisition that inbound never could.

Stop or pivot when

→close rate below 25% triggers list re-evaluation, not list expansion
→any time spent on non-list prospects is a tracked focus violation

Scripts

Before you start

· Defined different-future thesis (insight breakthrough complete)
· Board willing to enforce focus discipline
· Sales team comfortable with high-rejection outbound

customer-developmententerprise-salescategory-creationseedseries-aseries-b

The Go-For-The-No customer-development play

Outcome: Energy spent on prospects who do not value your advantage is more than wasted — they will dilute the product with feature requests that do not flow from your insight.

“I would meet with somebody at one of these companies. I would start by saying, this may not be a good use of your time. I would start to make body language like I was moving to leave. My goal was to have them pull me back.”
— Mike Maples

~5 minutes per qualifying call(proposed)

1
Open meeting with permission-to-leave
Within first 60 seconds say verbatim: This may not be a good use of your time. We sell [product]. If you do not need software like this, I just gave you 45 minutes back.
2
Add physical exit signal
Begin gathering materials, leaning toward the door — make body language consistent with leaving the meeting.
3
Wait for the pull-back
If the prospect does not actively pull you back with specific urgency (deadline, committed target, internal failure), the meeting is correctly ending.
4
Diagnose the pull
When pulled back, ask one question: what specifically forces you to solve this and by when? You are listening for a Wall-Street-committed-target-style hard deadline.
5
Disqualify the slow-walkers
If pull-back is generic curiosity rather than acute pain, exit anyway — protect calendar for prospects who will pull product out of you.

Stop or pivot when

→pull-back must include a specific deadline or committed external target
→prospects who only ask roadmap questions are disqualified

Scripts

Before you start

· Founder must be willing to accept high meeting-decline rate
· B2B context with identifiable acute-pain segments
· Pitch deck slide 2 ready to test the controversial secret similarly

customer-developmentsales-discoveryb2b-go-to-marketseedseries-a

Decision Moments

Actual decisions, real outcomes

Specific decisions narrated in the episode with their outcomes and transferable lessons.

Odeo wound down after Apple absorbed podcasting into iTunes; Ev Williams was returning capital to investors. Maples had to decide whether the failure proved the team unsuitable or whether to back the IP-spinout idea Williams had not yet validated.

Did: Asked Williams directly what he thought could come of the new Twttr/Voicemail-2.0 IP and listened for the controversial-secret reasoning ("a million people wrote blogs; podcasting is harder; what if 10 million wrote micro-blogs?"). Got a chill, told Williams he wanted in at the first nickel.Outcome: Floodgate became one of Twitter's earliest investors — one of the largest single returns in the firm's history.

Separate experiment-failure from operator-quality in your post-mortem; the same team that ran a failed experiment is often the team running your highest-information next bet.

Part of an emerging decision pattern across multiple episodes

Brian Chesky pitched Maples on Airbnb. Demo failed live; Chesky had brought no slides; meeting devolved into staring at cereal boxes. Maples could choose to pass cleanly or to dig for the earned secret beneath the broken pitch.

Did: Passed without teasing out the earned secret (ratings + photos manufacture trust > hotel-brand trust).Outcome: Missed Airbnb. Used the miss to install a permanent process: every passed founder gets a post-pass interview to extract the earned secret and feed Floodgate's mental models.

When the presentation is bad but the founder is great, the failure is the underwriter's, not the founder's — build a process that converts every pass into a model update.

Part of an emerging decision pattern across multiple episodes

As an operator selling broadband-rollout software to cable cos in the early 2000s, Maples faced an unbounded prospect list and limited team energy. Conventional move: take every meeting, qualify in the room, work the funnel.

Did: Rebuilt the discovery default: open every meeting with permission-to-leave framing ("if you do not need software like this I just gave you 45 minutes back") + physical exit body language. Filtered for prospects whose pain was acute enough to pull him back with specific external deadlines (Wall-Street-committed broadband targets).Outcome: Calendar concentrated on customers who pulled product out of him; team avoided building features for conventional thinkers; deals closed faster.

Energy spent on prospects who do not value your advantage is more than wasted — they will dilute the product with feature requests that do not flow from your insight.

Part of an emerging decision pattern across multiple episodes

Floodgate's "we are an apple in a sea of bananas" moment had passed by the late 2010s — there are now hundreds of seed funds. Maples had to decide whether to compete on price/terms (banana competition) or to build a differentiated wedge.

Did: Built three "awesome people networks" of pre-founders (super-founders 50M+ exits, builders going down inflection rabbit holes, third group). Provided insight-development frameworks and emotional preparation for breakthrough-builder life. When network members start a company, write a check without pitching — forces a choice ("do we want to work together") not a comparison ("collect term sheets").Outcome: Re-established Floodgate's force-a-choice positioning at the firm level; insulated from price competition by competing on relationship-depth and pre-formation insight transfer rather than on terms.

Apply the breakthrough-startup playbook to your own firm: when bananas multiply, you have to become a different apple, not a slightly better banana.

Part of an emerging decision pattern across multiple episodes

Tensions surfaced

Contradictions and trade-offs the episode raises — judgment calls a thoughtful operator has to navigate.

Tension

Tension: Backable founder vs backable market

Founder-bet high-skill-variance; market-bet obvious-large-TAM.

“Founder vs market. Depends on what you''re seeing.”Maples

Durability: Durable.

Productive tension.

Corpus connection

Where this episode fits for retrieval

What kinds of decisions this briefing is best pulled into.

Temporal flag

timeless