Peak One · Product
Finishing tasks is good. Knowing what for is better.
With Peak Goals and Peak Year you set goals and milestones and link them to the tasks that move them. So the team sees what has to be done next.
An example
Three stages to launch
Example: Nordwind Travel Goods is launching a new suitcase line. Mara sets three milestones: “Product photos done”, “Shop pages approved”, “Launch”. Every task on the board hangs on one of them. In the demo she steps through the stages.
Try it
Step 1 of 4 · Kick-off
Sample data · nothing is savedDay 0: goal, contacts and access are clear.
Interactive demo with invented sample data. No account, nothing is saved or sent.
How it works
Milestones as stages
Split a project into stages you can check, such as “Design approved” or “Shop live”.
Tasks contribute
Tasks can be linked to a goal. Progress comes from the work, not from estimates.
From the year to the project
Peak Year holds the big initiatives of the year, with projects and milestones beneath them.
Visible in the calendar
Due milestones appear next to meetings and tasks.
Honest limits
No timeline dependencies here
Milestones have no dependency logic of their own. Dependencies between tasks exist in Work V2, in beta.
No estimated progress
Peak does not guess progress. It comes from the values and tasks you keep up to date.
Frequently asked questions
What is the difference between a goal and a milestone?
A goal describes the outcome, a milestone a stage on the way there.
Are goals a separate table next to the tasks?
No. Goals are their own objects and tasks are linked to them. No tasks are copied.
What does the demo show?
It shows three sample milestones as steps. You click through them, nothing is saved.