What great technology strategy actually looks like

Our founder spent the early part of his career inside the Canadian telecoms industry, working through one of the largest technology consolidation programmes in the country. This is a first-person account of what he saw — and what it taught him about the difference between technology strategy on paper and technology strategy that actually wins.

What great technology strategy actually looks like

Technology strategy gets talked about in boardrooms like it's a plan you write and file. Something with a Gantt chart and a steering committee. In practice, the best technology strategy I've ever seen didn't look like a strategy document at all.

It looked like a billing migration. And it won Christmas.

Forty-two billing systems

In the early 2000s, a major Canadian telecoms company went on a buying spree. They'd been the dominant player in one province and decided to go national, acquiring smaller telcos scattered across the country. By the time the dust settled, they had — if I remember right — forty-two billing systems running across ten different types of wireless technology. Modern mobile phones, digital radios, wireless data networks, paging systems. A complete mess.

Every one of those acquired companies had its own billing platform, its own processes, its own quirks. Some were sophisticated. Most weren't. And now they were all supposed to operate under one brand.

The Fusion Project

The consolidation project was called Fusion, and the first smart decision was the target architecture. Not one billing system. Two.

The first system handled commodity billing — the bread and butter of telecoms. Minutes attached to a monthly rate plan with fixed additional fees. Straightforward stuff that the industry had largely standardised on. The platform they chose was extremely good at this and extremely inflexible. That was fine. You don't need flexibility for commodity. You need reliability and scale.

The second system handled everything else. Content downloads. WAP data. SMS text packages. These were the newfangled products that legacy telco billing systems had never been designed for. Nobody fully understood how to price them yet. The rules were still being written. This platform needed to be flexible above all else, because the products it would bill for didn't fully exist yet.

Two systems. One rigid and fast for what you know. One flexible and adaptable for what you don't. That's an architectural decision that looks obvious in hindsight but almost never gets made in practice. The instinct is always to consolidate to one. One system, one vendor, one contract. Cleaner. Easier to sell to the board. And almost always wrong when your product landscape is moving.

Three priorities. That's it.

Forty redundant billing systems needed to be retired and migrated without breaking billing continuity — which meant without breaking revenue. Miss a bill cycle and you've got a revenue recognition problem. Corrupt a customer record and you've got a complaint that costs more to fix than the migration saved.

The company ran a conventional priority list for its project portfolio. Normally fifty items long, ranked by business impact. But there was a line drawn on that list — below it, nothing gets done. For three years, that line sat between number three and number four.

Priority one: hardware competitiveness. Do you have phones that match your competitors? If someone walks into a store and you don't have the handset they want, they're walking next door.

Priority two: rate plan competitiveness. If you're offering thirty minutes and your competitor is offering sixty for the same monthly fee, you lose the comparison at the counter. Every time.

Priority three: Fusion. If it wasn't Fusion, it wasn't getting done.

That's discipline. Not the kind you write about in a strategy document — the kind where you look at forty-seven other projects and say no.

The Christmas problem

Here's something about the Canadian telecoms market that might apply elsewhere but was particularly sharp there: roughly fifty percent of annual subscriber volume happened in November and December. People buying phones for themselves in the run-up to Christmas. People buying phones as gifts. And then, one to three years later, those contracts expiring at roughly the same time and the whole cycle repeating.

This created a promotional arms race. On the first of November, every provider would launch their Christmas promotion. Whichever promotion was the most competitive would win the next two weeks — and winning meant taking eighty percent of new activations while everyone else fought over the remaining twenty. Then a competitor would launch a better offer, and they'd win the next two weeks. Four or five promotional cycles across November and December, each one potentially worth the difference between a good year and a bad one.

The constraint was speed. Back then, launching a new rate plan meant modelling the business impact, getting sign-off, implementing the change in the billing system, testing it, deploying it, testing it again in production. A proper waterfall. Compressing that into two weeks was considered aggressive. Most competitors couldn't go faster.

Twelve hours

After Fusion, this company could update rate plans in twelve hours.

Not two weeks. Twelve hours.

A competitor launches a promotion on Monday morning. By Tuesday morning, you've matched it — modelled, built, tested, deployed, live in stores. But here's where it gets interesting. You don't just match it. You beat it. You launch a better offer on that same Tuesday, because you can. And now your competitor is stuck. They're still on legacy billing technology. Their response cycle is two weeks. So for the next two weeks, you own eighty percent of new activations while they scramble to catch up.

When they finally respond, you do it again.

That's what happened across the Christmas selling period. Not for one year — for two or three consecutive years before competitors caught up. The Fusion project, which looked like a boring billing consolidation, had created a capability that directly drove the single most important commercial metric in the business.

The point

Nobody set out to win Christmas. The brief was to retire forty redundant billing systems because maintaining them was expensive and operationally painful. A sensible, defensive, cost-driven programme.

But the architectural decisions — two systems not one, flexibility where you need it, rigidity where you don't — created speed. And speed, in a market with sharp promotional windows, turned out to be the thing that actually mattered.

The technology decisions didn't just support the business strategy. They were the business strategy. The business just hadn't realised it yet.

If your technology stack is holding you back from moving at the speed your market demands, book a coffee with our founder.