Module 2 of 9 · 18 minutes
Set the vision
A one-page pitch memo that a stranger can read once and explain back to you.
What a vision is for
The goal of this module is to help you choose a problem worth years of your life, describe it so precisely that a stranger understands it in one read, and turn it into a one-page pitch memo you can send to anyone.
A vision is not a slogan. It's a short, specific statement of who you serve, what problem you solve for them and what changes if you succeed. A useful vision does three jobs:
- It helps you decide. When a feature request or partnership comes along, you can check it against the vision instead of arguing about taste.
- It helps you recruit. People join early companies because they understand where the company is going and want to help it get there.
- It helps you explain. Customers, partners, family and, if you choose to raise money, investors all need to grasp what you do without a 20-minute conversation.
"Empowering businesses through technology" does none of these jobs, because it could describe almost any company. Before you read on, write one sentence describing what your company does. You'll come back to it later in this module.
Choose a problem worth years of your life
Building a company usually takes many years, and most startups fail along the way. Choose a problem you'll still care about when progress is slow and money is tight. Excitement about a product idea tends to fade; caring about a group of people and what goes wrong for them tends to last.
Before you commit, put the problem through five questions:
- Do you know it from the inside? Have you worked in this field, lived with the problem or spent real time with people who have it? If not, can you get close to it quickly?
- Is it frequent and costly? A problem that happens every week and costs money, hours or risk is easier to build on than an annoyance that comes up once a year.
- Are people already working around it? Paper lists, spreadsheets, an extra employee, a clumsy tool they pay for: workarounds show the pain is real. "Nobody has tried to solve this" more often means nobody cares than that you've found a gap.
- Can you reach the people who have it? If you can't say where you'd find 10 of them this month, every later step gets harder.
- Is it the right size for what you want? Some problems can support a good, profitable small business; others might support a very large company. Both are valid, but they lead to different choices, including whether outside investment makes sense at all.
Be wary of starting with a technology and hunting for a use. "Something with AI in healthcare" is a solution looking for a problem. Start with people and their problem instead.
Be careful with success stories, too. You hear about the companies that worked, not the many that did the same things and disappeared. This is called survivorship bias, and it can make almost any idea look promising.
A former pharmacy assistant remembers that the small pharmacy where she worked threw away expired medicine every month, because expiry dates were checked by hand against a paper list. She saw the problem weekly, knows roughly what it cost and can name a dozen pharmacists who would take her call. That's a far stronger starting point than a social app for pet owners, which she finds fun but knows nothing about.
Describe the customer and the pain precisely
Vague customers lead to vague products. "Small businesses", "millennials" and "anyone who wants to save time" are categories, not customers: too broad to find, talk to or design for. A precise description names the role, the setting and the situation:
- Vague: "Healthcare businesses."
- Precise: "Owners of independent pharmacies with one to three branches who order their own stock."
Test your description by asking whether you could find 10 of these people this week. If you couldn't, narrow it.
Check, too, whether the person who uses your product is the person who pays. In a pharmacy, an assistant might use the tool every day while the owner pays for it and an accountant influences the decision. Write all three down.
Then describe the pain. A precise pain statement covers four things:
- What happens today, in concrete terms.
- How often it happens.
- What it costs in money, time, risk, stress or lost customers.
- What people do about it now, and why that falls short.
Instead of "pharmacies struggle with inventory", you might write:
Once a month, a staff member spends most of a day checking expiry dates by hand. Medicine still expires on the shelves, and the owners we spoke to say they throw away roughly a full day's sales in stock each month. Most track dates on paper. A few tried a spreadsheet and stopped updating it within weeks.
Use your customers' words rather than your own jargon. If they say "stock goes out of date", don't write "suboptimal inventory lifecycle management". And if you can't yet describe the pain this precisely, that tells you something useful: you need more conversations with customers, which is what the next module covers.
Why now, in words a stranger understands
Anyone reading about your idea will quietly wonder why nobody has done it already. Your "why now" answers that by naming a specific change that makes your solution possible, cheaper or more necessary than it was a few years ago. It usually comes from one of four places:
- Technology or cost: something that was expensive or impossible is now cheap and common.
- Rules: a new regulation creates a requirement, or an old restriction is lifted.
- Behavior: customers now do something routinely that they didn't before, such as paying by phone.
- Market shifts: a big supplier leaves, prices jump or a new group of customers appears.
A good why-now is specific to your customer. "AI keeps improving" is true for every company, so it explains nothing. "Since last year, every medicine pack sold in our country carries a scannable code that includes its expiry date, so a phone camera can log a whole shelf in minutes" explains exactly why the pharmacy tool works now and wouldn't have before. If there's no clear why-now, you need another honest answer, such as that the problem is unglamorous or needs insider knowledge most builders lack.
With that in place, rewrite the sentence you wrote at the start as a vision a stranger understands in one read. In one or two sentences, name the customer, the change in their life and, if you like, where it leads. Cut words that sound impressive but say little, such as platform, ecosystem, seamless and next-generation.
- Weak: "An AI-powered platform revolutionizing pharmaceutical inventory."
- Clear: "We help small pharmacies stop throwing away expired medicine. In time, we want every independent pharmacy to manage stock as precisely as the big chains do."
To test it, give it to someone outside your industry, let them read it once and ask them to explain it back. If they can't, rewrite it. You know your subject so well that it's hard to remember what others don't know, a trap called the curse of knowledge.
The one-page pitch memo
A pitch memo is a single page of plain writing, under short headings, that explains your company to someone who has never heard of it. It's meant to be forwarded, read in a few minutes and understood without you there.
It differs from a slide deck in a useful way. Slides are usually made to accompany a talk, so they can skip the reasoning between bullet points and still look finished. A memo has to work in full sentences, which makes gaps in your thinking hard to hide. Many founders find it easier to write the memo first and make slides from it later, if they need slides at all. A memo also suits more readers: a possible co-founder, an adviser, a partner, a grant committee and, if you decide to raise, an investor.
The sections, each two to four sentences long:
- Company and one-line description: who it's for and what it does.
- Problem: what happens today, how often and what it costs.
- Customer: precise enough to find, including who pays.
- Solution: what the customer does with your product and the result they get.
- Why now: the specific change.
- Traction or evidence so far: only what's true today, with numbers.
- Market and business model: how you charge, plus a bottom-up estimate of the market, meaning roughly how many customers you could realistically reach multiplied by what each would pay in a year.
- Team: who you are and why you're suited to this problem.
- The ask: one concrete request, and the milestone it helps you reach.
Common mistakes to avoid:
- running to two or three pages
- describing the technology before the problem
- a customer described as "everyone"
- top-down claims like "if we win just 1% of a huge market", which show no idea of how you'd reach anyone
- saying you have no competitors, when there's always an alternative, even if it's a spreadsheet or doing nothing
- counting compliments as traction
- ending without a clear request
If you use the memo to raise money, be aware that many countries restrict how and to whom you can offer an investment, so talk to a lawyer before sending a fundraising memo widely or posting it publicly. Many good companies never raise at all, and the memo is just as useful for recruiting, partnerships and your own clarity.
Do the work
Fill in the pitch memo builder at the end of this module, in this order rather than top to bottom:
- The customer and problem, using what you've actually seen and heard.
- The solution and why now.
- Evidence, market and business model, team and the ask.
- The one-line description last, once you know what the memo says.
Keep every section short. The finished memo should fit on one printed page, roughly 400 to 600 words. Where you have no evidence yet, say so and add what you're testing next. An honest "12 interviews booked for this month" reads far better than an inflated claim.
You're done when two people outside your industry have each read the memo once and can tell you, in their own words, who it's for, what problem it solves and what you're asking for. Wherever they stumble is the section to rewrite. Expect to revise the memo every few months as you learn; today's version is a starting point, not a promise.
Your document for this module
One-page pitch memo. A single page of plain writing that explains your company to someone who has never heard of it. Share it with possible co-founders, advisers, partners or, if you decide to raise money, investors.