Tutorial 10 · Beginner

Build a Lead Follow-Up System — Draft Only

Turn reviewed real business records or a complete fictional fallback into a manually approved draft queue and evidence-grounded message drafts without contacting anyone or changing an external system.

45–60 minutesNo coding8 guided stepsIncluded in Founder-Operator Program and Premium Pack

You will build

A reviewed lead tracker, a manually approved draft queue, evidence-grounded message drafts, visible holds, and a complete run receipt with external actions set to none

You will strengthen

Judging legitimate contact context, prioritizing from evidence, reviewing personalized drafts for consent and privacy, and separating internal approval from external action

Learning map

Tools and capabilities

Tools

CodexFounder Operating WorkspaceCSV or local file editor

Capabilities

Lead follow-upConsent reviewEvidence-grounded personalizationPrivacy reviewDraft reviewFounder-controlled approvalWorkflow reproducibility

Before you begin

What you need

  • Codex in the ChatGPT desktop app or another Codex surface
  • The extracted Founder Operating Workspace
  • Reviewed real business records in a CSV or local working file, or the complete ten-record fictional Sample Venture fallback

Practice assets

Download what you need

Step-one preview

Define the follow-up boundary

Objective

Set a draft-only completion state, one input route, and explicit prohibitions before reviewing any lead.

Try it now · In the Founder Operating Workspace and a Codex conversation

  1. Open AGENTS.md, ROUTING.md, workflows/lead-follow-up/METHOD.md, and workflows/lead-follow-up/CHECKLIST.md in the extracted Founder Operating Workspace.
  2. Write one bounded question that asks which reviewed leads merit a draft follow-up and what evidence supports each draft.
  3. Choose reviewed real business records by default only when their legitimate source, relationship, permitted channel, and consent basis are already recorded.
  4. Otherwise choose The Sample Venture CSV as the complete fictional fallback and keep all fictional labels and consent states visibly fictional.
  5. Record that completion is a reviewed draft queue and message drafts only: do not send or contact anyone, do not change or mutate a CRM, do not schedule messages or meetings, do not scrape or enrich data, do not purchase anything or recruit anyone, and do not fabricate people, familiarity, urgency, promises, or results.

Visible result

You can see one bounded draft-only question, one complete real or fictional input route, and explicit proof that sending, contacting, CRM mutation, scheduling, scraping, enrichment, purchasing, recruiting, and fabrication are not authorized or performed.

Completion check

I chose one complete route and confirmed that this tutorial produces reviewed drafts without contacting anyone or changing any external system.

If you get stuck

Stop the workflow, remove every external action, return to one reviewed input route, and restate the completion state as drafts awaiting manual approval.

I’m stuck on this step