> ## Documentation Index
> Fetch the complete documentation index at: https://altostrat.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Business Structure Modeling: Franchise, Enterprise, MSP & Partner Network Examples

> Complete guide to modeling business structures with workspace billing modes and organization hierarchies. Real-world examples for franchises, multinational corporations, MSPs, channel partners, and traditional businesses with implementation steps.

## How to Model Your Business Structure

This comprehensive guide demonstrates how to model complex business structures using workspace billing modes and organization hierarchies. Each real-world scenario provides complete implementation guidance including billing mode selection, hierarchy design, and resource management configuration.

**What you'll learn:**

* Choose optimal billing modes for different business models
* Design organization hierarchies for complex structures
* Configure resource management and usage tracking
* Implement best practices for scalability and management

## Franchise Business Model: Multi-Location Brand Management

### Franchise Business Scenario

A restaurant franchise with 50 locations across multiple regions. Each location is independently owned and requires separate billing, while maintaining brand consistency and enabling resource sharing across the franchise network.

**Business requirements:**

* Independent billing for each franchisee
* Shared resource pool for brand consistency
* Regional management and reporting
* Flexible resource allocation across locations

### Recommended Configuration: Pooled Billing Mode

**Why Pooled Mode?** Enables independent franchisee billing while creating a shared resource pool for brand-wide consistency and resource flexibility.

### Implementation

```mermaid theme={null}
graph TD
    subgraph "Franchise Workspace"
        subgraph "Resource Pool"
            BA1[Franchisee Smith<br/>3 Locations]
            BA2[Franchisee Jones<br/>2 Locations]
            BA3[Franchisee Chen<br/>5 Locations]
        end
        
        subgraph "Organization Structure"
            F[Franchise HQ]
            R1[Region: Northeast]
            R2[Region: Southwest]
            L1[Location: Boston]
            L2[Location: New York]
            L3[Location: Phoenix]
            L4[Location: Las Vegas]
            
            F --> R1
            F --> R2
            R1 --> L1
            R1 --> L2
            R2 --> L3
            R2 --> L4
        end
    end
```

### Franchise Implementation Steps

1. **Initialize Workspace**: Create workspace with Pooled billing mode for resource sharing
2. **Configure Franchisee Billing**:
   * Create individual billing accounts for each franchisee
   * Add secure payment methods for each account
   * Purchase subscriptions based on franchisee location count and needs
3. **Design Organization Structure**:
   * Create regional organizations for geographic management
   * Add franchise locations under appropriate regional organizations
   * Set location-specific resource limits as needed
4. **Setup Resource Management**:
   * Configure subscription pooling across all franchisees
   * Enable flexible resource allocation to any location
   * Implement usage tracking for franchisee reporting and chargeback

### Franchise Model Benefits

* **Financial independence**: Each franchisee maintains separate billing and payment control
* **Resource flexibility**: Shared pool enables dynamic allocation during peak periods
* **Centralized management**: Brand-wide visibility and control for corporate oversight
* **Scalable growth**: Easy addition of new franchisees and locations to existing structure

## Multinational Corporation: Global Enterprise Structure

### Multinational Corporation Scenario

A global technology company with subsidiaries operating in USA, Germany, and Japan. Each country requires complete operational independence including separate budgets, local currencies, and compliance with regional regulations.

**Business requirements:**

* Complete financial and operational isolation between countries
* Multi-currency billing and reporting
* Regional compliance and audit capabilities
* Independent budget management per subsidiary

### Recommended Configuration: Assigned Billing Mode

**Why Assigned Mode?** Provides complete isolation between subsidiaries for compliance, financial accountability, and independent operations.

### Implementation

```mermaid theme={null}
graph TD
    subgraph "Global Corporation Workspace"
        BA1[Billing: USA Corp<br/>Currency: USD<br/>Budget: $2M]
        BA2[Billing: Germany GmbH<br/>Currency: EUR<br/>Budget: €1.5M]
        BA3[Billing: Japan KK<br/>Currency: JPY<br/>Budget: ¥200M]
        
        USA[🇺🇸 USA Operations]
        DE[🇩🇪 Germany Operations]
        JP[🇯🇵 Japan Operations]
        
        USA_S[Sales Team: 50 users]
        USA_E[Engineering: 100 users]
        USA_M[Marketing: 30 users]
        
        DE_S[Vertrieb: 40 users]
        DE_E[Entwicklung: 80 users]
        
        JP_S[営業部: 30 users]
        JP_P[製品部: 50 users]
        
        BA1 --> USA
        BA2 --> DE
        BA3 --> JP
        
        USA --> USA_S
        USA --> USA_E
        USA --> USA_M
        DE --> DE_S
        DE --> DE_E
        JP --> JP_S
        JP --> JP_P
    end
```

### Setup Steps

1. **Create Workspace** with Assigned billing mode
2. **Establish Country Structure**:
   * Create top-level organization for each country
   * Create billing account for each country entity
   * Assign billing account to corresponding organization
3. **Configure Billing Accounts**:
   * Set appropriate currency for each account
   * Add country-specific payment methods
   * Purchase subscriptions based on local needs
4. **Build Department Structure**:
   * Create child organizations for departments
   * Set resource limits per department
   * Configure approval workflows as needed

### Benefits

* Complete financial separation between countries
* Local currency billing and budgeting
* Compliance with regional regulations
* Clear cost center management

## Managed Service Provider (MSP): Multi-Client Service Management

### MSP Business Scenario

A managed service provider delivering IT services to 100+ diverse clients. Each client requires complete billing separation and resource isolation, with enterprise clients needing multiple invoices for different departments.

**Business requirements:**

* Complete client isolation and separate billing
* Scalable client onboarding and management
* Multiple invoice capability for enterprise clients
* Efficient resource allocation and usage tracking

### Recommended Configuration: Assigned Billing Mode

**Why Assigned Mode?** Ensures complete client isolation required for MSP operations while supporting complex enterprise client billing needs.

### Implementation

```mermaid theme={null}
graph TD
    subgraph "MSP Workspace"
        subgraph "Standard Clients"
            BA1[Client A Billing]
            O1[Client A Org]
            BA1 --> O1
            
            BA2[Client B Billing]
            O2[Client B Org]
            BA2 --> O2
        end
        
        subgraph "Enterprise Client with Multiple Invoices"
            BA3["Enterprise Client - Billing Account<br/>Subscription 1: Marketing (20 users)<br/>Subscription 2: Operations (50 users)<br/>Total Pool: 70 users"]
            O3[Enterprise Client Org]
            O3M[Marketing Dept]
            O3O[Operations Dept]
            
            BA3 --> O3
            O3 --> O3M
            O3 --> O3O
        end
    end
```

### Setup Steps

1. **Create Workspace** with Assigned billing mode
2. **Onboard Standard Clients**:
   * Create organization for each client
   * Create corresponding billing account
   * Assign billing to organization
3. **Handle Enterprise Clients**:
   * Single organization with child departments
   * Single billing account with multiple subscriptions
   * Each subscription generates separate invoice line
   * Resources pool within the billing account

### Advanced Scenarios

#### Multiple Invoice Requirements

When a client needs more than 3 separate invoices (subscription limit):

1. Create additional billing account for same client
2. Use organization hierarchy to maintain unified structure
3. Assign different departments to different billing accounts

### Benefits

* Complete client isolation
* Flexible invoicing options
* Scalable client management
* Clear usage tracking per client

## Channel Partner / Reseller Network

### Scenario

A software vendor selling through a multi-tier partner channel. Need to track usage and manage resources through multiple levels of resellers down to end customers.

### Recommended Configuration

**Organization Hierarchy** (Billing mode depends on commercial model)

### Implementation

```mermaid theme={null}
graph TD
    subgraph "Partner Channel Hierarchy"
        V[Vendor/Root]
        MP1[Master Partner A<br/>Limit: 1000 users]
        MP2[Master Partner B<br/>Limit: 500 users]
        
        RP1[Regional Partner 1<br/>Limit: 400 users]
        RP2[Regional Partner 2<br/>Limit: 300 users]
        RP3[Regional Partner 3<br/>Limit: 200 users]
        
        C1[Customer 1<br/>Usage: 50 users]
        C2[Customer 2<br/>Usage: 100 users]
        C3[Customer 3<br/>Usage: 75 users]
        C4[Customer 4<br/>Usage: 60 users]
        
        V --> MP1
        V --> MP2
        MP1 --> RP1
        MP1 --> RP2
        MP2 --> RP3
        RP1 --> C1
        RP1 --> C2
        RP2 --> C3
        RP3 --> C4
        
        C1 -.50.-> RP1
        C2 -.100.-> RP1
        C3 -.75.-> RP2
        C4 -.60.-> RP3
        RP1 -.150 total.-> MP1
        RP2 -.75 total.-> MP1
        RP3 -.60 total.-> MP2
    end
```

### Setup Steps

1. **Design Channel Structure**:
   * Map out partner tiers and relationships
   * Determine resource allocation strategy
   * Plan for usage reporting needs
2. **Create Organization Hierarchy**:
   * Top-level: Master partners
   * Mid-level: Regional partners
   * Leaf-level: End customers
3. **Configure Resource Limits**:
   * Set limits at each partner level
   * Limits cascade down the hierarchy
   * Most restrictive limit applies
4. **Enable Usage Tracking**:
   * Direct usage at customer level
   * Automatic aggregation up the tree
   * Partner dashboards for visibility

### Benefits

* Complete channel visibility
* Automated usage rollup
* Flexible resource allocation
* Partner-specific limits and controls

## Traditional Business

### Scenario

A mid-size company with 200 employees across Sales, Marketing, Engineering, and Operations. All departments share the same budget and resources.

### Recommended Configuration

**Billing Mode**: Single

### Implementation

```mermaid theme={null}
graph LR
    subgraph "Company Workspace"
        BA[Company Billing Account<br/>200 User Licenses<br/>Premium Features]
        
        O[Company Root]
        S[Sales: 50 users]
        M[Marketing: 30 users]
        E[Engineering: 80 users]
        OP[Operations: 40 users]
        
        BA --> O
        O --> S
        O --> M
        O --> E
        O --> OP
    end
```

### Setup Steps

1. **Create Workspace** with Single billing mode
2. **Set Up Billing**:
   * Create single billing account
   * Add payment method
   * Purchase subscription for total needs
3. **Create Departments**:
   * Create organizations for each department
   * Optionally set departmental limits
   * All draw from same resource pool

### Benefits

* Simple, unified billing
* Flexible resource sharing
* Easy to manage
* Single invoice for accounting

## Key Considerations

### Choosing the Right Model

1. **Financial Structure**
   * Unified budget → Single or Pooled mode
   * Separate budgets → Assigned mode

2. **Resource Sharing**
   * Full sharing → Single mode
   * Controlled sharing → Pooled mode
   * No sharing → Assigned mode

3. **Compliance Requirements**
   * Strict separation → Assigned mode
   * Audit trails → Any mode with proper hierarchy

4. **Scalability**
   * Plan for growth in organization structure
   * Consider future billing requirements
   * Design hierarchy for long-term needs

## What's Next?

* Deep dive into [Organization Hierarchies](/workspaces/organization-hierarchies)
* Learn about [Subscriptions and Invoicing](/workspaces/subscriptions-and-invoicing)
* Review [System Limitations](/workspaces/limitations) for planning