THE SOURCE
Loom
→Every founder Loom, customer call, internal walkthrough — auto-transcribed, indexed, and surfaced to the rest of the system.
02 — DOCS AGENT
Docs that
keep up
with you.
Drop a Loom or merge a PR. An agent watches what you ship and keeps every doc surface current — in your voice.
The problem
Help articles last touched at v0.4.
Every founder ships the same thing. They Loom an explanation. Drop a Notion page. Type the same answer into Slack for the fifth time. Then ship the next thing. By Tuesday the Loom is buried, the Notion page is half-finished, and the help centre still describes the version from December. Support takes the hit. Onboarding takes the hit. The team takes the hit. The work was done — it just never landed where anyone could find it.
- — LOOM uploaded once, never transcribed, never reached the team.
- — INTERCOM articles last touched at v0.4. You shipped v0.9.
- — NOTION pages started by the cofounder, abandoned by Tuesday.
- — SLACK the same answer typed three, four, five times this month.
Your docs went stale the moment you shipped past them.
The shift
Write once.Forget forever.Kept current.
Most documentation tooling assumes a human will sit down and write. They won't. They'll ship. The Loom you recorded explaining the new flow has more context than any article you'd write afterwards — but it's a video file nobody can grep.
The docs agent flips the model. It watches what you ship — Looms, PRs, Slack threads, calls — and treats them as inputs to a continuously-rewritten doc surface. Your help centre, wiki, and social calendar are downstream of the work, not upstream of it. The next time you Loom an answer, it becomes an article. Quietly. Tagged with the source. Versioned with the ship.
Your team didn't write docs this week. They shipped product. The docs got written anyway.
What it watches
Everything you ship.
Not just code. Anything that's a knowledge artifact about how the product works, why a decision was made, or what to tell a customer.
- ·LOOMFounder walkthroughs, customer calls, internal demos.
- ·RELEASE NOTESEvery PR merged, every diff worth surfacing.
- ·SLACKInternal Q&A and the words your team actually uses.
- ·CALLSSales and support recordings, transcribed and indexed.
- ·EXISTING DOCSYour current help centre and wiki, kept in sync.
- ·SOCIALHighlights piped to the content calendar, in your voice.
How it works
One agent. Every doc surface.
When something shipworthy happens — a Loom drop, a merged PR, a recurring support question — the agent decides which surfaces care, drafts the update, tags the source, and ships it. Help centre, wiki, support thread, release-note PR, social-calendar draft. All from the same writeup. All in your voice.
“Updated by an agent.that’s the whole product
Integrations
Plugs intoyour stack.
Loom, Intercom, Notion, GitHub, Slack — the agent shows up wherever your team already works. Read access to the inputs, write access to the surfaces. Nobody learns a new tool; the docs just stay current.
PUBLIC ARTICLES
Help Center
→Articles drafted, updated, and version-tagged when you ship. Customers see the current state of the product, not December’s.
INTERNAL
Wiki
→Your Notion / Confluence / internal wiki, kept in sync with the help centre. One source, two audiences.
SLACK · CHANNELS
Support
→When a question lands in support — internal or customer-facing — the agent answers in-thread and cites the article it pulled from.
GITHUB · CHANGELOG
Release notes
→Every merged PR worth surfacing comes back as a drafted release note — for the changelog, the help centre, and the team channel.
QUEUE
Social calendar
→Every shipworthy moment becomes a draft in your content calendar — Twitter, LinkedIn, newsletter. Your voice, your moments.
Same tools your team already uses. Always current.
The side effect
Customer support
answers itself.
With docs that match what you actually ship, the most common customer questions get answered before they hit a human. The agent reads the support thread, finds the matching article, replies with the answer and the source. When the question is new, the answer becomes the next article. The help centre gets denser as the team ships more, and every cohort of customers needs less hand-holding than the last.
~80%
Repeat questions auto-answered
0 stale
Articles in the help centre
How it lands
We wire it. We seed it. It stays current.
01 · WIRE UP
Day one.
We connect Loom, your help centre (Intercom, Zendesk, custom), your wiki (Notion, Confluence), GitHub, Slack, and your social calendar. Read access to the inputs, write access to the surfaces.
02 · SEED
Week one.
We backfill what's already shipped, learn your voice from the docs that exist, and draft the first round of updated articles. Your help centre shows up populated, not empty.
03 · STAY CURRENT
Week two onward.
Every ship, every Loom, every PR — the agent updates. We're around when you want a new doc surface plugged in or a tone shift.
/ Ready when you are
See your docs kept current
Twenty minutes. We walk through what you ship, where your docs live, and what one looks like for your team.
Or email matthias@lifeisapitch.io