A week-long daily checklist that reveals accurate demand signals before you invest in production.

Every day, businesses invest weeks or months of work in products and services that the market does not want at the price being asked. This failure mode is not the result of bad ideas — it is the result of skipping validation. Validation is the process of testing whether the market will buy the product before building it, at a cost that is a tiny fraction of the build cost and in a timeframe that allows you to pivot before committing resources. For $1, this article gives you the one-week market validation checklist — seven days of specific, daily activities that produce accurate demand signals for any product or service idea, regardless of the sector or the business size.

The validation checklist is not about perfect information. It is about de-risking the decision to invest before the investment is made. Seven days of structured testing will not give you certainty — but it will give you enough signal to decide whether to proceed, pivot, or stop, with evidence rather than assumptions.

Spend day one confirming that the problem you are solving is real and acute. Talk to five people who match your target customer profile. Ask each one: 'How often do you experience [problem]?' and 'What have you already tried to solve it?' Acute problems are experienced frequently and have generated prior attempts at solutions. A problem that is mentioned reluctantly and has not been actively worked on is not sufficiently acute to drive purchase decisions.

Document the exact language your five interviewees use to describe the problem. This language is the foundation of your marketing copy — it is more accurate than any description you could write independently.

Ask the same five people: 'If I could reliably solve this problem for you, what would that solution be worth?' Do not suggest a price. Let them name the number. Record every number — both the amount and the certainty with which it was stated. 'I'd probably pay around £50' is a lower demand signal than 'I'd pay £200 without hesitation.'

Average the responses and identify the range. Your initial price should be at or slightly below the lower end of the range stated by the most enthusiastic respondents — not the average. The enthusiastic respondents are your launch customers.

Build a landing page in two days. It does not need to be beautiful — it needs to describe the problem, describe the solution, state the price, and include a purchase button. Use Gumroad, Stripe, or a simple Shopify page. The landing page is not for selling yet — it is for testing.

Share the landing page with a targeted audience: your own email list if you have one, a relevant online community, or a small paid social campaign. The target is 200-400 visitors within 48 hours. The metric you are measuring is the click-through rate on the purchase button — even if no purchase is completed yet.

Contact 20 people directly — by email, LinkedIn, or phone — with a personal message offering the product at a pre-sale discount. Not a broadcast message — a personal one, addressed to someone who matches your target profile. Your goal is three to five pre-sale purchases within 48 hours. Three purchases validates the demand. Zero purchases, after 20 personal contacts, is a clear signal that something in the offer needs to change.

If you get zero responses, diagnose before pivoting: is the problem real (go back to day one), is the price wrong (go back to day two), or is the offer unclear (rewrite the landing page)? Each failure mode has a specific fix.

On day seven, you have: five problem verification conversations, five willingness-to-pay data points, a landing page with click-through data, and a pre-sale attempt with results. Use these four inputs to make a binary decision: proceed (three or more pre-sales and clear willingness to pay in the right range), pivot (willingness to pay is there but the offer needs restructuring), or stop (no pre-sales and no clear willingness to pay signal).

Most validation rounds produce a pivot rather than a clean proceed or stop. That is the purpose of validation — not to confirm your initial hypothesis, but to give you the information needed to refine it before committing to the build.

Regardless of the outcome — proceed, pivot, or stop — document what the validation week revealed. What was the stated problem the market responded to most strongly? What price points generated the most willingness-to-pay? What format of the offer seemed most compelling?

This documentation is the foundation of your next iteration. A pivot based on documented validation learning is a precision adjustment. A pivot based on gut feeling is a fresh experiment with no baseline. The documented learning is what makes iteration faster and more efficient with each cycle.

Seven days of structured testing eliminates the primary failure mode of most new product launches: building something nobody will buy at the price you need to charge. The checklist costs nothing except the discipline to follow it.

—