How to set up "goal-driven runs" in Claude Code...

The previous week, I shared 5 Claude Code workflows: clean the CRM, score leads, enrich data, generate sequences, and package reports.

If you ran one a day, you've got the whole pipeline sitting in your project folder.

Here's the upgrade nobody's talking about yet.

Right now you're running those 5 as 5 separate sessions. You open Claude, run Workflow 1, check it, run Workflow 2, check it, and so on. That works. But it means you're the one chaining the steps together.

The shift happening at the frontier is from running commands to setting a goal and letting the agent run the entire trajectory itself. Plan the sub-tasks. Chain them. Pause only where it actually needs you.

You can wire your 5 workflows into one autonomous run this week. Here's exactly how.

Step 1: Create the orchestration file

In your project folder, make a new file: pipeline-goal.md. This is the master instruction the agent reads to understand the full outcome, not just one step.

cd ~/claude-gtm
claude --plan

Read pipeline-goal.md and execute the full pipeline.

Step 2: Write the goal, not the steps

Inside pipeline-goal.md, you describe the outcome and the guardrails. The agent figures out the trajectory.

GOAL: Take contacts.csv from raw export to a
finished pipeline-report.xlsx ready for campaign launch.

Read these context files first and treat them as
the source of truth for every decision:
- icp-context.md
- messaging-logic.md
- data-sources.md

Execute in this order. Do not skip a stage if the
prior stage failed validation.

Stage 1 — Clean: Deduplicate contacts.csv by email,
standardize titles, flag personal-domain emails,
remove anything that fails ICP criteria. Save
contacts-cleaned.csv with a removal log.

Stage 2 — Enrich + score: Enrich via Apollo direct
API (not MCP — token efficiency on bulk). Score
against icp-context.md into Tier 1/2/3. Filter out
already-emailed contacts via Gmail MCP and existing
customers via Stripe MCP. Save scored-leads.csv.

Stage 3 — Sequence: For Tier 1, generate 3-email
sequences using messaging-logic.md. Tier 2 gets a
2-email templated sequence. Drop Tier 3. Format
for Instantly. Save sequences-ready.csv.

VALIDATION GATES — pause and show me before continuing:
- After Stage 1: show removal count and a sample of
  what was removed and why
- After Stage 2: show tier distribution and 5 sample
  scoring rationales
- Before final save: show the full plan diff

Do not write sequences if Stage 2 tiering looks wrong.
Flag it and stop.

Step 3: Let it run the trajectory

Because you opened with --plan, the agent shows you its architecture before touching anything. You approve the plan once, then it executes Stage 1 → 2 → 3, pausing only at the gates you defined. (Already in a session? Shift+Tab twice cycles you into plan mode without restarting.)

You went from 5 manual sessions to one supervised run.

Why this is the real upgrade

The danger with autonomous runs is the agent drifting off course over a long task. The fix is the same thing that made last week's workflows work: the context files and the validation gates. The .md files keep it aligned to your actual GTM logic. The gates keep you in control at the moments that matter.

Autonomy without those is a liability. Autonomy with them is leverage.

This is also why you build the foundation first. You couldn't have done this in week one, there was nothing to orchestrate. Now that the pieces exist and are tested, wiring them into a single goal-driven run is the natural next move.

Your move this week

Don't build new workflows. Take the 5 you already have and write your pipeline-goal.md. Run it once with the gates on. Watch where it pauses, tighten those checkpoints, and run it again.

Give it a try this week and see how it handles the full run. Worst case, you learn exactly where your context files need sharpening.

The revenue is in the engineering.

Stay safe out there.

Much Love,

Benjamin Reed

Revyops & NextGen Founder

P.S. Check out ReyvOps at Revyops.com.

P.P.S. Want to help me on my journey to build RevyOps into a $1 Million SaaS? Please share this newsletter with your network so they can follow along. Anyone can sign up 100% free using this link: Click here

The Builder's Playbook is a series by Benjamin Aaron Reed on the tools, systems, and workflows that give founders and GTM operators an unfair advantage. New issues drop regularly.