The Manifesto

Leads with a worldview in long-form editorial; the product doesn't appear until the argument has been made.

Why

You must first make the problem exist before a product can be relevant. An unaware visitor isn't shopping; the only thing that holds them is a point of view worth reading. The product arrives late, as the logical conclusion of the argument.

Awareness fit

UnawarePrimary
Problem-awareAdapted
Solution-aware
Product-aware
Most aware

Sections

9

Typical length

Very long

Choose this when

  • +Your audience doesn't yet believe the problem exists; you're creating a category, not competing in one
  • +The founder has a genuinely contrarian, defensible point of view worth publishing on its own
  • +Traffic arrives via essays, podcasts or word-of-mouth rather than high-intent search
  • +You can wait for the payoff: this page's job is to change what someone believes, and belief converts on a slower clock than a demo request

Look elsewhere when

  • −Visitors arrive comparing solutions and will be irritated that the product hides below 2,000 words
  • −The 'manifesto' would just be marketing copy in a serif font; without a real thesis the format collapses
  • −You need short-term conversion volume; manifestos compound slowly

Anatomy

Editorial hero

MMotivationMotivation: builds desire, proof, identification
View section in library ↗

Open with the one claim the entire page exists to defend.

  • It's a position, not a topic: someone in your field should be able to disagree with it out loud
  • It works as the title of an essay you'd actually want to read, with no product name in sight
  • Nothing competes for the first ten seconds: no screenshot, no CTA, no logo strip

The thesis gets sanded down in review until nobody can object to it. 'Work should be simpler' is not a position, it's a mood. A visitor who wasn't looking for anything has no reason to keep reading a claim they already agree with and have already forgotten.

Problem framing

MMotivationMotivation: builds desire, proof, identification
View section in library ↗

Build the problem from nothing. The reader doesn't believe it exists yet, so this section has to make it exist before anything else on the page can matter.

  • Starts inside one specific situation the reader has lived through, and stays there long enough to be recognised
  • Explains why the problem stayed invisible: this reader has been coping with it, not naming it
  • Ends on a cost they hadn't added up, not on a solution

The section rushes: two paragraphs of problem, then the product. For a reader who hasn't accepted the problem yet that's far too fast, and the product arrives as an answer to a question they never asked. This is the longest section on the page for a reason, and shortening it is the single most common way a manifesto dies.

Why now

MMotivationMotivation: builds desire, proof, identification
View section in library ↗

Answer the question the reader hasn't asked out loud: if this problem is as real as you just argued, why is nobody solving it until now?

  • Names the specific thing that changed and roughly when — a technology that got cheap, a rule that came into force, a behaviour that flipped, a cost that crossed a line
  • Explains why the old way was a reasonable answer before that change and isn't any more; that contrast is what makes this an argument instead of a claim
  • Makes waiting expensive using the shift itself, not a deadline you invented

'The world is changing faster than ever.' No event, no date, nothing a reader could check. Without a specific change, the most obvious explanation for why nobody solved this is that it wasn't worth solving — and everything you just wrote about the problem quietly loses its credibility.

Principles / beliefs

MMotivationMotivation: builds desire, proof, identification
View section in library ↗
1
2
3
4

Turn the argument into a short list of convictions the reader can sign or reject.

  • Every principle names a trade-off you accepted; if the opposite is unthinkable, it isn't a principle
  • Written as things you believe, in your own voice, not as things the product has
  • Few enough that a reader could repeat two of them to a colleague tomorrow

Features in a serif font: 'We believe software should be fast.' Nobody believes the opposite, so the list proves nothing. Worse, the reader recognises the move — the essay was a wrapper around a feature list — and the trust the format spent a thousand words building is gone in one sentence.

Product reveal

MMotivationMotivation: builds desire, proof, identification
View section in library ↗

Land the product as the conclusion of the argument, not as a new subject.

  • The first sentence connects back to the thesis: this is what following the argument produced
  • Shows plainly and quickly what it is; the persuading was supposed to be finished by now
  • Doesn't restart the pitch — no feature tour, no benefits carousel

The page changes register: the essay ends and a product marketing site begins. A reader who was persuaded is suddenly being sold to, and that tonal break reads as bait and switch even when the product is exactly what the argument implied.

Logo proof strip

FFrictionFriction: removes doubt, risk, ambiguity
View section in library ↗

Show that this worldview already has serious company, now that the reader has decided whether they share it.

  • Placed after the reveal: opening with borrowed trust would have made this a vendor page instead of an essay
  • Names that mean something to this reader specifically; a manifesto audience is unmoved by volume
  • Presented quietly, as a footnote to the argument rather than a wall of trust badges

The strip gets moved to the top, because that's where logo strips go. It reframes the page as marketing before the first paragraph, and the essay never gets read as an essay at all.

Final CTA

MMotivationMotivation: builds desire, proof, identificationFFrictionFriction: removes doubt, risk, ambiguity
View section in library ↗

Ask for the smallest next step that matches how much the reader has actually decided.

  • The ask fits the intent you built: read the thinking, join the list, follow along — not 'Start your free trial'
  • Restates the conviction in the words the essay just taught them
  • One action. Someone who has only just adopted a worldview shouldn't be handed a decision tree

A hard conversion CTA at the end of a soft argument. The reader was recruited to a belief, not walked to a purchase decision, and being asked for a credit card makes the whole essay look retroactively like a long pre-sell.

Link to copied

Put this to work

I'm building a landing page using The Manifesto as the archetype: Leads with a worldview in long-form editorial; the product doesn't appear until the argument has been made. Why this structure: You must first make the problem exist before a product can be relevant. An unaware visitor isn't shopping; the only thing that holds them is a point of view worth reading. The product arrives late, as the logical conclusion of the argument. The sections, in order, and what each one has to achieve: 1. Navigation — Get out of the way. On an essay the navigation only has to prove there's a real company behind this, and then disappear. 2. Editorial hero — Open with the one claim the entire page exists to defend. 3. Problem framing — Build the problem from nothing. The reader doesn't believe it exists yet, so this section has to make it exist before anything else on the page can matter. 4. Why now — Answer the question the reader hasn't asked out loud: if this problem is as real as you just argued, why is nobody solving it until now? 5. Principles / beliefs — Turn the argument into a short list of convictions the reader can sign or reject. 6. Product reveal — Land the product as the conclusion of the argument, not as a new subject. 7. Logo proof strip — Show that this worldview already has serious company, now that the reader has decided whether they share it. 8. Final CTA — Ask for the smallest next step that matches how much the reader has actually decided. 9. Footer — Close the publication without breaking the spell. Before you write anything, interrogate me on these: - What do I believe about my field that most people working in it would actually dispute? - What specific thing changed in the world, and roughly when, that makes this problem solvable now? - What am I willing to be disliked for? How to work with me: - Don't give me visual, layout or brand identity advice. No colours, fonts or imagery. This is about the argument the page makes, not how it looks. - Don't flatter me. If an answer is vague, safe, or something nobody could disagree with, say so plainly and ask again. - Don't invent proof. No made-up numbers, customer names, quotes or case studies. Where the evidence is missing, name it as a gap I have to fill. - Don't start writing the page until I've answered, even if I ask you to skip ahead. Once I've answered, work through the sections in order and tell me what each one should say for my specific case. Flag any section I don't have the substance for yet.

Related archetypes

The Mechanism-Led Page

The Workflow Narrative

is made by Pieter de Kroon, designer of digital products. He kept explaining the same patterns to founders, so he wrote them down.