scaccogatto Guide the user through turning their product idea into a manual process they can start delivering today — before writing a single line of code.
Core Principle
Processize before you productize. Every great product started as someone doing the work by hand. Gumroad started with Sahil collecting PayPal emails and sending payments to creators one by one. Your product should start the same way.
"Most apps on the internet are just forms and lists."
Your job right now is not to build software. It's to prove you can deliver value to real people, manually.
Step 1: What's the Product Idea?
Ask the user to describe what they want to build. Then strip it down:
- What is the one thing this product does for a customer?
- What does the customer have before they use it, and what do they have after?
- If you had to deliver this value with zero technology — just you, a phone, and a spreadsheet — how would you do it?
"Can I ship it in a weekend?" If not, reduce scope until you can.
Step 2: Who Needs This Today?
Connect the idea back to a real community:
- Who is already trying to solve this problem with a workaround?
- Where do these people hang out? (Online forum, Slack group, subreddit, local meetup)
- Can you name 10 specific people who have this problem right now?
If you can't name 10 people, you don't know your community well enough yet. Go back to find-community.
Step 3: Design the Manual Version
This is the heart of processizing. Walk through exactly how you'd deliver the product's value by hand:
- What does the customer give you? (An email, a file, a description of what they need)
- What do you do with it? (Every step, in order)
- What do you give back? (The deliverable)
- How long does it take you? (Per customer)
Before Gumroad was software, Sahil collected PayPal emails and paid creators one by one. The "product" was Sahil doing it manually.
Be specific. "I process their request" is not a step. "I open their email, copy the file link, run it through X, format the output, and email it back within 2 hours" is a step.
Step 4: Write the Magic Piece of Paper
Document your manual process so clearly that someone else could do it:
Write down every step you take on a piece of paper. This is your "magic piece of paper" — if you went on vacation, someone else could pick it up and keep the business running.
Your magic piece of paper should include:
- Trigger — What kicks off the process? (Customer emails you, fills out a form, sends a message)
- Steps — Numbered list of exactly what to do, in order
- Tools needed — What you use at each step (spreadsheet, email, phone, etc.)
- Time per customer — How long each step takes
- Handoff — How you deliver the result back to the customer
Step 5: Charge for It
"There is a massive difference between free and $1."
The zero price effect means free users give you zero signal. Charging even $1 proves someone values what you do.
- Set a price based on the time it takes you and the value to the customer
- Reach out to 3 people from your community this week
- Deliver the manual version and collect payment
- Every interaction teaches you something no amount of building would
Step 6: When to Productize
Only automate what you've proven works manually. Signs you're ready:
- You've delivered the manual version to 10+ paying customers
- You can predict exactly what they'll ask for
- The steps on your magic piece of paper haven't changed in weeks
- You're spending more time on delivery than on finding customers
Then — and only then — automate one step at a time. The first thing to automate is whatever takes you the most time per customer.
Output
Help the user create:
- A one-sentence description of what their product does manually
- The magic piece of paper — their full manual process, step by step
- A list of 3 specific people to deliver it to this week
- Their initial price point
- The first step they'll automate when they're ready (not now)