Keegi
Your company already knows. It has no index.
Past about two hundred people the index is one or two well-connected colleagues answering from memory. That works, right up until they take a holiday. Keegi builds the index out of work the company has already done.
The loop
Somebody asks in their own words.
No filters, no tags, no dropdowns. “Who has dealt with a German works council on a software rollout?” Keegi returns at most three people, and for each one a name, a sentence about what they did, the evidence that sentence rests on, and a draft opening message to edit and send.
The sentence is the product. Nobody sends a cold message to a name on a list, which is why the directory you already have goes unused. “Ran the Betriebsrat consultation for the Berlin office’s Workday rollout in 2024” is what makes somebody hit send, and everything upstream exists to earn the right to write that sentence truthfully.
The refusal
Some questions come back with nobody.
Nobody at Northwind has evidence of taking a device through a regulatory submission. The person you want is a regulatory affairs or quality lead. Northwind has no one in that function.
Logged as a gap.
That is not a degraded answer, and it is the reason the other answers are worth reading. A system that always returns three names is a system where the third name is noise, and one wasted afternoon teaches somebody to stop asking.
It also names the kind of person who is missing and files the question. Those refusals accumulate into the one demand signal no other system in your company produces: not what people searched for, what they needed a person for and did not have one.
At company scale
Two things only work once it can see everyone.
The best answer is one you can reach.
Keegi reads the org chart, timezone and reporting line alongside the work, so it ranks on whether somebody can help you today. It spreads load on purpose: if one person has been the answer eleven times this month, the twelfth question prefers the second-best match and tells you it did. Every expertise product that skipped this was uninstalled by its own experts.
Everyone can read their own card.
Every employee sees the profile Keegi holds on them, down to the evidence behind each capability, and can suppress any of it or see who asked about them. People will not fill in a skills form. They will correct a wrong claim about themselves the same day, which is also the highest-quality correction signal in the system.
The boundary
What it is not.
Not a directory: there is no browse page and no filter panel. Not a chatbot that answers your question, because it tells you who can. And not a productivity tool — nothing here counts anyone’s output.
The last one is a design decision and not a policy, which means there is no setting to turn it back on. Keegi holds capability and coverage, never activity, so there is no ticket count to expose and no productivity number to leak into a review. The line Keegi does not cross states it in full, in the form a works council will ask for.
Twenty minutes. No demo, no pitch. I want to know whether this problem is real where you work.
Five questions firstBack to the demo