BD · Lynoia (Funding Predicts + HyroTrader)

Network sales (Hyro)Total Bast's whole network has sold for Hyro. Headline = the panel lifetime (the complete figure). 'Captured by tx' = what the scraper has logged as dated transactions (~79%); the Income tab uses that captured number, which is why the two can differ.

—

Panel lifetime · live · Panel updated

Captured by tx:

Hyro spend (to KOLs)What Hyro has paid the KOLs (Notion KOL Expenses: upfronts, payouts, SEO, monthly…). This is your CAC — Hyro's cost to run the network.

—

To KOLs · KOL Expenses

Hyro netHyro's net P&L on Bast's network = network sales − what Hyro pays the KOLs (expenses) − the BD override Bast earns. Panel/lifetime lens. The override is a separate stream (96% of expenses are tied to a specific KOL), so subtracting it does not double-count.

—

Sales − KOL spend − BD override · panel

BD commission (Bast)The commission the BD (Bast) earns on that revenue — NOT what the KOLs earn. This is the pot BEFORE your 50/50 split with Bast (see the Settlement tab). Headline = panel lifetime; 'Captured by tx' = the dated figure the Income tab uses.

—

of revenue · live

Captured by tx:

Active affiliatesAffiliates marked 'Active' in Notion (manual status). Unrelated to recent sales.

—

Status = active · Notion

In negotiationAffiliates currently in 'negotiation' status in the Notion pipeline.

—

Active deal pipeline

Two figures per KPI. The big number = Hyro panel (lifetime cumulative — the official total). “Captured by tx” = what the live scraper has logged transaction-by-transaction (auditable; the Income tab uses this one). They differ because the scraper only captures forward and hasn't rebuilt the full history yet — they converge over time.

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.

Revenue vs all costsHow the network's sales split into every cost and what's left. Left: waterfall (Sales − KOL spend − BD override = Hyro net). Right: the same sales sliced into each cost type plus the leftover net. Panel/lifetime figures.

Sales minus every accumulated cost — not just CAC.

What happened this week

Sales in the last 7 days vs the 7 days before, per affiliate.

🟢 Picking up

✨ Back selling

🔴 Slowing / stopped

Churn — who to reactivate

active cooling (30–60d) dead (>60d)

Reactivate first (most valuable cooling):

Momentum — who added the most revenue New revenue each affiliate added across the window: the latest panel value minus the value ~30 days ago. Measured endpoint-to-endpoint, so a one-off panel recalculation in between doesn't distort it. Ranked by dollars added; growth % is shown as a secondary cue.

Revenue added per affiliate since · d (history isn't 30 days yet)

Multi-level — direct vs level-2 Your sub-affiliates split by level. Tier 1 = signed up with your direct coupon (you keep ~30% of their sub-commission as override). Tier 2 = sales from your affiliates' own referrals (you keep ~10%). The affiliate panel doesn't expose each KOL's parent, so a full parent→child tree can't be built — only this per-level split.

Direct (tier 1)

your coupon · ~30%

Level-2 (tier 2)

override · ~10%

Affiliates

Revenue

KOL commission

Your commission

Your override

Tier 1 = signed up with your direct coupon. Tier 2 = sales from your affiliates' own referrals (you earn an override). No parent→child tree: the panel doesn't expose each KOL's upline.

Pipeline funnel — affiliates by status (Notion)Affiliates grouped by Notion pipeline status. The fullest bar is your bottleneck.

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

BD expenses by type — paid to KOLs (KOL Expenses)Payments to KOLs split by type (mirror of Notion 'KOL Expenses').

Total split by payment type.

Affiliates — Notion × Hyro (by username)Each affiliate joined by coupon across Notion (CRM) × Hyro panel (live sales). Rows with a Hyro match are the ones actually selling.

shown · with Hyro match · total

Only with Hyro match Only mismatches (≥$500)

Affiliate	Code	Via	Status	Hyro revenue	Your commission	Conv.	Notion rev.	Earned (KOL)	Commission paid	KOL balanceKOL balance = Earned − Paid. + means you still owe the KOL; − means you paid them ahead. Flagged when the gap is ≥ $500. Fix it manually in Notion.

No affiliates with these filters.

KOL balance = Earned (commission per the panel) − Commission paid (payout-type only; upfronts/retainers/SEO are CAC, counted separately). + you still owe commission · − paid ahead. Flagged at ≥ $500. A review flag, not a confirmed payable — Hyro may pay some commission directly, outside Notion.

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.

Revenue : CAC by affiliate (Hyro view)

≥4x1–4x<1x

Log scale (tame outliers) Hide top earner · affects this chart + the Pareto

Hyro's view (Hyro receives the sales and pays the KOL). LTV = revenue the affiliate generates for Hyro. CAC = what Hyro pays them (upfront, bonuses, retainer). Ratio = revenue ÷ CAC.

Only profitable

Affiliate	Revenue	CAC	Revenue:CAC	Conv.

No affiliates with these filters.

Revenue:CAC = ∞ = affiliate with no acquisition cost recorded (no upfront/retainer paid) → all their revenue came free of acquisition spend.

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

Empty by design · needs trader-level data

Net LTV per customer, pass-rate and cohort curves need per-trader data (who bought through each code, who passed the evaluation, who got funded). The affiliate panel doesn't expose that — it lives in the prop firm's risk backend — so these stay empty by design, not from a bug. They'd only fill if we connect that source.

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 split of the BD money between Alvaro and Bast, computed on the scraper (captured transactions) from the certification date onward. HyroTrader: the first $1,000/mo of commission stays with Bast; everything above is split 50/50 (Bast's $3,500 Hyro salary is outside this). Funding Predicts: not operating yet → $0 until it bills.

BD commissionTotal BD commission captured by the scraper since the certification date. This is the pot that gets split.

—

Since certification · scraper

Alvaro's takeFixed monthly (FP only) + Alvaro's % of the amount above the benchmark.

—

Liquidable to Alvaro

Bast's take

—

BD commission − Alvaro's split

Months

—

Monthly split since certification

Month	BD commission	Volume	Benchmark	Splittable	Alvaro	Bast

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

Affiliates from Aff Management (Notion) with a DM-able Telegram handle. [Write·FP] drops the approved opener as an editable draft in Chats — you review and Send there. Nothing is sent on its own (cap 22/day, from Bast's FP account).

KOL	Telegram	Notion status	Outreach