Information security for software delivery

ISO/IEC 27001
ISO/IEC 27001 certified
The economics
The four conditions under which a commercial DXP stops being expensive
The licence is a fixed cost; what varies is whether your estate generates the work that justifies it. Each driver below moves the answer.
| Variable | Effect on price | Why |
|---|---|---|
| Personalisation you will actually operate | The strongest justifier — and the most commonly idle | Serving different content by segment, market and behaviour at scale is what the platform is engineered for. It pays only when a named team writes the rules, feeds the data and reads the results week after week; bought without that team, it is the most expensive unused feature in enterprise software. |
| Sites and markets under one governance | Scales the value with every property added | Running many sites, brands and language pairs through one content model, one workflow and one permission scheme is where a DXP’s governance machinery earns real money. Two sites do not need it; fifteen sites across four markets struggle without it. |
| Depth of commerce and CRM integration | Raises both the value and the engineering bill | A DXP wired into commerce and CRM can carry a genuinely personal journey from first visit to repeat purchase. The wiring is real engineering with real maintenance, and it belongs in the adoption estimate — not discovered as a change order in month six. |
| The cost of leaving, priced at entry | The driver nobody prices until it is due | Content modelled in proprietary structures, templates coupled to the platform, and integrations written against its APIs all cost money to unwind. An estate that keeps its content model portable and its integrations behind its own seams pays a little more now to keep the exit affordable later. |
Ask any supplier quoting this
- Which licensed capabilities does our current contract include that no team here operates today?
- What would exporting our full content model and content into a neutral format involve, and who has done it?
The fork
Classic Sitecore and composable Sitecore ask for different organisations
The classic platform is one integrated product: content, rendering, personalisation and hosting in a single installation your team runs. Its strength is coherence — everything is designed to work with everything — and its costs are the infrastructure you operate and an upgrade path that moves the whole platform at once. The composable direction breaks that into cloud services — content as a headless service, your front-end built separately, capabilities subscribed individually. Its strength is that each piece can evolve or be replaced alone; its cost is that your organisation now assembles and operates an architecture rather than installing a product, which is a different engineering posture with a different team.
The honest reading of the vendor’s direction is that investment is flowing to the composable products, which matters for a decision with a ten-year horizon. But direction is not a command: an estate already live on the classic platform, staffed and stable, does not need to migrate on the vendor’s schedule, and a migration undertaken without a business reason is cost wearing strategy’s clothes. We have no stake in which path you take — the assessment is about your estate’s scale, your team’s shape and your contract’s dates, and those, not the roadmap slides, should set the timing.
The realities
What a Sitecore commitment has to budget for beyond the licence line
None of these is a reason not to adopt. Each is a cost that surprises the estates that did not price it.
- 01
The engineers are scarce and priced accordingly
Sitecore engineering is a specialist market: the pool is small, day rates reflect it, and a departure can stall an estate. The mitigations are architectural — keep custom code thin, document the seams, and pair specialists with strong general engineers who can grow into the platform.
- 02
A fraction of the platform, used at full price
The commonest failure is not a broken implementation; it is an estate using a DXP as an expensive page editor. The remedy is an operating plan for the licensed capabilities — owners, rules, review — agreed before renewal, or a smaller platform agreed instead.
- 03
Integration is where the real engineering lives
Commerce catalogues, CRM profiles, marketing automation — the connections carry the value and most of the effort. Each seam needs an owner, monitoring and a version discipline, or the estate degrades quietly at its joints.
- 04
The exit that was never designed
Estates that modelled content in deeply platform-specific structures discover at year eight that leaving costs as much as arriving did. Designing the content model to survive the platform is cheap on day one and unaffordable later.
Our role
Independent Sitecore work, and where the vendor relationship stays yours
- 01
The adoption case, or the case against
We model your estate against the licence — sites, markets, the personalisation you would truly operate, the team you would need — and give the recommendation in writing, including when it is a smaller platform.
- 02
Implementation with thin custom code
We build and extend the estate keeping customisation minimal and documented, the content model as portable as the platform allows, and the integrations behind seams your team can maintain and one day re-point.
- 03
The migration argued from your dates
Classic to composable, or off the platform entirely, is planned from your contract dates, your team and your estate’s real usage — not from a roadmap presentation — and delivered property by property with nothing switched off early.
The licence, its negotiation and the vendor relationship are yours; our independence from that relationship is exactly what makes the adoption and exit advice worth having.
Common questions
What buyers ask
Do we need a badged Sitecore partner for the implementation to be safe?+
A partner badge tells you a firm has a commercial relationship with the vendor and engineers who passed its exams; it does not tell you the implementation will be well-architected, and it creates an incentive to recommend the platform in cases where a smaller one would do. We hold no Sitecore partnership or certification, and we say so plainly. What to demand from any supplier, badged or not: reference architecture they can defend line by line, a position on keeping custom code thin, a content model designed to outlive the platform, and a willingness to tell you when the licence is more than your estate needs. Those properties, not the badge, are what make the work safe.
Is Sitecore too much platform for a single-brand site in two languages?+
Almost always, yes. One brand, one site and an Arabic–English pair is an estate a strong conventional or headless CMS governs comfortably at a fraction of the licence and the engineering rate. The DXP starts earning when the multiplicity arrives — several sites, several markets, personalisation with an operating team, deep commerce and CRM wiring. If your three-year plan genuinely contains that multiplicity, adopting early can beat migrating later; but the plan has to be real, with budgets and owners, not an aspiration slide. We would rather scope you a platform your estate fills than one it rattles around in.
What does it cost to leave Sitecore later, and can we lower that now?+
The exit bill has three parts: extracting content out of platform-specific structures, rebuilding the presentation layer somewhere else, and re-pointing every integration written against the platform’s APIs. Each part is priced by decisions made at entry. Model content in structures that mirror your business rather than the platform’s conveniences, and extraction becomes an export job instead of an archaeology project. Keep the front-end’s coupling to the platform behind a thin layer, and the rebuild shrinks. Route integrations through seams you own, and re-pointing is configuration. None of this costs much during the build — it is the kind of discipline that is nearly free early and nearly impossible late.
In this cluster
Weigh the licence with us
An estate-scale assessment that says plainly whether Sitecore’s licence would earn its keep on your sites, and what adopting or leaving it would actually cost.
Start the conversation