Partner Onboarding to Placement Process
Purpose
This page connects the full partner flow from first interest or existing relationship to active placement inside the Eprenz ecosystem.
It brings together:
- existing WorkDrive partner review
- PartnerStack applications
- manual partner applications
- direct outreach
- partner onboarding form
- approval and agreement status
- tracking setup
- founder problem mapping
- knowledge-layer mapping
- placement decision
- OS readiness
- activation
The goal is to move every partner out of an unclear status and into one clear state:
- ready to place
- needs completion
- needs update
- needs conversion review
- paused
- offboarded
Full Process Flow
flowchart TD
A[Partner Source] --> B{Source Type}
B --> C[Existing WorkDrive Partner]
B --> D[PartnerStack Application]
B --> E[Manual Application]
B --> F[Direct Outreach]
C --> G[Check Current Status]
D --> H[Use Standard Answer Bank]
E --> H
F --> H
G --> I[Partner Onboarding Form or Sheet Update]
H --> I
I --> J[Fit Review]
J --> K[Approval or Agreement Check]
K --> L[Tracking Check]
L --> M[Founder Problem Mapping]
M --> N[Top Category and Subcategory Mapping]
N --> O[Placement Surface Decision]
O --> P{OS Ready?}
P --> Q[Activate Partner]
P --> R[Needs Update]
P --> S[Pause or Offboard]
Q --> T[Track Results]
T --> U[Review Performance]Step 1, Identify the Partner Source
Each partner should start from one source type.
| Source Type | Meaning |
|---|---|
| Existing WorkDrive Partner | Partner already has a WorkDrive folder |
| PartnerStack Application | Partner uses PartnerStack for affiliate or partner program |
| Manual Application | Partner has its own application form |
| Direct Outreach | Eprenz contacts partner directly |
| Existing Sponsor or GFIS Relationship | Partner already has sponsor or event relationship |
| Existing Global Partner | Partner may have broader ecosystem value |
| Existing Solution Partner | Partner may provide service or expert support |
Step 2, Check Current Status
For existing partners, check:
| Status Area | Question |
|---|---|
| WorkDrive | Does a folder exist and is it usable? |
| Approval | Is Eprenz approved, pending, rejected, not applied, or unknown? |
| Onboarding | Is the partner onboarded, partially onboarded, or not onboarded? |
| Login | Does access exist and who owns it? |
| Agreement | Are terms or agreements available? |
| Tracking | Is there a link, code, dashboard, or manual method? |
| Strategic Fit | Does the partner fit the current strategy? |
Do not store passwords in the sheet.
Track only:
- whether login exists
- who owns access
- whether access was verified
- where the password is securely stored
Step 3, Choose the Application Path
| Path | Use When |
|---|---|
| PartnerStack | Partner program is managed through PartnerStack |
| Manual Application | Partner has its own application form |
| Direct Outreach | No formal application exists |
| Existing Relationship Review | Partner already exists and needs status cleanup |
Before applying or reaching out, Eprenz needs standard answers.
Do not create the standard answers inside this page.
This page only marks them as required.
Step 4, Use the Partner Onboarding Form
The partner onboarding form collects partner information:
The form should help confirm:
- partner type
- founder problem solved
- top category and subcategory
- stage fit
- country fit
- offer or member benefit
- tracking method
- agreement status
- placement surface
- relationship owner
Form submission does not mean the partner is OS ready.
Step 5, Review Fit
Each partner should be reviewed for:
| Fit Type | Question |
|---|---|
| Founder Problem Fit | What problem does this partner solve? |
| Stage Fit | Does it support Start, Grow, Profit, Exit, or multiple stages? |
| Country Fit | Which countries or regions does it serve? |
| Knowledge Fit | Does it connect to a guide, checklist, or topic? |
| Placement Fit | Where should this partner appear? |
| Brand Fit | Does this partner strengthen Eprenz positioning? |
| Strategic Fit | Should this remain affiliate, become Solution Partner, Global Partner, GFIS partner, sponsor, or advisor? |
Step 6, Map to Knowledge-Layer Taxonomy
Each partner should be mapped to the knowledge-layer taxonomy.
Required fields:
| Field | Example |
|---|---|
| Top Category | Website and Commerce Layer |
| Subcategory | Payments and Checkout |
| Founder Problem Language | I need to accept payments |
| Partner Category | Payment processor |
| Knowledge Fit | How to choose a payment processor |
This keeps partner placement connected to the founder problem instead of a random directory.
Step 7, Confirm Approval, Agreement, and Tracking
Before placement, confirm:
| Area | Required Status |
|---|---|
| Approval | approved, pending, rejected, not applied, unknown |
| Agreement | standard terms, partner terms, custom agreement, missing, not needed |
| Tracking | link, code, dashboard, manual, event tracking, social tracking, none |
| Revenue Model | affiliate, referral, sponsorship, strategic value, no revenue |
| Owner | internal person responsible |
If tracking is missing, mark the partner as Needs Tracking.
If agreement is unclear, mark the partner as Needs Agreement Review.
Step 8, Decide Placement Surface
A partner should be placed only where it helps the founder act.
| Surface | Use When |
|---|---|
| OS | partner supports a next action |
| Partner Page | partner should be searchable and filterable |
| Mighty Knowledge Layer | partner supports a guide, checklist, or topic |
| Learning Content | partner appears after educational context |
| Events | partner can teach, host, sponsor, or activate a topic |
| Network | partner supports relationships, rooms, or introductions |
| GFIS | partner fits summit sponsorship, speaking, or activation |
| Social Media | partner is brand-safe for public co-announcement |
| Email Follow-up | partner matches a survey or Compass response |
| Advisor Follow-up | partner requires human judgment before referral |
Step 9, OS Ready Decision
A partner is OS ready only when Eprenz can answer:
| Requirement | Needed |
|---|---|
| Problem mapped | Yes |
| Top category and subcategory mapped | Yes |
| Stage fit clear | Yes |
| Country fit clear | Yes |
| Partner type clear | Yes |
| Approval or agreement status clear | Yes |
| Tracking method selected | Yes |
| Placement surface selected | Yes |
| User-facing rationale written | Yes |
| Internal owner assigned | Yes |
| Next action clear | Yes |
Step 10, Final Decision
Each partner should end with one decision.
| Decision | Meaning |
|---|---|
| Activate | partner is ready to place |
| Complete | partner is useful but setup is unfinished |
| Update | partner is useful but missing data |
| Convert | partner should become Solution Partner, Global Partner, GFIS partner, sponsor, event partner, or advisor |
| Pause | partner should be hidden until details are clear |
| Offboard | partner should be removed from active use |
End-to-End Summary
Partner source
→ application path or WorkDrive review
→ onboarding form or sheet update
→ fit review
→ approval and agreement check
→ tracking check
→ founder problem mapping
→ knowledge-layer mapping
→ placement surface decision
→ OS-ready check
→ activate, update, convert, pause, or offboard
Final Rule
Do not move a partner into placement just because the relationship exists.
A partner moves into placement only when:
- it solves a defined founder problem
- it fits the knowledge-layer taxonomy
- it has clear stage and country fit
- approval or agreement status is clear
- tracking is ready or intentionally manual
- the placement surface is defined
- an internal owner is assigned
- the next action is clear