Head to head · two lead-gen plans, stress-tested

Your machine plan vs the other agent's, side by side

Short version: these two plans are more complementary than competing. They agree on the hard calls. Mine is stronger on strategy, sequencing, and doctrine accuracy. Theirs is stronger on build detail and the voice system. The best plan is a merge, and there is one real factual error in theirs you should know about.

Read this first: one number in the other plan is wrong. It uses a referral commission of $15 per shipment now, $30 after the threshold. Per your own confirmed decision (gtm-funnel-plan DECISION 7B, 2026-07-07) the live term is a tiered $20 / $50 / $100 by quote value, for life, which explicitly supersedes the old flat $15/$30 proposal. This matters because the higher fee is what makes referred shipments barely profitable before the 50-ton threshold, which the other plan misses entirely (it calls the fee a harmless "haircut, still nets $35-55").

Honest note: a stale line in RelayFBA's own hot.md still shows $15/$30 too, so this is partly our internal drift, not just their error. I did not silently change it (it is a pricing term, your call). Please confirm $20/$50/$100 is live so we fix the stale record everywhere.

1. At a glance

Dimension	MINE (recap)	THEIRS (Switch Catcher)
Primary engine	Founder-led proof layer (warm network + Hongheng intros + FB signal-mining) leads; referral outreach is the #1 automatable pillar, phase-2.	Community intent-monitoring (Reddit + forums + FB) as the primary machine; referral engine second.
Method	13 channels scored on 4 gates, 30-agent adversarial gate + red-team + a 5-persona roast, saved evidence.	Every channel hunted, one strong reasoned pass, a scored matrix, a self-run red team.
Killed	Seller cold email (no sourceable list), paid social, SaaS directories, WhatsApp cold.	WhatsApp cold, paid ads, YouTube/TikTok; cold email deferred (not killed).
Build detail	Loops + CRM tables + gates, less granular. No example copy.	Full CRM schema, named loops, tools, MVP-vs-full timeline, 2 example messages.
Voice system	A founder-voice profile the agents load. Mechanism light.	Corpus + few-shot exemplars + an automated voice-QA pass that flags AI tells. Strong.
Referral fee used	$20 / $50 / $100 for life (correct, canonical).	$15 / $30 for life (superseded, incorrect).
Content work	Routed to the Content brain as a scoped mission (per OS doctrine).	Built as a workstream inside RelayFBA.

2. Where they agree (both got the hard calls right)

Kill cold WhatsApp on compliance; reuse it as the reply-first nurture and closing layer. Identical, and correct per our WhatsApp constraint.
Kill paid ads pre-proof: CAC dwarfs a first shipment that is already negative after the $100 credit.
Automate discovery and drafting, never the voice or the send. A human sends every first message. This is the shared spine and it matches our Trust Doctrine exactly.
Founder takes every call and the deep WhatsApp chat. Pricing only from the quote engine, never invented.
Referral partnerships + SEO/quote-widget flywheel as core engines, and the freight-insider identity (never the "Amazon seller" badge), no em dashes, no pre-launch or locked-rate language.

Takeaway: the disagreement is not about what is compliant or what converts. It is about what LEADS, how much build detail to specify, and one wrong number.

3. Where MINE is stronger

1. It uses the warm core and the Hongheng partner

The single fastest path to the first proof for a pre-launch founder is the warm network (you have ~1,604 mapped contacts and 9 hot logistics signals) and warm intros from Hongheng, who already ships for real sellers. The other plan omits both entirely and waits for a switcher to post publicly. That is slower and lower-yield for customer number one.

2. Doctrine-correct referral fee + the margin-tax insight

Mine uses $20/$50/$100 and my roast flagged that a flat lifetime fee runs referred shipments breakeven-to-negative until the 50-ton threshold, and recommended switching to a percentage of margin (your call). Theirs uses the wrong $15/$30 and calls the fee harmless, so its referral economics read rosier than reality.

3. Referral list re-qualification (partner vs competitor)

My red team found the most freight-adjacent "partners" (prep centers, sourcing agents) are often competitors who forward freight themselves, and PPC agencies have no referral moment. The AI's real job is to segment partner from competitor. Theirs lists all three as partners without that filter.

4. Content routed to the Content brain

Per the OS doctrine, content production belongs to the Content brain (which already owns a built content-machine plan). Mine routes it there as a scoped mission. Theirs rebuilds a content workstream inside RelayFBA, duplicating what already exists and crossing a brain boundary.

5. Adversarial validation, not one pass

Mine ran a 30-agent gate (per-channel skeptic + red-team) plus a 5-persona roast, with every reach and competitor claim cited and saved, and it survived two independent review rounds. Theirs is a strong single reasoned pass but was not independently attacked.

6. Explicit proof-before-scale sequencing

Mine names a cold-fire gate: the referral machine list-builds now and only sends after 5 to 10 real shipments exist. It is clear about what is founder-heavy (proof) vs hands-off (inbound).

4. Where THEIRS is stronger

1. It is closer to a build ticket

Theirs specifies a full CRM schema (leads, touches, partners, referrals, compliance_log, content_assets, metrics_daily), named loops (ingestion, scoring, draft, approval, nurture, reporting), specific tools (Syften, Redreach, F5Bot), and per-loop failure/retry plus per-community circuit-breakers. Mine has the loops and gates but less of this operational depth.

2. A genuinely better voice system

Theirs is the stronger anti-AI design: a founder voice corpus, few-shot exemplars instead of rigid templates, and an automated voice-QA pass that blocks banned words, em dashes, invented prices, and AI tells before a draft reaches you. It even includes two concrete example messages. Mine names a voice profile but with less mechanism and no sample copy.

3. MVP-first staging

Theirs proposes a Reddit-only MVP in one to two weeks to prove reply rate before building the full machine (four to six weeks). That is smart de-risking. Mine gave rough effort but did not stage a prove-it-first MVP as crisply.

4. The intent triggers are spelled out

Theirs lists the exact switcher phrases to listen for (recommend a forwarder, forwarder ghosted me, customs/IOR/EORI hold, surprise fees, stuck for weeks, looking to switch, bad experience with a named competitor). Mine referenced buy-signals without enumerating them as usefully.

5. Fresher reach numbers

Theirs cites current 2026 community sizes (r/FulfillmentByAmazon ~141K, +22K a year). Mine leaned on our older watering-holes doc (~50K to 120K). Both flag figures as approximate, but theirs is more current.

6. It resolves the "what leads" question more cleanly

Fair point against me: theirs ranks the proof-manufacturing community channel #1 and referral #2, which actually matches my own roast conclusion (proof first, referral is phase-2) better than my recap's headline ranking did, where I ranked referral #1 and had to caveat it heavily. Their ordering is more internally consistent, even though mine adds the faster warm/Hongheng path they lack.

5. Stress test: does either have a fatal flaw?

No. Both are viable and neither collapses under attack. The surviving weaknesses, left visible:

Plan	Weakness that survives scrutiny	Severity / fix
Theirs	Wrong referral fee ($15/$30) makes referral economics look better than they are and hides the margin-tax problem.	Real. Fix the number, add the margin-tax flag.
Theirs	Omits the warm network and Hongheng intros, the fastest pre-launch proof path.	Real gap. Add them as engine A.
Theirs	Bets the primary on intent-post volume it admits may be under 10 a week, and the switch is the next shipment weeks out, in a thread swarmed by rival reps.	Volume-capped, not fatal. Pair with warm + referral.
Theirs	Content workstream partly re-owns the Content brain's mandate.	Doctrine slip. Route content out.
Mine	Recap ranked referral #1 then caveated it to phase-2, a framing tension (the reviewer flagged it too).	Framing. Their ordering is cleaner here.
Mine	Under-specified the build detail and the voice system vs theirs.	Real gap. Graft their spec in.
Mine	Our own hot.md carries the same stale $15/$30 line.	Internal drift. Reconcile on your confirm.

6. The verdict: merge them

Use my strategic frame and sequencing as the skeleton, and graft their build spec, voice system, and MVP-first staging as the implementation layer. Concretely, the best single plan is:

Skeleton (mine): lead with the founder-led proof layer, and add warm network + Hongheng intros as engine A1 alongside community signal-mining. Referral outreach is the #1 automatable pillar but phase-2, cold-fires after 5 to 10 real shipments, and its list is segmented partner-vs-competitor first. Content is routed to the Content brain.
Correct the money (mine): referral fee is $20/$50/$100 for life (pending your confirm), carried with the margin-tax flag and the recommendation to consider a percentage of margin.
Implementation (theirs): adopt their CRM schema, the named loops with circuit-breakers, the MVP-first staging (Reddit-only in one to two weeks to prove reply rate), the explicit intent-trigger list, and above all their voice system (corpus + few-shot + automated voice-QA pass).
Their intent-catcher is the concrete build for my under-specified signal-mine loop. They are the same machine; theirs is better drawn. Use it.

7. What I would do next

You confirm the referral fee ($20/$50/$100 for life vs $15/$30). This unblocks the referral economics in both plans and fixes the stale record.
Approve the merged plan, then the first build is their Reddit-only MVP (one to two weeks) to prove reply rate, running in parallel with engine A1 (you working the warm core + a Hongheng intro ask) to manufacture the first proof by hand.
The Content brain gets a scoped mission for the voice corpus, the value-snippet library, and the SEO articles, so RelayFBA does not rebuild content it already owns.
If useful, I can produce the single merged build plan as the next deliverable, or spec the Reddit MVP so you see it working on live threads before the rest is built.

Grounded in RelayFBA doctrine used this session: business-model, gtm-funnel-plan (incl. DECISION 7B referral terms), acquisition-channels, icp-and-psychology, brand-identity-and-voice, rates-and-services (margins, fees, FX 8%, quote validity), content-machine (content ownership + the existing plan). cpsc-efiling-compliance is product-eFiling doctrine and not relevant to this channel comparison. Both plans stopped at a plan; nothing was built or sent. The two source plans compared: my recap.html + validation-data.json, and the other agent's Switch Catcher recap + its ranked channel matrix CSV.