01 / The existing evidence
This connection is planned
A connected digital twin does not exist yet. This page reads and connects nothing.
Mapping
- Mapping
- Example
- Arrival
- Planned
Planned This capability is specified but not built yet. The page shows the plan with fictional examples. Available today: Today brief, Top 3, decisions with memory, goals, roadmap and scenarios.
Peak Command · digital twin · planned
A model of your company.
Built from what Peak One already knows.
Planned: a digital twin is meant to show revenue, costs, capacity and initiatives as one connected model on which you test assumptions. Today Peak Command computes single scenarios from Peak Finance and Peak Year.
See what-if todayPlanned feature · example mapping · no connection
Peak FinanceFigure in Peak OneTwin (planned)Node in the twinTwin (planned) · Example mapping
One mapping in detail
01 / Peak FinanceRevenue per month
02 / Fictional test valueExample: €84,000
03 / Twin (planned)
Revenue nodeA readable path as an example. No transfer.
View all 5 mappings
| Peak Finance | Place in Twin (planned) |
|---|---|
| Revenue per month | Revenue node |
| Fixed costs | Cost node |
| Team hours | Capacity node |
| Initiative | Project node |
| Ad budget | Assumption |
Example mapping
No transfer
No transfer
This connection is planned. Nothing is connected or transferred on this page.
One concrete targetTwin (planned)Place in Peak CommandPlanned
How it is meant to work.
Twin (planned)Place in Peak CommandPlannedThe mapping shows a planned connection. It is an example, not a live connection.
02 / How it is meant to work
Read. Link. Play through.
The twin is not meant to change anything. It is meant to show how figures relate before you decide.
- 01 / The sources
Read
Planned: revenue and costs from Peak Finance, capacity from Peak Plan, initiatives from Peak Year.
What Peak One knows.FinanceCapacityInitiatives - 02 / The model
Link
Planned: dependencies become visible, such as which initiative depends on which capacity.
How it connects.DependencyAssumptionEffect - 03 / The boundary
Play through
Planned: change assumptions, see the effect. Changes are applied only in the owning product.
Nothing changes.No writesSource visibleYour choice
Trust needs clarity
Planned means: not here yet.
Mapping02 / Your check
Built today
Today Peak Command computes scenarios for revenue, ad budget, a delay or skipping an initiative. A scenario changes nothing until you apply it in the owning product.
- Account
- Not connected here
- Status
- Not available yet
03 / The clear limit
No date promised
We do not say here when it arrives. We name it once it is provably available.
- Adapter
- Webhook
- Embed
- Planned
The next step
Play through a scenario today.
The what-if simulator shows what Peak Command computes from Peak Finance and Peak Year today.
See what-if today→Until then you use what Peak Command already reads today.
Frequently asked questions
Can I use the digital twin yet?
No. It is planned and no date is promised. Today Peak Command shows the daily brief, top 3, decisions, goals, initiatives and scenarios from the Peak products.
Which scenarios does Peak Command compute today?
What if revenue changes, ad budget rises, something is delayed or an initiative is skipped. It is computed from Peak Finance and Peak Year.
Does a scenario change my data?
No. A scenario changes nothing until you apply it in the owning product.