Skip to main content
Beast Launches

Writing a Product Manifesto That Sharpens Everything

Voice · 10 min read ·

A manifesto is a short, public statement of what your product believes and refuses. How to write one, test it, publish it and use it to guide decisions.

Illustration: A stark black page with numbered manifesto lines in white condensed type and one neon-green word highlighted per line

A manifesto is a public declaration of intentions, motives or views. Political and artistic movements have long used them to say what they stand for and against. A product can do the same, in miniature. A good product manifesto is a page of short, firm statements that tells customers what to expect, tells the team what to choose and tells everyone else what the product is about.

It is also one of the most useful things you can write before a launch, because the act of writing forces decisions you would otherwise put off.

What a manifesto does

Four jobs.

It sets expectations. Customers learn what the product will and will not do, which reduces disappointment.

It guides decisions. When a feature request, a pricing question or a marketing idea arrives, the team can check it against the page.

It attracts and repels. People who share the beliefs lean in. People who do not move on. Both outcomes are good.

It gives the launch a spine. Headlines, descriptions and press notes can all draw from the same source, so the message stays consistent.

Manifesto versus mission, vision and values

These terms blur, so draw the lines.

  • A mission says what you are trying to do: "Make invoicing painless for freelancers."
  • A vision says what the world looks like if you succeed.
  • Values are abstract qualities: honesty, curiosity, craft.
  • A manifesto states positions, in plain, specific language, and includes refusals: "We do not sell your data." "We do not bury cancellation."

Values are easy to claim and hard to test. Positions are specific enough to be broken, which is exactly why they carry weight.

Writing it: a method

Step 1: Collect your strong opinions

Spend half an hour listing things you believe about your product, your customers and your category. Do not edit. Include opinions that make you slightly nervous. Examples:

  • Software should respect people's time.
  • Pricing should be readable without a calculator.
  • Defaults should protect the user.
  • Support should be done by people who know the product.

Step 2: Turn beliefs into commitments

A belief tells people what you think; a commitment tells them what you will do. Convert each opinion into a promise or a refusal.

  • "We think pricing should be clear" becomes "Our pricing is on one page with no hidden extras."
  • "We think data belongs to customers" becomes "You can export everything at any time."

Step 3: Keep only those you can keep

For each statement, ask: could we break this under pressure? Would we? If a statement is aspirational but not yet true, either make it true before you publish or reword it honestly: "We are working towards X" is acceptable if it is the truth; "We do X" is not.

Step 4: Cut to the core

Aim for five to twelve statements. If you have thirty, group them and keep the strongest from each group. A manifesto that reads like terms and conditions has lost its force.

Step 5: Write each line as a short, firm sentence

  • Use the active voice and the present tense.
  • Prefer the concrete to the abstract.
  • Avoid hedging words such as "try" and "strive" unless you mean them.
  • Make each line stand alone.
  • Add a short second sentence only where the first needs a reason.

Step 6: Order for impact

Lead with your strongest or most distinctive line. End with something memorable. Number them if it helps readers quote them.

Step 7: Test it

Show it to three people: a customer, a colleague and a stranger. Ask which lines they remember, which they doubt and which they would quote. Rewrite the doubted ones or cut them.

Examples of the shape

These are invented, to show the form.

  • We charge for the product, not for your data.
  • Every price is on the pricing page. No sales call to find out.
  • If you want to leave, you can export everything first.
  • We answer support emails ourselves.
  • We say what is not finished yet.
  • We ship small and often, and we write it down.

Each is specific and testable. Customers can check, and the team can be held to them.

Keeping it honest

A manifesto invites scrutiny. Some precautions.

  • Do not claim what the product does not do. Advertising rules in many places require that claims be truthful and capable of substantiation, and a manifesto line is a claim.
  • Review it each time circumstances change. A line about data must be revisited when you add a new integration or a new supplier.
  • Record changes. If you alter or remove a commitment, say so with a date and a reason. Quiet edits look like retreat.
  • Do not weaponise it. Do not use a manifesto to criticise others unfairly.
  • Keep it independent from legal terms. Your terms and policies are the binding documents; the manifesto states intent. If they conflict, fix the conflict.

Making it findable and readable

Treat the manifesto page like any important page.

  • Give it a clear title and headings.
  • Write in plain English and use short paragraphs.
  • Make sure the text is real text, not an image, so it can be read by assistive technology and indexed. The Web Content Accessibility Guidelines emphasise that content should be perceivable and understandable.
  • Provide a way to link to each line, such as anchors, so that readers can quote precisely.
  • Link to it from your launch page, listing, documentation, onboarding emails and the footer.

Google's guidance on helpful content encourages pages that are original and make clear who stands behind them. A manifesto signed by the founders is a clear statement of ownership; it fits naturally beside an about page.

Using the manifesto day to day

A manifesto earns its keep in ordinary decisions.

  • Product. Before building a feature, ask whether it fits the statements.
  • Pricing. Check a proposed change against the lines about clarity and fairness.
  • Marketing. Draw headlines from the statements and avoid anything that contradicts them.
  • Support. Use it to guide how hard cases are handled.
  • Hiring. Share it with candidates and ask how they feel about it.

When the team disagrees, the manifesto is a reference point rather than a battle of opinions.

What to avoid

  • Vague virtues. "Excellence", "innovation" and "passion" are not positions.
  • Copying another company's lines. Their promises are their own.
  • Over-claiming. If a line makes you wince, cut it.
  • Treating it as a poster. If nothing in the product reflects it, it is decoration.
  • Letting it go stale. A manifesto that has not been reviewed for years is a relic.

A worked example

A three-person team is about to launch a time-tracking tool for freelancers. They hold a thirty-minute session and list opinions: tracking should not feel like surveillance; reports should be readable by clients; exports should never be locked behind a higher plan; the free tier should be useful, not a trap.

They turn each into a commitment. "Tracking is for you; we never show your timesheets to anyone you have not chosen." "Reports are clean enough to send to a client without editing." "Export is on every plan." "The free plan has no time limit." They test each against reality. The export line fails: a bulk export is on the roadmap but not built. They either have to build it before launch or reword. They choose to reword: "Every report can be downloaded as a file; full-account export is coming and we will say when it ships." Honest, specific and checkable.

They cut a line about "delighting users" because it cannot be tested, and add a refusal: "We will not sell or share your data with advertisers." Their legal adviser confirms that this matches the privacy policy. They publish six lines, signed by the founders, and link them from the footer. Within a month the lines are being quoted by customers in support emails, which is how the team knows the page is working.

Questions teams ask

Do we need a manifesto before launch? You do not need one, but writing it is the quickest way to find disagreements within a team, and it is cheaper to resolve them before the launch than after.

Can a manifesto change? Yes. Update it openly, with dates, when you learn something or when circumstances change. A manifesto that never changes may mean nobody is reading it.

What if a customer quotes it back at us? That is the best outcome. Thank them, and fix whatever fell short.

Should every team member agree with every line? They should be able to defend every line. If someone cannot, that is a useful conversation to have.

A quick review routine

Put a calendar reminder to read the manifesto aloud once a quarter with the whole team. For each line ask: did we keep it? Where did we come close to breaking it? Does it still describe what we want? Mark any line that needed an exception, and either tighten the practice or soften the line honestly. The routine takes twenty minutes and keeps the page alive.

Summary

A product manifesto is a short list of firm, testable statements about what you believe, promise and refuse. Collect opinions, turn them into commitments you can keep, cut to the core, write each line plainly and test it with outsiders. Publish it as real text with a clear owner, link to it widely and use it to settle everyday decisions. Done well, it sharpens the launch, the product and the team.

Questions and answers

What is a product manifesto?
A short public declaration of the beliefs, principles and refusals that guide how a product is made and sold.
How long should it be?
Short enough to read in two minutes: usually between five and twelve statements, each a sentence or two.
Is a manifesto the same as a mission statement?
No. A mission statement describes a goal. A manifesto states positions, including things you will not do.
Where should it live?
On its own page, linked from your launch page, listing and documentation, and quoted where it helps decisions inside the team.

Sources

Related guides

Questions?