
How to write a startup mission statement, with examples
A simple formula for a one-line startup mission statement, five examples, mission versus vision, and why not to polish it before you have customers.
A startup mission statement is one sentence that says why your company exists: who you do it for, and what changes for them because you did. Here's how to write a startup mission statement in an afternoon, with a simple formula and five examples.
Why bother this early
I think it helps to have a mission statement and a vision statement in the early days. They give you clarity, and they help you focus your work and what you're doing. When there are twenty things you could do this week, a written line about why you exist makes it easier to see which three matter. That only works if the line is short enough to remember.
Mission, vision and values
These three get mixed up:
- Mission: why you exist and who you do it for. It's about the work you do now.
- Vision: the picture of the world once the mission works. It's about the future.
- Values: how you behave while you get there. How to build startup culture covers those.
Your one-liner is a fourth sentence: it tells a stranger what the product does. Startup one-liner examples shows how to write it.
How to write a startup mission statement: the formula
Answer three questions:
- What problem are you solving? In the words of the people who have it.
- Who has it? A group specific enough that you could find them.
- What's different for them once you've done your job? Describe what changes in their day.
Then fill in the blanks:
To [the change you make] for [who], so that [what's different for them].
Reword it until it sounds like something you'd say out loud. Leave the product out: it will change as you find out more. A mission that names your app has to be rewritten every time the app does.
Start from a problem you've checked, not one you assume. How to validate a startup idea shows what counts as proof.
Five startup mission statement examples
Three real ones
Google: "Our mission is to organize the world's information and make it universally accessible and useful." (Google's company page)
Two plain verbs and one clear result. You can test almost any project against it: does this make information easier to find or use?
Microsoft: "Microsoft's mission is to empower every person and every organization on the planet to achieve more." (Microsoft's about page)
This one is wide, which suits a company that sells to almost everyone. For a startup with five customers, a line this wide would rule nothing out. Keep the shape (who, and what they can do because of you) and make the who much narrower.
Stripe: "Stripe is on a mission to grow the GDP of the internet." (Stripe's culture page)
Short, and it points at a result you could, in principle, measure. It doesn't say "payments" anywhere, so it still holds as the products change.
Two made-up ones
Both of these startups are invented.
A captioning startup for small theaters:
To make every show at a small theater one that deaf and hard-of-hearing people can follow.
The who is narrow and the change is plain. Its vision could be "a night out where nobody has to ask what was just said": the future the mission works toward.
A paperwork tool for independent electricians:
To get independent electricians paid for every job, without losing their evenings to paperwork.
The problem is in their words. It doesn't mention an app, so if the founders find the real fix is a person who does the paperwork for them, the mission still holds.
Use it for decisions and hiring
Decisions. Imagine the captioning founders, a few months in, are offered well-paid work captioning a conference's online talks. Their mission doesn't forbid it, but it shows the trade-off: the work doesn't help a single small-theater audience. They can take it for the cash, knowing it's a detour, or turn it down. Without the line, nobody notices that a choice is being made.
Hiring. Put the mission at the top of every job post and say it in the first interview. On a small team, everyone needs to care about the problem you're solving. Hire for that and for attitude. Caring about the problem has nothing to do with sharing your background.
Don't polish it before you have customers
Your first mission statement will be rough, and that's fine. Don't spend weeks on the wording before you have customers. Until real people pay you, you're still guessing who has the problem and what they'd call it. Revisit the line once customers have shown you what they value.
If you have a co-founder, write it together. If you can't agree on one sentence, you disagree about direction, and when co-founders disagree on company direction walks through that conversation.
Common mistakes
- Too broad. "To make the world a better place" rules nothing out.
- Too narrow. Naming one product, feature or technology ties you to it. A line built around the customer's pain still fits when the solution changes, and it helps you tell which kind of change you face when you ask when a startup should pivot.
- Buzzwords. "Revolutionize," "disrupt," "leverage." If a customer wouldn't say it, cut it.
- Putting it at the top of your landing page. That spot has to say what you do. The startup landing page covers what goes there. Your mission belongs on your about page, in job posts and in your planning notes.
- Writing it and filing it. If nobody has checked a decision against it in a month, it isn't doing anything.
Continue Reading
More in Building the companyReady to Move Faster?
Get actionable feedback and insights on your challenges and goals. 30 minutes focused on helping you move forward.
No sales pitch. No obligations. Just helpful advice.


