#Method
#Data
#AI & Agents
A normal CRM activity log is a set of form fields, type, subject, outcome, due date, written for a salesperson to scan. I threw that out and reshaped ...
Jesse James Richard
Read previous|
May 6, 2026An AI that writes and maintains your knowledge base
|
4 min read
#Product
#AI & Agents
Giant Context writes your knowledge base, the help articles a customer reads to answer their own question. Writing them is one job. Keeping them true as your product changes is the one that never stops, and it is the one this does.
Written from what you already have
The articles come out of your own material, the same way your pages do. Your specs, your documents, your product information. They describe your product rather than one a model imagined, and they are right on the day they publish.
The maintenance nobody does
The cost of a knowledge base was never the writing. It is the maintenance.
You ship a change. Somewhere in your articles, one now describes a button that moved, a screen that was redesigned, a feature that was renamed. Nobody notices, because reviewing old articles is nobody's job. A customer follows one into a dead end and trusts the rest of it less. You built it to take work off your support queue and it starts putting work back on.
Kept current by the thing that wrote it
Mind, the part of the platform that decides what your marketing needs, reads your articles back against what your business looks like now and finds the drift. An outdated reference, a stale screenshot, a section gone thin, an article missing the troubleshooting steps it should have. For each one it proposes a specific fix to a specific article, and you approve it before a customer sees it, the same review step the autonomous email uses.
One article, titled Exporting your data, walks a customer through a button labelled Download CSV. Two weeks ago that button was renamed to Export and moved. The article now sends people to a control that is not there. Mind, reading the article against the current product, catches the mismatch and proposes the fix on that one article, the new label and the new location. You read it, see it is right, and approve. Nobody went looking for the broken article, because the thing that wrote it was still reading it.
Nothing about this happens quietly. It does not rewrite a live article behind you. It names the article, names the problem, and waits.
A technical writer you do not hire
A knowledge base is a technical writer's job. Building one is a project and keeping it current is a standing cost, which is why most small businesses either never build one or let the one they have go stale. This gives you a support asset you could not otherwise staff, and takes away the part that made having one not worth it.
An article you write yourself stays right until your product moves. These stay right because something is still reading them.
And the help articles are not a special case. Mind is reading your pages, your posts and the emails going to your customers the same way, against the same picture of what your business is now. The knowledge base is one surface it watches.
Hiring an early engineer, or building something like this
Remote, Pacific time, full-time or contract. Get in touch.