FIELD GUIDE 02 · BUILD TO LEARN
A practical chapter for independent and aspiring founders building niche B2B SaaS. Turn a specific buyer problem into a small first version, choose a build path you can maintain, and use manual work where software is not needed yet.
Work from a real buyer’s example
STEP 01 · SCOPE THE CORE
Start with a recent example from the niche-validation work. Describe what the buyer does today, then reduce it to one path you can support end to end.
Start with a specific trigger in the buyer’s work: a request arrives, a job is scheduled, a document needs review, or a decision is due.
When [trigger] happens, [role] needs to [job] so [useful outcome].
Write down the information that comes in, the important action, the result the person needs, and any handoff. Follow one ordinary case before designing edge cases.
What is the first step, what changes, and how does the person know the job is done?
Mark which step needs software to reduce the friction you observed. Leave adjacent jobs, broad reporting, role systems, and polish out unless the core job cannot work without them.
If this one step worked reliably, what would the buyer be able to do next?
Describe what a complete first version must let a person do, and what it will not handle yet. This gives you a boundary when new requests arrive.
The first version is useful when [person] can [complete task]. It does not yet [out-of-scope job].
A QUICK SCOPE CHECK
The minimum steps needed for one person to complete the chosen job.
Other roles, workflows, and edge cases that do not block that job.
STEP 02 · CHOOSE A BUILD PATH
No-code and a familiar stack can both be reasonable starting points. Choose by the workflow, your current skills, and how you expect to change the first version.
Prompt: Can I demonstrate the whole chosen job without adding custom code for its important steps?
Prompt: What is the smallest version I can finish without first building a platform?
If neither option supports the essential step safely, narrow the workflow or learn only the missing piece. Do not choose a stack because it sounds more serious.
STEP 03 · WORK AROUND THE GAP
A first version can combine software with founder effort. A manual step can help you learn whether the workflow is useful before you automate it. Be clear with the buyer about what happens behind the scenes.
If an import is not ready, copy a small agreed set of records into the tool with the buyer’s permission. Note what was copied and what still needs review.
A founder can prepare a report, reconcile an exception, or route a request behind the scenes while the user sees the useful result. Tell them which work is manual and what turnaround to expect.
A spreadsheet, email, or calendar can bridge a gap during a small trial. Keep a record of the handoffs and avoid storing sensitive information in a tool that is not appropriate for it.
KEEP A SIMPLE WORK LOG
For each manual handoff, record the workflow step, who owns it, what is waiting, and what happened next. Review the notes before deciding which step to automate.
A GROUNDED NEXT STEP
Ask them to try the real task. Watch where they pause, note what you had to do manually, and separate what you observed from what you still need to test.