Draft · not indexed. Part of what this page describes is not generally available yet.
Peak One · Use case
The relaunch is waiting on one approval. You see early what that pushes back.
A relaunch has many dependencies: content, design, development, approvals. Peak One keeps them together in one project.
Try it
What happens if …?
Sample data · nothing is savedGo-live stays at day 24
Critical path: Concept → Design → Build → Go-live.
Interactive demo with invented sample data. No account, nothing is saved or sent.
Trigger, action, outcome
Phases as tasks, not slides
Concept, design, content, development and go-live become tasks with owners and dates. Board and list show the same rows.
Approvals for design and copy
Drafts go through the Inbox for approval. The frozen snapshot later shows which version was signed off.
Timeline and dependencies (beta)
Board V2 shows the timeline as a Gantt chart with dependencies and the critical path. It is part of Work V2 and not in the app catalog yet.
Scenarios are planned
A simulator for project delays is planned. The demo on this page only calculates in your browser with fixed rules.
An example
The copy arrives late
Example: Studio Kiel is building the new website for Nordwind Travel Goods. In the demo you delay the copy approval by five days and watch the critical path and the go-live date move.
All pages in this area
Frequently asked questions
Can tasks depend on each other?
Yes, in Work V2 (beta). It has dependencies and the critical path in the timeline.
How do I get design approvals from the client?
Approvals run through the Inbox with a frozen snapshot. The client needs access for this, for example as a guest.
Is there a relaunch template?
Templates for boards and workflows are in beta. Project templates with a timeline are still being built.
One relaunch, one plan.
Start with the tasks that are already clear today. Add the rest step by step.
Plan your relaunch
