Category and affiliate status come after founder problem.
Speaker note: This rule prevents the partner page from becoming a vendor directory.
06, Onboarding Flow/ 17
The form collects information. Review decides readiness.
A submitted partner form does not mean the partner is ready for OS, Mighty, events, social, GFIS, or email follow-up.
Partner onboarding flow
flowchart LR
A[Partner Interest] --> B[Onboarding Form]
B --> C[Fit Review]
C --> D[Approval or Agreement]
D --> E[Tracking Check]
E --> F[Problem Mapping]
F --> G[Placement Surface]
G --> H{OS Ready?}
H --> I[Activate]
H --> J[Needs Update]
Problem, stage, country, tracking, placement, owner, next action.
Final states
Ready, missing information, approved but incomplete, convert, pause, offboard.
Speaker note: This keeps intake and readiness separate. That distinction matters for Mohammed and the build team.
07, Application Paths/ 17
Three application paths need one standard answer bank.
PartnerStack, manual applications, and direct outreach should use the same approved Eprenz answers.
Application paths
PartnerStack
Manual Form
Direct Outreach
→
Standard Answer Bank
Answer bank inputs
Needed before applying
Why
Company name and legal name
prevents inconsistent applications.
Website and description
keeps Eprenz positioning consistent.
Audience and community size
supports affiliate and partner approvals.
Countries served
supports regional fit and compliance.
Promotion and placement plan
explains how the partner will be activated.
Speaker note: This prevents John, Diksha, or anyone else from applying with slightly different Eprenz details each time.
08, Ecosystem Placement/ 17
Partners should appear where they help the founder act.
No partner appears everywhere. Placement depends on founder problem, context, readiness, and trust level.
Placement surfaces
OS
Partner Page
Mighty
Learning
Events
Network
GFIS
Social
Email
Knowledge before partner
Guide, checklist, then partner option.
Human review when risk is higher
Legal, tax, funding, exit, CFO, compliance.
Placement follows context
Not partner convenience.
Speaker note: This tells Mohammed where partners show up, but also when they should not show up.
09, Onboarding to Placement/ 17
A partner moves to placement only after readiness is clear.
This is the end to end flow from source to activation.
Full process
flowchart TD
A[Partner Source] --> B[Application Path or WorkDrive Review]
B --> C[Onboarding Form or Sheet Update]
C --> D[Fit Review]
D --> E[Approval and Agreement Check]
E --> F[Tracking Check]
F --> G[Founder Problem Mapping]
G --> H[Knowledge Layer Mapping]
H --> I[Placement Surface Decision]
I --> J{OS Ready?}
J --> K[Activate]
J --> L[Update]
J --> M[Convert]
J --> N[Pause or Offboard]
Speaker note: This is the whole system in one slide. Existing and new partners both pass through the same logic.
10, Tracking Now/ 17
Track the minimum needed to make decisions now.
Do not build a full dashboard before the partner system is active. Track the fields that drive action.
Partner Status
Placement
Engagement
Referral
Revenue
Review Decision
Minimum sheet fields
Field
Why
Partner Status
shows current state.
Strategic Fit and OS Readiness
shows fit and usability.
Founder Problem, Top Category, Subcategory
connects to knowledge layer.
Placement Surface and Status
shows where partner is live.
Tracking Method and Revenue Model
supports performance review.
Next Action and Owner
prevents drift.
Speaker note: This is the practical baseline. Manual tracking is acceptable at first, as long as the fields exist.
11, Partner KPIs/ 17
KPIs should show whether partners are active, relevant, used, and valuable.
Measure partner system health before building a complex dashboard.
Activity
Reviewed, assigned owner, completed onboarding, moved out of unknown.
Placement
Live in OS, Mighty, events, GFIS, email, social, partner page.
Speaker note: The conversion path matters because not every valuable relationship should stay in the affiliate bucket.
15, Social Activation/ 17
Partner social media should lead with founder value.
Social should not make Eprenz look like an affiliate promotion channel.
WeakWe are excited to partner with X.
Leads with the partner.
Reads like an ad.
Does not explain founder value.
BetterFounders struggle to choose the right business bank. Here is what to compare.
Leads with the founder problem.
Educates first.
Partner appears as one relevant option.
Formats, co-announcement, educational post, partner spotlight, event promotion, GFIS sponsor feature, founder resource post, short interview, LinkedIn collaboration post.
Speaker note: This gives social a rule, not only a content type.
16, SOP Boundary/ 17
This plan sets the model. Detailed SOPs come next.
Keep the presentation strategic. Move execution details into separate SOPs and task lists.
Move to SOP
Deeper workflow
Why separate
John and Diksha application SOP
execution checklist.
WorkDrive cleanup task list
row by row work.
Standard answer bank final answers
requires approval.
Password and agreement storage
security and ownership process.
KPI dashboard build
after tracking fields exist.
Social media calendar
campaign planning.
This deck
Operating model and decisions.
Next docs
SOPs, owners, tasks, due dates, approval workflow.
Speaker note: This prevents the plan deck from becoming a task management document.
17, Final Decisions/ 17
Decisions needed before execution starts.
Approve the partner operating model, then move into the SOP and cleanup sprint.
Decision 1
Confirm the partner decisions, Keep, Complete, Update, Convert, Pause, Offboard.
Decision 2
Confirm WorkDrive cleanup before new partner outreach.
Decision 3
Name the owner for partner review and OS readiness approval.
Decision 4
Identify which partners Kevin should review for GFIS, sponsor, or Global Partner conversion.
Decision 5
Choose the first priority partner categories, banking, domains, website, payments, CRM, funding, legal.
Next step
Turn this model into a short execution sprint with owners, sheet updates, and SOPs.