Objection: "Why not another CMS?"
This page is for advocates who are asked "why not just use a more popular CMS?" The fair answer is never "because the other one is bad". It is "here is what Exponential does, here is how you check it, and here is where it is not the right fit". The rules come from Comparing Exponential factually.
Contents
- The rules
- Ask about needs first
- Where Exponential fits well
- Where it is not the right fit
- Reply templates
- Do not say
The rules
- Compare properties, not reputations. A license file, a release history, a list of databases.
- Every claim has a source.
- Never describe another product. What another product does is for the person to find in that product's own documentation.
- Date your figures.
- Volunteer the limits.
Ask about needs first
The best answer starts with questions:
- "What content do you manage, and does it have a structure (products, events, people) or is it mostly pages?"
- "How many sites and languages?"
- "Who edits, and do they need approvals and versions?"
- "What skills and hosting do you have?"
- "How long must the site live?"
Then match the answers to Exponential's documented strengths, or say honestly that it is not the best fit.
Where Exponential fits well
| Need | Exponential's property | Source |
|---|---|---|
| Structured content of many types | A fully customizable content model, defined in the administration | The content model and editing content |
| Several sites and many languages from one installation | Siteaccesses, translations per item, right to left | Feature highlights |
| Editorial control | Drafts, versions, approval workflows, an audit trail | Feature highlights |
| A shop in the same system | The built-in shop | Store dashboard |
| Freedom of hosting | Six databases, operating systems in tiers | Talking points: hosting |
| Long life and no lock-in | GPL code with a public history since 2002 | Talking points: longevity |
Where it is not the right fit
Say these yourself. Each is documented in Where Exponential is not the right fit:
- Microsoft SQL Server is required: no driver in 6.0.x.
- A Symfony-only project without the legacy kernel: then Exponential Platform DXP is the family member.
- Shared hosting that forbids long-running processes: Velocity usually cannot run there.
- More than 62 content languages in one installation.
- A fully translated administration in a language that is not complete today.
- A published SLA document: the project publishes none; contracts come from providers.
Reply templates
NEUTRAL
Depends what you need. Exponential is strongest when content has structure (many content types),
when you run several sites or languages from one install, and when editors need versions and approvals.
If you mostly need a simple blog, other tools may suit you better. What are you building?
AFTER THEY DESCRIBE THEIR NEEDS
For <their need>, Exponential has <property> (<link>). You can try it in a few minutes on SQLite:
<link to Install in one command>. Compare it with the other options on the same checklist.
WHEN IT IS NOT A FIT
Honestly, for <their need> Exponential isn't the best fit: <documented limit> (<link>). Good luck with
the project - and if your needs change, the forums are open.A comparison grid to fill in together is on Comparing Exponential factually.
Do not say
- Anything negative about another product, its company or its users.
- "Exponential does everything X does."
- "X is insecure / slow / dying."
- Popularity figures about any product.
Related pages
- Respecting other projects and companies
- Comparing Exponential factually
- Answering objections as an advocate
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.