OS Surfaces

Definition

An OS surface is any place inside the Eprenz Operating System where the founder receives guidance, takes action, or sees a recommended next step.

The surface is not the strategy.

The surface is where the strategy appears to the user.

Core Principle

A survey answer should not route directly to a partner, lesson, event, or advisor.

It should first route to the OS surface that best fits the problem.

Then that surface brings in the right mix of knowledge, partners, events, people, AI, or action steps.

flowchart LR
  A[Survey Problem] --> B[Best OS Surface]
  B --> C[Knowledge or Action]
  C --> D[Partner, Event, Network, Advisor, AI]
  D --> E[Progress]

OS Surface Responsibilities

OS Surface	Primary Job	Problem It Solves First	Supporting Elements
Home	Show current priority	I do not know what to focus on	Next action, progress, alerts, recommended path
Compass	Diagnose current state	I do not know where I stand	Survey logic, stage, score, priorities, blockers
Journey	Guide the business path	I need a structured path	Milestones, steps, knowledge, progress
Goals	Track commitment	I need accountability	Goals, deadlines, reminders, progress
Profile	Store founder context	Eprenz needs to understand me	Role, stage, country, business model, goals
Business Pulse	Measure business health	I do not know what is working	Finance, operations, performance, health signals
Sales Pipeline	Manage revenue activity	I need more customers	Leads, sales steps, CRM, marketing support
Network	Connect with people	I need relationships	Community, peers, groups, introductions, events
Partners	Find tools and providers	I need implementation help	Partner matches, tools, services, providers
Atlas AI	Provide thinking support	I need guidance now	AI answers, decision support, summaries, next steps
Learning	Explain the problem	I need to understand what to do	Lessons, guides, templates, checklists, stories
Journal	Capture reflection and progress	I need to track what I am learning	Notes, decisions, reflections, progress signals

Why This Matters

The OS should not treat every problem as a partner opportunity.

Some problems need knowledge first.

Some need a person.

Some need a tool.

Some need an event.

Some need AI support.

Some need progress tracking.

The OS surface decides where the founder should land first.

Examples

Survey Signal	First OS Surface	Supporting Routes
Networking	Network	Events, community, partner rooms, introductions
Marketing or visibility	Learning	Sales Pipeline, Partners, Events, Atlas AI
Getting more customers	Sales Pipeline	Learning, CRM partners, sales events, advisor support
Cash flow or profitability	Business Pulse	Learning, finance partners, CFO advisory, Atlas AI
Legal matters	Partners	Learning, advisor support, legal checklist
Knowing what to do next	Compass	Journey, Home, Atlas AI
Operations and systems	Journey	Learning, Partners, Atlas AI, templates
Finding service providers	Partners	Learning, advisor follow-up, country filter
Funding or lending	Partners	Business Pulse, advisor support, funding readiness content
Exit planning	Journey	Learning, advisor support, valuation partners

Relationship to Partners

Partners are one OS surface.

Partners should not become the default answer to every survey signal.

A founder should see partners when implementation help is relevant.

Example:

flowchart LR
  A[I need customers] --> B[Sales Pipeline]
  B --> C[Lead generation knowledge]
  C --> D[Sales action step]
  D --> E[CRM or marketing partner]
  E --> F[Progress]

Relationship to Knowledge

Learning is the surface for understanding.

It explains the problem before asking the founder to act.

Example:

flowchart LR
  A[I need to accept payments] --> B[Learning]
  B --> C[Payment setup guide]
  C --> D[Checklist]
  D --> E[Payment partner]
  E --> F[Payments live]

Relationship to Events

Events are not separate from the OS.

Events activate knowledge and relationships.

Example:

flowchart LR
  A[Founder Problem] --> B[Learning Topic]
  B --> C[Workshop or Roundtable]
  C --> D[Action Step]
  D --> E[Progress Signal]

Relationship to Country

Some OS surfaces need country logic.

Country impacts:

• banking
• lending
• legal
• tax
• payroll
• formation
• privacy
• compliance
• currency
• payment availability

Partners should include supported countries so the OS does not recommend tools or providers that do not work for that founder.

Phase 1 Decision

Before Phase 2 routing begins, every OS surface should have one clear responsibility.

Routing should send a founder to the best surface first.

Then that surface should assemble the relevant support around the problem.