Partner System
Purpose
The Partner System defines how Eprenz connects founder problems to partner categories, existing partners, partner gaps, placement surfaces, and OS readiness.
Partners should not live only on the Partner page.
They should appear where they help the founder act.
Main Flow
flowchart LR
A[Founder Problem] --> B[Partner Category]
B --> C[Existing Partner or Gap]
C --> D[Placement Surface]
D --> E[OS Ready or Not Ready]Partner Demand Signals
| Repeated founder need | Partner question |
|---|---|
| Banking demand | Do we have banking partners for their country? |
| Website demand | Do we have website, hosting, and domain partners? |
| Networking demand | Do we have event hosts, partner rooms, and expert circles? |
| Mentorship demand | Do we have advisors or partner experts? |
| Funding demand | Do we have lenders, investors, and funding readiness partners? |
| Exit demand | Do we have valuation, legal, CFO, and exit partners? |
Partner Gap Questions
| Question | Why it matters |
|---|---|
| Do we have a partner for this problem? | avoids missing support |
| Is the partner active? | avoids dead links or inactive accounts |
| Is the partner relevant to the founder stage? | avoids poor recommendations |
| Does the partner support the founder country? | avoids unusable recommendations |
| Is the partner approved or pending? | avoids showing unavailable partners |
| Do we have tracking in place? | supports revenue and reporting |
| Is the partner ready for OS placement? | protects user experience |
Gap Status
| Status | Meaning |
|---|---|
| Covered | we have a usable partner |
| Weak | we have a partner but need better fit |
| Missing | no partner exists |
| Unknown | research needed |
| Country limited | partner exists but not for all users |
Affiliate Sheet Direction
The affiliate sheet should move from:
Partner → Category → Link
to:
Founder Problem → Partner Category → Partner → Stage Fit → Country Fit → Placement Surface → OS Readiness
Required Partner Fields
| Field | Purpose |
|---|---|
| Partner name | company or provider |
| Website | partner website |
| Partner type | global partner, solution partner, affiliate, sponsor, advisor |
| Partner category | banking, payments, legal, CRM, marketing, etc. |
| Founder problem solved | plain-language problem |
| Stage fit | Start, Grow, Profit, Exit |
| Supported countries | countries or regions served |
| Primary country | strongest market |
| Affiliate program source | PartnerStack, direct, custom, none |
| Application status | not started, applied, approved, rejected, unclear |
| Tracking method | link, code, dashboard, manual, unknown |
| Revenue model | referral fee, revenue share, sponsorship, none, unknown |
| Agreement status | standard, partner terms, custom, missing |
| Login owner | who manages the account |
| OS readiness | ready, needs review, not ready |
| Why this partner | short user-facing rationale |
| Notes | context and next action |
Partner Placement Surfaces
| Surface | Partner placement role |
|---|---|
| Home | show one relevant next action or partner prompt |
| Compass result | show matched category after diagnosis |
| Journey | show partner tied to a stage step |
| Learning | show partner after knowledge and checklist |
| Mighty knowledge layer | show partner inside problem content |
| Checklist | show partner as implementation support |
| Business Pulse | show finance, operations, or health partners |
| Sales Pipeline | show CRM, sales, and marketing partners |
| Network | show partner rooms, experts, and introductions |
| Events | show partner as workshop or roundtable host |
| Advisor follow-up | show partner as referred provider |
| Partner page | show searchable and filtered partner database |
| Email follow-up | show partner after survey or Compass signal |
OS Ready Definition
A partner is OS ready when Eprenz knows:
- what problem the partner solves
- which stage the partner fits
- which country the partner supports
- where the partner should appear
- whether the partner is approved or active
- whether tracking exists
- what the user-facing reason is for showing the partner
If these are missing, the partner is not OS ready.