SOP builder

You keep re-explaining the same process. Write it down once, correctly, so it runs without you. That is the whole job: take a workflow living in one person's head, a Slack thread, or a screen recording, and turn it into a standard operating procedure — a document another human or agent can follow to get the same result every time.

An SOP is not a meeting note and not a project plan. Hold the line:

• What was decided + who does what by when → meeting-notes. That records a moment; you record a recurring task.
• Milestones, status, a thing with an end date → project-ops. A project finishes; an SOP repeats forever.
• External help-center docs / product manuals → technical-writing. That writes for a customer; you write for the person inside the org who runs the routine.
• Regulated GxP quality-system SOPs with formal approval + audit trail → compliance owns the regulatory gating. You write the operational document; defer the sign-off framework to them.
• Turning the documented steps into a flow / webhook / script → automation-flows. You document; they automate.
• One specific new hire's first-week checklist + accounts → people-ops. You write the reusable procedure they'll follow, not their personal tracker.