Home
cd ../playbooks
Developer ToolsBeginner

Minimalist MVP Scoping

Scope a weekend-shippable MVP using the manual → processized → productized progression. Build as little as possible; charge from day one.

5 minutes
By communitySource
#mvp#product-scoping#no-code#weekend-build#minimalist-entrepreneur#sahil-lavingia

Most 'MVPs' are still 3-month builds with five features and a splash page. The minimalist version does one thing, ships in a weekend, and charges money from customer #1.

Who it's for: first-time founders, indie hackers, weekend builders, makers drowning in scope, no-coders scoping their first product

Example

"Here's my product idea — help me scope an MVP" → The single thing it does, simplest possible implementation (manual/no-code/minimal code), what you can ship this weekend, initial price, and feedback loop

CLAUDE.md Template

New here? 3-minute setup guide → | Already set up? Copy the template below.

---
name: mvp
description: Guide building a minimum viable product the minimalist entrepreneur way — manual first, then processized, then productized. Use when someone is ready to build their first product or struggling with scope.
---

You are a business advisor channeling the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user build their MVP with maximum constraints and minimum effort.

## Core Principle

**Build as little as possible.** The goal is to start delivering value to your community as quickly as possible. Not to build something beautiful, polished, or complete.

## The Three Stages

### Stage 1: Manual (Do it yourself)
- Solve the problem by hand for each customer
- You are the product. You are customer service, fulfillment, and engineering
- Write down every step you take — this becomes your process
- Example: Before Gumroad automated payouts, Sahil collected PayPal emails and sent payments manually, one by one

### Stage 2: Processized (Systematize the manual work)
- Document your process on a piece of paper so anyone could do it
- If you go on vacation, someone else can take over
- You've built a system for working efficiently with each customer
- This is your "magic piece of paper"

### Stage 3: Productized (Automate the process)
- Now automate each task so customers can use your product without you
- This is when you actually build software or a product
- Only build what you've already proven works manually

## The Four Build Questions

Before building anything, answer:
1. **Can I ship it in a weekend?** If not, reduce scope until you can.
2. **Is it making my customers' life a little better?** That's the bar for MVP.
3. **Is a customer willing to pay for it?** Be profitable from day one.
4. **Can I get feedback quickly?** Build for people who can tell you if it's working.

## What to Build

Most apps on the internet are just **forms and lists** (CRUD: Create, Read, Update, Delete). Your MVP should be no more complex than that.

For your MVP:
- **One thing.** Your product does one thing, at first.
- **No polish.** It doesn't need to be pretty. CraigsList has never been pretty.
- **Charge money.** There's a huge difference between free and $1 (the zero price effect). Charge something.
- **Use existing tools.** Use Carrd, Gumroad, Stripe, Airtable, Google Forms, Zapier, Notion — whatever gets you to market fastest. Every business is tech-enabled now.

## What NOT to Build

- Don't build features you think you'll need "someday"
- Don't build for scale — you don't have scale problems yet
- Don't build a mobile app when a website works
- Don't write code when a spreadsheet works
- Don't hire an engineer when you can use no-code tools

## Ship Early and Often

- You will be wrong. The goal is to get less wrong as quickly as possible
- Gumroad has never shipped a "v2" — just thousands of incremental improvements over many years
- Each time you ship, you cross the threshold from "I may want this later" to "I need this now" for some customer
- Your goal is to move away from being paid directly for your time

## Essentials Checklist

Before you launch:
- [ ] Name your business (two real words combined > made-up word; pass the "radio test")
- [ ] Buy a domain (~$10/year)
- [ ] Build a simple website (Carrd, Gumroad, or similar)
- [ ] Create social media accounts (personal + business)
- [ ] Set up payments (Stripe or Square — 2.9% + 30¢ per transaction)
- [ ] Create an email for customer communication

## Output

Help the user define:
1. The single thing their MVP does
2. The simplest possible implementation (manual, no-code, or minimal code)
3. What they can ship this weekend
4. Their initial price point
5. How they'll collect feedback

Get new playbooks like this one

One email a week with new Claude Code workflows. Free, like everything here.

No spam. Unsubscribe anytime.

README.md

What This Does

A scoping skill that forces radical constraints on MVP scope. It runs your idea through:

The Four Build Questions

  1. Can I ship it in a weekend? If not, reduce scope.
  2. Is it making my customers' life a little better? That's the bar.
  3. Is a customer willing to pay? Profitable from day one.
  4. Can I get feedback quickly? Build for people who can tell you it's working.

The Three Stages

  1. Manual — you are the product
  2. Processized — the "magic piece of paper" anyone could follow
  3. Productized — only now do you automate

Quick Start

Step 1: Download the template

Click Download above for the CLAUDE.md.

Step 2: Save into your product folder

Drop it alongside your roadmap, specs, or just a notes folder.

Step 3: Scope the MVP

Ask Claude: "Scope a minimalist MVP for this idea: [idea]." You'll get the single-thing definition, simplest implementation path, weekend-shippable plan, price, and feedback loop.

What to Build

Most apps on the internet are just forms and lists (CRUD). Your MVP should be no more complex than that. Use existing tools: Carrd, Gumroad, Stripe, Airtable, Google Forms, Zapier, Notion.

What NOT to Build

  • Features you think you'll need "someday"
  • For scale — you don't have scale problems yet
  • A mobile app when a website works
  • Code when a spreadsheet works
  • An engineer when no-code works

Pre-Launch Essentials

  • Name (two real words > made-up, pass the "radio test")
  • Domain (~$10/year)
  • Simple site (Carrd, Gumroad, or similar)
  • Personal + business social accounts
  • Payments (Stripe or Square, 2.9% + 30¢)
  • Customer-comms email

Who Should Use This

First-time founders who keep redesigning instead of shipping, weekend builders whose "MVPs" have seven features, no-coders looking for permission to ship something rough, and anyone who read "Gumroad never shipped a v2" and wants to operate that way.

$Related Playbooks

Developer Tools

n8n Workflow Builder

Automate document workflows with n8n - 7800+ workflow templates

10 minutes
Advanced
Developer Tools

Nuxt UI Component Guidance

Build interfaces correctly with @nuxt/ui v4 — five core rules (UApp wrapper, semantic colors, reading generated theme files for real slot names, override priority, icon naming), a task-to-focus-area routing table, the Nuxt UI MCP server for live component API lookups, and full installation for both Nuxt and standalone Vue.

5 minutes
Beginner
Developer Tools

Office MCP Server Setup

MCP server with 39 tools for Word, Excel, PowerPoint, PDF, OCR operations

10 minutes
Intermediate
Developer Tools

Tech Debt Analyzer

Identify, analyze, document, and track technical debt in JavaScript/TypeScript codebases with automated detection and prioritized remediation plans.

10 minutes
Intermediate
Developer Tools

Test Specialist

Comprehensive JavaScript/TypeScript testing guidance with test writing, bug analysis, coverage analysis, and proactive issue detection.

10 minutes
Intermediate
Developer Tools

Accessibility Engineering for Components

Build accessible UI components at the code level, not just the audit level — 14 concrete engineering principles (focus-visible over bare :focus, roving tabindex for composite widgets, inert-based modal focus trapping, WCAG 2.5.8 hit-area minimums), a common-mistakes table with fixes, and a severity-rated review format ending in a hard Block/Needs-changes/Approve verdict.

5 minutes
Intermediate
Developer Tools

Adversary Emulation: MuddyWater

An intelligence-grounded, authorized purple-team emulation profile for MuddyWater (MITRE ATT&CK G0069), Iran's MOIS-linked cyber-espionage group — attribution, targeting, representative TTPs by ATT&CK tactic, emulation guidance mapped to generic red-team tooling, and paired detection/defense recommendations for every offensive technique, all under an explicit authorized-use caveat.

15 minutes
Advanced
Developer Tools

Adversary Emulation: Turla

An intelligence-grounded, authorized purple-team emulation profile for Turla (MITRE ATT&CK G0010), Russia's FSB-linked espionage group — attribution, distinctive TTPs (satellite C2 hijacking, steganographic email backdoors, parasitizing rival APT infrastructure), emulation guidance mapped to generic red-team tooling, and paired detection recommendations, under an explicit authorized-use and lab-only caveat for rootkit techniques.

15 minutes
Advanced
Developer Tools

AI Agent Red Team Methodology

A first-principles methodology for authorized red-team exercises against AI products, agents, MCP servers, skills, and repositories — capability and trust-boundary modeling, AI-specific attack hypothesis families (prompt injection, tool misuse, data leakage, SSRF), harmless-proof testing with canaries, one-variable-at-a-time adaptive iteration, and business-language evidence-based reporting.

10 minutes
Advanced
Developer Tools

Contribution PR Review

Review an external contributor's PR the way an open-source maintainer should — check automated bot security findings first (across every channel they might post to), watch specifically for suspicious AGENTS.md or workflow-permission changes, scale size and test-coverage expectations by contributor experience, and separate intent/scope alignment from code quality that bots already covered.

10 minutes
Intermediate
Developer Tools

Datadog Error Triage to PR

Take Datadog Error Tracking issues from raw occurrence counts to a reviewable, tested PR — a five-class bug taxonomy that filters out infra noise and deploy-skew before ranking, a recency premium that catches fresh regressions early, a mandatory approval gate before any fix is written, and a test-first fix workflow that generalizes past the one reported occurrence.

10 minutes
Advanced
Developer Tools

React Native Video (v6 & v7)

Give correct react-native-video guidance by detecting the installed major version first — v6's imperative <Video> component and v7's completely different useVideoPlayer/VideoView player-object model share a name but no API, and mixing them up is the single most common mistake when helping with this library.

5 minutes
Intermediate

Browse all Developer Tools playbooks →