BD · Lynoia (Funding Predicts + HyroTrader)

Network revenue

—

HyroTrader (sub-affiliates) · live

BD margin

—

of revenue · live

Active affiliates

—

Status = active · Notion

BD expenses (paid)

—

To KOLs · KOL Expenses

In negotiation

—

Active deal pipeline

Pipeline, expense and affiliate data (Notion × Hyro) live in the HyroTrader workspace. Pick HyroTrader above to see them. Funding Predicts will fill its own data when its pipeline starts.

Pipeline funnel — affiliates by status (Notion)

Bottleneck = the most congested status. Active = live relationship; reactivate inactive ones.

BD expenses by type — paid to KOLs (KOL Expenses)

Total split by payment type.

Affiliates — Notion × Hyro (by username)

with Hyro match · total

Affiliate	Code	Via	Status	Hyro revenue	Your commission	Conv.	Notion rev.

Joins what Notion says (Affiliates Pipeline) with what Hyro measures by username (the robust key). username = linked by the fixed key; coupon = transient match while Bast confirms the username. Still need to link the ones without a match.

BD commission : CAC by affiliate

≥4x1–4x<1x

LTV = your BD commission (what you earn from that affiliate). CAC = what you paid them (upfront, bonuses, retainer). Bubble = revenue they move.

Affiliate	Revenue	BD commission	CAC	BD net	LTV:CAC	Conv.

LTV:CAC = ∞ = affiliate with no acquisition cost (you paid no upfront) → commission is 100% margin.

Pareto ranking — the 20% that drives 80% of your commission

Green = affiliates that make up the first 80% of your BD commission. Concentrate upfronts and retainers there. Gray = tail.

No per-affiliate revenue yet.Funding Predicts has no affiliates yet.
Per-affiliate economics (BD commission : CAC) live in HyroTrader today — switch above to see them. Fills in when the Hyro mirror syncs revenue per sub-affiliate.

Per-customer economics · cohorts and pass-rate

Activates with per-trader sales

Net LTV per customer, pass-rate and cohort curves activate on their own when the per-trader sales data arrives (who bought through each code, pass/fail, payouts). It's finer than the LTV:CAC above: there you see the gross commission; here the net after payouts and by cohort.

Cohort curves — cumulative Net LTV

Lines that go negative = cohort with destructive payout exposure.

Pass-rate and Payout Exposure by affiliate

High pass-rate + high payout = candidate to lower commission or drop the retainer.

The cockpit only creates the deal request. The offer + the deal page are generated by the FP Assistant (or deal_bridge.py --process) server-side, respecting the commission ceiling.

KOL	Business	Phase	Commission	Upfront	Funded	Deal page	Pitch

These tables only record and track payout requests. The system moves no money and sends nothing — you approve and pay by hand. The KOL only REQUESTS via their link.

KOL self-service portal · permanent link

One permanent link per KOL (no account, opens only THEIR row). The KOL bookmarks it and comes back to request whenever — you don't have to generate or resend anything per request. They see their pending amount + the dual gate (post + sales) and request; you approve below. If you enter the same handle, their link is reused (not duplicated). Active business: —.

KOL	Requirements	Expires	Status	Link

Payout requests

Affiliate	Business	Amount	Period	Status	Requested by	Date

The KOL uploads proof of their post (link) from their page. Here you verify each one: only the verified ones this month count toward the payout's post gate. Nothing is approved on its own.

Add KOL post · already verified

To register a post you've already seen yourself (counts immediately). Active business: —.

KOL posts

KOL	Platform	Post	Date	Status	Action