Skip to content
Skills Library
Management & product · Planning

processize

/processize

Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.

Repository
superpowers ↗
Licence
MIT
Last repository change
15.05.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 15.05.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.

Original author description

Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.

How it works

  1. Core Principle
  2. Step 1: What's the Product Idea?
  3. Step 2: Who Needs This Today?
  4. Step 3: Design the Manual Version
  5. Step 4: Write the Magic Piece of Paper
  6. Step 5: Charge for It
  7. Step 6: When to Productize
  8. Output
Original SKILL.md headings · 88 lines, 755 words
SKILL.md preview
---
name: processize
description: Turn a product idea into a manual-first process you can start delivering today. Use when you have an idea and want to figure out how to deliver value by hand before writing any code.
---

You are a business advisor channeling the philosophy of The Minimalist Entrepreneur by Sahil Lavingia. Help the user turn their product idea into a manual process they can start delivering today - before they write 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:
1. **Trigger** - What kicks off the process? (Customer emails you, fills out a form, sends a message)
2. **Steps** - Numbered list of exactly what to do, in order
3. **Tools needed** - What you use at each step (spreadsheet, email, phone, etc.)
4. **Time per customer** - How long each step takes
5. **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:
1. A one-sentence description of what their product does manually
2. The magic piece of paper - their full manual process, step by step
3. A list of 3 specific people to deliver it to this week
4. Their initial price point
5. The first step they'll automate when they're ready (not now)

Versions

The database has no other skills named processize.

Identical content appears in 2 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version f417dad7e16e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 92writing-plans
    当你有规格说明或需求用于多步骤任务时使用,在动手写代码之前
  • 92writing-plans
    当你有规格说明或需求用于多步骤任务时使用,在动手写代码之前
  • 90intent-discovery
    Turning a new feature or product idea into a decided direction before any plan or code. Use when the user wants to build, add or launch something new and non-trivial (a feature, system, dashboard) and the why or the shape is open, in any language.
  • 100write-spec
    Use when asked to write, draft or start a spec for a change that already has an intent document, before any code exists.
  • 100validate-idea
    Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.
  • 86d2s-frame
    Stage 1 (frame) of a discovery-to-spec design exploration. Turns a feature request, idea or stakeholder ask into a one-page brief covering the problem, who it matters to, where it lives in the product today, the desired outcome, the appetite and the no-gos. Use whenever someone…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.