We've both been that engineer.
The one on a Friday night, staring at a Slack thread from three months ago that almost explains how the incident was fixed — if only someone had written the last part down.
ScribeOps started as a script. Then it became an internal tool. Then our teammates kept asking if they could use it. That's usually how this goes.
Two engineers. No VC pressure (yet).
Matt built infrastructure tooling at a Series B fintech for four years. Priya spent three years as a platform engineer at a 400-person SaaS company where they had 11 Slack workspaces and zero runbooks. They met at a conference talk about observability and spent the after-party complaining about documentation debt.
Matt Hollis
Co-founder, eng
Wrote the first version of the redaction engine on a train. Still maintains it, though it looks nothing like the original.
Priya Nair
Co-founder, product + eng
Runs beta, talks to customers, fixes whatever Matt breaks in prod. Occasionally also breaks things in prod.
Dom Vasquez
Infrastructure (part-time)
Keeps the deploy pipeline from catching fire. Has strong opinions about Kubernetes that nobody asks for and everyone benefits from.
The actual problem, as we see it
The documentation problem isn't laziness. Engineers are not lazy. Engineers will write a 400-line Terraform module on a Sunday if the problem is interesting enough. The documentation problem is that writing docs happens at the worst possible moment — right after an incident, when everyone is relieved it's over and wants to move on. The motivation has already evaporated.
Every tool we tried asked engineers to change their behavior. Fill in this template. Open this page. Write this doc. The behavior never changed. The docs never got written.
ScribeOps works differently because it doesn't ask. It watches how your team already works — in Slack, where the real conversations happen — and it writes the doc from what's already there. An engineer approves it in 30 seconds. Done.
“The best documentation tool is one your engineers don't know they're using.”
We don't think we've solved it. We've solved it for post-mortems and ADRs and onboarding FAQs. There's more to do. We're working on it.
~2,400
docs auto-generated in beta
31
beta teams across 9 countries
94%
approval rate (docs accepted as-is)
0
raw chat logs ever seen by us
Numbers from beta period, Mar – Aug 2025.
We'd like to hear from you.
Genuinely. Whether you want to try it, you have feedback on the idea, or you just want to tell us about your documentation horror story.