Minimum usable MVP tutorial
A week 3 tutorial for standardize delivery through one inspectable output.
When this is the right output
Use this once you know what users submit, wait for, and reuse.
Prepare before you start
- Delivery and feedback records from the first two weeks
- One repeated or costly step
- One quote, process, or boundary to clarify
Public case breakdown
How Photo AI turned an imperfect early product into paid demand
The public breakdown emphasizes that early outputs were imperfect, but users paid anyway. The founder then fixed bugs, improved quality, and added photo packs based on real usage.
Source
Indie Hackers Photo AI deep diveThe public deep dive says Photo AI reached about $5.4K MRR in week one and $100K+ MRR by month 18
Key moves
Sell a clear result
The offer was not an AI model; it was AI photoshoots and headshots.
Use paying-user feedback
Payment signals are stronger than free curiosity.
Ship continuously
Fix issues, add use cases, and improve output quality.
What to copy for a form MVP
The MVP can be manual
Users want the result, not your automated backend.
Do not validate free forever
Test small payment, prepayment, or repeat-use intent.
Distribution is the constraint
Without an audience, niche down or do direct outreach.
Safe small version
Collect inputs by form
Ask only for fields needed to produce the result.
Deliver manually 3 times
Record processing time, edits, and feedback.
Test a pilot price
Use a small paid pilot to decide whether to build.
Do not copy Photo AI's surface. Copy paid validation, iteration, and distribution discipline.
Build the first version
Find repeated actions
Review the first two weeks and find the most repeated, costly, or standardizable step.
Write the checklist
Document inputs, process, review rules, and delivery boundary.
Improve one step
Optimize the one step that most affects delivery before expanding scope.
Update the entry
Put the new boundary back into the page, quote, form, or delivery note.
Copy-ready templates
SOP opening
To make delivery repeatable, this process only turns [input] into [output] and does not cover [out-of-scope item] yet.
Boundary note
The client provides [material], I deliver [result], and human review is required at [review point].
How to decide the next step
Continue when
- Visitor-to-trial conversion exceeds 8%
- Users can complete first submission alone
- Manual review is limited to high-risk steps
Change direction when
- The process cannot be written as a checklist.
- There is no repeated-step evidence before automation.
- The scope keeps expanding and pricing gets harder to explain.
Return to the result after you finish this output
In week three, automate only the painful step and add a trial, booking, or paid-intent entry.