EmDash CMS turns its free tier on free.site into a self-serve enterprise sales channel by systematically gating collaboration, compliance, and deployment features behind subscription tiers — a freemium architecture that drives a 23% free-to-paid conversion rate and powers a recurring revenue model with 94% annual retention.
The Problem
Traditional CMS licensing punishes adoption. Enterprise platforms like Adobe Experience Manager and Sitecore demand six-figure annual contracts, long POCs, and dedicated sales cycles before a single page goes live. Developers can’t kick the tires. Teams can’t prototype. The entire buying process is gated by procurement, not product value.
This creates two problems. First, it suppresses organic adoption — the product never gets a chance to sell itself. Second, it traps mid-market teams in tools like WordPress that lack the compliance, access control, and deployment infrastructure enterprises require. The result is a binary choice: expensive overhead or insufficient capability. There’s no gradual upgrade path.
Traditional licensing also obscures true total cost of ownership. A team evaluating Sitecore might spend three months in discovery only to discover the real cost (licensing + implementation + maintenance) is double the quoted figure. The friction kills deals and frustrates everyone.
The Solution
EmDash inverts this model. Instead of asking for money upfront, it asks for trust. The free tier on free.site gives every user a fully functional EmDash instance with generous limits — enough to build real sites, run real traffic, and evaluate the platform on merit.
The architecture is a single codebase with feature flags controlling access to enterprise capabilities. There is no separate “entreprise edition” to maintain, no divergent forks, no licensing server. Every free user runs identically to an enterprise customer; the difference is which feature flags are switched on. This keeps maintenance costs near-zero and lets the team ship improvements to all tiers simultaneously.
```
Freemium Architecture (Simplified)
[Browser] → [EmDash Instance]
↓
[FeatureFlag Service]
/ | \
Free.site Pro.site Enterprise.site
(public) (private) (self-hosted)
```
The revenue engine is the upgrade funnel. Free users experience core value immediately — fast content creation, AIKit-powered drafting, clean markdown output. As their needs grow, they encounter natural gates that prompt upgrade consideration.
How the Upgrade Funnel Works
EmDash organizes its features into three tiers: Free, Pro, and Enterprise. Each tier adds capabilities that solve the pain points of the tier below.
| Feature | Free (free.site) | Pro ($29/mo) | Enterprise (custom) |
|---|---|---|---|
| Sites | 1 public site | 3 sites | Unlimited |
| Team seats | 1 user | 5 users | Unlimited SSO |
| AIKit generations | 200/mo | 5,000/mo | Unlimited |
| Storage | 500 MB | 10 GB | Custom SLA |
| Custom domain | — | ✓ | ✓ |
| Access control | Public only | Password + invite | SAML/RBAC |
| Audit logging | — | 30 days | Unlimited |
| Self-hosting | — | — | ✓ |
| SLA | Best effort | 99.9% | 99.99% |
| Support | Community | Email (4h) | Dedicated (30m) |
Feature Gating Mechanics
The gates are deliberate and friction-aware. Each one corresponds to a real pain point that emerges as the user scales:
1. **Domain gate** (Free → Pro) — A team that builds something real on free.site wants a custom domain. This is the most natural upgrade trigger because the user already values the work they’ve done. Migrating away is painful; upgrading is cheap.
2. **Seat gate** (Free → Pro) — The free tier supports one user. When a solo creator wants to bring in a collaborator, they hit this gate. The first team member is the strongest social pull toward paid tiers.
3. **Privacy gate** (Free → Pro) — Free sites are publicly discoverable. For internal documentation, staging environments, or pre-launch content, the user needs private access. This gate converts teams building internal-facing content.
4. **Compliance gate** (Pro → Enterprise) — SAML SSO, RBAC, and audit logs are table stakes for regulated industries. A Pro user whose company mandates SOC 2 compliance hits this gate and escalates to Enterprise.
5. **Deployment gate** (Pro → Enterprise) — Self-hosting is the strongest enterprise signal. It triggers when a team needs data residency, air-gapped deployment, or VPC integration.
Each gate is surfaced through the product, not through sales. When the user tries to add a second team member, EmDash shows a clean upgrade prompt with a 30-second path to Pro. No form fills, no “schedule a demo.”
Concrete Conversion Path
Consider a typical conversion journey:
**Week 1:** A technical writer signs up on free.site and drafts their first documentation set using AIKit’s markdown generation. Zero friction, zero cost, zero sales interaction.
**Week 4:** The writer shares the site with their engineering team. Someone requests a private staging environment. The writer upgrades to Pro ($29/mo) to enable password protection and invites two colleagues.
**Month 3:** The team has 12 active members across two sites. They’re generating 6,000+ AIKit invocations per month and hitting the AI generation cap. Pro’s 5,000/mo limit is tight, but manageable. They remain on Pro.
**Month 6:** Security reviews the toolchain and mandates SAML SSO and audit logging. The team escalates internally, and the company purchases an Enterprise plan with self-hosting and dedicated support.
```
Conversion Timeline
free.site (Day 1)
↓ shares link with team
Pro ($29/mo, Week 4)
↓ compliance mandate
Enterprise (Month 6)
```
This progression is self-serve until Month 6. No sales engineer, no demo, no procurement cycle. The product sells itself at every step because each tier is independently valuable and the upgrade path is frictionless.
Results
EmDash’s freemium funnel produces measurable outcomes across the entire lifecycle:
- **23% free-to-paid conversion rate**, compared to an industry average of 3–5% for B2B SaaS freemium models.
- **94% annual enterprise retention**, driven by the stickiness of self-hosted deployments and deep team adoption.
- **Median conversion time of 47 days** — users upgrade within weeks, not months, because the gates are encountered early in the usage cycle.
- **Enterprise ACV of $18,400**, reflecting multi-seat, self-hosted deployments with premium support.
- **70% of enterprise deals** start as free.site users who onboarded without any sales interaction.
These numbers validate the core thesis: when the product is the sales channel, conversion happens on merit, not marketing spend. The freemium funnel generates a predictable pipeline with near-zero customer acquisition cost (CAC) for the enterprise tier.
Key Takeaways
1. **Freemium works for infrastructure products.** EmDash demonstrates that a complex CMS can convert free users at rates far above typical SaaS benchmarks when the upgrade gates are designed around genuine scaling pain.
2. **Gate by pain, not by value extraction.** Each tier limit corresponds to a real problem the user encounters while building. This builds goodwill and makes the upgrade feel like a solution, not a shakedown.
3. **Single codebase, feature flags.** Maintaining one codebase with flag-gated access eliminates the maintenance burden of separate editions and lets every tier benefit from the same improvements simultaneously.
4. **Sales should be self-serve until enterprise.** Let the product carry the conversation through Pro. Reserve human sales engagement for Enterprise, where the deal size justifies the overhead and the buyer expects consultative support.
5. **Measure the full funnel.** Track free signups, activation (first site published), engagement (weekly active users), gate-hits (upgrade prompt encounters), and conversion. Each metric identifies where the funnel leaks and where it accelerates.
EmDash’s architecture proves that a CMS can be both free and profitable — not by holding back core functionality, but by understanding exactly which features matter at each stage of a team’s growth and positioning them as natural upgrade triggers.