Partner growth

Referral Network & Tracking Systems

Stronger than a static referral page — partner codes, QR brochures, tracked landing paths, attribution dashboards, and payout visibility with Stripe webhook settlement.

/ref/:partner Tracked entry paths

Neon Postgres event log

QR Brochure-ready links

Book a Consultation Free Growth Audit

Partner attribution that scales trust

Referral partners send work through brochures, word of mouth, and complementary trades — but generic analytics cannot tell you which partner earned credit. Disputes slow network growth when payout status lives in spreadsheets.

The referral infrastructure uses /ref/:partner entry paths, QR brochure assets, Neon Postgres event logging, referral-dashboard partner visibility, and Stripe webhook-driven payout settlement.

Knight Command embeds referral ops on the 5050 family inside the Referrals tab — partners self-serve status checks instead of email disputes with ownership.

Partner attribution fails when credit is verbal. Tracked /ref/:partner paths, QR referral scans, and Neon events document which partner earned the consult.

Stripe webhook payouts and referral-dashboard earned vs paid views reduce disputes as the Tampa Bay trade roster grows.

The problem

Partner referrals are impossible to attribute fairly

Brochure QR scans, word-of-mouth, and form fills all look the same in analytics. Partners dispute who sent the lead. Payout status lives in spreadsheets.

No unique path per partner or trade lane
Consult forms do not carry referral codes reliably
Payout earned vs paid is unclear to partners
Scaling a local trade network without attribution breaks trust

What this includes

Built from live Knight Logics workflows — not generic agency checklists.

Entry

QR brochures & codes

Print-ready QR links and partner codes that attribute every consult to the right source.

Routing

/ref/:partner paths

Branded landing paths with tracked forms — not generic UTM hacks.

Events

Neon Postgres logging

Scan, form, and conversion events stored for reporting and dispute resolution.

Dashboard

Referral dashboard

/referral-dashboard with partner visibility into leads, status, and payout progress.

Payouts

Stripe webhook payouts

Earned referral fees tracked with webhook-driven payout status.

Network

Local partner network

Framework for trusted Tampa Bay trade partners routing work responsibly.

Live system

Referral dashboard & partner paths

The same referral infrastructure behind the Knight Logics partner program — generate a partner code, print a QR brochure they can hand to customers, then track scans and payouts in production.

Create a unique partner QR inside Knight Command
Print a branded handout with that partner’s name and code (example: Sir Speedy · SIRPH250)
Scans land on /ref/:partner so credit is automatic before payout review

Creating a referral partner QR code in Knight Command — **Generate the code** Partner QR created in the referral ops UI

Printed Sir Speedy Palm Harbor referral brochure with customized QR code SIRPH250 — **Print the handout** Partner-named brochure customers scan at the counter

How referral tracking works

From QR scan to earned vs paid

Partner attribution is a different system from CRM outreach. Events live in Neon; payouts settle through Stripe webhooks; partners see their own lane only.

1. Issue a unique /ref/:partner path and print-ready QR brochure per partner.
2. Consult forms and landing events write to Neon Postgres with partner code attached.
3. referral-dashboard shows earned vs paid without exposing owner-only financials.
4. Stripe webhooks update payout status when fees settle — no spreadsheet reconciliation.
5. Knight Command Referrals tab embeds the same ops surface operators already open daily.

Typical deliverables

Referral tracking infrastructure — /ref paths, Neon events, partner dashboards, and payout sync.

Tracking infrastructure

/ref/:partner landing paths with consult form attribution
QR brochure assets for print and field distribution
Neon Postgres event store for scans, forms, and conversions
Attribution windows defined in written program terms

Partner experience

referral-dashboard with earned vs paid visibility
Partner onboarding with unique codes and assets
Webhook settlement for referral fee status
Data boundaries — partners see their stats, not owner-only leaks

Program operations

Knight Command Referrals tab embed
Stripe webhook integration for payout sync
Monthly owner review of top-performing partners
API integration hooks for CRM and invoicing lanes

Attribution you can defend — QR, /ref paths, and payouts

Partner referrals are tracked from brochure scan through consult form to Stripe settlement — screenshots from the live referral program, not spreadsheet disputes.

Print referral brochure for Sir Speedy Palm Harbor with partner-specific QR code SIRPH250 — **Partner brochure** Real print handout — Sir Speedy Palm Harbor · SIRPH250 QR.

Field attribution Print QR → /ref/:partner

Print-ready brochures with a QR unique to each partner

Partners like Sir Speedy keep a counter stack of Knight Logics handouts. Each print carries that partner’s name and QR (here SIRPH250) so walk-in customers scan into a tracked /ref/:partner path — not a shared UTM guess.

Company name + QR printed on the piece partners actually hand out
Scan → tracked landing path → Neon event with partner code
Same asset pattern for sign shops, printers, and complementary trades

Referral payout tracking dashboard with earned vs paid visibility

Settlement Earned → paid visibility

Partner dashboard shows lead status and payout progress

referral-dashboard gives partners earned vs paid visibility without owner-only data leaks. Stripe webhook settlement closes the loop when jobs convert — not a monthly spreadsheet argument.

Partner codes and consult attribution in one view
Webhook sync for referral fee status on booked work
Embeds in Knight Command Referrals tab for ops review

Knight Logics referral partner program brochure preview — **Network dashboard** Partner attribution, scan events, and payout lanes in one shell.

Knight Command Referrals tab embed for partner ops review — **Knight Command** Referrals tab embed for owner ops review.

Network growth

Referrals connect to outreach and growth systems

Referral partners complement outbound CRM — attribution must be defensible before scaling Tampa Bay trade network experiments.

business-growth-systems for full stack deployment
api-integration-services for Stripe and Neon wiring
performance-partner-program when shared upside fits
case-study-referral-network-system documents live workflow

Join Referral Program Referral Case Study API Integrations

How we build it

A clear path from intake to launch — scoped to what your team will actually use.

Partner rules & fees

Document attribution windows, fee structure, and who owns the customer relationship before any QR prints.

Codes & landing paths

Deploy /ref/:partner routes and brochure QR assets per partner — not shared UTM links.

Event logging & dashboard

Neon Postgres events and referral-dashboard views for partners and owners.

Payout workflow

Stripe webhook settlement with clear earned vs paid reporting inside Knight Command.

Outcomes & best fit

Partner attribution that cuts payout disputes — built for trades printing QR handouts and scaling referral fees.

Outcomes we design for

Dispute reduction

Partners check earned vs paid in dashboard instead of arguing over spreadsheets.

Faster onboarding

Unique codes and QR assets deploy in days — not weeks of custom dev per partner.

Data-backed expansion

See which partner codes produce consults before scaling network spend.

Embedded ops

Referral support lives in Knight Command — no orphan dashboard URLs.

Best fit for

Trades with complementary partners who send real work

Businesses printing brochures or yard signs with QR CTAs

Owners scaling referral fees without spreadsheet disputes

Networks testing Knight Local Partner Network concepts

Live workflow

Proof

Referral network system in production

QR brochures, partner codes, Neon event logging, and referral-dashboard payout visibility — live behind Knight Logics partner program.

Referral system case study

Related proof & examples

Referral network proof — tracked partner paths and Knight Command embed, not a generic CRM grid.

Live workflow

Referral network infrastructure

/ref/:partner paths, Neon Postgres events, QR brochures, and Stripe webhook payouts.

Knight Command ADMIN Command Center with live Referral, Outreach, Email, and Social status

Internal system

Knight Command ops shell

Unified /admin tabs for CRM, email, social, referrals, and logs on ports 5050–8501.

Common questions

How does partner attribution work?

Each partner gets a /ref/:partner path and optional QR. Scans, forms, and conversions log to Neon with that code so credit is defensible before payout.

How do partners check their referrals?

Partners use /referral-dashboard for lead status, attribution, and payout progress tied to their code or QR path — earned vs paid without owner spreadsheet emails.

What counts as an attributed lead?

Rules are documented upfront — typically tracked form submits or booked consults within the agreed window from /ref/:partner entry.

How is this different from CRM outreach?

CRM outreach is outbound list sending. Referral tracking attributes inbound partner-sent work and settles fees — different data store, dashboard, and payout path.

Can this work without Stripe payouts?

Yes — attribution and dashboard visibility can launch first; Stripe webhook payouts add automated settlement when you are ready.

What is the typical timeline?

Partner rules and codes often ship in days; QR print assets and dashboard access follow once attribution windows are written.

Join Referral Program Referral Case Study Growth Systems Automation Systems

Building a partner referral network?

We will scope codes, QR assets, dashboard access, and payout rules for your trade lane.

Book a Free Consultation