Podcast clipping & AI automation
No surprises. Here's exactly how it goes.
Every project follows the same four steps. You always know what's happening, what's next, and what you're paying for.
01 / Process
The four steps
-
You send the brief
A link to your episode, or a one-paragraph description of the task. If it's a podcast, I need the source file or a YouTube/Vimeo link. If it's automation, I need to know the repetitive task and where it currently lives.
Deliverable: You get a written scope confirmation within 24 hours.
-
I quote and you approve
Fixed price, fixed timeline. No hourly. No scope creep. If the project needs to change, we re-quote before any work continues.
Deliverable: A one-page scope doc: what's included, what's not, delivery date.
-
Build or edit
Podcast clips: I deliver a first batch within 48–72 hours. Automation: weekly demos so you see progress, not promises.
Deliverable: Progress, not silence. You always know the state.
-
Handoff
Clips: final files in the formats you ordered, ready to post. Automation: full source, README, deploy instructions. You own it.
Deliverable: Everything you need to run it without me.
02 / Your brief
What I need from you
For podcast work
- Source file or link
- Any brand assets
- Preferred caption style
- Deadline
For automation work
- The task description
- Any existing scripts or workflows
- Access method: local machine, VPS, or sandbox
- Success criteria
03 / Boundaries
What I don't do
- I don't take on projects where the scope isn't clear. I'll ask questions first.
- I don't ship automation that touches credentials or payment systems without a written security review.
- I don't guarantee virality. I guarantee craft and delivery.
04 / Communication
Response times
| First reply | Within 12 hours (usually much faster) |
|---|---|
| Scope confirmation | 24 hours |
| First draft / batch | Per the package you ordered |
| Revision turnaround | 24–48 hours |
05 / Get in touch