Skip to content
Peak Atlas

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 / Customer churn

Customers cancel quietly.You notice at month end.

Halde Kaffeerösterei (fictional) loses subscription customers every month and only learns from revenue. Peak Command is meant to show churn signals once a customer product is connected; that is planned and today “not available”. Today you make retention a goal and record the decision about it in Peak Log.

One answer changes the follow-up

Pick a sample rating.

Local draft · no product activation
Check cancellation reasons

Test the sample rule · planned · nothing is connected.

02 / The next question

0–6 Follow-up

Which three cancellations can you name, and what was the reason for each?

The reasons turn into a decision with a review date, first against the most frequent reason.

Sample rule · no real company data · not the product interface

Check the rule yourself

Change the rating. See the difference.

At 0 to 6 the clarifying question appears, at 7 to 10 it doesn't. Nothing is read, measured or sent.

Local rule demo · Please use neutral sample details only.

Peak Command / Question pathRULE DEMO
How sure are you why customers cancelled last month?
0 · No idea10 · Exactly

Pick a rating to see the next step.

The rule in actionLocal preview

The answer sets the direction.

Rating
—
Follow-up
Waiting for a rating

No example picked yet.

The rule behind the example

Reasons first, then the measure.

In the example a rating of 0 to 6 triggers a clarifying question. From 7 you know the reasons well enough to decide.

  1. 01Rate

    How well do you know the reasons?

    Reason

    The most frequent reasons, named by you.

    You honestly rate how surely you can explain the cancellations.

    Input → rating from 0 to 10
  2. 02Clarify

    At 0 to 6, gather reasons first.

    0–6Follow-up7–10Finish

    The sample rule asks for three concrete cancellations. A measure without a reason would be a guess.

    Condition → 0–6: clarifying question
  3. 03Decide

    With a review date.

    Review

    The reasons turn into a decision with a review date, first against the most frequent reason.

    From 7 it becomes a decision in Peak Log. In the trial run this is a local note.

    Sample artifact → churn note

What works today

See how Command follows up on decisions.

The interactive demo shows goals, decision cards and due reviews that you use for a retention goal today.

See the interactive demo

Peak Command / Your next step

Retention starts with the reason.

Check the rule in the example. Then ask three customers who left.

Check cancellation reasons
Local working example

Know why customers leave.

The reasons turn into a decision with a review date, first against the most frequent reason.

Frequently asked questions

Can I use churn risks 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.

Does Peak Command calculate a churn rate?

No. Peak Customer is not yet connected in Command. Command shows it as not available and never sets a value to zero.

Are the companies on this page real?

No. The companies and numbers are fictional examples. They show the flow, they prove no effect.

Does Peak Command store data of its own?

No. Peak Command owns no data. It reads the Peak products with your permissions and writes only through the owning product, such as decisions in Peak Log.

More in Peak Command

All pages in Solutions