Stronger than a static referral page — partner codes, QR brochures, tracked landing paths, attribution dashboards, and payout visibility with Stripe webhook settlement.
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.
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.
Built from live Knight Logics workflows — not generic agency checklists.
Entry
Print-ready QR links and partner codes that attribute every consult to the right source.
Routing
Branded landing paths with tracked forms — not generic UTM hacks.
Events
Scan, form, and conversion events stored for reporting and dispute resolution.
Dashboard
/referral-dashboard with partner visibility into leads, status, and payout progress.
Payouts
Earned referral fees tracked with webhook-driven payout status.
Network
Framework for trusted Tampa Bay trade partners routing work responsibly.
The same referral infrastructure behind Knight Logics partner program — QR, codes, events, and payout visibility in production.
Scoped to your trade, territory, and ops maturity — not a one-size package.
Referral partners complement outbound CRM — attribution must be defensible before scaling Tampa Bay trade network experiments.
A clear path from intake to launch — scoped to what your team will actually use.
Document attribution windows, fee structure, and who owns the customer relationship.
Deploy /ref/:partner routes and brochure QR assets per partner.
Neon Postgres events and referral-dashboard views for partners and owners.
Stripe webhook settlement with clear earned vs paid reporting.
Measurable operator results — not vanity dashboards.
Partners check earned vs paid status in dashboard instead of arguing over spreadsheet rows.
Unique codes and QR assets deploy in days — not weeks of custom dev per partner.
Owners see which QR campaigns and partner codes produce consults before scaling network spend.
Referral support happens inside Knight Command without orphan dashboard URLs.
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
QR brochures, partner codes, Neon event logging, and referral-dashboard payout visibility — live behind Knight Logics partner program.
Referral system case studyLive builds and internal workflows behind this service lane.
/ref/:partner paths, Neon Postgres events, QR brochures, and Stripe webhook payouts.
Unified /admin tabs for CRM, email, social, referrals, and logs on ports 5050–8501.
82 land clearing and forestry mulching pages across Central Florida — faithworks OutreachEngine lane, schema, GA4/GSC, and GBP alignment in the full growth stack.
Partners use /referral-dashboard for lead status, attribution, and payout progress tied to their code or QR path.
Rules are documented upfront — typically tracked form submits or booked consults within the agreed window from /ref/:partner entry.
Yes — attribution and dashboard visibility can launch first; Stripe webhook payouts add automated settlement when you are ready.
We will scope codes, QR assets, dashboard access, and payout rules for your trade lane.
Book a Free Consultation