Halfway through the year is a useful place to stop and look backwards.
Not because the year is over. Because there is still enough runway to change the shape of it, and because the next planning cycle is already being drafted.
Q3 is the quiet season for a specific kind of conversation. The one where finance, operations, and IT sit down and ask what the year actually delivered, separate from what it was supposed to deliver.
In businesses that are scaling, this conversation has been getting harder every year.
The two columns
The cleanest way to run this review is to split the year's IT spend and effort into two columns.
One column is the work the business asked for. A new market. A new product line. A customer-facing improvement. A report leadership has been waiting on. An integration that shortens the sales cycle. An automation that frees a team to do higher-value work.
The other column is the work the platform required. A compliance cutoff. A licensing restructure. A version upgrade. A mandatory migration. A consumption-pricing conversion. A dual-payment overlap during a cloud transition.
Both columns are real work. Both cost money. Both take hours from people who could have been doing other things.
The question is the ratio.
In a healthy year, the first column is bigger. In a year dominated by vendor deadlines, the second one is. Over the past twenty-four months, more businesses are finding that the second column has quietly become the larger one.
What the second column actually costs
The line-item cost of vendor-driven work is easy to see. It shows up as project spend, consulting days, and licensing adjustments.
The harder cost to measure is what those projects displaced.
Every consultant day spent on a forced migration is a day not spent building something customer-facing. Every sprint dedicated to compliance rework is a sprint not dedicated to revenue work. Every IT leader whose Q2 and Q3 were consumed by mandatory projects is a leader who was not in the room when the business was making its most important growth decisions.
There is also a cost that shows up later, in team energy.
When a high-performing team spends a year running to stand still, something shifts. The best people start asking whether the work they are doing is creating anything that lasts. Some of them stop asking. Some of them leave. The ones who stay learn to manage expectations downward. None of this appears in the budget.
What the two columns looks like in practice
Here is what we typically see when we run exercise with organisations on legacy enterprise platforms.
Column one — the work the business asked for includes items like: automating a purchase approval chain that was running through email, building a customer portal to reduce support ticket volume, connecting the sales pipeline to invoicing so no-one re-keys the same data, or generating a consolidated P&L report that previously took two people three days to assemble manually.
Column two — the work the platform required — includes items like, migrating off a compatibility pack before the vendor's May deadline, upgrading from a version hitting end-of mainstream maintenance, converting to a consumption-based licensing model to about audit exposure, onboarding an AI feature sold as a separate unit outside the base licence, or paying dual maintenance fees during a cloud transition overlap.
The contrast is usually stark. Column one is where the business moves forward. Column two is where it runs to stand still.
Why Q3 is the moment
The reason this conversation belongs in Q3, not Q4, is planning.
Q4 is when next year's budget gets finalised. By then, the shape of the year is mostly set. The vendor-driven line items are baked in first. Whatever is left is divided between the things the business actually wants to do.
Q3 is when there is still time to challenge the shape, not just the numbers.
Challenging the shape means asking a different set of questions.
What projects are already claimed on our 2027 capacity, and who claimed them? How many of those projects were chosen by us, and how many were inherited from a roadmap we do not control? If a vendor-driven project was not mandatory, would we still be doing it? If the answer is no, what is it actually buying us?
These are uncomfortable questions. They are also the ones that separate a planning cycle that moves the business forward from one that just keeps it compliant.
The 2027 layers already visible
For most businesses running mature enterprise platforms, the 2027 layer is already forming. Another version hitting end of mainstream maintenance. Another push toward consumption-based licensing. Another set of AI capabilities being sold as separate units rather than included in the base. Another audit framework being applied to integrations that were infrastructure five years ago.
None of these are surprises. They are visible on vendor roadmaps today.
The question is not whether these layers will land. They will. The question is whether your 2027 plan is being built around them, or around the business you are trying to become.
If the answer is the first, the pattern from 2026 will repeat, and the ratio between the two columns will stay where it is, or shift further.
If the answer is the second, something has to change. Not the team. Not the discipline. The platform underneath.
What a different platform ratio looks like
There is a reason the two-column persists year after year on legacy enterprise platforms: the architecture was built around large, infrequent upgrade cycles. Each cycle generates a wave of mandatory work — migrations, license restructuring, re-resting, retaining — that fills column two regardless of what the business actually needs.
Odoo was designed around a different assumption. Annual releases are included in the subscription. There are no forced migration projects. No compatibility pack expirations. No consumption-pricing conversions. No dual-maintenance billing during transitions. No AI features locked behind separate unit purchases — the capabilities ship with the platform.
The practical effect is that column two shrinks dramatically. Not to zero — every platform requires some maintenance — but to a level where it stops displacing the work in column one.
That changes the ratio. And the ratio is what determines whether your IT capacity is building the business forward or servicing the platform it runs on.
This is not a theoretical argument. It is a structured one. The two-column exercise surfaces it, and the platform architecture determines which side the weight falls on.
The honest Q3 check
Before the 2027 planning locks in, run one honest check.
Look at this year's two columns. Calculate the ratio. Then look at the 2027 capacity already claimed on your roadmap and calculate the same ratio for next year.
If the ratio is getting worse, not better, that is the signal. Not to panic. Not to rip and replace. Just to widen the conversation before the budget closes.
The best time to ask whether the platform is still working for the business is before the next planning cycle commits you to another year of the same answer.
Map your two columns
Book a short walkthrough with the Wiz.Asia team. We will help you split this year's IT spend into two columns — the work your business asked for and the work your platform required — and calculate the ratio heading into 2027.
You will leave with a clear picture of where your capacity is going and a scoped view of what the ratio would look like on a platform where column two does not consume the year.
No pitch. No obligation. The clarity is yours to keep whether you move forward or not.