Sitecore consultancy, upgrades and XM Cloud delivery

Most of what we are asked to do is not a greenfield build. It is an estate that has fallen behind and a team that needs it supported again - and as the ecosystem chases SaaS work, the people who know legacy XP and .NET are getting harder to find.

Sitecore Silver Partner - three consecutive years
Book a Sitecore assessmentCompare the platforms

When Sitecore is the right call

  • You run many sites, markets or brands from one team, and consistency of governance matters as much as the pages.
  • Personalisation and customer data are a funded programme with people behind them, not an aspiration in a business case.
  • You are already on Sitecore with real investment in it, and the question is upgrade or migrate - not whether to leave.
  • Compliance, audit and controlled release processes rule out a versionless platform you cannot pin.

When we'd point you elsewhere

  • Fewer than ten editors and a single market. You would be paying for a ceiling you will not reach.
  • The personalisation licence has been paid for three years and never switched on. That is a signal, not an accident.
  • Your constraint is the integration layer, not the CMS - in which case the CMS choice barely matters.
  • Budget is the binding constraint and the estate is modest. Umbraco will serve you better and we will say so.

What we do with Sitecore

Version upgrades

9.x and 10.x to 10.4, including the estates other teams have quoted and walked away from. Assessment first, so the cost is known before anyone commits.
Sitecore upgrades →

XP → XM Cloud migration

Replatforming with an honest view of what carries over and what has to be rebuilt - usually the personalisation rules and the rendering layer.
XM Cloud migration →

CDP and Personalize

Getting the products you already pay for into production: data model, segments, and personalisation your content team can maintain.

Headless front ends

JSS and the Content SDK, Next.js, a .NET BFF where the back office needs one - built so editors keep the preview and authoring experience they expect.

Architecture and Helix review

Where a solution has drifted from its own conventions, we map what is there, name what is costing you, and sequence the fixes.

Support and platform care

Ongoing support on the platform we built, or one we inherited - including Azure infrastructure, SQL Server and release automation.

Sitecore support dates - where your version stands

If your version is below the line, the support conversation is over and it is now a migration-path conversation.

VersionMainstream endsExtended endsSustaining ends
9.1Ended31 Dec 202431 Dec 2026
9.2 / 9.3Ended31 Dec 202531 Dec 2027
10.0 / 10.1Ended31 Dec 202631 Dec 2028
10.2Ended31 Dec 202731 Dec 2029
10.331 Dec 202531 Dec 202831 Dec 2030
10.431 Dec 202731 Dec 203031 Dec 2032

How an engagement usually runs

1

Assessment - two weeks, fixed price

We audit the estate, the customisations and the integrations, then give you three costed options and a written recommendation.
2

Delivery - three to nine months

A senior-only team of two to four, working in your process. Upgrades run in parallel with your live platform until cutover.
3

Support - ongoing

We stay on the platform we built. Same people, so nothing is relearned at your expense.

Recent Sitecore work

Sitecore XM Cloud · Next.js · .NET 8 · Azure

Rebuilding the digital front door of an international airport

A 12-year-old WCMS with 30-minute preview waits, replaced over 14 months and six phases. Time-to-publish fell from five to nine business days to under 30 minutes, across 32 contributors and three languages.
Read the case study →

Sitecore questions we get asked

01.
We're on 9.3. What are our actual options?

  • Upgrade to 10.4, which restores mainstream support to the end of 2027 and extended support to 2030 - usually the cheapest way to stop the clock.

  • Migrate to XM Cloud. If you already run a JSS application, the front-end half of that move is a Content SDK migration. Which is a bigger programme and a different platform, not an upgrade.

  • Last but not least, stay put and accept that 9.3 is in sustaining support until the end of 2027 with no security patches coming. Which is right depends on how much of your customisation is worth carrying forward.

02.
Can you take over a Sitecore solution someone else built?

Yes - it is most of what we do. We start with an assessment rather than a quote, because an inherited estate always contains something nobody documented. You get a written map of what is there before either of us commits to a delivery number.

03.
Is an upgrade cheaper than migrating to XM Cloud?

Almost always, and often by a large multiple - an upgrade keeps your customisations and your integrations, where a migration rebuilds the rendering layer and the personalisation rules. The case for XM Cloud is not cost; it is getting off infrastructure you maintain yourself. Decide it on that basis rather than on the licence line.

Let's talk

Thinking about Sitecore?

A two-week fixed-price assessment: current state, three costed options, a written recommendation. No obligation to run the project with us.
Book a Sitecore assessment

Already on XM Cloud? See Sitecore JSS to Content SDK migration

Reply time
~1 business day
Offices
Sofia, Bulgaria