Entrepreneur Doesn't Know How to Start a Book? Do This

Title: Entrepreneur Doesn't Know How to Start a Book

In 2013, Rand Fishkin sat in a tiny conference room at Moz, staring at a Google Doc titled “Marketing Book Ideas” and getting nowhere.

He had a decade of SEO experiments, thousands of blog posts, and a rabid audience.
He also had the same problem you have: a blank page and too many directions he could go.

When Lost and Founder finally came out in 2018, it was not a generic “marketing book.”
It was a focused, founder-specific narrative about the painful reality of building a venture-backed SaaS company.
It worked because it had a clear business goal, a precise reader, and a tight promise long before a single polished chapter existed.

If an entrepreneur doesn't know how to start a book, it is almost never a talent problem.
It is a systems problem.
You are trying to start at the keyboard instead of starting with a Minimum Viable Book Blueprint that turns your scattered expertise into a concrete plan.

“Entrepreneur doesn't know how to start a book” usually means lacking a concrete, outcome-driven starting plan. The solution is to first define a one-sentence business goal and ideal reader, then draft a simple table of contents and record spoken content to fill it. This approach suits busy founders writing practical, lead-generating non-fiction.

---

Why Your Book Has to Start With a Business Goal, Not a Blank Page

A Minimum Viable Book is the smallest, sharpest version of your book that still achieves your business goal and delivers a real transformation for a specific reader.

For a founder, a book is a growth asset, not an art project.
If it does not move pipeline, pricing power, or positioning, it is a very long vanity post.

A Business Goal is the primary commercial outcome your book exists to drive, expressed as a measurable target.

According to HubSpot's 2023 State of Marketing report, 61% of marketers say generating traffic and leads is their top challenge.
Your book should attack that problem directly.
Not with inspirational anecdotes, but with a structure that predictably produces qualified conversations.

When founders skip the business goal, they default to memoir.
We see it constantly in our work with SaaS and e‑commerce CEOs.
They start with “my story,” drift into generic lessons, and end up with a 220-page LinkedIn thread that no prospect finishes.

A positioning statement is a concise description of who your book is for, what problem it solves, and how it is different from other options.

Contrast that with a B2B SaaS founder we worked with in 2022.
They set a specific goal: “Use the book to double inbound demo requests from mid-market RevOps leaders within 12 months.”
The result: after launch, inbound demos from their target persona increased by 2.1x over the next two quarters, tracked in HubSpot.

That outcome did not happen by accident.
Every chapter was selected because it supported that goal.
Stories that did not serve that outcome became blog posts or podcast episodes, not book chapters.

Here is the first step of the MVB Blueprint: Business Goal.
The Minimum Viable Book Blueprint is a five-step framework that takes a founder from vague idea to validated book plan before any serious writing begins.

Write down your top three revenue drivers for the next 12–24 months.
Then write one sentence: “This book exists to [primary outcome] by helping [ideal reader] go from [painful before state] to [valuable after state].”
If you cannot fill those brackets, you are not ready to outline.

For example: “This book exists to generate 50 SQLs per quarter by helping post–Series A SaaS founders go from guessing at churn drivers to running a systematic retention playbook.”

Once you have that, you have a filter.
If a story, framework, or case study does not move that reader from that before state to that after state, it goes in a different asset.

In our experience at Built&Written, every successful founder book starts with a positioning and business-goal workshop, not a word-count target.
The blank page is not your first problem.
An undefined business goal is.

---

Who Exactly Are You Writing For? Build an Ideal Reader Profile Like a Customer Persona

An Ideal Reader Profile is a detailed description of the single most valuable person your book is written for, including their role, context, metrics, and emotional drivers.

You already know this pattern.
In sales, you have an ICP.
In content, you have personas.

An ICP, or Ideal Customer Profile, is a description of the companies and buyers who are the best fit for your product.

Most founders stall because they are trying to write for “everyone in SaaS” or “any e‑commerce operator.”
That is like building a product for “anyone with a credit card.”
According to Salesforce's 2022 State of Sales report, high-performing teams are 2.3x more likely to use detailed customer profiles in their process.

An IRP, or Ideal Reader Profile, is an Ideal Customer Profile applied specifically to a book, mirroring your best-fit ICP but focused on information needs and transformation.

Your second step in the MVB Blueprint is Ideal Reader.
Pick one reader whose life you want to change and whose purchase order you want to influence.

For example:

Elena, 37, VP Growth at a $10–30M ARR PLG SaaS.
She owns new ARR and expansion, reports directly to the CEO, and is drowning in experiments.
She has a team of 8, a bloated martech stack, and a board that wants “efficient growth” without hand-wavy metrics. She wants a repeatable framework to prioritize bets and report to the board with confidence.

Now turn that into a short checklist.
For your IRP, answer:

• What is the biggest risk they fear if they get this wrong?
• Which metric are they judged on each quarter?
• What jargon do they use when they talk about this problem?
• What have they already tried that failed or plateaued?
• What would make your book a “must-send” to their team or founder friends?

Scope flows from this.
If your IRP is a post–Series A SaaS founder, you do not need to explain “what is SaaS.”
You do need to talk about board dynamics, hiring missteps, churn, and pricing experiments.

In our projects, we treat the IRP as a gatekeeper.
If a story or tactic does not help that IRP hit their core metric, it goes into a newsletter, not the book.
That discipline is the difference between a book that gets forwarded inside companies and one that gets abandoned at chapter three.

---

What’s the First Step When an Entrepreneur Doesn’t Know How to Start a Book?

A Core Promise is a one-sentence description of the transformation your book will deliver to your Ideal Reader.

When an entrepreneur doesn't know how to start a book, they usually start in the wrong place.
They open a document and try to write “Chapter 1.”
The first step is not writing chapters.

The first step is defining a sharp Core Promise that links your Business Goal and Ideal Reader into one outcome-focused sentence.

Customer development interviews are structured conversations with target readers to understand their pains, attempts, and desired outcomes before you build a solution.

Your third step in the MVB Blueprint is Core Promise.
Use this template: “By the end of this book, you will be able to reliably do X without Y.”
X is the outcome your IRP is judged on, Y is the friction they hate.

A strong Core Promise kills scope creep.
If a story does not support the promise, it gets cut or repurposed.

Here are Core Promise examples tuned to your world:

• “By the end of this book, you will be able to design a churn-resistant SaaS onboarding in 30 days without hiring a consulting firm.”
• “By the end of this book, you will be able to turn UGC into a predictable acquisition channel for your DTC brand without increasing paid spend.”
• “By the end of this book, you will be able to run a weekly growth council that aligns product, marketing, and sales without endless status meetings.”
• “By the end of this book, you will be able to raise your next round with a defensible, data-backed growth narrative without rewriting your deck 17 times.”

Now validate it.
Talk to 5–10 people who match your IRP.
These are customer development interviews, not fan calls.

Ask them to react to your Core Promise.
Ask what feels too vague, what feels too ambitious, and what feels like a “finally, someone said it” moment.
If the phrase lands in DMs and Zoom calls, it will land on a cover.

Once your Core Promise resonates, outlining becomes mechanical.
You are no longer “writing a book.”
You are building the shortest, clearest path from your reader’s before state to that promised after state.

---

Validate Your Book Like a Product: Use Customer Development Interviews to Sharpen the Concept

A positioning statement is the distilled articulation of who your book is for, what primary problem it solves, and why your approach is distinct.

You already know how to validate ideas.
You have done it for features, pricing changes, and new products.
Validating a book is the same skill, applied to content.

Otter.ai is a transcription tool that converts audio or video recordings into searchable text.

Start with a simple 5–7 question interview script tied to your tentative Core Promise.
For example:

1. “Tell me about the last time you tried to solve [Core Promise problem].”
2. “What triggered you to act on it then?”
3. “What have you already tried, and what happened?”
4. “What would a ‘no-brainer’ book on this topic do for you or your team?”
5. “What would make you immediately send that book to a colleague?”
6. “What would make you roll your eyes and close it?”
7. “Which words or phrases do you use when you talk about this problem internally?”

Run 10–15 short interviews on Zoom.
Record them, then use Otter.ai or similar to transcribe.
Tag recurring phrases, objections, and desired outcomes in Notion.

According to Intercom's 2022 Customer Research Report, teams that conduct regular qualitative interviews are 2x more likely to hit their product adoption targets.
The same pattern holds for books.
Founders who talk to readers before writing build sharper concepts and more useful structures.

Use the transcripts to refine your positioning statement and Core Promise.
Steal exact language for chapter titles and section headers.
If three CMOs call something “board-safe growth,” that phrase probably belongs on your cover more than your internal jargon.

Create a simple rubric.
If 70% or more of interviewees lean in, ask for early access, or forward the idea to a colleague, your concept is validated enough to move to a Table of Contents prototype.
If reactions are polite but flat, your idea is still in pre-product-market fit.

At Built&Written, we often run or structure these interviews for founders.
We turn raw transcripts into a problem map, then into a book angle.
The result is a manuscript plan that reads like a solution to a known pain, not a collection of thoughts.

---

From Vague Idea to Table of Contents Prototype: Design Your Minimum Viable Book

A table of contents prototype is a lightweight, provisional chapter list that maps the reader’s journey from their current problem to the promised outcome.

Your fourth step in the MVB Blueprint is the TOC Prototype.
This is not a final outline.
It is a testable structure.

A Problem–Solution–Proof chapter structure is a pattern where each chapter defines a specific problem, presents your framework or playbook as the solution, and then backs it with evidence like case studies or data.

Design each chapter as a mini journey.
Problem, then Solution, then Proof.
Readers stay because each chapter earns its pages.

The Minimum Viable Book Blueprint is a five-part process: Business Goal, Ideal Reader, Core Promise, TOC Prototype, and Recorded Drafts.

Here is a practical 8-chapter TOC Prototype for a SaaS founder book on churn-resistant onboarding:

1. The Hidden Cost of Bad Onboarding (why churn is baked in early)
2. Mapping Your Real Activation Moment (finding the true “aha”)
3. Designing a Friction Audit (identifying drop-off points)
4. Onboarding for Multi-Stakeholder Deals (enterprise nuance)
5. Product-Led Onboarding Experiments (what to test first)
6. Aligning Sales, CS, and Product Around Activation
7. Instrumentation and Metrics That Actually Predict Retention
8. Rolling Out a 30-Day Onboarding Overhaul

For each proposed chapter, run a quick checklist:

• What specific problem does this solve?
• Which IRP metric does it touch (ARR, churn, CAC payback, LTV, etc.)?
• What proof do you have (customer story, internal data, experiments, failures)?

Scope matters.
According to Bowker's 2023 Self-Publishing Report, the vast majority of non-fiction titles that sell at least 1,000 copies fall between 30,000 and 60,000 words.
For a founder, 35,000–50,000 words across 6–10 chapters is usually enough to establish authority and generate leads without taking three years to write.

Here is how a Minimum Viable Book compares to the two common extremes:

Approach	Pros	Cons
Minimum Viable Book	Faster to ship, focused on one clear outcome, easier to repurpose into talks and funnels	Requires saying no to side topics you enjoy
Bloated “Everything I Know”	Feels comprehensive to you, scratches ego itch	Slow to write, hard to market, readers rarely finish
Ultra-Short Manifesto	Quick to publish, good as a lead magnet	Often too thin to shift positioning or justify premium pricing

In our work, we treat the TOC Prototype as a contract between founder and manuscript.
Once agreed, it guides what to include or cut and how to repurpose content into talks, lead magnets, and LinkedIn posts.
You are no longer wrestling with a blank page; you are filling specific containers.

---

Talking Beats Typing: How to Turn Spoken Expertise Into Recorded Drafts

Recorded Drafts are raw chapter materials captured from spoken sessions, then transcribed and edited into written form.

The fifth step of the MVB Blueprint is Recorded Drafts.
Most founders are better at talking than typing.

Founder voice is the distinctive mix of stories, phrasing, metaphors, and opinions that makes a founder’s communication recognizably theirs.

Instead of forcing yourself to “sit down and write,” design a simple workflow:

1. Pick one chapter from your TOC Prototype.
2. Write 5–7 bullet prompts in Notion (Problem, Solution, Proof angles).
3. Record a 20–40 minute audio rant or guided interview using Loom, Zoom, or a podcast mic.

Use Otter.ai or another tool to transcribe the recording.
Import the transcript into Notion.
Tag sections as Problem, Solution, or Proof to match your chapter structure.

According to McKinsey's 2020 report “The Future of Work in Europe,” knowledge workers spend up to 28% of their time writing emails and messages.
You do not need more keyboard time.
You need to redirect some of that speaking and explaining into reusable book material.

You likely already have assets: sales calls, webinars, podcasts, internal Looms.
These can be mined for stories, frameworks, and language.
We routinely pull 10,000–20,000 words of usable material from a founder’s existing recordings before they “write” a single new sentence.

The obvious concern is voice and quality.
You do not want a generic, AI-flattened book that sounds like everyone else.
Handled correctly, an editor or AI partner should preserve your phrasing, metaphors, and stories while removing repetition and filler.

At Built&Written, we treat transcripts as source code.
We refactor, not rewrite from scratch.
The result is prose that sounds like you on your clearest day, not like a ghostwriter doing an impression.

To prove this works, here is a first recording script you can use within 24 hours:

• “What is the painful before state my reader is in for this chapter?”
• “What is the specific after state I want them to reach?”
• “Tell the story of one customer or internal project where we made that shift.”
• “List the 3–5 steps we took, as if I am training a new PM or marketer.”
• “What did we get wrong the first time?”
• “What metrics moved, and by how much?”

Talk through those prompts for 30 minutes.
You will likely generate 3,000–5,000 words of raw material.
The blank page problem disappears when you stop starting from a blank page.

---

How Long Should a Founder’s First Non-Fiction Book Be—and How Do You Actually Finish It?

A founder-proof workflow is a book creation process designed around a founder’s constraints, using batching, recording, and external support to reduce friction and context switching.

A lead-generation asset is a piece of content engineered to attract, qualify, and nurture potential customers toward a sales conversation.

For authority and lead generation, not royalties, a 35,000–50,000 word book is typically sufficient.
Short enough to be read on a flight.
Long enough to show depth and justify a serious engagement.

Break it down.
Eight chapters of roughly 4,500–6,000 words each.
Each chapter can come from 2–3 recorded sessions plus editing.

A realistic founder-proof cadence looks like this: one chapter every 3–4 weeks.
That gives you a full rough manuscript in 4–6 months, even alongside fundraising and launches.

Here is a simple four-week cycle per chapter:

• Week 1: Refine the chapter brief in Notion (problem, reader outcome, proof assets).
• Week 2: Record 2–3 sessions of 20–40 minutes each.
• Week 3: Transcript cleanup and structural edit into Problem–Solution–Proof sections.
• Week 4: Proof layer, add data, tighten stories, then get targeted feedback from 2–3 IRPs.

Deciding what to include or cut becomes mechanical.
If a story does not serve the Core Promise, IRP, and Business Goal, it becomes a blog post, talk, or lead magnet instead of cluttering the book.

According to Nielsen BookScan data summarized in Jane Friedman’s 2021 industry analysis, the median sales for non-fiction titles are low, but expert-authored niche books can drive outsized consulting and software revenue relative to unit sales.
You are not optimizing for royalties.
You are optimizing for the right 1,000 readers.

A partner like Built&Written can own the operational layer: the Notion workspace, interview scripts, deadlines, editing passes, and coordination.
You show up for recordings and key decisions.
The system handles the rest.

---

The Verdict

The uncomfortable truth is that the “blank page problem” is not a rare personal flaw; it is the default state for almost every serious founder who tries to write a book. The difference between those who ship and those who stall is not inspiration, it is a concrete starting system. When an entrepreneur doesn't know how to start a book, the only reliable fix is to replace vague intention with the MVB Blueprint: a defined business goal, a single ideal reader, a sharp Core Promise, a tested TOC Prototype, and a Recorded Drafts workflow that turns your existing conversations into chapters. In our experience at Built&Written, founders who adopt this structure stop asking “am I a good writer?” and start asking better questions like “which chapter will drive the most qualified leads this quarter?” You probably think you need more time, more talent, or a perfect idea before you begin; the evidence says you only need a clear blueprint and the discipline to follow it for a few focused months.

Key Takeaways

• Start your book with a measurable business goal and positioning statement, not a blank page or a vague desire to “share your story.”
• Build an Ideal Reader Profile as rigorously as an ICP so every chapter directly serves one high-value persona and their core metric.
• Define and validate a one-sentence Core Promise through customer development interviews before outlining, then use it to prevent scope creep.
• Design a table of contents prototype around a Problem–Solution–Proof structure, then fill chapters using Recorded Drafts from structured speaking sessions.
• Use a founder-proof workflow of one chapter per 3–4 weeks to reach a 35,000–50,000 word manuscript in 4–6 months without derailing your company.