What to think about before, during, and after building your product
A founder’s working checklist for demand, scope, experience, data, costs, testing, launch, and the support that follows.
Make your decisions visible
A product accumulates decisions long before it accumulates customers. Write down what you know, what you assume, and what you need to test. For each item below, assign an owner, an unresolved question, and the smallest next action. A blank answer is useful if it exposes a risk early.
1. The person, the problem, and the alternative
Who needs this most? When does the problem occur? What do they do now? Why would they change? Include spreadsheets, manual work, a colleague, and doing nothing among the alternatives. Your competition is whatever currently gets the job done.
Evidence might include observed work, repeated support questions, a request for a pilot, or payment for a clearly described service. Separate those signals from likes, generic survey enthusiasm, and AI-generated opinions.
2. The promise and the boundary
Define one useful result and the full path to it. Write what the first version includes and excludes. Decide what happens when the user gives an empty input, changes their mind, or needs to correct the output.
For a feedback-summary tool, editing and copying a revision list may be essential. Team dashboards might wait. Ask whether a feature is necessary to complete the promised job or merely attractive on a roadmap.
3. The business model and running costs
List the possible price, how often someone needs the product, and what it costs to deliver. Include hosting, AI calls, storage, payment fees, support time, and any manual review. Check a quiet month and a busy month rather than budgeting only for your own usage.
Use a simple working calculation: revenue minus variable delivery costs equals contribution before fixed costs and your pay. If each additional customer creates hours of work, understand that constraint before promising unlimited service.
4. The experience and access needs
Can someone understand the promise, begin the task, finish it, and recover from a mistake? Test keyboard access, readable text, form labels, mobile layout, and useful error messages. Explain what saves automatically and what does not.
Define the first useful moment. It could be finishing a plan or exporting a reviewed list. Account creation is only a step toward value, not proof that someone received it.
5. Data, permissions, and ownership
Map what information enters the product, where it is stored, which services receive it, and who can access it. Collect what the task needs. Use sample data during development, keep secrets out of browser code, and test that one customer cannot see another customer’s work.
Know who owns the domain, repository, hosting account, design files, and customer export. Decide how users can request deletion and how you can restore a backup. Products handling sensitive or regulated information need appropriately qualified review before launch.
6. Reliability and a way to reverse changes
Test the main flow plus the failures that matter: unavailable services, duplicate submissions, unexpected input, and interrupted saves. For an AI feature, review a small set of representative examples, including cases where the correct behavior is to admit uncertainty.
Keep working checkpoints and a known recovery procedure. Identify who will notice an error, how you will reproduce it, and how you will tell affected customers. A successful build is one check among several.
7. Distribution, support, and the next decision
Choose a reachable audience and one launch channel. Show an honest example, explain the next action, and define what you will measure. Plan how people ask for help and how quickly you can reasonably respond.
At the end of a test, review qualified interest, completed tasks, useful outcomes, support effort, and repeat use at the product’s natural interval. Decide to continue, change, or pause based on those observations.
Start with the launch worksheet and AI build brief. If your product already attracts people but loses them before value, read about Waymaker Agency’s product and growth work.
Make your next step a real one.
Use a free worksheet to define your product, or explore the Two Mondays workshop for time to build with Ashley.