Skip to content
← All blueprints
SaaS Affiliate Hub

Creator economy

SaaS Affiliate Hub

Manage partners, generate trackable links, attribute revenue, and pay out commissions for indie SaaS — without an enterprise platform.

  • Full planning bundle — BRAND, MRD, BRD, PRD, DESIGN
  • Branded styleguide — typography, color, components
  • 4 previewable mockups

Cloning copies the full plan into a new project you own — edit it freely.

Inside the bundle

Styleguide and mockups

A look at the brand palette and screen-level mockups that ship with this plan. Cloning copies all of them into your project.

Style guide

Styleguide

What this blueprint gives you

The “affiliate program in a box” model for an indie SaaS: a partner portal where affiliates sign up, get a trackable link, watch clicks and conversions in near real time, and get paid on a schedule the founder controls.

Built for SaaS that does $5k–$500k MRR and wants to launch a partner program without an enterprise contract or a percentage of revenue taken off the top. Five planning documents (BRAND, MRD, BRD, PRD, DESIGN) at senior depth, covering attribution rules, payout pipelines, fraud controls, and a founder dashboard that makes the whole program a single screen of truth.

Planning documents

Preview the plan

Each blueprint includes the senior-level planning files. These cards show the opening text before you clone the full bundle.

Brand Guidelines Document

BRAND.md

Preview

BRAND — SaaS Affiliate Hub One line The affiliate program your indie SaaS would build for itself if you had the time. Who it speaks to The founder of an indie SaaS — typically $5k to $500k MRR, two to ten people, a couple of hundred to a few thousand customers. They've been paying a creator $200/month informally; their best converting customer wrote a blog post and they have no idea how many signups it produced. They want to formalize a partner program without paying a percentage to an enterpris

Design Specification Document

DESIGN.md

Preview

DESIGN — SaaS Affiliate Hub Information architecture Operator console: Dashboard (program health), Partners (list + applications), Conversions (event log + review queue), Rules (commissions + bonuses), Payouts (cycles + history), Program page (branding + content), Settings (connections, fraud thresholds, team). Partner portal: Overview (this period's earnings), Links (default + campaigns + QR), Performance (clicks → signups → paying), Ledger (every line, every reversal, every payout), Payouts (h

Market Requirements Document

MRD.md

Preview

MRD — SaaS Affiliate Hub The problem Indie SaaS founders who want to grow through partners face a frustrating choice. The enterprise affiliate networks take 20–30% of every payout and require contracts and account managers. The self serve "affiliate" plugins from large platforms are either buried inside another SaaS or barely track conversions correctly. Wiring it up by hand means writing attribution code, building a partner portal, calculating commissions across refunds and proration, schedulin

Business Requirements Document

BRD.md

Preview

BRD — SaaS Affiliate Hub Business outcomes 1. Programs that ship. Number of installed programs that publish a public page and approve their first partner. 2. Partner activation. Programs with ≥5 active partners by week 4. 3. Payouts that flow. Successful payout cycles per program per month — the load bearing trust event. 4. Operator stickiness. Programs renewing after one full quarter; the program becomes a channel they rely on. Success metrics (v1 targets) Time to launch: a founder publishes a

Product Requirements Document

PRD.md

Preview

PRD — SaaS Affiliate Hub Phase 0 — Foundations Operator account; one program per operator (multiple programs is a paid tier later). Auth + roles: operator owner , admin ; partner side accounts (separate identity space). Program identity: name, public page URL (custom subdomain or CNAME on operator domain), logo, brand color, terms of program text. Connections: payments processor (for revenue events), payouts processor (for payouts). Acceptance: an operator signs up, configures their program, pub

Keyboard shortcuts

Press ? anywhere to open this list. Esc closes it.

Go to dashboard
g d
Go to current project
g p
Save the editor
S
Send chat message
Open this cheat sheet
?

Sequence shortcuts (g _) only fire when no field is focused. On macOS use ; on other platforms Ctrl.