# #213: Don’t have an SOP… Start Here.

Page: https://stenobird.com/podcast/duo-on-air-podcast-4980211/213-don-t-have-an-sop-start-here
Text version: https://stenobird.com/podcast/duo-on-air-podcast-4980211/213-don-t-have-an-sop-start-here.md
Podcast: [Duo On Air Podcast](https://stenobird.com/podcast/duo-on-air-podcast-4980211)
Published: 2026-04-13T07:00:00+00:00
Episode link: https://duocollective.com/blog/how-to-write-an-sop
Audio file: https://episodes.captivate.fm/episode/844ee3d1-96cc-4d49-8ed2-401a31457b67.mp3
Processing state: not_requested
JSON: https://stenobird.com/v1/public/podcasts/duo-on-air-podcast-4980211/episodes/213-don-t-have-an-sop-start-here
Duration seconds: 1946

## Resource

If your business stopped tomorrow, could someone else step in and run it? In today's episode, we’re breaking down how to start building SOPs in a way that actually feels doable, not overwhelming. We’re sharing how we document our processes at Duo, from refining your offers and writing out every step to turning those workflows into repeatable systems your team can follow. We also talk about email templates, internal “how-to” libraries, and why SOPs are one of the biggest unlocks for growth, even if you’re still a team of one. Because the goal isn’t perfection, it’s creating clarity, consistency, and a business that doesn’t rely on you for every single decision. Episode Show Notes: https://duocollective.com/blog/how-to-write-an-sop Tuesday Tips & Sips: https://duocollective.com/subscribe Instagram: https://www.instagram.com/duoonairpodcast/

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/duo-on-air-podcast-4980211/episodes/213-don-t-have-an-sop-start-here/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/duo-on-air-podcast-4980211/213-don-t-have-an-sop-start-here.md` — Read the agent-friendly Markdown representation of this episode resource.

A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed.

## Transcript

Full transcripts are not published on public pages unless there is a clear rights basis.