Claude Code Cohort Project

Why do you need
what I build?

Because a great offer dies in an empty pipeline. I turn a fuzzy go to market idea into a running outbound system that puts your offer in front of the right buyers, every single day. This is the full engine I architected for my Claude Code cohort project.

3k to 5k
contacts per campaign
2
campaign engines
8
stage pipeline
21 day
warmup gate
The Build

A full go to market engine, from strategy to send.

For my cohort project I architected the complete outbound system for a client whose offer is a free QA audit on a prospect staging environment. Surface the critical bugs, hook the buyer, then upsell the paid backend. The ICP is B2B healthcare SaaS in the USA, reached across founders, engineering leaders and QA owners.

Strategy First

Nothing gets built until the thinking is settled.

The strategy doc is the brain. AI Ark, Clay, Claude Code, ScaledMail and PlusVibe are only the hands. Eight stages carry an idea all the way to a tracked, reviewed campaign.

01

Strategy

Outcome, ICP, offer and success signal, all decided before a single tool is opened.

02

List build

AI Ark builds the in ICP list and enriches it. Keys live in a git ignored env file.

03

Segment

Split by employee size and subvertical, then map a pain point to every slice.

04

Volume track

Founder led copy with spintax, pushed fast and wide across every segment.

05

Signal track

Intent triggers feed a rolling list, personalized one to one with Clay and Claygent.

06

Infrastructure

Domains and inboxes on ScaledMail, warmed a full 21 days before any send.

07

Approval gate

A human check plus a warm inbox check. No campaign goes live unreviewed.

08

Send and track

PlusVibe sends, every run lands in logs, weekly review loops back to strategy.

The Workflow

See the whole flow, end to end.

The full system as one interactive map. Pan and zoom through the strategy layer, both campaign tracks, the warmup lane and the send pipeline. Click open to explore it full screen.

workflow.diagram open full screen ↗
Two Campaign Engine

Volume for coverage. Signal for timing.

Both run at once. One blankets the market fast, the other catches the accounts raising their hand right now.

Volume based

Reach everyone in ICP, fast.

Three to five thousand contacts per campaign, sliced so every message has a reason to exist.

  • Employee size tiers of 1 to 10, 11 to 50 and 51 to 100
  • Subvertical slices, each with its own pain point
  • Founder led copy, three to four variations, spintax on everything
  • The reply test on every line before it ships
Signal based

Catch intent the moment it shows.

A rolling watch list built from the triggers that mean a company is ready to move.

  • Hiring for QA, fresh funding, a new product release
  • A new engineering leader stepping into the seat
  • Clay and Claygent enrich the site and pull the angle
  • One to one copy tied to the exact trigger
The Execution Layer
AI Ark · Clay · Claygent · Claude Code · ScaledMail · PlusVibe · AI Ark · Clay · Claygent · Claude Code · ScaledMail · PlusVibe ·
Built To Last

Systems, not one off blasts.

Human approval

Every send passes a review before it reaches a real inbox.

21 day warmup

No mailbox sends cold traffic until it warms and earns a healthy score.

Everything logged

Reply rate, positive rate and meetings booked, tracked run by run.

Secrets are safe

API keys live in an env file that never touches version control.

Shipped In This Repo

The thinking, made visible.

Strategy doc

The full brain of the system, written before any tool was opened.

Workflow diagram

An interactive map of the flow from strategy all the way to send.

Excalidraw canvas

The same flow as a hand drawn board you can drop straight into a review.

Repo scaffold

Env template, ignore rules, logs and data folders, ready to run.