FULL LIFECYCLE + KONGO

/cultivation + SaaS + Google Ads + Kongo Landing Pages

Looking for the base guide? /cultivation + SaaS + Google Ads covers the lifecycle without Kongo. This guide adds dedicated landing pages, 3-layer A/B testing, and the seed-to-conversion feedback loop.

Without Kongo, you optimize ad copy. With Kongo, you optimize the full funnel: ad copy → landing page → conversion. Every campaign gets its own page. Every page gets AI variants. Winners feed the next cycle. The heist runs itself.

Kelsier

THE COMMAND SEQUENCE

/cultivation install → Vault + Treasury + Revenue + Kongo API key + Daemon

/grow --setup → Google Ads credentials + billing verification

/grow → 6-phase protocol:

Phases 1-3: audit + SEO + content

Phase 3.5: Kongo generates landing pages per campaign

Phase 4: Google Ads campaigns built, pointed at Kongo pages

Phase 5-6: compliance + launch activation

[daemon takes over] → 24/7: A/B test pages, refresh winners, optimize spend

PHASE 0: /CULTIVATION INSTALL

Step	What Happens	You Provide
1	Financial vault (AES-256-GCM) + TOTP 2FA	Vault password + authenticator app
2	Treasury — monthly budget or Mercury/Brex bank connection	Budget amount or API key
3	Revenue tracking — connect Stripe read-only	Stripe restricted API key
3b	Kongo connection — enter API key (ke_live_...)	Kongo account at kongo.io + API key
4	Heartbeat daemon starts + registers Kongo jobs	Vault password to unlock
5	Wizard server + Danger Room dashboard	None

KONGO AT INSTALL

API key validated via GET /engine/pages?limit=1. On success, stored in the encrypted vault. Three daemon jobs registered:

kongo-signal (hourly) — polls growth signal for all published campaigns
kongo-seed (event-driven) — captures winning variant data when A/B tests conclude
kongo-webhook (event-driven) — receives page lifecycle events from Kongo

PHASE 3.5: KONGO PAGE GENERATION

Every Google Ads campaign gets its own dedicated Kongo landing page — not a generic homepage link.

STEP 3.5.1 — SEED EXTRACTION (RAODEN)

Raoden builds a PrdSeedContent from the PRD + Phase 3 content output:

PrdSeedContent {
  projectName: "YourSaaS"
  headline: "Ship faster with AI-powered workflows"
  valueProps: ["50% faster deploys", "Zero-config CI", "Team collaboration"]
  ctaText: "Start free trial"
  ctaUrl: "https://yoursaas.com/signup?ref=kongo"
  brandColors: { primary: "#2563eb", accent: "#3b82f6" }
  socialProof: ["Used by 500+ teams", "4.8★ on G2"]
  campaignId: "gads-nonbrand-search"
}

STEP 3.5.2 — PAGE GENERATION (RAODEN)

For each campaign (typically 3), Raoden calls Kongo. Each page is tailored to its campaign's intent:

Brand Searchyoursaas-brand.kongo.ioBrand story + trust signals

Non-Brand Searchyoursaas-nonbrand.kongo.ioProblem/solution + competitive differentiators

Performance Maxyoursaas-pmax.kongo.ioMultiple value props + social proof

STEP 3.5.3 — VARIANT GENERATION (SHALLAN)

For each page, Shallan generates AI variants: 3 headline × 2 CTA = 6 testable combinations per page.

Cost: ~$0.01 per 5 variants (~3 seconds, Claude Sonnet on Kongo's side)

STEP 3.5.4 — CAMPAIGN LINKING

https://yoursaas-nonbrand.kongo.io
  ?utm_source=voidforge
  &utm_medium=paid
  &utm_campaign=gads-nonbrand-search
  &utm_content={kongo_variant_id}
  &utm_term={keyword}

Rotation: equal split initially → bandit (multi-armed bandit auto-optimization) after 500+ impressions per variant.

Self-marketing note: If marketing your own product (the one hosting Kongo), use yourdomain.com/lp/{slug} instead of subdomain URLs. See “The /lp/ Route” below. For client products, subdomain URLs work as described.

Gate: All 3 pages must reach READY status before Phase 4. Blocks with polling if any page is still generating.

WAYNE'S THREE TEST LAYERS

Tests run in strict sequence — never simultaneously:

Layer 1 — CreativeFirst

Tests: Ad headlines + descriptions. Evaluated: 500+ impressions, 3+ days, 95% confidence

Layer 2 — PageAfter creative winner frozen

Tests: Kongo landing page variants. Evaluated: Growth signal + daemon analytics

Layer 3 — AudienceAfter page winner frozen

Tests: Targeting segments. Evaluated: Proven creative + page combo

Running creative and page tests at the same time confounds the signal. Freeze the ad winner first. Then test the pages. Then test the audience. Each layer builds on the last.

Dockson

GROWTH SIGNAL COMPUTATION

Growth Signal for gads-nonbrand-search:
  Winner: variant-3 (headline: "Ship 2x faster")
  Confidence: 0.97
  CVR delta: +23% over control
  Recommendation: SCALE
  Sample: control=847 views, variant-3=892 views

Confidence	Delta	Views	Action
≥ 0.95	Positive	200+ total	SCALE — winner found, pause losers
≥ 0.80	Positive	200+ total	ITERATE — promising, need more data
≥ 0.95	Negative/zero	500+ per variant	KILL — this approach isn't working
Below thresholds	—	—	WAIT — insufficient data

THE WEEKLY FEEDBACK LOOP

MON

Vin pulls Google Ads metrics + Kongo page analytics. Growth signal computed.

TUE

Kelsier reviews signals. Identifies winning copy patterns from best ad+page combos.

WED

Raoden sends NEW seed content to Kongo (informed by winners). Shallan generates fresh variants.

THU

New Kongo pages go live. Wax updates campaign destination URLs. Old winners become the new control.

FRI

Vin monitors first 24h performance. Circuit breakers active. Underperformers flagged.

PHASE PROGRESSION

Phase A (manual): You trigger /grow --content to refresh.
Phase B (suggested): After 10+ successful page generations, daemon suggests refreshes.
Phase C (autonomous): After 50+ pages with proven lift + /grow --auto-pages, daemon generates and rotates automatically.

THE FULL DATA FLOW

CONTENT PIPELINE PRD ──> Phase 3 ──> PrdSeedContent ──> KONGO API (copy) (seed) │ │ POST /engine/pages │ POST /variants/generate v KONGO PAGES (3 pages x 6 variants) │ ┌───────────────┤ │ │ Subdomain Direct render slug.kongo.io kongo.io/lp/slug (client products) (self-marketing) │ GA4 on same domain │ │ └───────┬───────┘ UTM-linked v GOOGLE ADS ←──(dest URLs)──── CAMPAIGN BUILDER │ │ │ clicks │ campaign CRUD v │ KONGO PAGE ──(convert)──> YOUR APP ──> STRIPE ──> TREASURY │ │ │ analytics │ revenue v v GROWTH SIGNAL ←──(hourly)── DAEMON ──(hourly)── SPEND LOG │ │ │ scale/kill/iterate │ reconciliation v v A/B DECISIONS CIRCUIT BREAKERS │ │ winner declared v KONGO-SEED JOB ──> NEXT CYCLE SEED ──> NEW PAGES ──> ...

WHAT KONGO CHANGES

Aspect	Without Kongo	With Kongo
Landing pages	Homepage for all campaigns	Dedicated page per campaign, tailored to intent
A/B testing	Ad copy only	Ad copy + page variants + audience (3 layers)
Optimization	Optimize clicks and bids	Optimize full funnel: ad → page → conversion
Page refresh	Manual redesign	AI variants in ~3 seconds
Cost per variant	Designer time	~$0.01 per 5 variants
Conversion tracking	Single homepage path	Per-campaign UTM → distinct paths
Feedback loop	Weekly manual review	Hourly growth signal + weekly auto-refresh

SELF-MARKETING: THE /LP/ ROUTE

When you use Kongo to market Kongo itself (or any product hosted on the same domain as Kongo), there's an iframe sandbox constraint.

THE IFRAME SANDBOX

Published sites serve inside sandbox="allow-scripts allow-forms allow-popups" (no allow-same-origin). This means:

GA4 can't set cookies inside the iframe (no session stitching)
window.location.search returns about:srcdoc (UTM params invisible)
CTA links can't navigate the parent window

THE FIX: DIRECT HTML RENDERING

Create a route at /lp/[slug] that serves the Kongo-generated HTML directly (no iframe) inside the marketing layout. GA4, consent, and UTMs all work natively because it's the same domain.

// src/app/(marketing)/lp/[slug]/page.tsx
// Renders generatedHtml via dangerouslySetInnerHTML
// Only admin-owned projects (security boundary)
// GA4 + PostHog + consent from marketing layout

This only applies to self-marketing. When Kongo generates pages for a client product (e.g., yoursaas.kongo.io), GA4 runs on the client's marketing site — the iframe constraint doesn't affect them.

MINIMUM VIABLE WITH KONGO

Kongo account + API keyPage generation and variant testing

Google Ads API + OAuthCampaign management

Financial vault + TOTPAll credential storage

Heartbeat daemonToken refresh + growth signal + seed capture

StripeROAS — pages are only valuable if you know which convert to revenue

Total Kongo cost: ~$0.01 per 5 variants. 3-campaign setup with weekly refreshes: ~$0.12/month in variant generation. Landing pages included in your Kongo plan.

That's the full-funnel heist. PRD seed → Kongo pages → Google Ads → conversions → Stripe → growth signal → next cycle seed → new pages. The loop runs itself. You watch the Danger Room.

Kelsier

← Tutorial Hub Base Guide (no Kongo) →/grow →/cultivation →