Resources

Governed, not merely fluent

Written for the people who have to answer for the number: what makes a natural-language answer governed rather than merely fluent, and how to test whether a platform's version of that holds up.

14 guides published

Getting answers out of your business systems

Why a simple question takes weeks, what self-service analytics keeps getting wrong, and how to judge an AI analytics tool without being technical.

Why does every report take three weeks?The delay is rarely the query. It is the queue, the definitions argument, and the fact that your data lives in six systems that were never introduced.
One view of the customer, without an 18-month data projectYour customer exists in the CRM, finance and the support desk under three different names. What it takes to join them up, and what to insist on.
What to ask an AI analytics vendor before you buyNine questions that separate a tool your finance team will actually use from a demo that impresses once. No technical background needed.
Self-service analytics: why it keeps failing, and what changedThree waves of self-service tools promised to remove the analyst bottleneck. Here is why each stalled, and what is genuinely different this time.

Rolling it out without it becoming shelfware

What the first ninety days actually require, who owns definitions, what security will ask, and how to tell early whether it is working.

Governed AI analytics

How natural-language analytics stays trustworthy at scale: semantic layers, certified metrics, row-level security, and testing a vendor's accuracy claim.

How we measure answer quality

The corpora, the grading tolerance, what blocks a release, and how often the system declines a question it should have answered — published in full, including why there is no headline accuracy percentage.

Read the method