Daniel × John — Two-Week Growth Sprint

Window: Fri Jul 10 → Fri Jul 24, 2026

Purpose: Prove that Daniel (product/dev/design) + John Heavey (marketing/ads/lead gen) can scale a demo-led agency directly on top of The Cloud — then decide the shape of the partnership, up to and including cofounding.

The split

• Daniel — Product & Infrastructure. Make The Cloud's contacts + campaign system beautiful end-to-end for humans and fully drivable by AI over MCP. Build the demo factory. Remove every bottleneck John hits.

• John — Targeting & Distribution. Own ICPs, pitch angles, copy, send approval, reply triage, and booked calls. He is the daily operator of the machine Daniel is building.

• Ora / The Cloud — the engine. Lead scouting, enrichment, per-lead demo generation, campaign packaging, sending, and CRM sync run as agent loops.

What already exists (day-0 inventory)

• Campaign Execution Studio Phase 1 shipped: contact folders → campaign packages → prep / finalize / simulate / gated-send, with per-lead links.

• CAN-SPAM compliance configured (Teka, Springville UT; sender: Daniel Hanks, Teka) — sends are unblocked.

• Three connected inboxes: daniel@teka.ai (primary), team@teka.ai, aetherlands@gmail.com.

• Live lead pools: Hiring-tech FDE wedge (Iterative Health active, P-1 AI 25 contacts, hiring-tech bracket), Marketplace outreach (Contra/Fiverr/Upwork, folder scaffolded), ~11.5k csv-imported marketplace buyers, plus scoutLeads for net-new SMB pulls (60/run, deduped, consent-stamped).

• Eight draft campaigns already scaffolded by persona.

Week 1 (Jul 10–16) — Wire the machine, first real volume

Daniel — product track

• Contacts app for campaigns, end-to-end. Bulk operations first: bulk add-to-folder, bulk tag, bulk stage-move, and MCP tools for each (the 11.5k Sunday Post import already proved per-contact MCP can't bulk-file — this is the known gap). Then: suppression/do-not-contact surfacing, dedupe/merge, folder rules, and a campaign-ready view (who's contactable, who's pending, who replied).

• MCP surface parity. Every action a human can take on a contact/folder/campaign should be one clean MCP call, batched where it counts — this is what lets agent loops run outreach at volume.

• Demo factory v1. A repeatable pipeline: lead card → branded per-market demo (Studio app or page) → per-lead link injected into the campaign package. Pure Pastry / P-1 Archie console are the proven templates.

• Send-rail throughput. Instrument the send path for volume: batch queueing across all three inboxes, per-inbox daily caps, bounce/reply detection feeding contact stage automatically.

John — growth track

• Day 1–2: pick 3 SMB niches + own the two existing wedges (hiring-tech, marketplace). Define ICP, pain, and pitch angle per pool; write the master pitch + 2 variants each.

• Day 2–3: onboard to The Cloud — contacts, folders, campaign packages, approve/send flow. (His friction list = Daniel's bug list. This is the dogfood loop.)

• Day 3–7: launch first campaigns across all three pools — scoutLeads loops filling SMB folders daily, marketplace folder populated, FDE-wedge bracket extended. Approve and push batches daily.

Volume ramp (push-volume posture)

• Days 1–3: ~50–100/day across the 3 existing inboxes while warming.

• Immediately procure 3–5 secondary sending domains + inboxes (e.g. tekahq.com, gettteka.com variants) — this is the hard prerequisite for hundreds/day without burning teka.ai's reputation. Daniel wires them in as they warm.

• Days 4–7: 150–300/day as new inboxes come online.

• > [!⚠️] Deliverability is the one non-negotiable even in push-mode: keep per-inbox cold volume ≤ ~100/day, keep teka.ai for replies and warm threads, monitor bounce rate daily (pause any inbox over ~3%).

Week 2 (Jul 17–24) — Scale + decide

• Scale sends toward 500–1,000+/day as domain pool warms; scoutLeads loops running on schedule per niche.

• Double down on whichever pool shows reply-rate signal; kill or park the weakest by Jul 20.

• Demo factory v2: auto-generate the per-lead demo inside the campaign prep step, no manual assembly.

• John shifts time from sending to replies and calls — the funnel's bottom is his home turf.

• Retro Fri Jul 24: partnership decision.

Day-14 decision criteria

• Volume: did the machine sustainably clear 300+/day with a path to 1,000+?

• Signal: reply rate ≥ 2–3% on at least one pool; ≥ 5 qualified conversations; ≥ 1 deal in motion.

• Fit: did the Daniel-builds / John-distributes split hold under load, and did both sides want more of it?

• Outcome options: formalize cofounder terms on the agency-on-Cloud entity · rev-share partnership · project-based collaboration · part ways clean.

Metrics (tracked daily)

• Leads scouted / enriched / contactable per pool

• Pitches sent · delivered · bounced (per inbox)

• Demos generated · demo link opens

• Replies · positive replies · calls booked · deals in motion

• Daniel: MCP/product gaps John hit vs. gaps shipped

Operating rhythm

• Daily async standup (Telegram thread): yesterday's numbers, today's batches, blockers.

• Daniel ships product fixes same-day when they block sends.

• All state lives in The Cloud — contacts, folders, campaigns, this page. If it's not in the Cloud, it didn't happen.