[ Enterprise CMS · Full playbook ]
// 10 / 20The buyer's playbook.
The working reference behind Drupal vs WordPress: Enterprise CMS Comparison 2026: what to ask, what to watch and how to run the first 90 days.
← Back to the guide[ RFP questions ]// 01
Questions that reveal real capability.
Ask for a relevant example, the decision made, the result or learning, and the person who would own the work.
- 01Which requirements genuinely differentiate Drupal from WordPress?
- 02How will roles, delegation and separation of duties work across departments?
- 03Which multilingual needs apply to content, interfaces, configuration and search?
- 04How are plugins or contributed modules selected, reviewed and retired?
- 05What is the security-advisory, patch, testing and emergency-release process?
- 06How will configuration move from development to staging and production?
- 07What accessibility standard, test method and remediation SLA will apply?
- 08Show the five-year cost model, upgrade path and vendor-exit plan.
[ Risk ]// 02
Make failure visible before signature.
| Risk | Early warning | Control |
|---|---|---|
| Platform chosen by preference | Decision precedes requirements | Use weighted scenarios and proof-of-concept |
| Extension sprawl | Plugins/modules overlap or lack coverage | Architecture register and approval policy |
| Permission failure | Broad administrator access | Least privilege and workflow testing |
| Upgrade shock | Custom code blocks core releases | Lifecycle budget, automation and compatibility reviews |
| Editor workarounds | Publishing moves into documents and email | Prototype with real editors and approvals |
[ Value case ]// 03
Measure outcomes—not activity.
01Editorial cycle time and approval stepsBaseline ________
90-day target ________
90-day target ________
02Accessibility conformance and defect ageBaseline ________
90-day target ________
90-day target ________
03Security patch-response timeBaseline ________
90-day target ________
90-day target ________
04Publishing success by language and departmentBaseline ________
90-day target ________
90-day target ________
05Platform availability and page performanceBaseline ________
90-day target ________
90-day target ________
06Annual operating cost and upgrade effortBaseline ________
90-day target ________
90-day target ________
[ First 90 days ]// 04
Move from evidence to operating rhythm.
01
Days 1–30
Stakeholder discovery, content model, obligations and weighted requirements
Exit evidenceApproved baseline, owners, scope and risk log
02
Days 31–60
Prototype priority workflows in both platforms; test permissions, languages and integrations
Exit evidenceWorking outputs, QA evidence and decision record
03
Days 61–90
Select platform, approve lifecycle model, migration plan, governance and procurement package
Exit evidenceMeasured result, learning backlog and operating owner
[ Reference desk ]// 05
Speak the same language.
| Term | Plain-language meaning |
|---|---|
| Content model | Structured types, fields, relationships and reuse rules. |
| Multisite | A network of WordPress sites administered together. |
| Configuration management | Versioned movement of platform settings between environments. |
| Contributed module / plugin | Third-party extension maintained outside platform core. |
| Least privilege | Giving each role only the access needed for its work. |
| Total cost of ownership | Implementation plus hosting, licences, support, upgrades and internal labour. |
[ Playbook in hand? ]