The first three modules looked backward and inward. The origin story was the inciting moment. The problem was the structural condition you discovered. The technology was the proof that your answer was real. All three were grounded in what already exists — what you experienced, what the market has failed to solve, what your team built.
This module is the only one that moves in the opposite direction. It looks forward and outward — toward a world that doesn't yet exist. And because it has nowhere to land except in your conviction, it is both the most expansive thing in the arc and the most intimate. The vision is the origin story grown up. It names what you were really building toward from the beginning — even before you had language for it.
A Vision Manifesto answers one question: what must be true in the world if this company fully succeeds? Not what revenue you'll generate. Not what products you'll build. Not what values you hold. What changes — in human experience, in industry behavior, in the expectations a market carries — when your work reaches its full horizon. Everything else — mission, purpose, strategy, roadmap — is downstream of that answer.
These prompts move from the most expansive to the most grounding. Start with the world you're building toward. Then find the thread that connects it to where you started. Then name the organizing principle that makes it coherent across time. Don't edit while drafting. The vision lives in what you actually believe — not in what sounds right.
Describe the future state — not in financial terms, not in product terms, but in terms of what changes in human experience, industry behavior, or market expectation when this company has fully succeeded. What does the world stop accepting as normal? What does the world start taking for granted? Write at the 10–15 year horizon. This is not a prediction. It's the future you're building toward — and the standard against which every strategic decision you make will eventually be measured.
What is the single conviction — the belief about the world that you've held since before the company existed — that runs directly from your origin story to the future state you just described? This isn't your product insight or your market thesis. It's the underlying truth you saw that nobody else was acting on. Name it in one or two sentences. If your vision is the destination, the throughline is the reason you were the one who was going to build it.
You are going to spend the next ten years of your life on this. Probably more. There will be stretches where the capital is thin, the progress is invisible, and the people around you are questioning whether it's worth it. What is the thing — the belief, the conviction, the change in the world — that makes all of that make sense? Not to an investor. Not to a board. To you, at 2am, when the doubt is loudest. Name it without softening it. This is the organizing principle that will let you grow beyond your first product, enter markets you haven't imagined yet, and still know — with certainty — whether a decision is right or wrong. But before it does any of that strategic work, it has to be true. Write the version you'd believe if no one was funding it.
Read back what you've written. Not for logic. Not for completeness. For voice. The vision manifesto is the one document in your entire clarity infrastructure that an investor, a partner, or a new team member should be able to read and feel the person behind the company. If it sounds like a pitch, rewrite it. If it sounds like a consultant wrote it, rewrite it. If it sounds like something you'd be embarrassed to say out loud in a room of people you respect — that's probably the truest version.
The first draft of a vision is almost always either too small or too inflated. Write it anyway. The honest version is usually somewhere inside the ugly one — you find it by editing, not by thinking harder before you start.
Origin story → problem → technology → vision. Read all four in one sitting. The vision should feel like the inevitable last sentence. If there's a gap anywhere in the sequence, close it before you finalize.
Not on an investor. Not on an advisor. On the person who was in the room when this started. If they read it and say "yes, that's it" — you're done. If they say "that's not quite right" — they're pointing at the gap the document is avoiding.
The vision is not a living document. It's a stable one. Resist the urge to update it every time the strategy evolves. If the vision needs to change because of a product pivot, that's a signal the prior version was a strategy dressed as a vision — not that visions should change.
With the Vision Manifesto, Track 1 is complete. You have an origin story, a problem and solution framework, a technology narrative, and a long-horizon vision — four documents that form a single, coherent arc from the moment that started everything to the world you're building toward. Every commercial asset downstream — the pitch deck, the investor narrative, the website, the case study — is derived from this foundation. The vision has a direct downstream application in fundraising: an investor narrative that translates the long-horizon future state into the mental model you want capital partners to hold. That's Track 4 work. This is where it starts.