BACKED BY
what did we actually pay Meridian last quarter?
$184k across Q3 — from the finance runbook.
One more detail only you can see: that’s $61k under cap after the June renegotiation. The memo’s restricted to finance-leads.
Every answer tracks which sources it used and who’s cleared for each — so the cleared part posts in the channel, and the rest reaches you as a DM. Ask in public without thinking about what the answer might touch.
why did we drop the Q3 vendor?
Nothing written down — asking Dana, she made the call.
pricing held, but their SLA slipped twice — we moved on.
Captured — next time this answers instantly.
When the answer was never written down, most tools shrug. We route the question — inside Slack — to the person who actually knows, get their answer, and remember it so nobody has to ask again.
What your company didn’t know this week:
▁▃▅█ Refunds over $10k — asks ↑3.1×, no owner → nudged @maya
▁▂▃▅ Q3 pricing — 12 asks, the answer lives with one person
▁▁▂▃ 41% of all questions hit the same 3 people
Every question routes through one layer, so the gaps become visible: what’s surging, what has no owner, who the org quietly depends on. Delivered as a Monday brief — measured from live question traffic, not an annual survey.
Answers from your company’s knowledge, with sources you can check — plus the parts nobody else does.
In the channel, in the thread. No new tab, no portal.
The cleared part posts publicly; the restricted part arrives as your DM.
Unwritten answer? It finds the person, asks, and brings it back.
Every captured answer joins the record. The org stops re-asking.
Surging topics surface before they hit a deadline — with a nudge to the owner.
Who the org depends on, measured from live question flow — not surveys.
Sources and confidence attached to every answer. Check the work.
An MCP endpoint with the same ACL checks as a person. Coming soon.
Give it a question that needs five people’s answers. It asks each one, assembles, reports back.
Captured answers become browsable, always-current pages — compiled from what people actually asked.
New hires ask the layer instead of interrupting the team — and get the tribal answers too.
Unanswered and surging? It climbs the chain politely, with the context attached.
A private email can never surface in a public channel.
That’s not a policy — it’s the architecture.
