"A framework you have to reconstruct from memory every time you need it isn't a framework. It's a nice idea you had once."
Why This Chapter Exists
Every chapter in this handbook has introduced at least one structured template — the Problem Statement (Chapter 1), the Dork Session Log (Chapter 2), the Reddit Research Log (Chapter 3), and so on through Chapter 10's Master Validation Scorecard. This chapter collects all of them in one place so you have a single reference to copy from during active research, instead of flipping back through ten chapters to find the right table.
Nothing here is new theory. This is your working binder.
Discovery-Stage Templates
The Friction Log (Chapter 1)
Date
What I Observed
Who Experienced It
Tier (1-5)
Worth Researching?
The Problem Statement (Chapter 1)
PROBLEM STATEMENT
Who experiences this problem?
What are they trying to accomplish?
What currently stands in their way?
How do they cope with it today?
What is the cost of this problem?
What evidence do you have that this is real?
What tier is this problem? (1-5)
What would have to be true for someone to pay to solve this?
Search-Channel Templates
Dork Session Log (Chapter 2)
Query Used
Platform
Result URL
Pain Category
Tier (1-5)
Notes
Reddit Research Log (Chapter 3)
Subreddit
Thread Title
URL
Pain Category
Tier (1-5)
Quote (paraphrased)
Workaround Mentioned?
Recurring Question Log (Chapter 3)
Date of Post
Question Asked
Tools Mentioned
Complaint Attached to Each
Consensus Winner?
Hacker News Research Log (Chapter 4)
Thread Type (Show/Ask/Hiring)
Title
URL
Pain Category
Tier (1-5)
Key Comment (paraphrased)
Competitors Named
Who Is Hiring Log (Chapter 4)
Month
Company
Role
Stack Mentioned
Pain/Automation Language
Salary (if given)
GitHub Issues Research Log (Chapter 5)
Repo
Issue Title
URL
Label
Reactions
Age (open since)
State
Workaround Mentioned
Tier (1-5)
Competitive & Industry Templates
Competitor Teardown (Chapter 6)
COMPETITOR TEARDOWN
Company name:
Founded / funding stage:
Target customer (be specific):
PRICING
Entry price:
Enterprise price (if disclosed):
Pricing model:
FEATURE SET
Core features:
Notable gaps:
Recently shipped features:
CUSTOMER SENTIMENT
Average review rating:
Most common complaint theme:
Most common praise theme:
"Switched from" mentions:
GO-TO-MARKET
Primary acquisition channel:
Sales motion:
STRUCTURAL WEAKNESS
What segment do they serve poorly?
What would it cost them to fix that weakness?
Why haven't they fixed it already?
Competitor Comparison Matrix (Chapter 6)
Competitor A
Competitor B
Competitor C
Status Quo (workaround)
Your Opportunity
Target customer size
Entry price
Core strength
Core weakness
Top complaint theme
Underserved segment
Gap durability (1-5)
Review Analysis Log (Chapter 6)
Competitor
Platform
Rating
Segment
Top Dislike Theme
Switch-From/To Mentioned
Industry Playbook (Chapter 7)
INDUSTRY PLAYBOOK: [Industry Name]
1. WORKFLOW MAP
2. PAIN INVENTORY
3. EXISTING TOOLS LANDSCAPE
4. BUDGET AND BUYING PROCESS
5. REGULATORY AND COMPLIANCE CONTEXT
6. WHERE THIS INDUSTRY CONGREGATES ONLINE
7. INDUSTRY-SPECIFIC VOCABULARY
8. SEED QUERY LIBRARY
9. MVP HYPOTHESIS
Subject: Quick question about [specific workflow], not selling anything
Hi [Name],
I saw your [post/comment/thread] about [specific topic] and wanted
to reach out — I'm researching how [role] handle [general area] and
would love to hear about your experience if you have 15-20 minutes.
This isn't a sales call — I'm not launching anything yet, just trying
to understand the problem space properly before I do.
Would you be open to a quick call this week or next?
Thanks,
[Your name]
- [ ] Gate 1-5 all cleared (Ch. 10) with logged evidence for each
- [ ] MVP scope written, including human-in-the-loop design if
applicable (Ch. 8)
- [ ] Beachhead segment explicitly defined (Ch. 6)
- [ ] At least 1-3 design partners identified from your interview
pool (Ch. 9), ideally with a pricing commitment
- [ ] Distribution channel identified and tested
- [ ] Competitor monitoring set up (Competitor Tracker above)
Common Mistakes When Using Templates
Mistake 1: Treating a Template as a One-Time Form
Most of these are living logs, not one-off worksheets — the Dork Session Log, Reddit Research Log, and Competitor Tracker are all meant to be added to continuously, not filled out once.
Mistake 2: Skipping Fields That Feel Obvious
The "why" fields (Structural Weakness, Five Whys, root cause) are the ones people skip first under time pressure — and they're the fields that produce the actual insight. A partially filled template is worth less than it looks.
Mistake 3: Not Centralizing Templates in One Place
Keep all of these in a single connected workspace (a spreadsheet workbook or a linked notes system) so a finding in one log can be cross-referenced against another — this is how you catch patterns like "this complaint showed up in both Reddit and GitHub Issues."
Chapter 11 Checklist
Before moving to the Startup Idea Database in the final chapter, confirm you have:
Set up a working copy of the Master Validation Scorecard
Started a Competitor Tracker for your top 2-3 competitors
Adopted the Weekly Founder Research Review as an ongoing cadence
Confirmed a Launch Planning Checklist is ready for any opportunity that clears all five Validation Stage Gates