We run the first campaign. Your team builds the setup that runs the next one. Half at the start, half on day 90, and the second half only if we get there.
90 DAYS. HALF ON RESULTS.
90 DAYS. HALF ON RESULTS.
The Stack You Will Run
We Run Cycle One
The first campaign is ours. Meetings land while your team is still building.
Half On Results
Half now. The rest only if we hit the number.
The System Stays With You
Your repo, your Supabase, your Clay account, from session one.
Skills In Your Own Words
Your ICP, your scoring and your voice, written as skills Claude reads.
Marcos and David built the Demand Compass, run it this way themselves, and teach every session in person.
Three Campaigns in Ninety Days, and a Repo That Keeps Running
The Demand Compass
CYCLE 1
SESSIONS
Session 1
Set Up The Workstation
While our campaign runs, your team installs Claude Code, forks the Compass Kit and writes its own CLAUDE.md.
Session 2
Give It Memory: Supabase On MCP
Accounts, signals and evidence live in your own Supabase, queried in plain language.
Session 3
Clay stops being columns you drag and becomes something you ask, with a spend cap before anything runs.
CYCLES 2–3
Session 4
Put Your Own Criterion And Your Angles Inside
A skill is a text file where your team writes how it thinks. Two of them: who is worth a rep’s hour, calibrated against deals you won and lost, and which angle each segment gets, so the model picks the argument instead of inventing one.
Session 5
Make It Send, And Make It Land
MCP out to the sequencer, LinkedIn and the CRM, and the deliverability that decides whether any of it arrives: domains, warm-up, SPF, DKIM, DMARC, and the bounce rate at which you stop sending. Your team sends the second campaign itself.
Session 6
Make It Run Without Us
Six long requests become one command, and a second person who can run it. If you produce inbound, it goes through the same scoring and routing, so a demo request and a cold account are ranked by one criterion instead of two.
Automate list building
How to connect Apify Google Job Post Scraper with Clay
Automate Copywriting
Why You Don’t Need a Copywriter for Cold Emails Anymore
Clay Fundamentals
Clay Fundamentals for Sales Professionals: Workflow Building Basics
The RevOps Community We Run Every Week
Revenue teams comparing what moved pipeline and what did not.
Here is how it starts:
90 DAYS. HALF ON RESULTS.
We run the first campaign, so the result is ours to produce. The number is two deals at your average size, counted in your CRM.
A proven offer, a market above 50,000 contacts, an average deal above $100,000, and one repo owner. We check all four before quoting.
One repo in your own GitHub, wired to your Supabase and to Clay, running the whole cycle from a chat window.
No. Everything is plain English in files your team can read and change.
Quoted for your team after a first call. Half to start and half on day 90, the second payment only if we reach the number in the agreement.
