Draft · not indexed。 Part of what this page describes is not generally available yet.
Peak One · Use case
The deal is won. Now nothing may get lost in the handoff.
Between yes and kick-off, agreements often get lost. Peak One captures them as tasks, in the same workspace as the project.
Try it
Step 1 of 4 · Check the result
Sample data · nothing is savedAll tasks of the milestone are done, the last approval is in.
Interactive demo with invented sample data. No account, nothing is saved or sent.
Trigger, action, outcome
Agreements as tasks
What sales promised becomes tasks with owners. The delivery team sees them on the board, in the list and in My Day.
Templates for repeat starts (beta)
Board and workflow templates help you set up every kick-off the same way. Project templates with a timeline are still being built.
Handoffs as a flow are planned
Deliverables and handoffs as their own flow are planned. The checklist on this page shows the idea as a demo.
One reality instead of two tools
Client, tasks and project live in Peak One. There is no export from a sales tool into a project tool that goes stale.
An example
A handoff in five steps
Example: Studio Kiel wins a project with Nordwind Travel Goods. In the demo you go through the handoff checklist: scope, contacts, dates, open questions, kick-off.
All pages in this area
Frequently asked questions
Can I save a handoff checklist as a template?
Templates for boards and workflows are in beta. You can use them to set up repeat starts the same way.
Does the delivery team see what was promised?
Yes, as long as the promises are tasks or notes in the project. Everyone works on the same rows.
When will the handoff flow arrive?
It is planned. We will only name a date once it is built and tested.
Promise and delivery in one place.
Start with a handoff list as tasks and make it your standard.
Prepare a handoff
