Partner Placement
Partner Placement Inside the Ecosystem
Purpose
Partner placement defines where an approved and reviewed partner should appear across Eprenz.
A partner should not automatically appear everywhere.
Placement should depend on:
- founder problem
- stage fit
- partner relevance
- country fit
- tracking readiness
- content fit
- brand fit
- relationship type
The goal is to place partners where they help founders take the next step.
Placement Logic
flowchart TD
A[Partner Ready] --> B[Founder Problem]
B --> C[Best Placement Surface]
C --> D[Knowledge, OS, Event, Network, GFIS, Social, Email]
D --> E[Member Action]
E --> F[Engagement and Revenue Tracking]
Placement Surfaces
| Surface | When to Use |
|---|---|
| OS Home | Partner supports a priority next action for the founder |
| Partner Page | Partner belongs in a searchable and filterable partner directory |
| Mighty Knowledge Layer | Partner supports a guide, checklist, lesson, or resource |
| Learning Content | Partner should appear after educational context |
| Events | Partner can teach, sponsor, host, or activate a topic |
| Network | Partner supports introductions, rooms, expert threads, or relationship-building |
| GFIS | Partner fits summit sponsorship, speaking, activation, or post-event conversion |
| Social Media | Partner fits co-announcement, educational post, or partner visibility campaign |
| Email Follow-up | Partner matches a survey or Compass response |
| Advisor Follow-up | Partner should only be recommended after human review |
Placement Rules
| Rule | Meaning |
|---|---|
| Problem first | Partner must connect to a founder problem |
| Context before partner | If the founder needs education first, show knowledge before partner |
| Surface fit matters | Do not place every partner on every surface |
| Country matters | Do not show country-specific partners to unsupported users |
| Tracking matters | If engagement or revenue should be measured, tracking must be ready |
| Brand fit matters | Social, GFIS, and co-announcements require stronger brand alignment |
| Human review when needed | Legal, funding, exit, tax, and complex advisory partners may need advisor follow-up first |
Surface Decision Guide
| Partner Situation | Best Placement |
|---|---|
| Solves a clear setup task | Mighty Knowledge Layer, OS, Partner Page |
| Supports a guide or checklist | Mighty Knowledge Layer, Learning Content |
| Helps with a high-priority next action | OS Home |
| Needs filtering by problem, stage, or country | Partner Page |
| Can teach or activate a topic | Event |
| Can support relationship-building | Network |
| Has strategic sponsor or summit value | GFIS |
| Has public collaboration value | Social Media |
| Matches a specific Compass or survey response | Email Follow-up |
| Requires judgment before referral | Advisor Follow-up |
Examples
| Founder Problem | Partner Type | Best Placement |
|---|---|---|
| I need a domain name | Domain registrar | Mighty guide, Partner Page, OS |
| I need a business bank account | Banking partner | Mighty guide, Partner Page, Email Follow-up |
| I need to accept payments | Payment processor | Mighty guide, OS, Partner Page |
| I need a website | Website builder, hosting, web design | Mighty guide, Partner Page, Event |
| I need more customers | CRM, lead generation, email marketing | Sales route, Event, Partner Page |
| I need financial control | Accounting, bookkeeping, CFO | Business Pulse, Mighty guide, Advisor Follow-up |
| I need legal structure | Formation, legal, IP partner | Mighty guide, Partner Page, Advisor Follow-up |
| I need funding | Lender, grant partner, investor network | Funding event, Advisor Follow-up, Partner Page |
| I need the right relationships | Community, event, expert partner | Network, Event, GFIS |
| I need exit readiness | Valuation, CFO, legal, M&A partner | Advisor Follow-up, Event, GFIS |
OS Placement
Use OS placement when the partner supports a clear next action.
Examples:
- open a business bank account
- set up payments
- choose a website platform
- connect accounting
- start a CRM
- prepare for funding
- attend an expert session
OS placement should be specific, not generic.
Bad:
“Check out our partners.”
Better:
“You said you need to accept payments. Start with the payment setup guide, then compare available payment partners.”
Mighty Knowledge Layer Placement
Use Mighty when the partner supports practical learning.
The structure should be:
Problem → Guide → Checklist → Partner Options
Examples:
| Knowledge Topic | Partner Placement |
|---|---|
| How to choose a domain name | domain registrar options |
| How to choose a business bank | banking partner options |
| How to accept payments | payment processor options |
| How to choose a website platform | website builder and hosting options |
| How to choose a CRM | CRM and sales tool options |
| How to prepare for funding | funding readiness and advisory partners |
The partner should appear after the founder understands what decision they are making.
Partner Page Placement
Use the Partner Page for partners that should be searchable and filterable.
Filters should include:
- founder problem
- top category
- subcategory
- partner category
- stage fit
- country fit
- relevance
- relationship type
- readiness
- placement surface
The Partner Page should not feel like a random directory.
It should help founders find the right support by problem.
Event Placement
Use events when the partner can teach, activate, or build trust around a topic.
Examples:
| Topic | Event Type |
|---|---|
| Business banking | banking setup session |
| Payments | payment setup clinic |
| Website | website launch workshop |
| Marketing | lead generation workshop |
| Finance | CFO office hour |
| Legal | legal Q and A |
| Funding | funding readiness session |
| Exit | valuation or exit readiness roundtable |
Events are useful when the partner needs trust-building before conversion.
Network Placement
Use network placement when the partner helps with relationships.
Examples:
- founder roundtable
- expert thread
- partner room
- advisor introduction
- community discussion
- peer group
- office hours
Network placement is best for partners connected to mentorship, relationships, partnerships, service providers, and expert access.
GFIS Placement
Use GFIS placement when a partner has summit-level value.
Possible GFIS roles:
- sponsor
- speaker
- panelist
- workshop host
- exhibitor
- partner session
- post-event offer
- co-branded campaign
GFIS placement should be reviewed separately because it affects Eprenz brand visibility and sponsor value.
Social Media Placement
Use social media when the partner relationship is clear and public-facing.
Possible formats:
- co-announcement
- educational post
- partner spotlight
- event promotion
- GFIS sponsor feature
- founder resource post
- short video or interview
- LinkedIn collaboration post
Social media placement should not make Eprenz look like an affiliate promotion page.
The content should lead with founder value.
Example:
Bad:
“We are excited to partner with X.”
Better:
“Many founders struggle to choose the right business bank. Here is what to look for, and why we are adding partner options to help founders compare.”
Email Follow-up Placement
Use email follow-up when the partner directly matches a survey or Compass response.
Examples:
| Signal | Email Follow-up |
|---|---|
| Founder needs banking | send banking guide and partner options |
| Founder needs website | send website guide and setup options |
| Founder needs funding | send funding readiness content and event invite |
| Founder needs legal help | send legal checklist and advisor route |
| Founder needs networking | send network or event invitation |
Email should not only send a partner link.
It should include context, a useful next step, and the reason the partner is relevant.
Advisor Follow-up Placement
Use advisor follow-up when the recommendation requires judgment.
This is especially important for:
- legal
- tax
- funding
- exit
- CFO support
- complex compliance
- high-cost services
- country-specific matters
In these cases, Eprenz may show content first, then route the founder to an advisor or team review before naming a specific partner.
Placement Decision Table
| Question | If Yes | Placement Direction |
|---|---|---|
| Does this partner support a specific knowledge topic? | Yes | Mighty or Learning |
| Does this partner support a high-priority next action? | Yes | OS Home |
| Should founders compare options? | Yes | Partner Page or comparison chart |
| Does this partner need trust-building? | Yes | Event or Network |
| Does this partner have summit value? | Yes | GFIS |
| Is this partner public-facing and brand-safe? | Yes | Social Media |
| Does this partner match a survey or Compass answer? | Yes | Email Follow-up |
| Does this partner require human judgment? | Yes | Advisor Follow-up |
Final Rule
Partner placement should follow founder context.
Do not ask:
“Where can we promote this partner?”
Ask:
“Where would this partner help the founder make progress?”