01 / Evidence fileAgency · Proposal open
Sample customer A
TimingIdeal window
Example: a reply was promised five days ago; the window has been reached.
Is now a good moment to get in touch?
Peak CRM · Next Best CustomerSample data · No real customers
Not the loudest customer.The most valuable next step.
When ten customers are waiting, gut feeling often decides. Here you compare two sample customers with the same questions and see why one comes first.
What decides it for you?
Is now a good moment to get in touch?
One clear question
Who is next, and why?
Two customers. The same questions. A recommendation with a visible reason.
01 / Your first perspectiveSample customer AAgency · Proposal open
02 / Your second perspectiveSample customer BConsultancy · Existing customer
01 / The basis for deciding
Two customers. The same questions.
Pick a focus. Each row asks both sample customers the same question. The values are made up and marked as an example.
4 dimensions · Same standard for both options
02 / Evidence fileConsultancy · Existing customer
Sample customer B
TimingNot due yet
Example: last conversation yesterday, next contact planned in two weeks.
Is now a good moment to get in touch?
| The criterion | Sample customer A | Sample customer B |
|---|---|---|
| TimingIs now a good moment to get in touch? | Sample customer AIdeal window Example: a reply was promised five days ago; the window has been reached. Demo exampleFictional sample data. No real customers, no real numbers, nothing is saved or sent. Sample data on this page | Sample customer BNot due yet Example: last conversation yesterday, next contact planned in two weeks. Demo exampleFictional sample data. No real customers, no real numbers, nothing is saved or sent. Sample data on this page |
| Open promiseIs someone waiting for an answer from you? | Sample customer AYes, proposal promised Example: a revised proposal was promised in the last meeting. Demo exampleFictional sample data. No real customers, no real numbers, nothing is saved or sent. Sample data on this page | Sample customer BNo Example: all promises are done. Demo exampleFictional sample data. No real customers, no real numbers, nothing is saved or sent. Sample data on this page |
| Possible valueWhat is at stake for both sides? | Sample customer ANew engagement Example: open opportunity in the “Proposal” stage. Demo exampleFictional sample data. No real customers, no real numbers, nothing is saved or sent. Sample data on this page | Sample customer BRenewal later Example: running contract, renewal only next quarter. Demo exampleFictional sample data. No real customers, no real numbers, nothing is saved or sent. Sample data on this page |
| Risk of waitingWhat happens if you do nothing today? | Sample customer AOpportunity cools down Example: without a reply, the proposal gets older every day. Demo exampleFictional sample data. No real customers, no real numbers, nothing is saved or sent. Sample data on this page | Sample customer BNo acute risk Example: stable relationship, nothing open. Demo exampleFictional sample data. No real customers, no real numbers, nothing is saved or sent. Sample data on this page |
Transparency is part of the comparison.
Source code is evidence of implementation. It does not replace a current live test.
Our standard
No black box.Reasons you can check.
A recommendation only helps if you understand it. That's why every reason is visible, and missing knowledge stays visible too.
Explainable signals
Every recommendation states its reasons.
Timing, last action and open promise sit next to the recommendation, not behind it.
- 01
Same questions
Both customers are looked at with the same criteria, not with sympathy.
- 02
Reason before rank
An order without a reason is just a list. Every suggestion names its reason.
- 03
Unknown stays unknown
If information is missing, it is shown as open, not estimated.
02 / From feature to moment
Test it with your own customers.
Pick a check and run it with two real customers from your work, in your head or on paper.
Where do you want to start?
Take two real customers from your work and ask them the same questions.
Your checkFor both options
The same task
The open promise
Find two customers you promised something to. Who has been waiting longer?
What you check
You know whom to answer first today and why.
Backed by code
Features marked “built” in the Peak CRM requirement register. A register doesn't replace your own test in your workspace.
Source checked:
Peak-Admin/peak-one@191601e · docs/prd/peak-crm-prd.md (requirement register)Task selected. No test run.
See the steps03 / Before the next step
From the reason to the action.
In Peak CRM the comparison becomes a work stack: one contact after another, with a reason and a suggested action.
- 01Bring in contacts and open opportunities
- 02Set a contact window per contact
- 03Start the stack and work through it
Switching is a separate decision. Prepare it and keep the open evidence in view.
From choice to action
Justify first. Then call.
The recommendation stays a suggestion. You decide what happens.
The next sensible step
Your next customer is already waiting.
Start Peak CRM and get the next contact with its reason. The decision stays with you.
Start Peak CRMThe sample customers on this page are made up. Work stack with reason and suggested action per the Peak CRM register.
The next step
One customer. One action. Today.
Peak CRM puts the next contact in front of you with a reason; you do the work.
Frequently asked questions
How does Peak CRM know who comes first?
The order comes from transparent rules: due steps, open deals, last activity. Every entry shows its reason.
Does an AI decide for me?
No. Peak CRM suggests an order; you decide and can move or skip any step.
Are the customers on this page real?
No, they are clearly labelled sample data. You see real customers only in your own workspace.