06-reference

ship30for30 ai automations writing business

2026-08-01·reference·source: Ship30for30·by Mitch Harris
ai-workflowsautomationclient-managementhuman-in-the-loopsolopreneur-ops

Ship30for30: three client-ops automations built on an approve-before-send gate

Why this is in the vault

Three concrete, prompt-level automations for solo/small writing businesses — lead follow-up, meeting confirmation, loose-ends-to-tasks — each explicitly built with a "draft only, don't send/act until I approve" clause baked into the prompt itself.

The core argument

Mitch Harris frames the administrative surface of a one-person writing/consulting business (following up with leads, confirming meetings, tracking loose ends across email/notes/calls) as individually trivial but collectively expensive — minutes per task, multiplied across a week of prospects and clients, adds up to lost hours. He gives three specific automations, each as a literal prompt template rather than an abstract description:

  1. Lead follow-up. After a sales call, an AI reviews the transcript/notes, extracts the prospect's problem, objections, and agreed next step, and drafts a personalized follow-up email — with the prompt explicitly instructing "Do not send the email. Give me the draft to approve first." A second workflow checks for a reply and drafts a second follow-up 3-5 days later if none arrives.
  2. Meeting confirmation. An AI reviews tomorrow's calendar and drafts a confirmation email per meeting (time, link, purpose, prep needed, outstanding action items from the last conversation), personalized from prior email threads and notes — again gated: "Do not send anything until I approve it."
  3. Loose-ends-to-tasks. An AI scans recent client emails, meeting notes, and project records for unfinished commitments, unanswered questions, missing documents, and overdue follow-ups, and turns each into a task with owner, due date, source, and consequence-if-dropped — gated with "Show me the task list before adding or changing anything in my project-management system."

Harris's synthesis: non-technical operators don't need to code, just define three things per automation — the triggering event, the information the AI needs, and the finished draft/action it should produce. The email opens and closes with a pitch for Ship30for30's live "ChatGPT Work For Writing Businesses" bootcamp (waitlist CTA before and after the content, plus a Zoom-cohort pitch in the PS) — the three automations are the free preview of what the bootcamp teaches live.

Mapping against Ray Data Co

Most concrete connection: this is RDCO's own architecture, described independently and simplified for a solo operator. The approve-before-send clause on automation #1 is exactly the constraint already logged in feedback_no_autonomous_external_email.md (Ray drafts, founder sends — send-button is human-gated), and automation #3's "show me the list before touching the PM system" mirrors the Notion-board discipline in feedback_queue_work_to_the_board.md and the outcome-named-ticket convention. Seeing a course brand arrive at the identical human-gate pattern from scratch, aimed at solopreneurs with zero agent infrastructure, is a weak-signal confirmation that the gate is the right default rather than an overcautious one — it isn't a phData-scale-only concern, it shows up the moment anyone lets AI touch outbound client communication at all.

Gap exposed: automation #2 (meeting confirmation drafted from calendar + prior thread + open action items) doesn't have a direct RDCO equivalent yet. /morning-prep is calendar-aware but oriented at the founder's own day, not at drafting outbound confirmations to external meeting attendees. If Ray ever runs founder-facing client meetings (phData, CAF, or an RDCO client engagement), this is a ready-made template for the confirmation draft — subject to the same human-send gate.

⚠️ Sponsorship

Self-promotional bookends: the email opens with an "ICYMI" waitlist push for Ship30for30's paid live bootcamp ("ChatGPT Work For Writing Businesses") and closes with a longer PS repeating the pitch (topics list, live Zoom cohort, waitlist link again). The three automations in between are genuinely specific and usable independent of the pitch — they aren't watered down to force the upsell — but the whole piece functions as a lead magnet for the bootcamp, so treat the framing ("you need this system, join to build it live") as marketing, not as evidence the techniques require paid instruction.

Related