Skip to content

Partner Onboarding Flow and Questions

Partner Onboarding Flow

Purpose

The partner onboarding flow defines how a partner moves from interest, existing relationship, or partial setup into an approved, tracked, and ecosystem-ready partner.

The full onboarding questions are collected through the Eprenz partner onboarding form:

Zoho Survey Affiliate Partner Standard Answers

The form collects the partner information. The review process decides whether the partner is ready to place, needs completion, should be converted, paused, or offboarded.

Onboarding Flow

flowchart TD
  A[Partner Interest or Existing Relationship] --> B{Application Path}
  B --> C[PartnerStack Application]
  B --> D[Manual Partner Application]
  B --> E[Direct Manual Outreach]
  C --> F[Use Standard Answer Bank]
  D --> F
  E --> F
  F --> G[Complete Partner Onboarding Form]
  G --> H[Review Fit]
  H --> I[Check Approval or Agreement Status]
  I --> J[Confirm Tracking]
  J --> K[Map to Founder Problem]
  K --> L[Map to Placement Surface]
  L --> M{OS Ready?}
  M --> N[Activate]
  M --> O[Needs Update]

Partner Application Paths

Partner onboarding can start in three main ways.

1. PartnerStack Application

Use this when the partner runs its affiliate or partner program through PartnerStack.

This path usually requires:

  • PartnerStack account access
  • correct Eprenz company details
  • correct website URL
  • approved company description
  • approved contact person
  • program approval status
  • affiliate link or tracking link
  • dashboard access
  • commission or referral terms

Before applying through PartnerStack, Eprenz needs a standard set of approved answers so John, Diksha, or anyone else does not submit inconsistent information.

2. Manual Partner Application

Use this when the partner has its own application form outside PartnerStack.

This may include SaaS partner programs, affiliate forms, referral forms, agency partner programs, or direct vendor applications.

This path usually requires:

  • partner application URL
  • standard Eprenz company answers
  • contact person
  • business description
  • audience description
  • traffic or community size
  • website and social links
  • country or company location details
  • tax or payout details if required
  • follow-up owner
  • approval status

Manual applications also need a shared answer bank so every application uses the same approved Eprenz positioning and details.

3. Direct Manual Outreach

Use this when there is no formal application form and Eprenz needs to contact the partner directly.

This path may apply to:

  • solution partners
  • advisors
  • local providers
  • GFIS sponsors
  • event partners
  • global partners
  • custom collaboration partners

This path usually requires:

  • outreach message
  • partner value proposition
  • founder problem the partner solves
  • proposed relationship type
  • possible placement surface
  • tracking or referral expectation
  • agreement expectation
  • internal owner
  • follow-up date

This should not start from scratch each time. Eprenz needs a standard partner outreach framework before manual outreach begins.

Standard Answers Needed Before Applying

Before anyone applies to partner programs or reaches out manually, Eprenz needs a shared answer bank.

This should include approved answers for:

  • Eprenz company name
  • legal company name, if different
  • company website
  • company location
  • short company description
  • longer company description
  • audience description
  • founder and community size
  • countries served
  • social media links
  • contact person
  • contact email
  • role or title of applicant
  • how Eprenz will promote or place the partner
  • expected use case
  • why Eprenz wants to join the partner program
  • payout or tax information, if required
  • standard partner positioning language
  • standard GFIS positioning, if relevant

Do not create these answers inside this section yet.

For now, mark this as a required input before execution.

What the Onboarding Form Should Help Confirm

The onboarding form should help Eprenz confirm:

  • what founder problem the partner solves
  • which top category and subcategory the partner fits
  • which business stage the partner supports
  • which countries or regions the partner serves
  • what offer or benefit is available to Eprenz members
  • whether the partner is an affiliate, solution partner, sponsor, advisor, event partner, or global partner
  • whether tracking exists
  • whether agreement terms exist
  • where the partner should appear in the ecosystem
  • who owns the relationship internally

OS Ready Rule

A partner is not ecosystem-ready just because the form is submitted.

A partner becomes ready only when Eprenz can clearly answer:

Question Required Answer
What problem does this partner solve? Founder problem tag
Where does this fit in the knowledge layer? Top category and subcategory
Which stage does this support? Start, Grow, Profit, Exit, or multiple
Where can this partner serve founders? Country or region fit
How do we track engagement or revenue? Link, code, dashboard, manual tracking, or not applicable
Where should this partner appear? OS, Mighty, events, GFIS, social, email, advisor, Partner page
Who owns the relationship? Internal owner
What is the next action? Activate, update, convert, pause, or offboard

Placement After Onboarding

Once reviewed, the partner should be assigned to one or more placement surfaces:

  • OS
  • Partner page
  • Mighty knowledge layer
  • Learning content
  • Events
  • Network
  • GFIS
  • Social media
  • Email follow-up
  • Advisor follow-up

Sheet Fields Needed for Application Tracking

Add these fields to the affiliate or partner sheet:

Field Purpose
Application Path PartnerStack, manual application, or direct outreach
Application URL where to apply
Standard Answers Needed? yes or no
Application Owner who applies or contacts
Application Submitted? yes, no, pending
Submission Date when application was submitted
Approval Status approved, pending, rejected, unknown
Login Exists? yes, no, unknown
Dashboard Exists? yes, no, unknown
Tracking Link Received? yes, no, unknown
Follow-up Date when to check back
Notes context and next step

Final Rule

The onboarding form collects the information.

The application path defines how the partner enters.

The review process decides whether the partner is:

  • ready to place
  • missing information
  • approved but not onboarded
  • not a fit with current strategy
  • useful for a future opportunity
  • ready for conversion into a stronger partner relationship
  • paused or offboarded