Per-Site Pricing

Master this essential documentation concept

Quick Definition

A billing model where costs are calculated based on the number of separate documentation sites or properties managed, rather than a flat rate or per-user model.

How Per-Site Pricing Works

graph TD A[Organization Account] --> B[Site 1: Product A Docs] A --> C[Site 2: Product B Docs] A --> D[Site 3: Client Portal] A --> E[Site 4: Developer Hub] B --> B1[Custom Domain] B --> B2[Unique Branding] B --> B3[Unlimited Contributors] C --> C1[Custom Domain] C --> C2[Unique Branding] C --> C3[Unlimited Contributors] D --> D1[Client-Specific Access] D --> D2[Isolated Content] E --> E1[API Documentation] E --> E2[Developer Resources] A --> F[Centralized Billing] F --> G{Pricing Tier} G --> G1[Tier 1: 1-3 Sites] G --> G2[Tier 2: 4-10 Sites] G --> G3[Tier 3: 11+ Sites] A --> H[Unified Dashboard] H --> H1[Cross-Site Analytics] H --> H2[Global Search] H --> H3[Team Management]

Understanding Per-Site Pricing

Per-Site Pricing is a documentation platform billing approach that charges organizations based on the number of distinct documentation sites or properties they manage. Unlike per-user or flat-rate models, this structure aligns costs directly with the scope of documentation infrastructure, making it a strategic choice for teams operating multiple independent documentation portals, knowledge bases, or developer hubs.

Key Features

  • Site-based cost calculation: Each unique documentation portal, help center, or knowledge base counts as a billable site, regardless of how many users access or contribute to it.
  • Independent site management: Each site can have its own branding, domain, content structure, and access controls while being managed under a single account.
  • Scalable tiers: Pricing typically scales in tiers (e.g., 1-5 sites, 6-15 sites), allowing organizations to grow incrementally without sudden cost spikes.
  • Centralized billing: All sites are managed and billed through a single administrative account, simplifying financial oversight.
  • Cross-site analytics: Many platforms offer aggregated reporting across all managed sites within the pricing tier.

Benefits for Documentation Teams

  • Predictable cost scaling: Teams can forecast documentation costs accurately as they launch new products or onboard new clients.
  • Client isolation: Agencies can maintain completely separate documentation environments for each client without commingling content or access.
  • Team flexibility: Add or remove contributors across sites without triggering per-seat cost increases, ideal for cross-functional teams.
  • Portfolio management: Documentation managers gain a unified dashboard to oversee multiple sites, streamlining governance and quality control.
  • Cost efficiency for large teams: Organizations with many contributors but few sites save significantly compared to per-user pricing models.

Common Misconceptions

  • More sites always means higher costs: Tiered pricing often makes adding sites within a tier essentially free, so the marginal cost per site decreases as you scale.
  • Per-site pricing limits collaboration: Most platforms allow unlimited users per site within the per-site model, actually enabling broader collaboration.
  • It only benefits large enterprises: Small agencies managing even 3-5 client documentation sites can find per-site pricing more economical than per-user alternatives.
  • Each site requires separate logins: Modern platforms with per-site pricing typically offer single sign-on and unified dashboards across all managed sites.

Real-World Documentation Use Cases

SaaS Company Managing Multiple Product Documentation Sites

Problem

A SaaS company with four distinct software products needs separate, branded documentation portals for each product. Using per-user pricing, their 50-person team would face enormous costs, even though most contributors only work on one or two products.

Solution

Adopt a per-site pricing model to create four independent documentation sites, each with its own branding, domain, and content structure, while keeping all contributors under one billing account without per-seat charges.

Implementation

['Audit existing documentation to identify which content belongs to each product line', 'Select a documentation platform offering per-site pricing with at least a 4-site tier', 'Set up four separate sites with unique subdomains (docs.producta.com, docs.productb.com, etc.)', 'Assign product-specific contributors to each site with appropriate roles', 'Configure centralized analytics to monitor engagement across all four portals', 'Establish a cross-site style guide to maintain brand consistency while allowing site-level customization']

Expected Outcome

The company reduces documentation platform costs by 60% compared to per-user pricing, while achieving cleaner content separation, faster site-specific search results, and improved user experience for each product's customer base.

Documentation Agency Onboarding Multiple Clients

Problem

A technical writing agency manages documentation for eight different clients, each requiring isolated, white-labeled knowledge bases. Sharing a single site risks content leakage and makes client-specific customization nearly impossible.

Solution

Implement per-site pricing to provision a dedicated documentation site for each client, enabling full isolation, custom branding, and independent publishing workflows while the agency manages everything from a single administrative account.

Implementation

['Select a per-site pricing plan that accommodates 8-10 sites within a single tier', 'Create a standardized site setup template to accelerate new client onboarding', "Configure each site with the client's custom domain, logo, color scheme, and navigation structure", "Set up client-specific contributor access so clients can review and approve content without seeing other clients' sites", 'Establish separate publishing schedules and version control workflows per site', 'Use centralized billing to generate a single monthly invoice, then allocate costs per client']

Expected Outcome

The agency achieves complete client isolation, reduces onboarding time for new clients by 40%, and presents a professional, fully branded documentation experience to each client, strengthening retention and enabling premium pricing.

Enterprise Separating Internal and External Documentation

Problem

A large enterprise needs to maintain separate documentation sites for external customers, internal employees, and partner integrators. Mixing these audiences on one site creates security risks and confusing navigation experiences.

Solution

Use per-site pricing to operate three distinct documentation environments—a public customer help center, a private internal wiki, and a partner developer portal—each with tailored access controls and content strategies.

Implementation

['Map audience needs and access requirements for each of the three documentation types', 'Provision three separate sites under one per-site pricing account', 'Configure public access for the customer help center, SSO-gated access for the internal site, and API-key authentication for the partner portal', 'Assign dedicated documentation owners and contributor teams to each site', 'Establish content reuse workflows to share common content (e.g., product overviews) across sites without duplication', 'Set up audience-specific analytics dashboards to measure self-service success rates per site']

Expected Outcome

The enterprise eliminates unauthorized content access incidents, improves search relevance by 70% within each audience-specific site, and enables documentation teams to optimize content strategies independently for each user group.

Open Source Project Managing Community and Commercial Documentation

Problem

An open source project offers both a free community edition and a paid commercial version. Maintaining documentation for both on a single site creates confusion about which features are available in each tier and complicates the upgrade messaging.

Solution

Deploy two separate documentation sites under a per-site pricing model—one for the open source community edition and one for the commercial product—allowing distinct navigation, feature coverage, and call-to-action strategies for each audience.

Implementation

['Identify content that is unique to each edition versus shared across both', 'Set up two sites: one publicly accessible community docs site and one commercial docs site requiring login or license verification', 'Migrate and reorganize existing documentation into the appropriate site', 'Implement content mirroring for shared topics to avoid maintaining duplicate pages', 'Add upgrade prompts and feature comparison tables in the community site to drive commercial conversions', 'Monitor search queries on the community site to identify documentation gaps that commercial users frequently encounter']

Expected Outcome

The project sees a 35% reduction in support tickets from users confused about feature availability, a measurable increase in commercial trial sign-ups driven by strategic upgrade prompts, and higher community satisfaction scores due to cleaner, more relevant documentation.

Best Practices

âś“ Audit and Consolidate Before Committing to a Tier

Before selecting a per-site pricing tier, conduct a thorough audit of all existing documentation properties to determine how many true sites you actually need. Many organizations discover they can consolidate overlapping content into fewer, better-organized sites, reducing costs while improving the user experience.

âś“ Do: Map all current documentation properties, identify overlapping content, and determine the minimum viable number of distinct sites needed to serve your audiences effectively before purchasing a plan.
âś— Don't: Don't assume you need a separate site for every product version, feature, or team. Over-provisioning sites increases costs and fragments your documentation, making it harder for users to find information.

âś“ Define Clear Site Ownership and Governance Rules

Each site in a per-site pricing model should have a designated owner responsible for content quality, publishing schedules, and access management. Without clear ownership, sites can become outdated or inconsistent, undermining the value of having separate properties.

âś“ Do: Assign a documentation owner or team lead to each site with defined responsibilities for content review cycles, contributor management, and site-level analytics reporting.
âś— Don't: Don't leave sites without a designated owner or allow multiple teams to publish to the same site without a coordinated editorial workflow, as this leads to inconsistent quality and duplicated content.

âś“ Standardize Site Templates to Accelerate Deployment

Creating a reusable site template with pre-configured navigation structures, branding guidelines, and content frameworks dramatically reduces the time and effort required to launch new documentation sites. This is especially valuable for agencies or enterprises that frequently provision new sites.

âś“ Do: Build a master site template that includes standard navigation categories, a style guide, reusable content components, and default SEO settings that can be cloned and customized for each new site.
âś— Don't: Don't build each new site from scratch without referencing established patterns, as this wastes time, introduces inconsistencies, and makes cross-site maintenance significantly more difficult.

âś“ Plan for Tier Transitions in Your Documentation Roadmap

Per-site pricing tiers often have significant cost jumps between levels. Building site growth projections into your documentation roadmap helps you anticipate when you will cross tier thresholds and budget accordingly, avoiding surprise cost increases mid-fiscal year.

âś“ Do: Include projected site count milestones in your annual documentation planning, and negotiate multi-year contracts or volume discounts with your platform vendor when you anticipate significant site growth.
âś— Don't: Don't add new sites reactively without considering how they affect your pricing tier. Launching a site that pushes you into the next tier just before a budget freeze can create financial and operational disruptions.

âś“ Leverage Cross-Site Analytics to Justify ROI

One of the most powerful aspects of per-site pricing platforms is the ability to aggregate analytics across all managed sites. Using this data to demonstrate the collective impact of your documentation portfolio strengthens the business case for continued investment and helps identify underperforming sites that may need consolidation.

âś“ Do: Establish monthly cross-site reporting that tracks metrics such as total page views, search success rates, support ticket deflection, and user satisfaction scores across all sites to present a unified documentation ROI narrative to stakeholders.
âś— Don't: Don't evaluate each site in isolation without comparing performance across the portfolio. Siloed reporting misses opportunities to identify best practices from high-performing sites and apply them to underperforming ones.

How Docsie Helps with Per-Site Pricing

Book a Demo

Build Better Documentation with Docsie

Join thousands of teams creating outstanding documentation

Book a Demo