The champagne moment is a dangerous one.
I don't mean that metaphorically. Well, I do - but it's also literally true. I've been in the room when a firm launches a new platform, everyone applauds, someone opens a bottle, and within about forty-five minutes the conversation has moved on to whatever's next on the board agenda. The website's live. The CRM integration works. The portal doesn't crash. Job done. Let's talk about something else.
And then, slowly - over weeks, then months - the thing starts to rot.
Not dramatically. Nobody wakes up to a broken website. It's more like a new kitchen that nobody cleans. Beautiful on day one. By month three there's a drawer that sticks and nobody's fixed it. By month six the grout's discolouring. By year two you're apologising for the state of the place when guests come round - and quietly wondering whether you should just redo the whole thing.
I've seen this so many times that I'd almost call it the default outcome of digital transformation in mid-sized B2B firms. The build gets done. The launch happens. And then the thing gets quietly abandoned to whoever happens to be nearby.
We'll cross that bridge when we come to it. Let's just get the project delivered first.
I hear this in almost every project kick-off. And honestly, I get it - when you're mid-transformation, juggling stakeholders, wrestling with scope, trying to keep the budget from inflating, the last thing you want to think about is what happens after. It feels like planning your retirement on your first day at work. But the commercial reality is this: a successful launch is the starting line. And firms that don't plan for what comes after lose most of the value they've just paid to create.
Let me describe what typically happens. A firm spends, say, £250,000 on a new digital platform - could be a website rebuild, a client portal, a CRM integration. The project runs for four to six months. There's a discovery phase, a design phase, a build phase, a testing phase, and a launch. Senior people are in meetings. Decisions get made. It's intense, it's expensive, and it works.
Then the agency invoices their final milestone and moves on. The internal team - who were already doing their day jobs alongside the project - breathe a sigh of relief and go back to doing their day jobs full-time. Nobody's tasked with monitoring performance. Nobody's measuring adoption. Nobody's optimising anything because nobody's been asked to.
Six months later, the content is stale. The blog hasn't been updated since launch week. The analytics dashboard that was carefully configured during the build hasn't been opened in three months. The personalisation rules that everyone got excited about in the demo are still set to their defaults. A new joiner asks "why does the portal work like that?" and nobody can remember.
This isn't a technology failure. It's an ownership failure. And based on what we've seen across 170-plus projects over the past two decades, fewer than one in three firms have a credible plan for what happens after launch.
So what does good look like? I'll be specific, because vague advice about "continuous improvement" helps nobody.
The first thing to get right is measurement - and I mean proper measurement, not vanity metrics. Not page views or "engagement" in the abstract, but the specific commercial indicators you identified in the business case. Enquiry volume. Conversion rates. Time-to-publish for the content team. Portal adoption rates. Whatever the original problem was, you should be tracking whether it's been solved. If you can't demonstrate the investment is delivering returns, the budget for ongoing optimisation will be the first thing cut when things get tight.
After that, you need a regular optimisation rhythm. Quarterly works for most firms. Every three months, review performance data, identify what's working and what isn't, and make targeted improvements. This isn't a redesign - it's a focused sprint, maybe two or three days of work, to address what the data is telling you. A form that's getting abandoned at step three. A service page with high traffic but no conversions. A piece of content that's ranking well but leading nowhere. Small interventions, done consistently, add up faster than you'd expect.
Then there's adoption - which gets overlooked constantly. You've built a platform that gives your content team editorial independence, or your partners a self-service dashboard, or your clients a better way to interact with you. But are they actually using it? Adoption doesn't happen automatically. People revert to old habits unless someone is watching the numbers and doing something about it when usage drops.
I worked with a professional services firm - mid-sized, financial advisory, about 180 people - that built a genuinely excellent client portal. Fast, well-designed, intuitive. Six months after launch, I asked how it was going. Turns out fewer than 20% of clients had logged in more than once. The technology was fine. The onboarding and communication around it had been, well, nonexistent. Nobody had thought to tell clients it existed in any meaningful way, and nobody had been watching the adoption numbers because nobody had been asked to. The portal just sat there, quietly not being used, while the team continued emailing PDFs back and forth like it was 2011.
Content is the other one. A new platform without a content plan is a sports car without petrol - looks gorgeous on the drive, goes nowhere. Someone needs to own the editorial calendar. Someone needs to be responsible for updating service pages when propositions change, for making sure the thought leadership section doesn't become a graveyard of posts from launch month. This sounds obvious. And yet.
And then there's the unglamorous stuff: security patches, CMS updates, plugin compatibility checks, SSL renewals, hosting performance monitoring. None of it is interesting. All of it is essential. If you've read our guide on the fragility of digital foundations, you'll know that neglecting platform maintenance compounds fast - and the longer you leave it, the more expensive and risky the catch-up becomes.
Ongoing post-transformation investment typically runs at 15-25% of the original build cost, annually. So if you spent £250,000 on your transformation, you should be budgeting somewhere between £37,500 and £62,500 a year to keep it healthy, optimised, and delivering returns.
I know. I've watched the expression change in real time.
But think about it this way. If you spend £250,000 on a new platform and then invest nothing in maintaining or improving it, the value of that investment starts depreciating from day one. Customer expectations keep rising. Competitors keep improving. Content goes stale. The gap between what you've got and what good looks like widens every quarter. Within two years, you're back where you started. Within three, you're having the same conversation about needing a rebuild - and wondering where the last quarter of a million went.
If you spend £250,000 on the build and then £50,000 a year on ongoing optimisation and maintenance, you're protecting the original investment and compounding its returns. That £50,000 a year isn't a cost. It's the thing that turns a one-off project into a long-term commercial asset.
Earlier this year I was in a board meeting with a mid-sized consulting firm - about 200 people, strategy and operations work, the kind of firm that's been around long enough to have opinions about everything. We were there because their digital platform, which they'd invested heavily in eighteen months earlier, had quietly stopped performing. The CEO - not someone who minces words - said something I've been quoting since. "We spent eighteen months and a quarter of a million pounds getting to this point, and then we just... stopped paying attention." He wasn't angry about the original investment. He was frustrated that nobody had put the ongoing commitment in front of him at the start. "I'd have budgeted for it," he said. "Someone just needed to tell me."
That's on us, as an industry. Agencies and delivery partners scope the build. The aftercare gets left as "TBC" or quietly dropped from the conversation because it's easier to close the deal without it. It's like selling someone a house and not mentioning that roofs need maintenance.
This is the shift I'd push for. If you're about to embark on a transformation - or if you're mid-way through one right now - build the post-launch plan into the original business case. Not as an afterthought. Not as a line item that says "ongoing support TBC." As a costed, scoped, committed component of the programme.
That means including year-one and year-two post-launch budgets in the investment case you present to the board. If the board approves £250,000 for the build, they should also be approving £50,000 per year for ongoing optimisation. Separate those conversations and the second one never happens - because by the time launch is done, everyone's attention has moved on and nobody wants to go back asking for more money.
It also means defining who owns the platform after launch. Not which team. Which person. Someone with the authority to make decisions, the time to monitor performance, and the accountability for outcomes. "Marketing will look after it" isn't an answer. Which person in marketing? How much of their time? What are they measured on? If you can't answer those questions before launch, you don't have an owner - you have a vague intention.
And agree the optimisation rhythm in advance. Quarterly works for most firms, with monthly check-ins in the first six months while adoption is still building. Whatever the cadence, agree it before launch and put the dates in the diary. I'm a broken record on this, but it's the single most effective thing you can do - because if the dates are in the diary, the reviews happen. If they're not, they don't. Simple as that.
This is where I'll mention our WHNN framework - and yes, I'm aware that "not because I'm trying to sell it" is exactly what someone trying to sell something says, so let's skip that bit. I'm mentioning it because it was designed specifically to solve the drift that happens after the initial energy of a transformation programme fades, and it works.
WHNN runs on a quarterly cycle. Every three months, you bring the leadership team together to review what's working, reassess priorities, and make decisions about where to invest time and money next. What did we set out to achieve? What's the data telling us? What needs to change? What are we committing to for the next ninety days?
The reason this matters post-transformation is that without a structured cadence, the optimisation work just... doesn't happen. Everyone agrees it's important. Nobody schedules it. Three months pass, then six, then twelve, and suddenly you're in a meeting where someone says, "Has anyone actually looked at the website analytics since we launched?" and the silence tells you everything.
Most firms I talk to have no equivalent rhythm for their digital investment. They review financial performance quarterly, they review sales pipeline weekly, but their digital platform? That gets looked at when something breaks or when someone important complains.
If you want something practical to take away from this, here's what I'd focus on in the first three months post-launch - written as prose rather than a checklist, because you're a grown-up and you don't need bullet points to tell you to check your forms are working.
In the first two weeks, confirm your analytics are tracking correctly and check every conversion point. You'd be amazed how often a form breaks during the final pre-launch scramble and nobody notices for weeks because everyone assumes someone else is checking. It's always someone else's job until it's nobody's job.
From week two to four, watch adoption. Are the people who are supposed to be using the new platform actually using it? Content editors, partners, clients - whoever your key user groups are, check. If adoption is low, find out why. It's almost always a training or communication issue, not a technology issue. The technology is fine. Nobody told anyone it existed.
By month two, run your first proper performance review. Compare against the baseline metrics you captured before the transformation. Where are you seeing improvement? Where aren't you? Be honest. If a section of the site isn't performing, that's useful information - not a failure, just a signal.
Month three: first optimisation sprint. Based on the data from month two, pick three to five specific improvements and make them. Not a wish list. Three to five things, prioritised by impact, delivered in a focused burst. Then repeat. Every quarter. For as long as the platform is live.
The firms that get the most value from their digital transformation aren't the ones that spend the most on the build. They're the ones that treat launch as the beginning of an ongoing commitment - and who had the foresight to budget for it before the champagne was opened.