Ledger and Cloverpop
Ledger or Cloverpop?
Cloverpop helps a large company run decisions through a set process and keep a record of each one. Ledger asks your team to write down what a decision should change, then brings in the numbers that show whether it did.
Launch the partner referral program
Decision · Approved · Announced in #sales
Rationale and the data the team used are attached.
Outcome: to be tracked by the partnerships team.
Launch the partner referral program
- Deals sourced by partners≥ 12 a month
- Watching: sales cycle lengthNo worse
- ReadingsDaily from HubSpot
- Check onJan 15
The verdict waits on the numbers, and a person settles it
Where the two part ways.
- 1
The expectation comes first
A decision in Ledger names the numbers it should move and a date to check them before any result exists. After it settles, nobody can edit it, only replace it with a new decision that points back.
- 2
The numbers arrive on their own
Connect the tool a metric lives in, and readings come in hourly, daily or weekly. Cloverpop doesn't advertise pulling results from your metrics tools.
- 3
Side effects stay on the record
A decision can watch the numbers it shouldn't hurt, measured against the weeks before the change, so a win that broke something else still shows the damage.
- 4
It shows how far to trust a result
Ledger reads a change that went to everyone at once as low confidence, and one tested against a held-out group as high, and says why.
- 5
It starts from what you already have
Upload decks and minutes, or paste meeting notes, and Zero drafts the decisions in them for your team to keep or drop.
When Ledger is the right choice
- You want to know whether your decisions moved the numbers they were meant to move.
- The numbers live in tools like Stripe, Amplitude, HubSpot or Pipedrive.
- You want a reminder with the evidence attached when a check date arrives.
- You want a team record of how often expectations held, with no one ranked.
Job by job
What a record holds
Cloverpop: What was decided, why, by whom, the data used and the outcome.
Ledger: Why, the numbers it should move with targets, a check date, the evidence and the lesson.
Getting a decision made
Cloverpop: Playbooks, polls and approvals, often inside Slack or Teams.
Ledger: Ledger records the call your team already made, in Ledger or in a ZeroWidth room.
Where results come from
Cloverpop: The team tracks results, and the record exports to Excel.
Ledger: Feeds from connected tools, your code, a pasted spreadsheet or a typed reading.
Changing it later
Cloverpop: Cloverpop doesn't advertise a lock on settled decisions.
Ledger: Open decisions can be edited, and settled ones can only be replaced.
Coming back to it
Cloverpop: Track results from Slack.
Ledger: A reminder by bell and email when the date arrives, with the readings already on the page.
Learning across decisions
Cloverpop: Search past decisions and their outcomes.
Ledger: Searchable lessons, a team record of expectations that held and a map of what nobody has decided on lately.
Already deciding in Cloverpop? Bring the results here.
Some teams keep the approval process where it is and use Ledger to check each approved decision against the numbers.
- Export your decisions from Cloverpop to a spreadsheet, add it to a folder, and ask Zero to draft the ones worth tracking.
- Connect the tool each metric lives in so readings arrive without anyone pulling them.
- When a decision settles, the lesson sits next to it for the next person who asks why.
Questions
- Can we change an expectation after we see the result?
- An open decision can be edited. A settled one can only be replaced by a new decision that points back to it.
- How does Ledger show how well the team decides?
- Ledger shows how often the team's expectations held across the whole workspace, and it never splits that by person.
Try Ledger with your domain.
Pick one decision your team made last month, and write down what it should have changed.
No website? Describe what you do
If you'd like help with the first changes, talk to us.