Every company has a plan. Few can explain why.
Vesper guides the building of strategy through blocks that depend on each other — external environment, competitors, ideal customer, value proposition, journey, funnel and metrics tree. The cross-analysis shows where two blocks contradict each other.
25 blocks with declared dependencies · Deterministic cross-analysis · Contradictions flagged, not hidden
Block in progress
Illustrative dataBlock
Value proposition
Depends on
Ideal customer and external environment analysis — a dependency declared in the block itself
Cross-check
Contradiction: the ideal customer describes a technical decision-maker; the tone of voice was written for the owner
AI draft
Saved after its required fields and the quality check are confirmed
Illustrative data — a fictional project created for this page.
The strategy exists. The reasoning behind it does not
The document did get written. What does not survive is the path: which information was considered, what was left out and why that choice was made. Without it, the first change of context brings everything down.
The analysis happens once and ages alone
One plan a year, made over two days of meetings, turned into a deck and archived. Six months later the market has moved and nobody knows which part of the analysis still holds — so it is all redone from scratch, with the same opinions.
Each piece was made apart from the others
The ideal customer in one file, tone of voice in another, metrics in a spreadsheet and the plan on a board. Since nothing looks at anything else, nobody notices when one piece contradicts another — and the operation runs both at once.
Priorities change and nobody records why
The decision was made in a conversation, the reasoning stayed in two people’s heads and the metric kept measuring what mattered before. When someone asks the reason, the answer is memory — and memory disagrees with itself.
From organised opinion to reconstructable reasoning
The path Vesper guides you through — and the point where the machine stops and hands the decision back to people.
“Strategy is not filling in a document. It is choosing with method.”
- Business context is entered once and feeds every block.
- The external environment is mapped in its own block, which the value proposition declares as a dependency.
- A competitor becomes a comparable profile, not a meeting impression.
- The ideal customer is described with entry and exclusion criteria.
- The value proposition declares the ideal customer as a dependency.
- Personas and journey come from that same ideal customer, with no parallel versions.
- The funnel follows the journey, and the metric follows the funnel.
- The cross-analysis flags reinforcement, contradiction and gap between blocks.
- The 30, 60 and 90 day plan comes out with an owner and a metric.
- Each presentation section is marked approved or sent back to draft.
Vesper guides. Genesis produces. Entropia questions. Arena rehearses.
Four systems with four different verbs, and mixing them up costs time. Vesper is the one that builds the strategy step by step.
Guiding is not producing. Questioning is not rehearsing.
Vesper
Guides the building of strategy through blocks with declared dependencies, flags contradictions between them and ties each choice to a metric.
Genesis
Starts from a briefing and returns a structured blueprint, consolidating positioning, differentiation and opportunity into a direction.
Entropia
Takes a strategy that is already formed and stresses it: fragile premise, hidden dependency, the blind spot nobody wanted to look at.
Arena
Rehearses the decision against scenarios and opposing forces before it meets the actual market.
All four are separate systems, contracted separately. This page does not claim automatic integration between them: each runs in its own system, and moving material from one to another is human work. Oracle is a different thing again — it organises the delivery of a consulting engagement (diagnosis, proposal, meetings, client follow-up), while Vesper builds the strategy itself.
The block, the chain and the delivery
Three illustrative screens: how a block is filled, what the cross-analysis returns and what the client sees at the end.
View 1 — the guided block
Illustrative dataThe question, the answer and the gap
- Block
- Ideal customer profile
- Guided question
- Which trait makes a customer work well with you — and which one makes it go wrong?
- Recorded answer
- Manufacturer with in-house operations, over 50 people, decision concentrated in the owner
- Gap flagged
- No exclusion criteria were written — only the positive side is filled in
The guidance for each block comes from the product itself and is always the same. The artificial intelligence can propose a draft; the company still answers.
View 3 — the delivery
Illustrative dataThe marked section and the report
- Section
- Value proposition
- State
- Draft — not yet marked approved
- Presentation
- Not published
- Report
- Shared by link, with every block of the project
In the internal presentation, a section is marked approved or stays in draft, and a preview mode shows only the approved ones. The report link does not read that marking.
View 2 — the chain
Illustrative dataWhat each block does to its neighbour
- Reinforcement · the competitor map supports the territory chosen in positioning
- Contradiction · the ideal customer describes a technical decision-maker; the tone of voice was written for the owner
- Gap · the metrics tree does not measure the most expensive stage of the journey
How this is calculated
By deterministic rule over the block content, with no model call — the same input always returns the same reading
What the chain does not do
It does not decide for you, does not fix the block on its own and does not claim the choice will work
Screens built for this page, with an invented project. No real client, company or result appears here.
What Vesper does, with no promise of what is coming
Every item below is in operation. What is common in strategy tools but does not exist here does not appear on this page.
Blocks with dependencies
25 fillable blocks, each with its own schema, required fields and the list of blocks it depends on. Assisted filling follows that structure.
The frameworks behind the analysis
PESTLE, SOAR, competitor map, ideal customer, personas, value proposition, positioning, journey, funnel and metrics tree — in the same project.
Deterministic cross-analysis
Executive summary, priority actions, risks, opportunities, allocation guidance and the links between blocks, calculated by rule and with no model call.
Validation of AI drafts
In AI-assisted filling, a draft is saved only after schema, required fields and minimum length are checked; in competitors and ideal customer, unreplaced placeholders are rejected as well.
An assistant that drafts
The artificial intelligence fills blocks from the context already recorded, in dependency order, and suggests the next step.
Collection with the client
A form sent by link for the client to answer without creating an account, with the answers recorded in the project and used when the strategy is generated.
Execution and portfolio
A 30, 60 and 90 day plan, an experiment plan with a declared hypothesis, execution tasks and base segmentation by recency, frequency and value.
Approval and delivery
Per-section approval marking in the internal presentation, with a preview of approved sections only, and a report shared by link that gathers every block without applying that marking.
Want to see the chain of blocks running on your own scenario?
Talk to a specialistFrom context to a plan with an owner
The highlighted step is where the system stops: a flagged contradiction does not fix itself.
Cycle of a strategy project
Illustrative dataContext
Segment, region, average ticket, channels in use, cycle objective and execution window.
Diagnosis
External environment, strengths and aspirations, and the map of who competes for the same customer.
Customer and offer
Ideal customer, personas, value proposition and positioning — in this order, because each depends on the previous one.
Execution
Journey, funnel architecture, metrics tree and the 30, 60 and 90 day plan.
Cross-check
The analysis walks the blocks and classifies each link as reinforcement, contradiction or gap.
Human review
A flagged contradiction does not resolve itself: someone decides which of the two blocks changes.
Approval
In the internal presentation, each section is marked approved or returned to draft.
Follow-up
Tasks with owners, experiments with a declared hypothesis and the strategy revisited when the context changes.
An eight-step flow: context, diagnosis, customer and offer, execution, cross-check between blocks, human review of the contradiction, section-level approval marking and follow-up.
Vesper organises the reasoning and shows where it is loose. The artificial intelligence can draft direction and priorities, but that content should be reviewed by the team, which answers for the decisions; the product does not guarantee a choice will work.
What belongs to the machine and what belongs to the company
A strategy system that does not state its own limits ends up used as an oracle — and that is where decisions get worse.
The role of artificial intelligence, stated
It drafts blocks from the recorded context, including objectives, positioning and priorities, and suggests the next step. It does not validate hypotheses; what it generates should be reviewed by the team, which answers for direction and priorities.
Analysis that does not depend on a model
The cross-check between blocks is a deterministic rule: the same input always returns the same reading. You can check the arithmetic instead of trusting generated text.
A hypothesis stays a hypothesis
The experiment plan keeps the hypothesis as its own field, with expected impact. Until it is tested it does not become a conclusion or enter the plan as fact.
Trail and version per block
Relevant actions are recorded in a trail, and each strategy block keeps its own version number.
What this page does not promise: market prediction, a promise of being right, replacement of the strategy consultant or a finished plan without human work. What exists is a stated method, dependencies between blocks, contradictions flagged and actions recorded in a trail.
People who must defend the choice, not just present it
Vesper pays off when the strategy has to survive a hard question — and more than one person.
Agencies and consultancies
Those delivering strategy to third parties who need to show the reasoning, not just the final deck — and repeat the method with each new client.
Marketing and growth teams
Those who need to tie positioning, channel and metric together without each piece living in a different file and contradicting its neighbour.
Owners and directors
Those who decide and want to be able to answer, six months later, why that was the priority — with the information available at the time.
Teams turning a cycle
Those about to redo the plan who want neither a blank page nor last year’s document repeated.
System plans
Three tiers that unlock more as you grow. On Max, you get access to everything.
Essentials to start
- Initial context: segment, region, ticket, channels and cycle objective
- External and internal diagnosis: PESTLE, SOAR and competitor map
- Customer and offer: ICP, personas, value proposition and positioning
- Schema and required fields per block, with quality checks on AI drafts
Full operation
- Initial context: segment, region, ticket, channels and cycle objective
- External and internal diagnosis: PESTLE, SOAR and competitor map
- Customer and offer: ICP, personas, value proposition and positioning
- Schema and required fields per block, with quality checks on AI drafts
- Message and identity: tone of voice, editorial lines and message house
- AI assistant that drafts blocks from the context
- Link-based form for the client to answer, no account needed
Everything unlocked
- Initial context: segment, region, ticket, channels and cycle objective
- External and internal diagnosis: PESTLE, SOAR and competitor map
- Customer and offer: ICP, personas, value proposition and positioning
- Schema and required fields per block, with quality checks on AI drafts
- Message and identity: tone of voice, editorial lines and message house
- AI assistant that drafts blocks from the context
- Link-based form for the client to answer, no account needed
- Execution: customer journey, funnel architecture and metrics tree
- Deterministic cross-analysis: reinforcement, contradiction and gap between blocks
- 30/60/90 plan, experiment plan and RFM segmentation of the base
- Report by link to present to the client
Frequently asked questions
What is Centriu Vesper?
It is a system for building company strategy through blocks that depend on each other. Each block has a guided question, required fields and the list of blocks it depends on. A cross-analysis then runs over the filled content, flagging where blocks reinforce each other, where they contradict and where information is missing.
Does Vesper create the strategy on its own?
It can draft it: the artificial intelligence can fill every block, including objectives, positioning and priorities, from the recorded context and the model’s own knowledge. It does not validate hypotheses, and that content should be reviewed by the team, which answers for direction, hypothesis validation and priorities.
Which frameworks are available?
External environment via PESTLE, strengths and aspirations via SOAR, competitor map, ideal customer profile, personas, value proposition, brand positioning, message house, tone of voice, editorial lines, customer journey, funnel architecture, metrics tree, 30/60/90 day plan, experiment plan and portfolio segmentation by recency, frequency and value — among other blocks in the same project.
What is the difference between Vesper and Genesis?
Vesper guides the build step by step: you walk the blocks, answer, and the cross-analysis flags what does not add up. Genesis starts from a briefing and returns a structured blueprint with positioning, differentiation and opportunity. One guides the reasoning; the other produces a piece. They are separate systems, contracted separately.
What is the difference between Vesper, Entropia and Arena?
Vesper builds the strategy. Entropia takes a formed strategy and stresses its premises, exposing blind spots and hidden dependencies. Arena rehearses the decision against scenarios and opposing forces. They fit different moments, and this page does not claim automatic integration between them: moving material from one to another is human work.
Does Vesper replace a strategy consultant?
No. It brings method, order and memory to the work — judgement stays human. In practice the people who benefit most are consultants themselves, because they repeat the same method with every client without starting from scratch. Worth noting: Oracle is a different thing, organising the delivery of a consulting engagement (diagnosis, proposal, meetings, follow-up), while Vesper builds the strategy itself.
Do the blocks relate to each other?
Yes, and that is the central idea. Each block declares which others it depends on, and a deterministic analysis walks the content classifying each link as reinforcement, contradiction or gap. It is a rule, not generated text: the same input always returns the same reading.
How are hypotheses handled?
The experiment plan keeps the hypothesis as its own field, together with the expected impact. Until the experiment is run it stays a hypothesis — it does not become a conclusion or enter the plan as if it were proven fact.
Can the strategy be updated later?
Yes. Blocks remain editable and the cross-analysis runs again over the updated content, which usually reveals new contradictions after a change. Revision is part of normal use, not an exception.
Is history preserved?
Each artefact keeps a version number and relevant actions are recorded in a trail. There is not yet a navigable timeline that lets you open and compare the strategy from six months ago side by side — we would rather say so than promise what the product does not do today.
Does Vesper track metrics and execution?
It ties objective to metric in the metrics tree and organises the 30, 60 and 90 day plan with tasks and owners. It is not a day-to-day task manager: detailed execution belongs to operational systems, and Vesper keeps the direction layer.
What is recorded in the project?
Relevant actions are recorded in a trail, and each block keeps its version number. What does not exist is a browsable timeline to compare the strategy from months ago side by side.
Start with the reasoning, not the slide.
Set up a project, walk the blocks in the order they depend on each other, and see in black and white where your strategy contradicts itself.