Chapter 15: Business Models

Introduction: The Democratization of Software

"There has been a massive change in the landscape. Rather than Big Blue IBM and Microsoft making all the big apps, it's small teams making amazing apps that scale and people love. You don't need 1,000 engineers. You need the right patterns, the right architecture, and the right business model."

The old world (1980-2010): - Software required massive teams (100+ engineers) - Sales cycles measured in years (18-24 months) - Price tags in millions ($1M-50M for enterprise software) - Only big companies could build big software - Implementation took years (3-5 year projects)

The new world (2010-present): - Small teams ship globally (2-10 engineers) - Sales cycles measured in minutes (self-service signup) - Price tags in hundreds ($10-500/month SaaS) - Anyone can build and distribute software - Implementation measured in days (cloud deployment)

What changed: - ✅ Cloud infrastructure (AWS, Azure, GCP) - No data centers needed - ✅ Open source (React, Node.js, PostgreSQL) - No license fees - ✅ SaaS distribution (web/mobile) - No installation, auto-updates - ✅ Payment platforms (Stripe, PayPal) - Collect money globally - ✅ No-code tools (Webflow, Airtable) - Lower barrier to entry

The opportunity for you:

You can build pattern-based systems that serve thousands of customers with a small team. You can compete with enterprise vendors. You can make excellent money without VC funding.

This chapter shows you how. We'll cover: 1. Business model archetypes (SaaS, consulting, hybrid, marketplace) 2. Pricing strategies (per user, per feature, per outcome) 3. Market positioning (vertical vs horizontal) 4. Hybrid model example (product + services) 5. Scaling strategies (1 customer → 1,000 customers) 6. Which model fits your situation

Section 1: Business Model Archetypes

There are four main ways to make money with pattern-based systems:

Model 1: Pure SaaS (Software as a Service)

What it is: Build once, sell many times. Monthly/annual subscriptions.

Example: Homeschool co-op management SaaS - Built once: Generic co-op management platform - Sold to: 1,000+ homeschool co-ops - Price: $50/month per co-op - Revenue: $50k/month ($600k/year) - Team: 2-3 engineers + 1 support

Pros: - ✅ Recurring revenue (predictable income) - ✅ Scales efficiently (1,000 customers on same code) - ✅ Self-service (customers sign up online) - ✅ No custom work (every customer gets same product) - ✅ High margins (90%+ gross margin)

Cons: - ❌ Slow to start (takes time to build product) - ❌ Churn risk (customers can cancel anytime) - ❌ Feature competition (must keep innovating) - ❌ Support burden (thousands of customers) - ❌ Marketing cost (must acquire customers continuously)

When to choose SaaS: - Your solution works for many customers without customization - You can self-fund initial development (6-12 months) - You're comfortable with marketing/sales - You want recurring revenue - You want to scale beyond your time

Financial model:

Year 1:
- Development: $100k (2 engineers × 6 months)
- Launch: 10 customers × $50/month = $500/month
- End of year: 100 customers = $5k/month ($60k/year)
- Burn: -$40k (investment phase)

Year 2:
- Growth: 100 → 400 customers = $20k/month ($240k/year)
- Costs: $120k (2 engineers + hosting + support)
- Profit: $120k

Year 3:
- Growth: 400 → 1,000 customers = $50k/month ($600k/year)
- Costs: $200k (3 engineers + hosting + support + marketing)
- Profit: $400k

Year 5:
- Maturity: 2,000 customers = $100k/month ($1.2M/year)
- Costs: $400k (5 engineers + infrastructure + marketing)
- Profit: $800k

Real example: Basecamp - Team: 50 people (mostly support, not engineering) - Customers: 100,000+ - Revenue: $100M+/year - Profitable since day 1 (no VC funding) - Small team, focused product, massive scale

Model 2: Pure Consulting (Custom Implementations)

What it is: Build custom solutions for each client. Time & materials or fixed-price projects.

Example: Healthcare form implementation consulting - Project: Custom patient intake system for clinic - Duration: 3 months - Price: $80k - Team: 2 consultants - Projects/year: 4 (one per quarter) - Revenue: $320k/year

Pros: - ✅ Immediate revenue (get paid for current work) - ✅ High per-project revenue ($50k-500k) - ✅ Deep client relationships (long-term partnerships) - ✅ Interesting variety (different problems each project) - ✅ Cashflow positive (payment milestones throughout project)

Cons: - ❌ Linear scaling (revenue tied to your hours) - ❌ Lumpy revenue (project ends = revenue drops) - ❌ Sales effort (must constantly find new projects) - ❌ Context switching (different codebases per client) - ❌ Support burden (maintain custom code for each client)

When to choose consulting: - You're starting with zero capital - You want immediate revenue - You enjoy variety and client work - You have domain expertise clients value - You're not ready to build a product yet

Financial model:

Year 1:
- Projects: 4 × $80k = $320k
- Costs: $160k (2 consultants × $80k)
- Profit: $160k

Year 2:
- Projects: 6 × $100k = $600k (raised prices, more clients)
- Costs: $280k (3 consultants + overhead)
- Profit: $320k

Year 3:
- Projects: 8 × $120k = $960k
- Costs: $480k (5 consultants + overhead)
- Profit: $480k

Challenge: Hard to scale beyond 5-10 people without becoming management company

Real example: Thoughtbot - Model: Ruby on Rails consulting - Team: ~50 consultants - Projects: Custom web apps for startups - Revenue: $10M+/year - Sustainable, profitable, but linear scaling

Model 3: Hybrid (Product + Services)

What it is: Sell SaaS product + implementation/customization services.

Example: Document automation platform - Product: Platform subscription ($50/user/month) - Services: Custom template creation ($5k-20k per domain) - Customers: 100 organizations - Revenue mix: 60% product, 40% services - Total revenue: $600k product + $400k services = $1M/year

Pros: - ✅ Diversified revenue (product + services) - ✅ Faster adoption (services help customers succeed) - ✅ Higher lifetime value (services upsell) - ✅ Smoother cashflow (immediate services revenue + recurring product) - ✅ Customer success (services ensure implementation success)

Cons: - ❌ Complex operations (manage both product and services teams) - ❌ Resource allocation (engineering vs consulting time) - ❌ Margins diluted (services lower overall margin) - ❌ Two sales motions (product self-service + services enterprise)

When to choose hybrid: - Your product needs customization for each customer - Customers need help implementing (complex domain) - You want recurring revenue but need immediate cashflow - You enjoy both building product and consulting - Market is willing to pay for both

Financial model:

Year 1:
- Product: 20 customers × $50/user/month × 10 users = $10k/month
- Services: 10 implementation projects × $10k = $100k
- Total: $220k
- Costs: $150k (2 engineers + 1 consultant)
- Profit: $70k

Year 2:
- Product: 60 customers × $50/user/month × 10 users = $30k/month = $360k
- Services: 20 projects × $12k = $240k
- Total: $600k
- Costs: $320k (3 engineers + 2 consultants)
- Profit: $280k

Year 3:
- Product: 120 customers = $60k/month = $720k
- Services: 30 projects × $15k = $450k
- Total: $1.17M
- Costs: $550k (4 engineers + 3 consultants + ops)
- Profit: $620k

Year 5:
- Product: 300 customers = $150k/month = $1.8M
- Services: 40 projects × $20k = $800k
- Total: $2.6M
- Costs: $1.2M (8 engineers + 5 consultants + ops)
- Profit: $1.4M

Real example: Salesforce (early days) - Product: CRM platform (monthly subscription) - Services: Implementation partners (setup, customization) - Model: Both drove each other (services helped adoption, product enabled scale) - Eventually: Product dominated, but services remained strategic

A proven platform approach: - Platform: One codebase serves all domains - Templates: Custom per customer (homeschool, legal, healthcare) - Revenue: Monthly licensing + setup fees - Scale: Same platform, different configurations

Model 4: Marketplace (Platform Connecting Buyers/Sellers)

What it is: Build platform where others sell solutions built on your patterns.

Example: Form builder marketplace - Platform: Form builder with pattern library - Developers: Build domain-specific solutions (healthcare forms, legal forms) - Customers: Buy ready-made solutions from marketplace - Revenue: 20-30% commission on transactions

Pros: - ✅ Network effects (more developers = more solutions = more customers) - ✅ Scales exponentially (others build solutions) - ✅ Low marginal cost (platform supports many solutions) - ✅ High margins (30% of transactions) - ✅ Community-driven (developers promote platform)

Cons: - ❌ Chicken-egg problem (need developers AND customers) - ❌ Quality control (developers vary in skill) - ❌ Complex platform (must support developer tools) - ❌ Long time to market (build platform + recruit developers) - ❌ High initial investment (12-24 months to launch)

When to choose marketplace: - You have funding or can self-fund 12-24 months - You want exponential scale - You're good at building communities - You can attract developer ecosystem - Your patterns are broadly applicable

Financial model:

Year 1-2: Build platform + recruit developers
- Investment: $500k (team of 4 × 18 months)
- Developers: 20 building solutions
- Revenue: Minimal (early transactions)

Year 3: Launch and grow
- Developers: 100 active
- Solutions: 500 in marketplace
- Transactions: $1M GMV (gross merchandise value)
- Revenue: $300k (30% commission)
- Costs: $400k (5 engineers)
- Loss: -$100k (still investing)

Year 5: Scale
- Developers: 500 active
- Solutions: 5,000 in marketplace
- Transactions: $20M GMV
- Revenue: $6M (30% commission)
- Costs: $2M (15 engineers + ops)
- Profit: $4M

Year 10: Mature
- Developers: 2,000 active
- Solutions: 25,000 in marketplace
- Transactions: $200M GMV
- Revenue: $60M (30% commission)
- Costs: $15M (50 engineers + ops + marketing)
- Profit: $45M

Real example: Shopify - Platform: E-commerce system - Developers: 8,000+ building apps and themes - Merchants: 2M+ stores - Revenue: Subscriptions + app commissions + payment processing - Scale: One of largest e-commerce platforms globally

Section 2: Pricing Strategies

How you price matters as much as what you build.

Strategy 1: Per-User Pricing

How it works: Charge based on number of users accessing system.

Examples: - Slack: $8/user/month - GitHub: $4/user/month - Your permit system: $25/user/month

Pros: - ✅ Scales with customer value (more users = more value) - ✅ Simple to understand (everyone gets this model) - ✅ Predictable (count users = know price) - ✅ Aligns incentives (you want them to add users)

Cons: - ❌ Limits adoption (customers hesitate to add users due to cost) - ❌ Seat optimization (customers share logins to avoid paying) - ❌ Doesn't capture value for high-usage small teams

When to use: - Your software is used by teams (multiple people) - Value scales with number of users - Usage per user is relatively similar

Pricing tiers:

Starter: $25/user/month
- Up to 10 users
- Basic features
- Email support

Professional: $50/user/month
- 11-50 users
- Advanced features
- Priority support
- API access

Enterprise: Custom pricing
- 50+ users
- All features
- Dedicated support
- SLA guarantees
- Custom integrations

Strategy 2: Tiered Feature Pricing

How it works: Different tiers unlock different features.

Example: Permit management system

Basic ($99/month):
- Online permit applications
- Basic workflow
- Standard reports

Professional ($299/month):
- Everything in Basic
- Advanced workflows
- Custom reports
- API access
- Integrations (GIS, payment)

Enterprise ($799/month):
- Everything in Professional
- Multi-department
- Custom branding
- Dedicated support
- SLA guarantees

Pros: - ✅ Captures different customer segments - ✅ Clear upgrade path (feature motivation) - ✅ Revenue expansion (customers upgrade over time) - ✅ Predictable (flat fee per tier)

Cons: - ❌ Feature gatekeeping (frustrates customers) - ❌ Complex to position (which features in which tier?) - ❌ Doesn't scale with usage

When to use: - Clear feature differentiation between segments - Some features much more valuable to certain customers - Customers prefer predictable pricing

Strategy 3: Usage-Based Pricing

How it works: Pay for what you use (per form, per document, per transaction).

Example: Document generation system

Starter: $0/month + $0.10/document
- Pay only for what you generate
- Up to 1,000 documents/month

Growth: $50/month + $0.05/document
- Lower per-document cost
- Up to 10,000 documents/month

Enterprise: $500/month + $0.01/document
- Lowest per-document cost
- Unlimited documents

Pros: - ✅ Aligns with value (high usage = high value = high price) - ✅ Low barrier to entry (start for $0 or very low cost) - ✅ Scales naturally (usage grows with customer success) - ✅ Fair (pay for actual use, not potential)

Cons: - ❌ Unpredictable revenue (usage varies month to month) - ❌ Customer uncertainty (hard to budget) - ❌ Complex billing (track and charge for usage) - ❌ Can limit adoption (worry about costs)

When to use: - Usage highly variable between customers - Marginal cost per transaction is significant - Customers prefer pay-as-you-go

Application example: Document platforms can charge per document generated.

Strategy 4: Outcome-Based Pricing

How it works: Charge based on value delivered, not features or usage.

Example: Permit approval acceleration

Traditional: $299/month (flat fee)

Outcome-based:
- Baseline: Current approval time is 10 days
- Promise: Reduce to 2 days
- Pricing: $5,000/month based on value of:
  - Faster projects = economic growth
  - Fewer staff hours = cost savings
  - Better citizen satisfaction = political value

Pros: - ✅ Premium pricing (charge based on value, not cost) - ✅ Aligns incentives (you succeed when customer succeeds) - ✅ Differentiation (most competitors price on features) - ✅ Customer success focus (must deliver outcomes)

Cons: - ❌ Hard to measure (define "success") - ❌ Complex to sell (requires ROI justification) - ❌ Risk (if outcomes not achieved, pricing pressure) - ❌ Long sales cycle (enterprise buying process)

When to use: - Clear, measurable outcomes - High-value use cases (enterprise) - You're confident in delivering results - Market sophisticated enough to buy on value

Example ROI calculation:

City permit department:
- Current: 10,000 permits/year × 10 days = 100,000 days of projects delayed
- With system: 10,000 permits/year × 2 days = 20,000 days
- Improvement: 80,000 days saved
- Economic value: $500/day per project (conservative) × 80,000 = $40M/year

Your pricing: $60k/year (0.15% of value created)
Customer saves: $39.94M/year
ROI: 666x

Hard to say no to this deal!

Strategy 5: Freemium

How it works: Free tier to acquire users, paid tiers for premium features.

Example: Form builder

Free:
- 1 form
- 100 submissions/month
- Basic features
- Community support

Pro ($29/month):
- Unlimited forms
- 10,000 submissions/month
- Advanced features
- Email support

Business ($99/month):
- Everything in Pro
- 100,000 submissions/month
- Team collaboration
- Priority support
- Remove branding

Pros: - ✅ Viral growth (free users share, invite others) - ✅ Try before buy (reduces sales friction) - ✅ Land and expand (free → paid over time) - ✅ Large user base (good for network effects)

Cons: - ❌ Low conversion (2-5% free to paid typical) - ❌ Support burden (free users need support too) - ❌ Infrastructure cost (free users cost money) - ❌ Slow to revenue (takes time to convert)

When to use: - Low marginal cost per user - Network effects or viral growth - Can afford to support free users - Clear upgrade path (free users hit limits naturally)

Conversion math:

Month 1: 1,000 free users, 20 paid (2%) = $580/month
Month 6: 10,000 free users, 300 paid (3%) = $8,700/month
Month 12: 50,000 free users, 2,000 paid (4%) = $58,000/month
Month 24: 200,000 free users, 10,000 paid (5%) = $290,000/month

Key: Conversion rate typically improves over time (users grow into limits)

Section 3: Market Positioning

Vertical (deep) vs Horizontal (wide) is a critical choice.

Vertical SaaS (Industry-Specific)

What it is: Build for ONE specific industry. Go deep.

Examples: - Homeschool co-op management (only homeschools) - Dental practice management (only dentists) - Auto repair shop software (only auto repair)

Document platform example: Pick ONE vertical (e.g., homeschool co-ops), become THE solution for that vertical.

Pros: - ✅ Focused product (solve industry-specific problems deeply) - ✅ Domain expertise (you become THE expert in this industry) - ✅ Less competition (most competitors are horizontal) - ✅ Higher prices (specialized = premium pricing) - ✅ Better retention (switching cost high, you understand industry) - ✅ Word-of-mouth (everyone in industry knows each other)

Cons: - ❌ Limited TAM (total addressable market is one industry) - ❌ Industry risk (what if industry declines?) - ❌ Feature expectations (must build ALL features industry needs) - ❌ Slower growth (can't expand to other industries easily)

When to choose vertical: - You have deep domain expertise in an industry - Industry is underserved (still using Excel, paper) - Industry is large enough (10,000+ potential customers) - You want to be the #1 player in a niche - You prefer depth over breadth

Example: Vetstoria (veterinary practice management) - Vertical: Only veterinary clinics - Customers: 5,000+ clinics - Pricing: $200-500/month per clinic - Features: Appointment scheduling, medical records, billing, inventory (all vet-specific) - Competition: Limited (most practice management is horizontal) - Result: Dominant player in vet industry

Market sizing:

Homeschool co-ops in US:
- Total homeschool families: 2.5M
- Families in co-ops: ~500k (20%)
- Average co-op size: 50 families
- Number of co-ops: 10,000

TAM (Total Addressable Market):
- 10,000 co-ops × $50/month = $500k/month = $6M/year

If you capture 10%: $600k/year
If you capture 20%: $1.2M/year
If you capture 50%: $3M/year (market leader)

Horizontal SaaS (Cross-Industry)

What it is: Build for MANY industries. Go wide.

Examples: - Stripe (payments for everyone) - Slack (team communication for everyone) - Monday.com (project management for everyone)

Document platform example: Horizontal platform (serves homeschool, legal, healthcare, any document domain).

Pros: - ✅ Huge TAM (every industry is potential customer) - ✅ Diversified risk (not dependent on one industry) - ✅ Faster growth (more industries = more opportunities) - ✅ Network effects (different industries cross-pollinate) - ✅ Exit opportunities (horizontal platforms worth more)

Cons: - ❌ Feature bloat (every industry wants different features) - ❌ Tough competition (competing with large horizontal players) - ❌ Generic positioning (hard to stand out) - ❌ Lower prices (can't charge premium for specialization) - ❌ Harder sales (must explain value to many different industries)

When to choose horizontal: - Your solution is truly cross-industry (patterns that apply everywhere) - You want maximum growth potential - You have capital to compete in broad market - You don't have deep expertise in any single industry - You want to build a "big" company

Example: Airtable - Horizontal: Serves all industries - Use cases: Project management, CRM, inventory, recruiting, anything - Customers: 300,000+ across all industries - Pricing: $10-20/user/month - Competition: Intense (Notion, Monday, Asana, Smartsheet, etc.) - Result: $11B valuation (horizontal scales bigger)

The Hybrid Approach: Start Vertical, Expand Horizontal

Best of both worlds: Start focused, expand carefully.

Strategy: 1. Year 1-2: Pick ONE vertical (e.g., homeschool co-ops) - Become THE solution for that industry - Build deep feature set - Capture 20-30% market share

Year 3-4: Expand to SIMILAR vertical (e.g., youth sports leagues)
Leverage existing platform
Add vertical-specific features
Cross-sell between industries
Year 5+: Platform play (generalized tool)
Abstract common patterns
Verticalized templates
Multiple industries on one platform

Example: Toast (restaurant POS) - Started: Quick-service restaurants only - Expanded: Fine dining, bars, cafes - Platform: Now serves all food service - Revenue: $1B+

Document platform strategic path: - Start: Horizontal (any document domain) - Alternative: Pick ONE vertical (homeschool co-ops) - Dominate that vertical first - Then expand to other document-heavy industries

Section 4: Example Business Model Analysis

Let's analyze a practical document automation platform approach:

Current Model (Hybrid Horizontal Platform)

Product: - Document automation platform (DataPublisher) - Runs in Microsoft Word as task pane add-in - Imports data from CSV, databases, APIs - Generates documents in bulk - Works for any document domain

Revenue streams: 1. Platform licensing: Per-user/per-organization fees 2. Template creation: Custom templates for each customer domain 3. Implementation services: Setup, training, support

Customers: - Homeschool co-ops (DataPublisher for Coop School) - Potentially: Legal firms, healthcare clinics, any document-heavy organization

Strengths: - ✅ One codebase serves many domains (efficient) - ✅ Leverages Microsoft Word (familiar tool, no new UI to build) - ✅ Flexible (any data source, any document format) - ✅ Multiple revenue streams (product + services)

Opportunities: 1. Verticalize: Pick ONE domain (homeschool co-ops), dominate it 2. Productize templates: Pre-built template library for common use cases 3. Marketplace: Let others build/sell templates on your platform 4. Recurring revenue: Shift from one-time to monthly subscription

Optimization Path 1: Vertical SaaS (Homeschool Focus)

Strategy: Become THE homeschool co-op management platform.

Product positioning: - "Coop School Manager" (not "DataPublisher") - Built specifically for homeschool co-ops - All features co-ops need (not just documents)

Features (in priority order): 1. Document automation (enrollment forms, transcripts, attendance) - Your current strength 2. Enrollment management (student roster, family info) 3. Class scheduling (courses, teachers, rooms) 4. Attendance tracking (check-in, absences) 5. Communication (email blasts, newsletters) 6. Payment processing (tuition, fees) 7. Volunteer coordination (signups, tracking)

Pricing:

Basic: $50/month (up to 50 families)
- Document automation (unlimited)
- Student roster
- Class scheduling
- Attendance tracking

Pro: $99/month (up to 150 families)
- Everything in Basic
- Payment processing
- Email communication
- Volunteer management

Enterprise: $199/month (150+ families)
- Everything in Pro
- Multiple locations
- Custom templates
- Priority support
- Phone support

Go-to-market: 1. Initial customers: Leverage your existing homeschool network 2. Content marketing: Blog posts on running successful co-ops 3. Facebook groups: Homeschool co-op Facebook groups (thousands exist) 4. Partnerships: Homeschool curriculum providers 5. Word-of-mouth: Co-op coordinators talk to each other

Financial projection:

Year 1:
- Customers: 50 co-ops × $75 avg = $3,750/month = $45k/year
- Costs: $60k (you + 1 developer part-time)
- Loss: -$15k (investment phase)

Year 2:
- Customers: 200 co-ops × $80 avg = $16k/month = $192k/year
- Costs: $120k (you + 1 developer full-time)
- Profit: $72k

Year 3:
- Customers: 500 co-ops × $85 avg = $42.5k/month = $510k/year
- Costs: $200k (you + 2 developers)
- Profit: $310k

Year 5:
- Customers: 1,000 co-ops (10% market share) × $90 avg = $90k/month = $1.08M/year
- Costs: $400k (you + 3 developers + support)
- Profit: $680k

Optimization Path 2: Marketplace Platform

Strategy: Build the "Shopify for documents" - let others build vertical solutions on your platform.

Platform offering: - Document automation engine (your DataPublisher core) - Template builder (visual editor) - Integration marketplace (data sources) - Distribution (host customer instances)

Developer offering: - SDK for building vertical solutions - Template marketplace (sell templates) - Revenue share (70/30 split)

Customer offering: - Browse vertical solutions (homeschool, legal, healthcare) - One-click deploy - Monthly subscription - Support from solution provider

Example marketplace solutions: - "Coop School Manager" (your solution) - $50/month - "Legal Case Intake" (another developer) - $99/month - "Patient Forms Generator" (another developer) - $75/month - "Real Estate Documents" (another developer) - $60/month

Revenue model:

Platform fee: $10/month per customer (base platform)
Solution fee: 30% of solution price

Example:
- Customer subscribes to "Coop School Manager" at $50/month
- Platform revenue: $10 (base) + $15 (30% of $50) = $25/month
- Developer revenue: $35/month

Financial projection:

Year 1-2: Build platform + recruit developers
- Investment: $200k (team of 2-3 × 18 months)
- Developers: 10 building solutions
- Customers: 100 (early adopters)
- Revenue: $2,500/month = $30k/year
- Loss: -$170k (investment phase)

Year 3: Growth
- Developers: 50 active
- Solutions: 100 in marketplace
- Customers: 1,000 across all solutions
- Revenue: $25k/month = $300k/year
- Costs: $250k (team of 4)
- Profit: $50k (approaching breakeven)

Year 5: Scale
- Developers: 200 active
- Solutions: 500 in marketplace
- Customers: 10,000 across all solutions
- Revenue: $250k/month = $3M/year
- Costs: $1M (team of 12 + ops)
- Profit: $2M

This is the highest-risk, highest-reward path.

Section 5: Scaling Strategies

How do you grow from 1 customer to 1,000?

Stage 1: Manual (1-10 customers)

What you're doing: - Selling one-on-one (personal outreach) - Manually onboarding each customer - Custom building for each customer - You do everything (sales, development, support)

Goal: Prove product-market fit. Do things that don't scale.

Time investment: 40+ hours per customer (sales + implementation)

At this stage: Each customer requires significant manual effort.

Stage 2: Semi-Automated (10-100 customers)

What changes: - Self-service signup (website with pricing) - Automated onboarding (email sequences, video tutorials) - Productized offering (no more custom builds) - Hire first support person

Goal: Repeatability. Same process for every customer.

Time investment: 5-10 hours per customer (mostly support, minimal sales)

Key milestone: First customer signs up without talking to you.

Stage 3: Automated (100-1,000 customers)

What changes: - Inbound marketing (content, SEO, ads) - Self-service everything (customers never talk to you) - Automated support (help center, chatbot, then human) - Team of 5-10 (engineering, support, marketing)

Goal: Leverage. System runs without you.

Time investment: <1 hour per customer (automated onboarding, only support escalations)

Key milestone: You can take a vacation and company keeps running.

Stage 4: Platform (1,000-10,000+ customers)

What changes: - Ecosystem (partners, integrations, marketplace) - Community (user groups, conferences, certification) - Enterprise (dedicated sales, custom contracts) - Team of 20-50+ (departments, specialized roles)

Goal: Market leadership. You define the category.

Time investment: Minimal (delegated to team)

Key milestone: Competitors position against you ("We're like [you], but for...")

Section 6: Which Model Fits You?

Decision framework:

Choose Pure SaaS if:

[ ] You have 6-12 months of runway (savings or revenue)
[ ] You want recurring revenue and scale
[ ] You're comfortable with marketing/sales
[ ] Your solution is horizontal (works for many without customization)
[ ] You want to build a "big" company (10+ employees)

Choose Pure Consulting if:

[ ] You need revenue immediately
[ ] You have deep domain expertise clients value
[ ] You enjoy variety (different projects)
[ ] You're not ready to build a product yet
[ ] You want lifestyle business (just you, or small team)

Choose Hybrid if:

[ ] You want both immediate revenue and recurring revenue
[ ] Your solution needs customization per customer
[ ] You enjoy both product and consulting
[ ] Your market is willing to pay for both
[ ] You want flexibility (can pivot between product/services mix)

Choose Marketplace if:

[ ] You have 12-24 months of runway
[ ] You want exponential scale
[ ] You can attract developer ecosystem
[ ] Your patterns are broadly applicable
[ ] You want to build a "huge" company (50+ employees)

For Document Platform Builders:

Typical situation: - Existing product platform - Multiple potential verticals (homeschool, legal, healthcare) - Hybrid model (product + services) - Small team (1-3 people)

Recommended path:

Option A: Vertical SaaS (lower risk, faster to profit) 1. Pick ONE vertical (homeschool co-ops - you have domain expertise) 2. Rebrand as vertical-specific ("Coop School Manager") 3. Build out vertical features (beyond just documents) 4. Charge monthly subscription ($50-99/month) 5. Capture 10-20% of market (1,000-2,000 co-ops) 6. Revenue target: $500k-1M/year 7. Team: 3-5 people 8. Lifestyle business or growth business (your choice)

Option B: Horizontal Platform (higher risk, bigger upside) 1. Keep horizontal platform (DataPublisher) 2. Build marketplace for templates 3. Recruit developers to build vertical solutions 4. Revenue share model 5. Capture many verticals (100+ niches) 6. Revenue target: $3-10M/year (5-year goal) 7. Team: 10-20 people 8. Venture-scale business

My recommendation: Option A first, Option B later.

Start vertical (co-ops), dominate it, then expand. Vertical gives you cash flow, customer base, and proof. Then you can fund horizontal expansion.

Conclusion: Small Teams, Big Impact

The landscape has changed: - You don't need 1,000 engineers to build transformative software - You don't need $10M in VC funding to reach customers globally - You don't need 5-year projects to see revenue

What you need: - The right patterns (this book provides them) - The right architecture (Chapter 13) - The right migration strategy (Chapter 14) - The right business model (this chapter)

Small teams are winning: - Basecamp: 50 people, $100M revenue - Notion: Started with 3 people, now $10B valuation - Mailchimp: Bootstrapped to $700M revenue, sold for $12B - Plenty of Fish: ONE person built, grew to $10M/year revenue, sold for $575M

You can do this too.

Pick your model. Start building. Ship to customers. Iterate. Scale.

The software industry has proven it: From text-based terminals to modern document automation. From one customer to many. From one domain to multiple.

Your journey starts now. 🚀

Next chapter: Sales & ROI (how to sell pattern-based systems and prove value).

Chapter 15: Business Models

Introduction: The Democratization of Software

Section 1: Business Model Archetypes

Model 1: Pure SaaS (Software as a Service)

Model 2: Pure Consulting (Custom Implementations)

Model 3: Hybrid (Product + Services)

Model 4: Marketplace (Platform Connecting Buyers/Sellers)

Section 2: Pricing Strategies

Strategy 1: Per-User Pricing

Strategy 2: Tiered Feature Pricing

Strategy 3: Usage-Based Pricing

Strategy 4: Outcome-Based Pricing

Strategy 5: Freemium

Section 3: Market Positioning

Vertical SaaS (Industry-Specific)

Horizontal SaaS (Cross-Industry)

The Hybrid Approach: Start Vertical, Expand Horizontal

Section 4: Example Business Model Analysis

Current Model (Hybrid Horizontal Platform)

Optimization Path 1: Vertical SaaS (Homeschool Focus)

Optimization Path 2: Marketplace Platform

Section 5: Scaling Strategies

Stage 1: Manual (1-10 customers)

Stage 2: Semi-Automated (10-100 customers)

Stage 3: Automated (100-1,000 customers)

Stage 4: Platform (1,000-10,000+ customers)

Section 6: Which Model Fits You?

Choose Pure SaaS if:

Choose Pure Consulting if:

Choose Hybrid if:

Choose Marketplace if:

For Document Platform Builders:

Conclusion: Small Teams, Big Impact

Further Reading

Business Model Innovation

SaaS Business Models

Professional Services

Open Source Business Models

Marketplace Platforms

Freemium Models

Financial Planning

Sales and Marketing

Legal and Contracts

Related Trilogy Content