Make every AI claim clickable

Customers told me the same thing in workshop after workshop: they don’t want the AI to just give them the answer. They want to check it. I heard it running AI study-analysis sessions at Lyssna, where the room was full of researchers whose whole job is to not get fooled by a confident summary. The output that impressed them in the demo was the same output they didn’t trust enough to put their name on. The gap between those two reactions is where most AI features quietly die.

The thing that closes the gap is small and unglamorous. Make every claim clickable. When hey anna says a change is statistically significant, that claim is a link: click it and you land on the test behind it, the two groups, the sample sizes, the p-value, the rows it ran on. Not a restatement that it held; the working itself. When it says revenue rose 18%, the number resolves to the 340 orders it was computed from, not a summary of them but the orders. It is the same move deep-research tools made when they started footnoting every sentence back to a source you can open, and at hey anna the whole product is built on it: verification over generation, which is what makes the brand line “analyst, not chatbot” true.

There is a deeper point under the citations, and it is closer to what hey anna actually is. Because every claim resolves to your own rows, the agent stops being a box you query and becomes an interface to your data. It works in your dataset and updates it as you go; you can stay fully hands-off and let it run the analysis, or drop into the sheet and work the numbers yourself, and either way it is the same data in the same place. A collaborative workspace, where plain language is just the fastest way in.

What clickable actually means

Clickable is not a citation icon that opens a vague “sources” panel. The bar is higher and it is specific.

A claim is clickable when three things are true. The link points at the exact evidence, not the general neighbourhood: the rows, the source document, the calculation, not “the sales table.” The path is short enough that a sceptical user will actually take it, which in practice means one click, not a five-step drill-down. And the evidence is legible when they arrive, so a person can look at it and agree the claim is fair, rather than landing in a wall of raw data they now have to re-analyse themselves.

Miss any of the three and you have a decoration. A citation that resolves to “rows 1 through 9,000” is honest and useless. A claim that takes four clicks to verify gets verified once, by you, in the demo, and never again by a customer. The work is in making verification cheaper than doubt.

Why it changes adoption, not just trust

The intuition is that citations make people trust the AI more. That is half of it, and the less interesting half. The bigger effect is on what the user does next.

An AI feature is adopted when it becomes a step in someone’s actual workflow. A summary that lands in their inbox is not a step; it’s a thing they read, nod at, and route around when the real decision gets made, because they can’t defend it to the person who asks “where did this come from?” A clickable claim survives that question. The user can forward it, cite it in a deck, drop it into a board pack, because the evidence travels with the assertion. That is the difference between a feature people try and a feature people build on.

The pattern shows up as a fork in the usage data. The uncited version gets opened, admired, and abandoned; sessions are short and they don’t repeat. The cited version gets opened, clicked into, and returned to, because the user has learned that the claims hold when they pull on them. Verification is not friction you tolerate. It is the thing that lets someone stake their own credibility on your output, and people only stake their credibility on tools they can check.

What it costs to build

This is not free, and pretending it is would set you up to cut it under deadline. Clickable claims force an architecture where every assertion is traceable back to its evidence by construction. The number has to be computed deterministically, carry a reference to its inputs, and survive the trip into the sentence the user reads.

In practice that means the model is never the thing doing the counting; it renders facts that were settled before it saw them. It means a UI layer that keeps the link between a phrase and its source intact instead of flattening everything into prose. And it means resisting the demo-friendly shortcut of letting the model freestyle a narrative, because a narrative with no anchors is exactly the thing your customer has already learned not to trust.

Why it’s worth it

The cost buys two things that are hard to get any other way. It buys adoption, because a checkable claim is one a professional can act on without putting their own judgement at risk. And it buys a moat, because traceability is slow to copy and gets harder to fake as your product touches more of a customer’s real data. A competitor can match your model in a weekend; matching a system where every claim resolves to its evidence takes them as long as it took you.

There’s also the economics, which happen to point the same way. hey anna runs at under a dollar a day against analyst alternatives that start north of $400 a month, and the thing that makes the cheap version trustworthy enough to replace the expensive one is not a smarter model. It’s that you can click on what it tells you. Cheap and checkable beats expensive and opaque.

Build the feature so a sceptic can audit it in one click. The sceptic is your most valuable user, because the sceptic is the one who decides whether anyone else gets to depend on it.