How to Validate Your Expertise Before You Build Anything

Desire is when a prospect nods and says your idea sounds great. Demand is when they open their wallet, rearrange their calendar, or push a competing priority aside.

They feel identical in a conversation. They behave completely differently in a market.

Validation is the discipline of telling them apart before you build. Signals of desire — polite enthusiasm, form fills, likes, waitlist signups — cost the prospect nothing, so they mean nothing on their own. Signals of demand — money, a booked call, a signed pilot, a written commitment, a public referral — cost something, so they mean everything.

Every Nordic Assistant validation exercise is designed to force the cost onto the prospect. If they will not pay any cost, you do not have demand. You have interest. Do not build on interest.

A problem is worth building on when all of these are true:

• Frequent enough. It recurs in the customer's life or work — monthly or more. One-off problems rarely sustain a business.
• Painful enough. They can describe the cost of not solving it — missed revenue, lost time, embarrassment, risk — without prompting.
• Concrete enough. The problem has an edge. "Growing my business" is not a problem; "getting past €10k months" is.
• Alternatives are unsatisfactory. They've tried something. It didn't work well enough. They can tell you why.
• Solvable by expertise. The bottleneck is knowledge, judgement, or method — not capital, headcount, or luck.

When a candidate problem fails two or more of these, it is not the wrong problem to care about — it is the wrong problem to build on. Reframe until it passes, or pick a different problem.

Write a one-paragraph description of the offer and ask ten people in the target audience: would you pay for this today? A "yes, here is my card" beats any survey. Anything softer is not validation.

Ask these before you commit to building anything. Answer honestly.

1. Have five specific people already told me — in their own words — that this is a problem? Not "in general." Named individuals.

2. What are they currently doing about it? If the answer is "nothing," the problem is not urgent enough to sell.

3. Have any of them paid to solve it before? Money in the past predicts money in the future. If nobody has ever paid anyone for this, be cautious.

4. Will three of them pay me now, at a real price, before I build it? Pre-sale is the only unambiguous validation.

5. Can I describe the buyer, their trigger moment, and their alternative in one sentence each? If not, the offer is not sharp enough to sell.

At least four "yes" answers before you build. Fewer means you're validating on the way, not before.

Not all evidence is equal. Rank the signals you gather.

Proxy signals — search volume, forum threads, competitor products, book sales in the category. Cheap to gather, easy to over-read. Prove that a market exists; prove nothing about whether your offer sells.

Direct signals — customer interviews, structured discovery calls, survey answers from people who match your buyer profile. Reveal language, urgency, and alternatives. Still costless for the prospect, so still not proof of demand.

Wallet signals — pre-orders, paid pilots, booked-and-paid discovery, letters of intent with money attached, deposits. The only signals that translate reliably into revenue.

Build the case in that order: proxy to know the market is real, direct to know the buyer, wallet to know they'll actually pay you. Skipping to wallet without the first two wastes prospects; stopping before wallet wastes months of building.

Likes, replies and "sounds great" are interest signals, not validation. Validation is money, a signed intent, or a booked call with a deposit. Track those, ignore the rest.