10 February 2026 · 1 min read
The prompt library is one of our most valuable assets
We've been building a prompt library internally for about 6 months.
Started as a few things that worked well, shared in a Teams channel. Now it's a structured system, prompts organised by use case, output type, which tool works best for what.
The thing I didn't expect: it's become one of the more valuable assets in the business. New staff get up to speed faster. Experienced staff produce more consistent work.
Why it works
A prompt library sounds like a small thing. In practice it's closer to a playbook, it captures how we think about problems, not just how we use a tool.
When a senior consultant writes a great prompt for scoping an AI readiness assessment, that knowledge doesn't leave when they go on leave. It's in the library. The next person uses it, improves it, adds a note about what to watch out for.
That's institutional knowledge. The kind that used to live in people's heads.
The businesses that build this kind of asset early are going to have a meaningful advantage. Not a technology advantage, the tools are available to everyone. An institutional knowledge advantage.
That's harder to copy.
More writing
19 March 2026
How I deployed an enterprise AI agent on Azure with Teams, email, and SharePoint
Full walkthrough: OpenClaw on a Linux VM, connected to Microsoft 365 via Graph API and Bot Framework. What I built, what broke, and what I'd do differently.
24 February 2026
We rebuilt how we write proposals
It used to take half a day. Now it takes 45 minutes. The interesting part isn't the time saving.