Output tutorial

Build a form-based MVP with a manual AI backend

Let users submit real inputs, deliver manually, and validate with repeat-use or prepayment signals.

Week 1 output Form-based MVP No signup required

Start with the steps Run my assessment

When this is the right output

Best for builders who can validate demand before writing a full product.

Prepare before you start

One single workflow problem
Three users willing to submit real material
A log for input, processing time, output, and feedback

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 dive

The 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

Define one workflow

Compress the product into one input and one output.

Build the form

Collect only fields required to produce a useful result.

Deliver manually

Use AI plus human review, then record time and edits.

Decide what to build

Automate only after repeat use, prepayment, or referral intent appears.

Copy-ready templates

Form note

This is an early MVP. I will process your material manually and return the result to test whether it deserves a product.

Feedback questions

Would you use this again? Would you pay per use, per month, or per project? What keeps the result from being used at work?

How to decide the next step

Continue when

Three users submit real material
At least one user wants to reuse or prepay
Users are willing to wait for the result

Change direction when

Users avoid submitting real material
No repeat-use intent after delivery
Processing cost is too high for a lightweight product

Tool choices for this output

Tally: forms and surveys

Use: Build the MVP input form

Alternative: Google Forms

Open tool

Make: automation workflows

Use: Automate validated steps

Alternative: Manual SOP

Open tool

Webflow: landing page builder

Use: Publish waitlist and paid-intent page

Alternative: Framer or Carrd

Open tool

Return to the result after you finish this output

Do not build login or admin first. Build an intake form, manual processing flow, and collect 3 real inputs.