What Entrepreneurs Can Learn from The Confidence Code
You've built the product, tested it with real users, and the numbers are good enough to show someone. But the deck has sat untouched in your drafts folder for three weeks, and the ten warm intros your advisor sent are still unanswered. You tell yourself you're "refining the narrative," but really you're waiting to feel like the kind of founder who deserves a yes before you're willing to ask for one. Meanwhile a competitor with a shakier product and rougher pitch is already three investor meetings in. You've already done the hard, competence-building work — customer interviews, iteration, a working demo. What's missing isn't skill. It's the willingness to act while unsure how the ask will land, and to treat the silence or "no" that follows as information about this pitch, not a verdict on whether you deserve to run a company at all.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Confidence isn't the same as having a fundable business
You can build a genuinely strong company and still feel like an imposter walking into a term sheet negotiation. Competence and confidence get tracked separately in your head, and founders often assume the second must catch up to the first before they're allowed to act. Waiting for certainty before pitching, hiring, or raising prices puts the order backwards.
A founder delays raising prices for eight months because she doesn't "feel like" someone who charges what the market would bear, even though three customers have told her the product is underpriced. She keeps polishing the pricing slide instead of testing a higher number with new signups.
Before your next investor or customer conversation, write down the specific evidence that you're capable of running this business, separate from how confident you feel walking in the door.
Ship the version that isn't fully ready
In a startup, waiting for a fully validated plan usually means someone else ships first. Confidence tends to build after you've made the call and watched the market respond, not before you've made it.
A two-person team spends four months polishing a "complete" onboarding flow before letting a single outside user near it, then discovers in week one that the core assumption behind step three was wrong — four months a rougher, faster test would have caught in a week.
Pick one decision you've been "still researching" for more than two weeks and give yourself 48 hours to act on the best information you already have.
A cold "no" is data about this pitch, not about you
An investor pass, a churned customer, or a failed launch tells you something specific about the offer, the timing, or the audience — not something permanent about your judgment or your worth as a founder. Founders who separate the two keep raising, pricing, and shipping; the ones who don't quietly start avoiding the room.
After two investors pass in the same week, a founder stops sending the deck to the other names on his list, privately deciding the whole idea must be dead — when both passes actually cited the same fixable objection about market size that one new slide could address.
After any rejection, write one sentence naming the specific, fixable reason it might have happened before you decide what it means about the business.
Confidence compounds like a habit, not a personality trait
Founders who look unshakeable in the boardroom didn't start that way — they built the habit of acting on partial information across dozens of small, low-stakes moments: a scrappy first sale, an early hire made on gut feel, a rough beta launched before it was pretty. There's no personality trait reserved for founders; it's a muscle built one uncomfortable ask at a time, strengthened by use rather than by natural gift.
Moving fast and treating failure as data can pull against each other: sprinting from one attempt to the next without pausing just repeats the same mistake at higher speed. Resolve this by keeping the bias toward action but adding a short, non-negotiable debrief after every pitch or launch — five minutes to name what the outcome actually taught you before the next attempt.
Name one thing, honestly
Where in your business are you still waiting to feel like a "real" founder before making the call a real founder would already have made?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
After any rejection, write one sentence naming the specific, fixable reason it might have happened before you decide what it means about the business.