The knowledge and expertise maps
One page each: where answers live and where they don't; who knows what, including what's only in heads. The two pages that change how you think about hiring and leaving.
Half of what your organization knows is in a document nobody can find. The other half is in someone's head. Your AI assistant can only answer from the first half, and only if it's current, not duplicated and not contradicted by another version. The Knowledge Diagnostic maps where answers live, who knows what, what's stale or wrong, and how your AI actually performs on real questions. You leave with a 90-day plan you keep.
CAD 3,500, fixed.
Credited against the Pilot First Class set-up or the GoodOps retainer if you go ahead within 60 days.
Two weeks. Read-only. Nothing is changed
until you say so.
Each lens is scored with the evidence beside it. Nothing in the report is an opinion without a screenshot, an export or an interview behind it.
Where answers live today: Drive, SharePoint, Notion, Slack, the wiki from 2022, the inbox. Where they're missing entirely.
Who the team actually goes to for answers, and which of that knowledge is written down nowhere.
Stale, conflicting, duplicate and ownerless material, with examples. The two policies that disagree. The template everyone copies from.
Twenty real questions your team asks, put to your AI assistant. Scored for accuracy, citations and whether it respected access.
What people and AI can see, what they shouldn't, and where sensitive material sits in a folder with the wrong permissions.
How knowledge moves into onboarding, support, proposals and the daily questions, and where it stops.
Delivered in a 60-minute walkthrough with the owner, then yours to keep.
One page each: where answers live and where they don't; who knows what, including what's only in heads. The two pages that change how you think about hiring and leaving.
Twenty real questions, your assistant's answers, and why they were right, wrong or blind. Usually the clearest argument for fixing the sources first.
Clean up, capture, connect: what to retire, who to interview, what to build first. Priorities, owners and a baseline to measure against. Yours whether or not we build it.
You can stop after the report and keep everything. Most organizations don't, because the fix list is already written.
Agreed sources reviewed. Short interviews with the four or five people everyone goes to. Twenty real questions collected from the team.
The AI answer check run and scored. Maps, content review and plan written. A 60-minute walkthrough with the owner.
A focused Pilot set-up with First Class, Voice Memory to capture what's only said out loud, or your own team with the plan.
Credited against the Pilot First Class set-up or the GoodOps retainer if you go ahead within 60 days.
Book the assessmentThe things owners ask us on the first call.
A wiki is where someone once wrote things down. The diagnostic measures whether the team actually uses it, whether it agrees with the other three places answers live, and whether your AI can find anything in it.
Pilot is the knowledge engine we use to connect, organize and govern what your organization knows, without moving the originals, so people and AI tools like Claude and ChatGPT answer from the same trusted sources. GoodOps runs the diagnostic; Pilot First Class does the build if you go ahead.
We collect twenty real questions from your team, ask your AI assistant, and grade the answers for accuracy, citations and access. It's the fastest way to see what's wrong with the sources underneath.
No. Sources stay where they are. The diagnostic maps them; the build organizes how they appear and what AI can see. Any migration is scoped separately and agreed with you.
Book the Knowledge Diagnostic. Two weeks, four interviews, twenty real questions, and a 90-day plan you keep.
Book a 30-minute callA conversation about your organization.
Not a demo of software.