Telling the Why Behind Your Product
Story · 10 min read ·
Why you built it is the part of your story people remember. How to find your why, tell it in a paragraph, keep it honest and use it across your pages.
Ask a founder what their product does and they will tell you. Ask them why they built it and something changes. Their voice slows. They remember a specific day, a specific person, a specific irritation. That memory is often the most compelling thing about the product, and it is the thing they leave off the page.
Your why is not a slogan. It is the real reason, told simply. This guide shows how to find it, shape it and use it, honestly.
What the why is, and is not
A mission statement is, in the usual definition, a short statement of an organisation's purpose and aims. Many are vague and interchangeable. A why is something more particular: the story of the moment you decided to make this thing.
A why is:
- Specific. A moment, a person, a place.
- True. What actually happened.
- Human. Something another person can feel.
- Connected to the product. It explains why this exists in this form.
A why is not:
- A market analysis. "The market for X is growing" may be true but it is not a reason.
- A grand vision. "Changing the world" says nothing.
- An invention. If it did not happen, do not tell it.
- A sob story. You do not need hardship to have a reason.
Why it matters
People decide whether to trust a new product on thin evidence. A real reason is a kind of evidence: it shows that the founder knows the problem from experience, not from a slide. It also makes the product easier to describe and to remember. Few people recall a feature list; many recall "she built it because her grandmother could not use her phone".
A clear why also helps you. It keeps decisions honest: does this feature serve the reason we started? It helps a team stay aligned. And on bad days it reminds you why you are doing this at all.
Finding it
You may know your why already, or you may have to dig. Here are five prompts. Spend ten minutes on each, writing without editing.
- When did I first notice the problem? Describe the day, the place, what happened.
- Who did I see struggling with it? A colleague, a relative, yourself.
- What did I try first? The workaround, the tool that did not fit.
- What made me decide to build something? The moment of "someone should fix this".
- What did I hope would change? Not for the market, for a person.
Read what you wrote. Underline the sentences that surprise you or that you would not have said in a pitch. Those are usually the true ones.
Shaping it into a paragraph
Take the underlined material and write a paragraph of three to six sentences. A reliable shape:
- The scene: where and when you met the problem.
- The frustration: what was wrong, concretely.
- The turning point: what made you act.
- The result: what you built, in one line, and what you hope it does.
Keep it plain. Cut adjectives. Replace general statements with specifics: a number, a name (with permission), an object, a time.
Example: "Last spring my father had a fall and the care team asked me for a list of his medicines. I spent an evening reading faded labels and searching messages. Everything I needed existed, but in six different places. I built a small tool that keeps medicines, doctors and appointments in one list a family can share. It is not clever; it is the thing I wished I had that night."
That paragraph is under a hundred words and carries a whole story.
Test it
Read the paragraph to a friend and ask: do you believe it? Would you remember it? If they hesitate, ask which sentence felt false or empty and fix that sentence. Then read it to someone who does not know you. If they can repeat the gist an hour later, it works.
Check it against the facts. If your why involves a timeline, a number or another person, make sure it is right and that the other person is happy to be mentioned. Honesty matters here more than anywhere, because the story is part of your credibility. Google's guidance on helpful content asks pages to show who created the content and how they know what they say; a true personal reason is one of the clearest ways to show it.
Where to use it
The launch page: a short version, in your founder note, near the top.
The about page: the full paragraph, perhaps with more of the story.
Your listing: one line that captures the reason, if there is room.
Press and introductions: the elevator pitch, a short spoken description of a product or idea, can open with the why. A pitch that begins with a person and a problem is easier to follow than one that begins with a category.
Support and onboarding: a line in a welcome email reminding people of what the product is for.
Internal decisions: a poster on the wall. When in doubt, ask whether the choice serves the reason.
Keep the facts the same everywhere. The longer versions can add detail, but they should not contradict the short one.
Variations when the story is not personal
Not every product starts with a personal crisis. You may have built it because of a client's repeated request, a technical curiosity or a business opportunity you spotted. That is fine. The test is still truth and specificity.
- A client's request: "Three clients in a row asked me for the same report. I built it once, then put it online."
- A curiosity: "I wanted to see whether a browser could do this without a server. It could, and I could not stop."
- An observation: "I noticed that every small shop in my street had a handwritten sign about opening hours that changed each week."
Each is a real reason, and each is more interesting than "we saw a gap in the market".
What to avoid
- Exaggeration. "I almost lost everything" when you did not.
- Borrowed stories. Using someone else's experience as your own.
- Using other people's hardship as a marketing device.
- Over-polishing. A story with no rough edges feels fake.
- A different story each time. Pick a version and keep it consistent.
- Never updating. As the product grows, the why may deepen. Revisit it yearly.
A worked example
A founder building a tool for tracking houseplant watering has a why that begins as "I like plants and I like software". She tries the prompts and finds something more specific: after a long hospital stay, she came home to find her flat full of dead plants, many of them gifts. She wanted a way to ask a neighbour to look after them, and to keep a schedule they could both follow.
Her paragraph: "When I came home from a week in hospital, nearly every plant in my flat had died. Several had been gifts from people I love. I asked a neighbour to help me start again, and we kept the watering schedule on a scrap of paper that kept getting lost. I built a small app so that anyone can share a plant's schedule with whoever is helping. It is a modest thing, and I hope it saves a few plants."
She uses it on her launch page and her listing. Visitors mention the line about the neighbour. She did not invent anything; she simply told the true reason.
Questions founders ask
What if I have several reasons? Pick the one that came first, or the one you tell most easily. A story with one thread is stronger than a bundle of reasons. The others can appear on your about page.
What if the reason is embarrassing? Sometimes the honest reason is that you were annoyed by something small. That is fine. Small and true beats grand and false.
Can the why change? Yes. As you learn more about the people who use the product, your reasons may deepen or shift. Update the story and be honest about how it evolved.
Should I tell the story in every conversation? Not word for word. Use it as a base and adapt it to the person and the occasion. Keep the facts the same.
What if a co-founder has a different why? Ask each person to write theirs. Often the two are compatible, and showing both makes the story richer.
A fifteen-minute exercise to try today
Set a timer. For five minutes write the story of the first time you noticed the problem, in full sentences, as if telling a friend. For five minutes write what you did next. For five minutes cut it down to five sentences, keeping the most specific details. Read the result aloud. If you can say it without squirming, you have a why you can use. If you squirm, find the sentence that sounds like a pitch and replace it with what really happened.
Summary
Your why is the real reason your product exists, told simply. Find it with a few honest prompts, shape it into a short paragraph with a scene, a frustration, a turning point and a result, and test it with people. Use it consistently on your page, listing, about page and pitches. Keep it true, specific and human. A real reason is the part of your story that people will carry away.
Questions and answers
- What is the why behind a product?
- The real reason it exists: the problem you met, the frustration you could not ignore or the belief that drove you to build it.
- Do I need a dramatic story?
- No. Small, specific, true reasons are more convincing than dramatic ones.
- What if my reason is simply that it seemed like a good business?
- Say what you noticed about the market and why you care. Honest, practical reasons are fine.
- Where should the why appear?
- On the launch page in a short note, on the about page in more detail and in the description of your listing in one line.