A working first version lets you move from discussing the idea to watching someone use it. For the reporting tool, that means following an agency from uploading an export to using the finished report. Plan how you will reach those users and learn where the workflow still breaks down.
By the end of this guide
A small launch plan and a record of what users do after arriving.
01 / Choose the goal
What should the first users accomplish?
Choose one outcome for the release. A reporting product might need a user to import data, generate a report and use it with a client. Define that action before counting signups.
Invite people who fit the intended buyer. Offer help getting started, explain what is unfinished and make it easy to report a problem. You can learn from a small release without a large launch event.
- Arrival
- Where did the person come from, and are they the intended user?
- First useful result
- Did they finish the task you designed the release around?
- Return or commitment
- Did they use it again, ask to continue or pay for the result?
02 / Watch the work
Find the point where they get stuck.
Ask the first agency user to try their own export while you watch. Notice where they hesitate, which fields are missing and whether they still need to edit the report somewhere else. Get permission before recording the session.
Pair usage data with conversations. An abandoned import might mean the file format is unsupported, the sample data is confusing or the person has no real report to make. The event alone cannot explain it.
- Check that the core workflow and its error states work.
- Invite relevant users and watch their first attempt.
- Record the blocker and what you changed.
- Check whether the change helped the next user finish.
03 / Keep reaching buyers
Treat launch day as one channel.
Once you can observe that workflow, you can judge a launch channel by what it brings. A Product Hunt post might produce visits without reaching anyone preparing agency reports. An introduction in an agency community might bring fewer visitors but more people with the task. Record what happens rather than assuming either will work.
A traffic spike does not establish repeatable acquisition. Keep track of which channel brought the users who got value, and test how you could reach more people like them.
Tools for the task
Where to do this work
Start with the people you reached during discovery. A launch channel such as Product Hunt may broaden the audience if it fits your buyer; market research becomes useful again when feedback points to a different need.
Your next action
Invite users and follow the whole task.
Write down who you will invite, what they should be able to finish and how you will hear about problems. After each attempt, record the blocker and decide which change to test next.
0 of 3 ready
Sources and limits
These are practical recommendations drawn from the sources below. Founder accounts are retrospective, and vendor guides describe their authors' approaches. They do not establish a guaranteed result for your project.
Advice on early releases, measuring use and iterating with customers.
A vendor account of launch goals and outcomes. Its historical launch figures are self-reported examples.
An overview of outreach, communities and search. Channel results depend on the product and audience.