Eprenz Operating System | Affiliate Program/Global Partners
Purpose
Help entrepreneurs make meaningful business progress by connecting them with the right knowledge, people, tools, partners, and actions at the right time.
flowchart LR
A[Founder Signal] --> B[Founder Context]
B --> C[Current Problem]
C --> D[Knowledge Solution]
D --> E[Action Step]
E --> F[Tool, Partner, Person, Event]
F --> G[Progress Signal]
G --> B
Phase 1 Focus
Understand the system before designing the process.
Current questions:
- What are we building?
- Why does it exist?
- Who is it for?
- How do the pieces connect?
- How should survey signals become useful guidance?
- Where do partners fit?
- Where does knowledge fit?
Current Working Model
The entrepreneur does not enter a course.
The entrepreneur does not enter a partner directory.
The entrepreneur enters through a business problem.
The OS surrounds that problem with the right mix of knowledge, people, tools, partners, events, and actions.
Documents
Phase 1: Understanding
| Document | Purpose |
|---|---|
| Project Definition | Purpose, goal, ICP, scope, success metrics |
| Fundamental Principles | Core design principles |
| System Map | How the ecosystem connects |
| Compass | In-OS survey and diagnostic layer |
| User Journey | Founder experience |
| OS Surfaces | Ecosystem interaction touchpoints |
| Survey Routing | X answer into Y route package |
| Knowledge Layer | How problems become understanding |
| Partner Layer | How implementation happens |
| Things to Remember | Meeting notes and future tasks |
| Open Questions | Unresolved decisions |
| Decisions Log | Agreed decisions |
Phase 2: Logic Design
| Document | Purpose |
|---|---|
| Overview | Overview of logic routing and partner supply |
| Meeting Priorities | Priorities and goals for logic design |
| Founder Need Routing | Compass answers and routing maps |
| Problem Taxonomy | Core taxonomical mapping of issues |
| Partner System | Logic for gaps and partner mapping |
| Knowledge & Events | Integrating content and events |
| Country & Compliance | Assumptions for geographic routing |
| Progress Signals | Measuring success/momentum |
| Open Questions | Outstanding logic design items |
Phase 3: Partner Execution
| Document | Purpose |
|---|---|
| Overview | Overview of partner execution |
| Partner Process & Plan | High-level process design |
| Existing Partner Strategy | Strategy for 60-80 existing partners |
| Partner Sorting Logic | Sorting by problem, stage, and relevance |
| Knowledge Layer Sheet Update | Mapping sheets to knowledge problems |
| Affiliate Sheet Sorting | Outreach priority and sorting setups |
| Partner Onboarding Flow | Intake questions and flow |
| Partner Placement | Distribution across OS, Mighty, events, etc. |
| Onboarding to Placement Flow | End-to-end partner onboarding funnel |
| Current Tracking Setup | Immediate fields and metrics to track |
| Partner KPIs | Measuring activity, placement, and performance |
| Future Workflows & SOPs | Deferrals and SOPs for the next phase |