Appendices: Calendar, Prompts, Budget, and Legal
Appendix A: The 60-Day Calendar
Print this. Pin it to your wall. Check off each day as you complete it.
Week 1: Foundation (Days 1-7)
| Day | Focus | Key Tasks | Deliverable |
|---|---|---|---|
| Day 1 | Validation | Mine complaints on Reddit, G2, LinkedIn. Research 5+ competitors. | Pain point research notes |
| Day 2 | Validation | Define buyer profile. Validate willingness to pay. Write business case. | One-page business case |
| Day 3 | Infrastructure | Register domain on Cloudflare. Set up Google Workspace. Configure DNS, SPF, DKIM, DMARC. | Live domain + working email |
| Day 3-4 | Website | Write website spec. Generate copy with AI. Build site with Claude Code. | Website code ready |
| Day 5 | Website + Deploy | Polish website. Deploy to Cloudflare Pages. Set up analytics. | Live website at yourdomain.com |
| Day 5-6 | Distribution | Submit to 25+ marketplaces. Write and distribute press release. | 25+ directory listings |
| Day 7 | Distribution | Set up social profiles. Publish first week of content. Start email capture. | Active social presence |
Week 2: Build the MVP (Days 8-14)
| Day | Focus | Key Tasks | Deliverable |
|---|---|---|---|
| Day 8 | Spec + Scaffold | Write product spec. Generate project foundation with AI. Set up database. | Project scaffolded |
| Day 9 | Auth | Build authentication (signup, login, logout). Test end-to-end. | Working auth system |
| Day 10-11 | Core Feature | Build the primary feature. Focus on one thing. Iterate with AI. | Core feature working |
| Day 12 | Payments | Integrate Stripe (checkout, webhooks, customer portal). | Payment flow working |
| Day 13 | Polish | Loading states, error handling, empty states, mobile check. | Polished UX |
| Day 14 | Deploy + Test | Deploy to production. Full manual testing. Fix critical bugs. | Live product |
Week 3: Launch (Days 15-21)
| Day | Focus | Key Tasks | Deliverable |
|---|---|---|---|
| Day 15 | Soft Launch | Send to 5-10 friends. Fix bugs. Prepare launch assets. | Validated, stable product |
| Day 16 | Product Hunt | Launch on PH at 12:01 AM PT. Engage all day. Share on social. | PH listing live |
| Day 17 | Content Blitz | Publish "why I built this" post. Share on HN, Reddit, communities. | Content distributed |
| Day 18 | Email + Outreach | Email waitlist. Message LinkedIn connections. Reach out to bloggers. | Waitlist activated |
| Day 19 | Follow Up | Respond to all feedback. Follow up with trial users. Fix reported bugs. | Active user conversations |
| Day 20 | Analyze | Check metrics. Identify top channel. Plan outreach sprint. | Growth data collected |
| Day 21 | Convert | Focus on converting trial users. Personal outreach to most engaged users. | First paying customer(s) |
Weeks 4-5: Outreach Sprint (Days 22-35)
| Day | Focus | Key Tasks |
|---|---|---|
| Days 22-23 | Cold Email Setup | Build prospect list (200-300). Write email templates. Set up sending. |
| Days 24-28 | Outreach | Send 20-30 cold emails/day. 10 LinkedIn DMs/day. Engage in 3 communities. |
| Days 29-35 | Follow Up + Convert | Follow up on all outreach. Book demos. Convert trial users. Iterate product. |
Weeks 6-8: Scale (Days 36-60)
| Day | Focus | Key Tasks |
|---|---|---|
| Day 36 | Growth Audit | Analyze all channels. Identify top performers. Kill underperformers. |
| Days 37-42 | Content Engine | Publish 2 articles/week. 5 LinkedIn posts/week. 1 comparison page. |
| Days 43-49 | Outreach + Referrals | Continue email/LinkedIn outreach. Launch referral program. Seek partnerships. |
| Days 50-56 | Optimize | Pricing experiments. Onboarding automation. Conversion optimization. |
| Days 57-60 | Systematize | Document what works. Set up recurring processes. Plan month 3. |
Appendix B: Prompt Templates
These are the AI prompts referenced throughout the playbook, collected in one place for easy reference.
Problem Validation Prompts
Competitive Analysis:
I'm building a competitive analysis for [product idea].
Competitors: [list them]
For each competitor, identify:
1. Primary value proposition (one sentence)
2. Pricing model and tiers
3. What users praise in reviews
4. What users complain about in reviews
5. Features they lack that users request
6. Apparent go-to-market strategy
Then identify patterns: what do ALL competitors miss?
Where is the whitespace?
Pain Point Research:
I'm researching pain points in [industry/niche].
Analyze these sources and extract:
1. Top 5 most frequently mentioned frustrations
2. Workarounds people currently use
3. Price sensitivity signals
4. Specific quotes that capture the pain
5. Unmet needs no current tool addresses
Sources:
[Paste Reddit threads, review excerpts, etc.]
Website and Content Prompts
Homepage Copy:
Write homepage copy for [product name],
a [one-sentence description].
Target buyer: [buyer profile]
Structure:
1. Hero: headline (under 10 words), subheadline
(1-2 sentences), CTA
2. Problem: 3 pain points the buyer experiences
3. Solution: how the product solves each pain
4. Features: 4-5 with short descriptions
5. Social proof placeholder
6. Final CTA
Tone: [professional / friendly / technical]
Avoid: buzzwords, vague claims, superlatives
Focus: specific outcomes and benefits
White Paper:
Write a 2,500-word white paper on [topic].
Target audience: [buyer profile]
Tone: authoritative, data-driven, practical
Structure:
- Executive summary (150 words)
- Problem overview with data
- Current landscape analysis
- 3-5 key findings or insights
- Practical recommendations
- Conclusion
Include: data points, industry statistics,
actionable takeaways.
Do not include: product pitches, vague claims.
Blog Article:
Write a 1,500-word blog article on [topic].
Target keyword: [primary keyword]
Target audience: [buyer profile]
Tone: [your brand voice]
Structure:
- Compelling introduction (problem-focused)
- 3-5 main sections with H2 headings
- Practical examples or data in each section
- Conclusion with key takeaways
- FAQ section (5 questions) at the bottom
Include internal links to:
- [your product page URL]
- [your pricing page URL]
- [related blog post URL]
Comparison Page:
Write an honest comparison page:
"[Your Product] vs [Competitor]"
Target audience: [buyer profile searching for alternatives]
Structure:
- Quick summary table (features, pricing, pros, cons)
- Detailed comparison by category
- Who should choose [Your Product]
- Who should choose [Competitor]
- Final recommendation
Be honest. Acknowledge competitor strengths.
Highlight where we differ, not just where we are better.
Product Development Prompts
MVP Spec:
Build the foundation for this SaaS product:
[Paste your full product specification]
Generate:
1. Complete project structure
2. Database schema (migrations)
3. Authentication system
4. Basic dashboard layout
5. Stripe integration skeleton
6. Environment variable configuration
Tech stack: [your stack]
Make it production-ready. No placeholder logic.
Feature Implementation:
Build [feature name].
Input: [what the user provides]
Output: [what the user sees]
Edge cases to handle:
- [edge case 1]
- [edge case 2]
- [edge case 3]
Error handling:
- [how to handle failure scenario 1]
- [how to handle failure scenario 2]
Bug Fix:
Bug: [describe the bug in detail]
Expected behavior: [what should happen]
Actual behavior: [what actually happens]
Steps to reproduce: [step by step]
Relevant code: [paste the relevant code]
Error message (if any): [paste error]
Fix this bug and explain what caused it.
Sales and Outreach Prompts
Cold Email Personalization:
Write a personalized opening sentence for a cold email.
Recipient: [name, title, company]
Their LinkedIn/recent activity: [paste relevant info]
My product: [one-sentence description]
The opening should reference something specific
about them and naturally connect to the problem
my product solves. One sentence only.
Press Release:
Write a press release for the launch of [product].
Product: [one-sentence description]
Founder: [name and brief bio]
Website: [URL]
Key features: [3-5 features]
Target audience: [buyer profile]
Standard format: headline, sub-headline, city/date,
opening paragraph, problem, solution, founder quote,
features, availability, boilerplate, contact info.
Tone: professional, newsworthy, not salesy.
Include at least one industry trend or data point.
Support Response Draft:
Draft a response to this customer support email:
Customer email: [paste the email]
Product context: [brief description of your product
and the feature they are asking about]
Tone: helpful, friendly, concise
Include: the solution or next steps
If the issue requires investigation, acknowledge
the issue and give a timeline for resolution.
Appendix C: The $1,000 Budget Tracker
Copy this table and track your actual spending:
| Item | Budgeted | Actual | Date | Notes |
|---|---|---|---|---|
| Domain (.com) | $10 | Cloudflare Registrar | ||
| Google Workspace | $16 (2 months) | $8/month | ||
| Claude Pro | $40 (2 months) | $20/month | ||
| Gemini Advanced | $40 (2 months) | $20/month | ||
| Virtual phone | $20 (2 months) | $10/month (optional) | ||
| Press release | $200 | One-time (optional) | ||
| Cloud infrastructure | $10-40 | Monthly | ||
| AI API costs | $40-100 | Monthly | ||
| Miscellaneous | $25 | Buffer | ||
| Total Budget | $401-491 | |||
| Buffer Remaining | $509-599 |
Monthly Cost After Launch
Once you are past the initial 60 days, here is your expected monthly cost:
| Item | Monthly Cost | Annual Cost |
|---|---|---|
| Domain renewal | $0.83 | $10 |
| Google Workspace | $8 | $96 |
| Claude Pro | $20 | $240 |
| Cloud infrastructure | $5-25 | $60-300 |
| AI API costs | $20-50 | $240-600 |
| Total | $54-104/month | $646-1,246/year |
At $10K MRR, your operating margin is over 98%. That is the power of building on free and near-free infrastructure.
Appendix D: Legal Basics
Warning
This section provides general guidance, not legal advice. Consult a qualified attorney in your jurisdiction for specific legal questions. Laws vary significantly by country and region.
Do You Need an LLC or Corporation?
Short answer: Not immediately. In most jurisdictions, you can operate as a sole proprietor until you have meaningful revenue.
When to formalize:
- When you hit $5K MRR (enough revenue to justify the cost and admin)
- When you sign your first enterprise customer (they may require it)
- When you want liability protection (LLC separates personal and business assets)
Options:
- LLC (US): $50-500 depending on state. Simplest structure for a solo founder. Consider Delaware or Wyoming for favorable laws.
- Stripe Atlas: $500 to incorporate a Delaware C-Corp or LLC. Includes bank account, tax ID, and legal templates. Worth it if you are outside the US and want a US entity.
- Local equivalent: Most countries have a single-member limited company structure similar to a US LLC. Research your jurisdiction.
Terms of Service and Privacy Policy
You need both on your website before collecting user data or processing payments.
Use AI to draft initial versions:
Draft a Terms of Service for a SaaS product with
these characteristics:
- Product: [description]
- Pricing: [tiers]
- Free trial: [details]
- Data handling: [what data you collect and store]
- Jurisdiction: [your country/state]
Include standard sections: acceptance of terms,
account creation, payment terms, intellectual property,
limitation of liability, termination, dispute resolution.
Draft a Privacy Policy for a SaaS product:
- Product: [description]
- Data collected: [list all data types]
- Third-party services: [Stripe, Supabase, analytics]
- Cookie usage: [yes/no, what types]
- Data storage location: [country/region]
- User rights: [GDPR-applicable? CCPA-applicable?]
Include standard sections: data collection, usage,
sharing, security, retention, user rights,
contact information.
Note
AI-generated legal documents are a solid starting point, but they are not a substitute for legal review. Get a lawyer to review your Terms and Privacy Policy when you hit $5K MRR or sign your first enterprise customer. Until then, having AI-generated documents is much better than having nothing.
Tax Obligations
As soon as you earn revenue, you have tax obligations. The specifics depend entirely on your jurisdiction, but general principles:
- Keep records of all income and expenses from Day 1. Use a simple spreadsheet or QuickBooks (free for the first 30 days).
- Set aside 25-30% of revenue for taxes. This varies widely by location, but setting aside money from the start prevents a painful surprise at tax time.
- Sales tax / VAT. If you sell to consumers (not businesses), you may owe sales tax or VAT. Using a Merchant of Record (Lemon Squeezy, Paddle) handles this for you. Stripe does not handle tax collection by default, you need Stripe Tax or a separate solution.
- Consult a tax professional when you hit $3K-5K MRR. The cost of a one-hour consultation ($100-300) is negligible compared to the tax mistakes it prevents.
Intellectual Property
Your code: You own it. If you built it, you own the copyright. No registration needed (though registration strengthens your claim in disputes).
Your brand: Register a trademark when you can afford it ($250-350 in the US). Until then, using the TM symbol (not the registered symbol) signals your claim.
Open source: If you use open-source libraries (you will), respect their licenses. MIT and Apache 2.0 licenses allow commercial use. GPL licenses have stricter requirements. Check the license of every library you include.
AI-generated code: The legal landscape for AI-generated code ownership is still evolving. In practice, treat AI-generated code the same as code you wrote: review it, modify it, take ownership of it. The AI is a tool, like a compiler or an IDE.
Final Checklist
Before you close this book and start building, make sure you have:
- Read the full playbook (or at least Chapters 1-2 and 7-9)
- Identified a problem worth solving
- Validated willingness to pay
- Written your one-page business case
- Set aside $500-1,000 and 60 days of focused time
- Chosen your AI coding assistant(s)
- Bookmarked the tech stack reference (Chapter 11)
- Committed to a launch date (60 days from today)
The playbook is here. The tools are ready. The cost is minimal.
The only variable is you.
Go build something.