Founder Unfriendly: The AI Powered Fundraising Companion to the Bestselling Book

Before you run these exercises

Chapter 10 is about the endgame — and specifically about not mistaking the words investors use for what they actually mean. The chapter opens with a sharp observation about the most dangerous word in fundraising. It also covers what a real yes requires to become money in the bank, how to read and respond to the four different types of no, and what to do if the raise fails entirely.

Read the chapter before you run these exercises. The framework for decoding investor signals — and the specific mechanics for getting soft commits to hard closes — are detailed there in ways the exercises below reference directly.

Claude

Exercise 01

Decode What an Investor Is Actually Saying

The chapter's most important observation: "interested" is not a commitment — it's camouflage. It keeps founders hopeful while giving investors all the optionality to keep watching without closing. The chapter translates several specific phrases investors use that sound positive but mean something else entirely. Those translations are in the book — read Chapter 10 first, then use this exercise to apply the same framework to what you're actually hearing.

Read those translations in the chapter before you run this exercise. Then use Claude to apply the same framework to the specific language you're actually hearing.

📸

Before running this prompt, snap a photo of the investor signal translations in Chapter 10 and upload it directly into Claude along with the prompt text.

Prompt → Claude

Here's what investors have said to me recently: [paste the exact phrases — from emails, calls, or meeting notes — that you're unsure how to interpret] For each statement: 1. Translate what they most likely actually mean using the framework in the photo 2. What specific follow-up question would force them to be more precise? 3. What would a real yes look like from this investor at this stage? 4. Should I keep this investor in my active pipeline, treat them as "track but don't chase," or consider them a soft no? I want the honest read, not the one that makes me feel better about the pipeline.

📖

Have you read about the "gone rogue" pattern yet? The chapter has a specific name for what happens when a junior investor — sometimes called a "little p" partner — gets excited about your company and starts pulling you through a process that was never going to go anywhere. If you're spending a lot of time with someone who isn't clearly a decision-maker, you need to understand this pattern before your next meeting. It's in the chapter.

Claude

Exercise 02

Diagnose Your No — and Know What It Demands

The chapter identifies four fundamentally different types of no — and they each demand a completely different response. Treating them as the same thing is what causes founders to either work on the wrong fix or give up on an investor who might have come back around with a different story.

The four types: they doubt your ability to execute. They question the size of the market. They dismiss the urgency of the problem. Or they believe you could succeed — but the outcome will never be big enough to matter to their fund. Each one has different implications for what to do next.

Prompt → Claude

Help me diagnose what type of "no" I'm getting from investors, using the framework from Founder Unfriendly. The book identifies four different kinds: 1. They doubt my ability to execute — they're not sure I can actually pull this off 2. They question the size of the market — they don't think this is big enough to matter to their fund 3. They dismiss the urgency of the problem — they don't believe enough people care enough to pay for this 4. They believe I could succeed, but the outcome would never be big enough for their return model Here's what I've been hearing from investors who've passed: [paste the actual language investors have used when passing — in emails, verbally, or in follow-up notes] Here's how many investors have passed and what patterns you see: [number of passes, anything consistent across them] For each rejection: 1. Which of the four types does it most likely represent — and what in their language points you there? 2. What's the specific thing that would directly address that type of no? 3. Is this a no that's fixable before my next raise attempt, or does it point to a structural issue I need to think harder about? 4. What's the right way to keep this relationship alive — what would I send them, and when, that addresses their specific concern rather than just sending general good news?

💡

The chapter has a real story about a founder who came back to an investor with exactly the wrong update. It's a small thing, but it captures everything about why rejections don't turn into yeses for most founders. It's in the "Don't Argue, Don't Vanish" section — worth reading before you send any investor update.

Closing mechanics

Claude

Exercise 03

Move Soft Commits to Hard Closes

The chapter is direct: soft commits don't pay bills. Verbal yeses that don't turn into signed docs and wired money are not closed. The chapter lays out a specific closing sequence — get docs signed first, then money wires when you hit a round minimum — and gives clear guidance on follow-up cadence (at least every 48 hours for unsigned docs), how to handle ghosters, and when a "calendar meeting for the close" is the right move.

Use Claude to draft the actual follow-up sequences for investors at different stages of the close.

Prompt → Claude

Help me move soft commits to hard closes for my fundraise. Here's the current state of my round: - Round size and minimum threshold: [e.g., "raising $1.5M, minimum viable close at $750K"] - Investors who have verbally committed but not signed: [list them with any notes on where they are] - Investors who have signed but not wired: [list them] - Investors who have gone quiet after a verbal yes: [list them] For each category, draft: 1. The 48-hour follow-up for unsigned investors — warm, direct, specific about what I need from them and by when 2. The wire nudge for signed but not wired — factual and clear without being aggressive 3. The "calendar meeting" message for ghosters — the one that invites them to a specific call to finalize and makes it easy to just respond rather than ignore 4. The closing update message for the whole group — showing momentum without giving a deadline that will make me look like I'm still raising if I miss it Tone: confident founder who is managing a close, not a supplicant asking for a favor.

💡

The chapter's framing on persistence: how you herd investors to a close is a signal for how you bring enterprise customers and partners on board. An investor who feels you're incredibly on top of things and can't be shaken will feel more confident about you — not more harassed. They said yes. If following up feels awkward, the awkwardness is on their side, not yours.

Granola + Claude

Exercise 04

Build Your Post-No Investor Update System

The chapter's most actionable advice on rejection: don't argue, don't vanish. A no is almost never permanent — it's usually "not yet," with a specific thing that needs to change. The investors who come back around are the ones who kept getting updates that directly addressed their concern, not founders who resurfaced two years later hoping things had changed.

The workflow: after a pass, use Granola + Claude to identify the specific concern from the meeting transcript, then set a recurring update cadence that shows progress on exactly that thing. The investor doesn't need to hear everything going well — they need to see that the one thing they doubted has been addressed.

Prompt → Claude after any pass — use with Granola transcript

An investor just passed. Here's the Granola transcript or notes from our meeting: [paste] Here's what they said when they passed (their exact language if you have it): [paste] Help me build a post-no update system for this investor: 1. What is the single most specific concern they expressed — not the polite language, the underlying doubt? 2. What evidence would directly address that concern — what would I need to show them, and what's a realistic timeline for getting there? 3. Draft a "keeping you in the loop" message to send in 4–6 weeks — not asking for anything, just showing a specific piece of progress that maps to what they doubted 4. What's the 90-day update that would make them want to re-engage — the milestone that, if I hit it, makes their specific concern harder to hold onto? 5. Is there a point at which I should explicitly re-ask, rather than just update? What would that moment look like?

💡

The update is not a newsletter. Sending general good news to every investor who passed is noise. The update that brings someone back is the one that says: "You told me you weren't sure we could sell to enterprise. Here's what happened." Specific, direct, and mapped to their exact concern. That's the difference between a founder who disappears and a founder who's impossible to ignore when the time comes.

If the raise fails

Claude

Exercise 05

Triage a Failed Raise

The chapter is one of the few places in fundraising literature that addresses this honestly: sometimes the round just doesn't come together. And the founders who handle it well are the ones who treat the failed raise itself as data — not a verdict, not a reason to keep pitching the same story to the same people, but a signal that something in the process needs to change.

The chapter makes a specific point about timing: try to fail when you still have enough runway to do something different. A failed raise with six months of cash left is a problem you can solve. A failed raise with two weeks of cash is a crisis.

Prompt → Claude

My fundraise isn't coming together and I need to honestly triage what happened and what to do next. Help me work through this as data, not as a verdict. Here's what I tried: [how many investors you approached, what stage, over what timeframe, what you were raising] Here's what I heard most: [the recurring objections or pass reasons, even the vague ones] Here's where I am financially: [runway remaining, current burn rate] Walk me through the chapter's post-mortem framework: 1. Process-level diagnosis — did I sequence the outreach correctly? Did I try to raise before I had the proof points investors needed? Was my target list right for the kind of company I'm building? 2. Story-level diagnosis — was the narrative sharp enough? Were the milestones convincing? Was the market timing argument clear? 3. Triage — given my runway, what's the right immediate move? (Cut burn and extend timeline / focus on specific traction that addresses the main objection / approach a different type of investor) 4. The "not yet" message — what would I send to the investors I met to keep them in the loop without looking like I'm flailing? 5. What does the next raise attempt need to look like to be different — what specifically has to change before I go back out?

💡

The chapter's most important line on this: "Don't disappear." The founders who vanish after a failed raise — who go dark from investor inboxes and resurface two years later desperate — have to reintroduce themselves from scratch. The founders who keep sending updates that show they're still building and still learning give investors a reason to come back around. The failed raise doesn't have to be the end of the relationship. It only becomes that if you treat it that way.

Final Thoughts from the Book

The book ends with something worth sitting with. Charlie writes about the founders who last longest — and what they have in common isn't that they never doubted themselves or never failed. It's that they were honest about the possibility of failure, which gave them the clarity to keep going without panic.

The book ends with something worth sitting with — a reframe on what it means to be a founder that doesn't show up in most startup advice. It's in the Final Thoughts section. Read it.

Dogs and Cats, Living Together

Before you run these exercises