Skip to content

Your company forgets why.

Why do we price it this way? Why did we drop that vendor?
The pieces are in Slack, Notion, GitHub, your CRM, a meeting nobody wrote up, and one person’s head.
Conscilliance puts the reasoning back together.
One question, half-answered in six places. None of these is the answer.
SLACK · #PRICING11 AUG
“Support costs follow usage, not seats.”
Nobody wrote down what was decided
HUBSPOT · MERIDIAN HEALTH
“Their finance team can’t process usage-based invoices.”
THE DECISION
We changed how we price.
Nobody recorded why
Priya R.
PRODUCT
“Three of our five biggest accounts tripled usage on flat seats.”
WRITTEN DOWN NOWHERE
Does that exception still apply when they renew?
01 / THE PROBLEMSUBJECT: HOW WE PRICE

The information exists.
The context doesn’t.

Everything needed to answer it is written down somewhere. The answer itself is written down nowhere.

“Why do we price it this way?”

WHAT SEARCH FINDS
  • A Slack thread from August
  • A Notion doc last edited in March
  • Two notes on a CRM record
  • A comment on a pull request
  • A meeting nobody wrote up
  • One person who was in the room
WHAT YOU STILL HAVE TO WORK OUT
  • What was actually decided
  • Why — and what was ruled out
  • What has changed since
  • Which of it is now out of date
  • What nobody has an answer to yet

Everyone who asks does that work again. Six months later the answer walks out of the building with the person who did it.

02 / THE ANSWERANSWER COMPLETE · 1 SOURCE IT COULD NOT READ

“Why do we price it this way?”

ASKED BY SOFIA D. · ANSWERED FROM WHAT SOFIA IS ALLOWED TO SEE
WHAT IT READ · 6 PIECES
SLACK · #PRICING · 11 AUG
Support costs follow usage, not seats
NOTION · REVENUE REVIEW
Seats flat, usage tripled on 3 of the 5 biggest accounts
MARIE R. · FINANCE
Charging purely on usage makes revenue impossible to forecast
HUBSPOT · MERIDIAN HEALTH
Can’t process usage-based invoices
LINEAR · BIL-241
Usage is charged above the included allowance only, never per seat
WRITTEN DOWN NOWHERE
What happens to the exception at renewal?

ONE QUESTION · ONE ANSWER

THE ANSWER
TODAYSince 1 September you charge a flat fee per company, plus usage above 250,000 calls a month. One plan, not three tiers.
WHYSeats had stopped tracking value: three of your five biggest accounts tripled usage without adding a seat. Support costs followed usage, not headcount.
WHAT CHANGEDPer-seat pricing was replaced. Charging purely on usage was rejected — Finance could not forecast revenue on it.
WHO KNOWSPriya Raman decided it · Dana Whitfield found the discounting · Léa Moreau owns the Q4 launch that depends on it.
STILL UNCERTAINFinance and Sales disagree on when existing annual contracts move over: Finance says at renewal, Sales has told customers 1 January. Open since 29 August.
SOURCES
NOTION · REVENUE REVIEWHUBSPOT · MERIDIANSLACK · #PRICINGPRIYA RAMAN1 SOURCE YOU CAN’T ACCESS
03 / BEFORE / AFTER

Your company remembers what happened.
Conscilliance remembers why.

BEFORE
  • Search results to read through
  • Documents that may be out of date
  • The reasoning in someone else’s head
  • The same debate, twice a year
  • Old and current answers, side by side, unlabelled
AFTER
  • What is true now
  • Why it was decided that way
  • What changed, and what it replaced
  • What is still unresolved
  • Who to ask, and where every claim came from
04 / OVER TIMESUBJECT: HOW WE PRICE

Old decisions don’t disappear when you change your mind.

A decision that loses its history gets argued again every six months. So the ones it replaced stay readable — struck through, never deleted.

D-072
06 MAR 2025
REPLACED
Per-seat pricing, three tiers, annual commitment.

Chosen when buyers understood seats and billing could not measure usage. Three signed accounts and the sales playbook still describe it.

D-104
21 JUL 2026
REPLACED
Usage-based pricing, tested with three customers.

Run to test whether usage could be billed reliably for every account. It could not — but its data made the current model credible.

D-118
22 AUG 2026
CURRENT
Flat fee per company, plus usage above the included allowance.

Owned by Priya Raman, decided 22 August, effective 1 September. One plan, 250,000 calls a month included. Per-seat quoting survives as one named exception: Meridian Health, whose finance team cannot process usage invoices.

STILL OPEN · WHEN CONTRACTS MOVE OVER
WHAT MOVEDWEEK OF 31 AUG
  • NOW OUT OF DATEPer-seat pricing is no longer the plan. Two things you own still describe it: the pricing FAQ and the trial email sequence.
  • DISAGREEMENTFinance and Sales still read the migration date differently. No decision from the owner yet.
  • STILL UNKNOWNWhether Meridian’s exception survives their renewal. Asked twelve days ago, answered by nobody.

A feed of the same week would have shown four file edits and three comments. None of them said the plan had changed.

05 / WHERE IT HELPSONE CONTEXT, MANY USES

What it’s good for.

These aren’t six products. They are six things that get easier once the reasoning behind the work is written down and stays current.
  • Ask the company a questionAn answer with its reasoning attached, not ten links to read.
  • Onboard in weeks, not quartersNew people read why things are the way they are instead of asking around for it.
  • Keep what people know when they leaveWhat someone decided, and why, stays behind after they do.
  • Catch contradictions earlyTwo teams working from two different answers — before a customer finds out.
  • Give your AI agents real contextAgents that inherit your decisions and constraints instead of guessing at them.
  • See what actually changedOnly the things that moved in the work you depend on.
06 / TRUSTWHAT IT DOES · WHAT IT NEVER DOES

An answer you can check.

  • EVERY CLAIM HAS A SOURCEYou can see where every part of an answer came from, and when.
  • YOU SEE WHAT YOU CAN ALREADY SEEAnything you are not allowed to read is left out — and counted, so you know it was.
  • IT SAYS WHEN IT DOESN’T KNOWDisputed and unknown are answers too. They come with who is arguing and how long it has been open.
  • AI SUGGESTS, PEOPLE DECIDENothing a model works out on its own becomes company truth until a person confirms it — and the record shows who did.
NEVER
  • Screenshots or keystrokes
  • Hours, presence or activity scores
  • Ranking people against each other
  • Connecting a source without telling people

When a Slack channel is connected, the people in it are told. Privacy is something you can watch happen, not something you have to take our word for. Read the full position →

07 / PILOT

Start with one question you keep re-answering.

We work with a small number of teams. Pick one subject — how you price, why the roadmap moved, what you promised a customer — and in six weeks we build the reasoning behind it with you. After that it stays current with your team: automatically where the sources can prove it, and with a person where they can’t.

  1. ONE SUBJECT, BUILT WITH YOU
  2. YOUR TOOLS CONNECTED, YOUR TEAM TOLD
  3. DECISION RECORDS THAT ARE YOURS TO KEEP
  4. DIRECT ACCESS TO THE TEAM
  5. NO CREDIT CARD