Validating a Product Idea Before Writing Code

Problem interviews done properly

The first mistake is pitching. Describe your idea and people will be kind, and kindness tells you nothing. Instead ask about the last time they had the problem: what they did, what it cost them, what they tried, what they pay for today. Listen for workarounds, because a spreadsheet, a WhatsApp group or a paid intern is proof the problem is real and already has a budget. Take notes on their words, not your interpretation, and stop each interview by asking who else has this problem. Fifteen conversations with the right people beat a survey of five hundred strangers.

Landing page and waitlist tests

A landing page tests whether the promise, written in your customer's words, makes strangers act. Describe the product as if it were available, state a price, and offer a button. What the button does is the design decision: an email waitlist is the weakest signal, a request for a demo is stronger, a pre-order with card details is strongest. Drive a small, targeted audience to it through a few hundred kronor of ads, a niche forum or a LinkedIn post, and read the numbers honestly. Under Swedish marketing law you must not take payment for something you cannot deliver, so a pre-order page needs to state clearly that it is a reservation and how refunds work.

Pre-sales and letters of intent

For B2B products the strongest validation is a sale before the product exists. Offer a founding-customer deal: a discounted first year, direct influence on the roadmap, in exchange for payment or a signed letter of intent with a start date. Some companies will refuse to pay for something unbuilt, which is fine; ask instead for a written commitment naming the budget owner. A few Swedish companies willing to sign are worth more than a hundred waitlist emails, and they become your design partners when you do build. Keep the pilot scope small enough to deliver by hand or with no-code tools if needed.

• Name a real price, not a placeholder; discounting from a stated price is fine, inventing it later is not.
• Ask for money or a signature, never for feedback, in the closing question.
• Write down every objection verbatim; three companies raising the same one is a requirement, not an opinion.
• Agree what a successful pilot looks like before it starts, in one measurable sentence.

Polite interest vs real demand

Sweden is a polite market, and that makes validation harder. People will say an idea is exciting, agree to a follow-up and then vanish. The way through is to score only behaviour that costs the other side something. An introduction to a colleague costs reputation. A second meeting with a decision-maker costs time. A deposit costs money. Enthusiasm in a first meeting costs nothing and predicts nothing. Keep a sheet with every contact and the most expensive thing they have done for you; if the column stays at compliments after a month, the demand is not there yet.

When to stop or pivot

Set the stopping rule before you start: a number of paying commitments by a date. Missing it does not always mean the idea is dead; it often means the customer, the problem or the price was wrong while one of the three was right. A pivot keeps what the evidence supported and changes the rest. If interviews confirmed the problem but nobody paid, the price or the buyer is wrong. If the page converted but interviews were flat, the promise is ahead of the product. When the evidence supports building, an MVP planning and architecture blueprint turns the validated scope into a buildable plan; the price is on our pricing page.

When you do not need this: if you are building a tool for your own company with a budget already approved, or a copy of a proven product for a market you already sell into, the demand question is answered and the risk is execution. Go straight to scoping. If you have validated and want to know what building would cost and take, book a short call and bring your interview notes.

Frequently asked questions