---
# === IDENTITY ===
id: business/customer-success/support-infrastructure-setup/2026
canonical_question: "How do I set up support infrastructure — Intercom vs Zendesk vs Linear, SLA design, self-service KB, scaling triggers?"
aliases:
  - "Customer support infrastructure setup 2026"
  - "Intercom vs Zendesk comparison and setup"
  - "SLA design and self-service knowledge base builder"
entity_type: execution_recipe
domain: business > customer-success > support-infrastructure-setup
region: global
jurisdiction: global
temporal_scope: 2025-2026

# === VERIFICATION ===
last_verified: 2026-03-12
confidence: 0.88
version: 1.0
first_published: 2026-03-12

# === TEMPORAL VALIDITY ===
temporal_validity:
  status: evolving
  last_breaking_change: "Intercom shifted to $0.99/resolution AI pricing model in 2024, fundamentally changing cost calculations for high-volume teams"
  next_review: 2026-09-08
  change_sensitivity: high

# === CONSTRAINTS ===
constraints:
  - "Platform migration after 6+ months of data accumulation costs 40-120 hours of engineering time — choose carefully upfront"
  - "SLA timers only count business hours unless explicitly configured for 24/7 — verify timezone and schedule settings before launch"
  - "Self-service KB requires minimum 30-50 articles to achieve measurable ticket deflection — do not launch with fewer than 20"
  - "AI-powered features (Intercom Fin, Zendesk AI) add $0.99-$50/agent/month on top of base pricing"
  - "GDPR compliance requires data processing agreements with all support platform vendors before handling EU customer data"

# === SKIP CONDITIONS ===
skip_this_unit_if:
  - condition: "User needs a customer success strategy, not infrastructure setup"
    use_instead: "business/customer-success/customer-success-model-selection/2026"
  - condition: "User already has support infrastructure and needs to optimize SLA performance"
    use_instead: "Search knowledgelib.io for support SLA optimization — no dedicated unit yet"
  - condition: "User has 500+ agents and needs enterprise contact center platform"
    use_instead: "Search knowledgelib.io for enterprise contact center platforms — no dedicated unit yet"

# === AGENT HINTS ===
inputs_needed:
  - key: platform_preference
    question: "Which support platform should be used?"
    type: choice
    options: ["Intercom", "Zendesk", "Freshdesk", "Help Scout", "no preference — auto-select"]
  - key: team_size
    question: "How many support agents will use the platform?"
    type: choice
    options: ["solo founder (1)", "small team (2-5)", "growing team (6-20)", "large team (20+)"]
  - key: budget_for_tools
    question: "What's the monthly support tooling budget?"
    type: choice
    options: ["free tier only", "up to $100/month", "up to $500/month", "$500+/month"]
  - key: ticket_volume
    question: "Expected monthly ticket volume?"
    type: choice
    options: ["under 200/month", "200-1000/month", "1000-5000/month", "5000+/month"]

# === EXECUTION METADATA ===
execution:
  required_inputs:
    - name: "Product/service description"
      source: "founder or product team"
      format: "document"
    - name: "Target customer segments"
      source: "business/customer-success/cs-program-design or founder"
      format: "structured data"
    - name: "Team size and budget constraints"
      source: "founder or operations lead"
      format: "structured data"

  outputs:
    - name: "Configured support platform"
      format: "configured platform"
      description: "Live helpdesk with ticketing, routing, and SLA rules ready for production use"
    - name: "SLA policy document"
      format: "document"
      description: "Tiered SLA definitions with response and resolution time targets per priority level"
    - name: "Self-service knowledge base"
      format: "deployed URL"
      description: "Customer-facing KB with 20+ articles covering top contact reasons"
    - name: "Escalation matrix"
      format: "document"
      description: "Routing rules and escalation paths by issue type and severity"

  tools_required:
    - name: "Intercom"
      purpose: "Unified helpdesk with live chat, ticketing, and AI resolution"
      tier: "paid"
      cost: "$29-139/seat/month + $0.99/AI resolution"
      alternatives: ["Zendesk", "Freshdesk", "Help Scout"]
    - name: "Zendesk"
      purpose: "Enterprise-grade ticketing with advanced routing and analytics"
      tier: "paid"
      cost: "$19-169/agent/month + $50/agent for Advanced AI"
      alternatives: ["Intercom", "Freshdesk"]
    - name: "Freshdesk"
      purpose: "Cost-effective helpdesk with strong automation"
      tier: "freemium"
      cost: "$0-79/agent/month"
      alternatives: ["Zendesk", "Help Scout"]
    - name: "Help Scout"
      purpose: "Simple shared inbox with integrated knowledge base"
      tier: "freemium"
      cost: "$0-65/user/month"
      alternatives: ["Freshdesk", "Groove"]

  credentials_needed:
    - service: "Chosen support platform"
      type: "username+password"
      where_to_get: "Platform signup page"
      free_tier_limits: "Freshdesk: 2 agents free; Help Scout: 1 user free; Zendesk/Intercom: 14-day trial only"
    - service: "Email provider (for support@ address)"
      type: "SMTP/IMAP credentials or forwarding"
      where_to_get: "Google Workspace, Microsoft 365, or domain registrar"
      free_tier_limits: "Most domains include email forwarding for free"

  estimated_duration: "2-5 days for full setup (platform + SLA + KB + routing)"
  estimated_cost: "$0 (Freshdesk free) to $500+/month (Zendesk Enterprise with AI)"

# === DISTRIBUTION ===
canonical_source: "https://knowledgelib.io/business/customer-success/support-infrastructure-setup/2026"
suggested_citation: "Source: knowledgelib.io — AI Knowledge Library (verified 2026-03-12)"

# === RELATED UNITS ===
related_kos:
  depends_on:
    - id: "business/customer-success/customer-success-model-selection/2026"
      label: "Choosing a CS coverage model — high-touch vs tech-touch vs hybrid by ACV tier, CSM-to-account ratios and capacity plan (the coverage decision, not a full CS program design)"
  related_to:
    - id: "business/customer-success/customer-onboarding-design-playbook/2026"
      label: "Customer onboarding program design — first 7/30/90 days, activation milestones, first-session activation"

# === SOURCES ===
sources:
  - id: src1
    title: "Intercom Pricing Plans"
    author: Intercom
    url: https://www.intercom.com/pricing
    type: official_docs
    published: 2025-01-01
    reliability: authoritative
  - id: src2
    title: "Zendesk Pricing Plans"
    author: Zendesk
    url: https://www.zendesk.com/pricing/
    type: official_docs
    published: 2025-01-01
    reliability: authoritative
  - id: src3
    title: "Freshdesk vs Zendesk Comparison"
    author: Freshworks
    url: https://www.freshworks.com/freshdesk/compare-helpdesks/zendesk-vs-freshdesk/
    type: vendor_comparison
    published: 2025-01-01
    reliability: established
  - id: src4
    title: "SLA Best Practices: How to Set and Manage Customer Expectations"
    author: Pylon
    url: https://www.usepylon.com/blog/sla-best-practices
    type: industry_guide
    published: 2025-06-01
    reliability: established
  - id: src5
    title: "Customer Support Department Size Benchmarks"
    author: CompanySights
    url: https://www.companysights.com/resources/customer-support-department-size-benchmarks-how-many-people-do-you-really-need
    type: research
    published: 2025-01-01
    reliability: established
  - id: src6
    title: "How to Create a Self-Service Knowledge Base: 2025 Guide"
    author: ProProfs
    url: https://www.proprofskb.com/blog/self-service-knowledge-base/
    type: industry_guide
    published: 2025-01-01
    reliability: established
---

# Support Infrastructure Setup: Platform Selection, SLA Design & Self-Service KB

## Purpose

This recipe produces a fully operational customer support infrastructure — configured helpdesk platform with ticketing workflows, tiered SLA policies with escalation rules, a self-service knowledge base with 20+ launch articles, and analytics dashboards tracking resolution time, CSAT, and deflection rate. The output is a production-ready support system that handles customer inquiries from first contact through resolution. [src4]

## Prerequisites
<!-- Agents: verify ALL prerequisites before executing. Missing prerequisites = failed execution. -->

- [ ] **Product/service description** available from founder or product team — needed to write KB articles and configure ticket categories
- [ ] **Customer segment definitions** — who contacts support, through which channels, with what types of issues
- [ ] **Support email address** — dedicated support@yourdomain.com configured with SMTP forwarding
- [ ] **Team member list** — names, emails, and roles for all agents who need platform access
- [ ] **Budget approval** — monthly tooling budget confirmed (see Cost Breakdown below)

## Constraints
<!-- Hard rules. Agents: enforce throughout execution. Violating these = broken output or legal risk. -->

- Platform migration after 6+ months costs 40-120 hours of engineering time. Choose the right platform upfront based on 18-month projected needs, not just current state. [src3]
- SLA timers count business hours by default. Configure timezone and business-hours schedule before activating any SLA policies. [src4]
- Self-service KB needs minimum 20 articles at launch to achieve measurable ticket deflection. Plan content creation time into the schedule. [src6]
- AI resolution costs ($0.99/resolution on Intercom Fin) can exceed $5,000/month at high volume. Model expected volume before enabling. [src1]
- GDPR: execute Data Processing Agreements with platform vendor before onboarding any EU customer data.

## Tool Selection Decision

<!-- Agent selects the right tool path based on user inputs.
     Each path leads to a different execution flow below. -->

```
Which path?
├── Budget = free AND team = 1-2 agents
│   └── PATH A: Freshdesk Free — 2-agent free tier with basic ticketing + KB
├── Budget < $200/month AND team = 2-10 agents
│   └── PATH B: Freshdesk Growth or Help Scout — $15-29/agent with automation
├── Chat-first SaaS AND budget $200-1000/month
│   └── PATH C: Intercom — live chat + AI resolution + in-app messaging
└── Enterprise needs OR 20+ agents OR complex routing
    └── PATH D: Zendesk Suite — advanced workflows, skills-based routing, HIPAA
```

| Path | Tools | Cost | Setup Time | Best For |
|------|-------|------|------------|----------|
| A: Free Tier | Freshdesk Free | $0 | 1-2 days | Solo founders, pre-revenue startups |
| B: SMB Growth | Freshdesk Growth / Help Scout | $15-29/agent/mo | 2-3 days | Seed-Series A, 200-1000 tickets/mo |
| C: Chat-First SaaS | Intercom Advanced | $85/seat/mo + $0.99/AI resolution | 3-5 days | Product-led SaaS, in-app support |
| D: Enterprise | Zendesk Suite Professional | $115/agent/mo + $50 AI add-on | 5-10 days | Series B+, 20+ agents, compliance needs |

## Execution Flow

### Step 1: Choose Platform and Create Account

**Duration**: 1-2 hours
**Tool**: Selected platform (see Tool Selection Decision)

Evaluate your position in the decision tree above. Key decision factors in priority order:

1. **Channel mix**: If >60% of support is in-app chat, choose Intercom. If primarily email/form-based, choose Freshdesk or Zendesk.
2. **Budget**: Freshdesk free tier supports 2 agents with basic ticketing. Help Scout free supports 1 user. Zendesk and Intercom require paid plans.
3. **Scale trajectory**: If you expect to exceed 20 agents within 12 months, start with Zendesk to avoid migration. [src2]
4. **Compliance**: HIPAA required? Zendesk Suite Professional ($115/agent) or Zendesk Suite Enterprise ($169/agent). [src2]

Create the account, add your support email domain, and invite team members with appropriate roles (admin vs agent).

**Verify**: All team members can log in, support email forwards to platform inbox, test ticket received.
**If failed**: Check DNS/MX records for email forwarding. Most platforms provide a platform-specific forwarding address as fallback.

### Step 2: Configure Ticket Categories and Routing

**Duration**: 2-4 hours
**Tool**: Platform admin panel

Define ticket categories based on your top contact reasons. Start with 5-8 categories maximum:

```
Ticket Categories (example for SaaS):
├── Billing & Payments
│   ├── Refund request
│   ├── Invoice question
│   └── Plan change
├── Technical Issue
│   ├── Bug report
│   ├── Integration problem
│   └── Performance issue
├── Account Management
│   ├── Password reset
│   ├── Account access
│   └── Data export
├── Feature Request
├── Onboarding Help
└── General Question
```

Configure auto-routing rules:
- Billing tickets route to billing-trained agents or finance team
- Technical issues route to technical support / engineering escalation
- Feature requests auto-tag and route to product feedback channel

Set priority levels: P1 (critical — service down), P2 (high — degraded functionality), P3 (medium — inconvenience), P4 (low — question/request).

**Verify**: Submit test tickets in each category. Confirm they route to correct agent/group and display correct priority.
**If failed**: Check routing rule order — most platforms evaluate rules top-down and stop at first match.

### Step 3: Design and Implement SLA Tiers

**Duration**: 2-3 hours
**Tool**: Platform SLA configuration

Create SLA policies tied to priority levels. Industry-standard benchmarks: [src4] [src5]

```
SLA Tier Matrix:
┌──────────┬──────────────────┬──────────────────┬──────────────┐
│ Priority │ First Response   │ Next Response    │ Resolution   │
├──────────┼──────────────────┼──────────────────┼──────────────┤
│ P1       │ 15 min (24/7)    │ 30 min           │ 4 hours      │
│ P2       │ 1 hour (biz hrs) │ 2 hours          │ 8 hours      │
│ P3       │ 4 hours          │ 8 hours          │ 24 hours     │
│ P4       │ 8 hours          │ 24 hours         │ 72 hours     │
└──────────┴──────────────────┴──────────────────┴──────────────┘

Premium/Enterprise customer overlay:
- P1: 5 min first response, 2 hour resolution
- P2: 30 min first response, 4 hour resolution
```

Configure SLA breach notifications:
- At 75% of SLA time: warning to assigned agent
- At 90% of SLA time: escalation to team lead
- At 100% (breach): alert to support manager + auto-reassign to senior agent

**Verify**: Create test tickets at each priority level. Confirm SLA timers start correctly and breach notifications fire at configured thresholds.
**If failed**: Verify business hours calendar is set correctly. SLA timers pause outside business hours unless configured for 24/7.

### Step 4: Build Self-Service Knowledge Base

**Duration**: 2-5 days (content creation is the bottleneck)
**Tool**: Platform KB module or standalone (Notion, GitBook, ReadMe)

Structure the KB around top contact reasons. Analyze your first 100-200 tickets (or anticipated questions) and group into categories: [src6]

```
Knowledge Base Structure:
├── Getting Started
│   ├── Quick start guide
│   ├── Account setup
│   └── First project walkthrough
├── Billing & Plans
│   ├── Plan comparison
│   ├── How to upgrade/downgrade
│   ├── Invoices and receipts
│   └── Cancellation policy
├── Features
│   ├── [Feature 1] guide
│   ├── [Feature 2] guide
│   └── Integration setup guides
├── Troubleshooting
│   ├── Common error messages
│   ├── Performance issues
│   └── Login problems
└── API & Developer Docs (if applicable)
    ├── Authentication
    ├── Rate limits
    └── Endpoints reference
```

Write articles following this template for consistency:
- Title: action-oriented (How to..., Setting up..., Fixing...)
- Problem statement: 1-2 sentences
- Solution: numbered steps with screenshots
- Related articles: 2-3 links at bottom

Launch target: minimum 20 articles covering the top 80% of contact reasons.

**Verify**: Search for 10 common questions in the KB search. At least 8 should return relevant results. Test article links from within the helpdesk agent interface.
**If failed**: KB search quality depends on article titles and first paragraphs. Rewrite titles to match how customers actually phrase questions.

### Step 5: Configure Escalation Paths

**Duration**: 1-2 hours
**Tool**: Platform workflow builder

Define escalation matrix by issue type and severity:

```
Escalation Matrix:
┌────────────────────┬─────────────┬──────────────────┬──────────────────┐
│ Issue Type         │ Tier 1      │ Tier 2           │ Tier 3           │
├────────────────────┼─────────────┼──────────────────┼──────────────────┤
│ General questions  │ Any agent   │ Senior agent     │ Support lead     │
│ Technical bugs     │ Tech agent  │ Engineering      │ Engineering lead │
│ Billing disputes   │ Any agent   │ Billing lead     │ Finance / Legal  │
│ Security incidents │ SKIP        │ Security team    │ CTO / CISO       │
│ Account deletion   │ Any agent   │ Account manager  │ Legal            │
└────────────────────┴─────────────┴──────────────────┴──────────────────┘

Auto-escalation triggers:
- 2+ replies without resolution → escalate to Tier 2
- Customer sentiment = angry (if AI detection available) → flag for senior agent
- SLA at 90% → auto-escalate to next tier
- VIP/Enterprise customer → start at Tier 2
```

**Verify**: Test each escalation path with mock tickets. Verify notifications reach the right people and tickets move between tiers correctly.
**If failed**: Check that agent groups and skills are correctly configured. Most routing failures are caused by missing group membership.

### Step 6: Set Up Analytics and Scaling Triggers

**Duration**: 1-2 hours
**Tool**: Platform reporting + spreadsheet for tracking

Configure dashboards tracking these core metrics:

| Metric | Target | Scaling Trigger |
|--------|--------|-----------------|
| First response time | Within SLA targets | Consistently breaching P2+ SLAs |
| CSAT score | > 85% | Drops below 80% for 2+ weeks |
| Tickets per agent per day | 30-40 | Exceeds 45 for 2+ weeks [src5] |
| Agent utilization | 70-85% | Exceeds 85% consistently |
| KB deflection rate | > 20% | Below 15% after 30 days |
| Resolution time | Within SLA targets | P3+ average exceeds target by 50% |
| Ticket backlog | < 1 day of volume | Exceeds 2 days of volume |

Scaling triggers — when to act: [src5]
- **Hire next agent**: When ticket volume exceeds 600-900 tickets/agent/month for 2+ consecutive months
- **Add AI/automation**: When >30% of tickets are repetitive questions answerable by KB
- **Upgrade platform tier**: When you need features in the next tier (routing, HIPAA, sandbox)
- **Evaluate platform switch**: When annual cost exceeds $50K and feature utilization is below 40%

**Verify**: Dashboard loads correctly with real or test data. Alert rules fire when thresholds are crossed.
**If failed**: Most platforms need 48-72 hours of data before analytics populate. Use test tickets to validate dashboard structure.

### Step 7: Launch and Validate

**Duration**: 2-4 hours
**Tool**: All configured tools

Pre-launch checklist:
1. All team members trained on platform (30-60 min onboarding session)
2. Support email confirmed working (send test from external account)
3. Live chat widget installed on website/app (if applicable)
4. SLA timers validated with test tickets
5. Escalation paths tested end-to-end
6. KB articles reviewed and published (minimum 20)
7. Canned responses / macros created for top 10 repetitive questions
8. Analytics dashboard configured and accessible to team leads

Post-launch monitoring (first 2 weeks):
- Daily review of SLA compliance
- Daily review of unassigned/stale tickets
- Weekly review of CSAT and first-response-time trends
- Collect agent feedback on workflow friction

**Verify**: Process 10+ real tickets end-to-end. Measure actual first response time vs. SLA target.
**If failed**: Most common launch issues are missed email routing (check SPF/DKIM), incorrect business hours, and missing canned responses.

## Output Schema

<!-- Exact format of the deliverable. Downstream agents and dashboard cards
     reference this schema to consume the output. -->

```json
{
  "output_type": "support_infrastructure",
  "format": "configured platform + documents",
  "components": [
    {"name": "helpdesk_platform", "type": "configured SaaS", "description": "Live ticketing system with routing, SLA, and agent assignments", "required": true},
    {"name": "sla_policy", "type": "document", "description": "4-tier SLA matrix with response and resolution targets per priority", "required": true},
    {"name": "knowledge_base", "type": "deployed URL", "description": "20+ articles organized by category, searchable, linked from helpdesk", "required": true},
    {"name": "escalation_matrix", "type": "document", "description": "Routing rules by issue type and severity with named owners per tier", "required": true},
    {"name": "analytics_dashboard", "type": "configured platform", "description": "KPI tracking for response time, CSAT, agent utilization, deflection rate", "required": true},
    {"name": "scaling_triggers", "type": "document", "description": "Defined thresholds for hiring, automation, and platform changes", "required": false}
  ]
}
```

## Quality Benchmarks

<!-- How to evaluate if the output is good enough.
     Links to benchmark cards where applicable. -->

| Quality Metric | Minimum Acceptable | Good | Excellent |
|---------------|-------------------|------|-----------|
| SLA compliance rate (first 30 days) | > 80% | > 90% | > 95% |
| First response time (median) | < 4 hours | < 1 hour | < 15 minutes |
| KB article coverage (top contact reasons) | > 60% | > 80% | > 95% |
| CSAT score | > 75% | > 85% | > 92% |
| Ticket deflection rate (KB self-service) | > 10% | > 20% | > 35% |

**If below minimum**: Review top unresolved ticket categories, add missing KB articles, retrain agents on SLA workflows, or adjust staffing levels per scaling triggers.

## Error Handling

<!-- Common failures and recovery actions. Agents need this to handle
     execution errors without human intervention. -->

| Error | Likely Cause | Recovery Action |
|-------|-------------|----------------|
| Support emails not appearing in platform | DNS/MX misconfiguration or SPF/DKIM failure | Verify forwarding rules and DNS records; use platform-provided forwarding address as fallback |
| SLA timers counting 24/7 instead of business hours | Business hours calendar not configured | Set timezone and business hours schedule in platform settings; reprocess active tickets |
| KB articles not appearing in search | Articles saved as draft or search index not rebuilt | Publish all articles; trigger manual reindex if platform supports it |
| Agent unable to see assigned tickets | Incorrect group membership or role permissions | Verify agent is added to correct team/group with appropriate role level |
| Escalation notifications not firing | Workflow automation disabled or email channel misconfigured | Enable automation engine; verify notification email addresses; check spam folders |
| AI resolution costs exceeding budget | Higher than expected ticket volume or low deflection rate | Set monthly AI resolution cap; increase KB coverage to deflect more before AI engages |

## Cost Breakdown

<!-- Real cost analysis so agents can warn users before execution. -->

| Component | Free Tier | Growth ($200/mo) | Scale ($1000+/mo) |
|-----------|-----------|-------------------|---------------------|
| Platform (3 agents) | Freshdesk Free: $0 | Freshdesk Growth: $87/mo ($29x3) | Zendesk Pro: $345/mo ($115x3) |
| Platform (10 agents) | N/A (2-agent limit) | Freshdesk Growth: $290/mo | Zendesk Pro: $1,150/mo |
| AI features | Not available | Intercom Fin: ~$200-500/mo at 200-500 resolutions | Zendesk AI: $500/mo ($50x10 agents) |
| Knowledge base | Built-in (basic) | Built-in (full) | Built-in + custom theming |
| Analytics | Basic metrics | Custom dashboards | Advanced + API export |
| **Total (3 agents, 500 tickets/mo)** | **$0** | **$87-185/mo** | **$345-845/mo** |
| **Total (10 agents, 3000 tickets/mo)** | **N/A** | **$290-790/mo** | **$1,150-1,650/mo** |

## Anti-Patterns

### Wrong: Starting with the Most Feature-Rich Platform
Buying Zendesk Enterprise ($169/agent/month) for a 3-person team handling 200 tickets/month. Result: 80% of features unused, $500+/month wasted, team overwhelmed by complexity. [src2]

### Correct: Match Platform to Current Scale + 12-Month Projection
Start with Freshdesk Growth or Help Scout for small teams. Migrate to Zendesk/Intercom when you hit specific scaling triggers (20+ agents, need skills-based routing, or compliance requirements). [src3]

### Wrong: Launching Knowledge Base Without Enough Content
Publishing 5 articles and expecting ticket deflection. Result: customers search, find nothing, lose trust in self-service, and stop trying. KB becomes a ghost town. [src6]

### Correct: Launch with 20+ Articles Covering Top Contact Reasons
Analyze first 200 tickets (or anticipated questions), group by theme, write articles for the top 80% of contact reasons before launching self-service publicly.

### Wrong: Setting Aggressive SLAs Without Staffing to Match
Promising 15-minute first response for all tickets with 2 agents. Result: chronic SLA breaches, meaningless metrics, agent burnout, and customers who distrust your commitments. [src4]

### Correct: Set Achievable SLAs, Then Tighten as Capacity Grows
Start with realistic targets (4-hour first response for P3, 1-hour for P2). Tighten SLAs only when you consistently exceed them by 20%+ for 30 days.

## When This Matters

Use when an agent needs to stand up actual support infrastructure — not plan a support strategy, but configure a real helpdesk, write real SLA policies, build a real knowledge base, and set up real escalation workflows. Requires product description and team/budget constraints as inputs. Most valuable for startups moving from founder-handles-everything to structured support operations.

## Related Units

- [Customer Success Program Design](/business/customer-success/cs-program-design/2026)
- [Customer Onboarding Setup](/business/customer-success/customer-onboarding-setup/2026)
- [Support Metrics Dashboard](/business/startup-metrics/support-metrics-dashboard/2026)
- [SaaS Unit Economics Benchmarks](/finance/saas-benchmarks/support-cost-benchmarks/2026)