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
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

Office MCP Server Setup

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

10 minutes
Intermediate
Developer Tools

PR Review Toolkit

Six specialist reviewers — comments, tests, error handling, type design, general quality, and simplification — each triggered by name or automatically based on what changed in the diff.

5 minutes
Intermediate
Developer Tools

Ralph Wiggum Autonomous Loop

Self-referential development loop that keeps Claude iterating on the same task until it hits a completion promise or an iteration cap — a Stop hook that blocks exit and re-feeds the same prompt.

5 minutes
Advanced
Developer Tools

Redesign Existing Projects: UI Audit and Upgrade

A design audit checklist that finds generic AI-look patterns in an existing codebase and fixes them without breaking functionality or migrating frameworks

10 minutes
Intermediate
Developer Tools

Prompt Optimizer (EARS)

Transform vague prompts into precise, well-structured specifications using EARS (Easy Approach to Requirements Syntax) — ideal for AI-generated code, products, and docs.

10 minutes
Intermediate
Developer Tools

Promptfoo Evaluation

Configure and run LLM evaluations with Promptfoo — build promptfooconfig.yaml, write Python custom assertions, implement llm-rubric judges, and compare models systematically.

15 minutes
Intermediate
Developer Tools

QA Expert

Establish a comprehensive QA process — test strategies, Google-standard test cases, P0–P4 bug tracking, quality metrics, OWASP security testing, and 90% coverage targets.

20 minutes
Advanced
Developer Tools

Repomix Safe Mixer

Package codebases with repomix while automatically detecting and removing hardcoded credentials before packing — so you never leak secrets when sharing code.

5 minutes
Beginner
Developer Tools

Repomix Unmixer

Extract files from repomix-packed repositories — restore the original directory structure from XML, Markdown, or JSON output, reversing the packing process.

5 minutes
Beginner
Developer Tools

Scientific Fluidsim

Framework for computational fluid dynamics simulations using Python. Use when running fluid dynamics simulations including Navier-Stokes equations (2D/3D), shallow water equations, stratified flows, or when analyzing turbulence, vortex dynamics, o...

15 minutes
Advanced
Developer Tools

Scientific Get Available Resources

This skill should be used at the start of any computationally intensive scientific task to detect and report available system resources (CPU cores, GPUs, memory, disk space). It creates a JSON file with resource information and strategic recommend...

5 minutes
Beginner

Browse all Developer Tools playbooks →