A knowledge agent grounded in the company’s own work.
An internal agent that answers across departments: procedures, work instructions, ERP how-tos, policy. Grounded in the source documents, with references that point back. Email drafting and data work live on the same surface.
Answers
Grounded, with citations
Email drafting
One click into Outlook
Department leads
Live dashboards, live commentary
01 · The situation
Company knowledge lived in the wrong shape.
Procedures sat in a shared drive. Work instructions in an old wiki. ERP how-tos in a vendor-supplied PDF. Policy in a different folder again. Most employees had no idea where to look for half of it. Asking the institutional question always defaulted to pinging the person who had been there longest.
The cost was not just slow answers. Capable people across departments could not act with confidence because they did not have direct access to the company’s own knowledge. The longer-tenured people became routing layers for questions they had already answered a hundred times.
The pattern repeats wherever institutional knowledge is real, fragmented, and tribal.
02 · The approach
One surface for every employee, with the depth on demand for leads.
We built an internal agent grounded in the company’s own knowledge base — procedures, work instructions, ERP manuals, training materials, and policy documents — synced to the agent’s index. Every answer is grounded in source documents and the agent shows the reference, so the asker can verify, share, or escalate when the document itself is wrong.
The surface does more than question-and-answer. Drafting an email is one click to a populated Outlook draft. Working with a CSV or an Excel file happens in an integrated environment that can read, transform, and produce files. Forms tied to common workflows write back to the company database, so requests that used to live in inboxes become tracked entries.
Department leads get an advanced layer on top of the same surface: live dashboards stitched from ERP integration, with the agent surfacing what changed and why, updated as data moves. The admin team gets conversation flagging and usage monitoring — a way to see where the system is being trusted and where it is not.
03 · The result
Institutional knowledge stopped being someone’s job to hold.
Before
- Procedure question = ping the senior person
- Department silos with their own institutional memory
- Email drafting from a blank page
- Data analysis queued through the data team
- ERP knowledge buried in a vendor PDF
- Department dashboards built once, slowly going stale
- Tracked workflows spread across inbox threads
- System trust hard to read
After
- Procedure question answered with a citation
- Cross-department answers available to anyone
- Email drafting populated into Outlook in one click
- Data analysis on the same surface as the question
- ERP knowledge answerable in plain language
- Department dashboards live, with AI commentary on what changed
- Tracked workflows on integrated forms writing to the DB
- System trust visible in the admin dashboard
04 · What this pattern looks like
Any company whose knowledge runs on people who know how it’s done.
The more the company runs on tribal knowledge — the senior buyer who knows which supplier made which spec, the operator who knows why this step has to come before that one — the more this kind of system replaces “ping the senior person” with grounded, citable answers everyone can act on. It does not replace the senior person. It captures what they know in a form the rest of the company can use without queuing them.
The pattern fits manufacturing, distribution, professional services, public-sector operations, and any operation with depth of procedure. Anywhere a new hire’s first three months are spent learning how the company actually runs, a grounded internal agent earns its place quickly.
This work was built and shipped by Shane in a prior operational role, before founding McIntosh Systems. Anonymised here in the standard way; substantive details available on request.
Knowledge that runs on the longest-tenured people’s heads?
Send it over. We’ll tell you whether it’s a fit and what a first step looks like.
[email protected]