Platform strategy
Definition
Platform strategy
Platform strategy is the decision about which underlying technology your business builds on, and why. It covers cloud, core applications, data and integration. The point is to pick a small number of defaults everyone uses, then hold the line on them.
That is narrower than it sounds, deliberately so. A platform strategy is not the commercial question of running a two-sided marketplace, and it is not the internal developer tooling discipline either.
It is also not an architecture diagram. The diagram shows what connects to what — the strategy says which platforms are allowed at all, who decides, and what happens to everything they displace.
Key takeaways
- A platform strategy names the technology defaults the business builds on.
- Fewer platforms, held firmly, beat more platforms chosen case by case.
- Exit cost matters as much as fit, because every choice is reversible at a price.
- The strategy has to say what happens to the systems it replaces.
How it works
A platform strategy works by naming defaults and setting the bar for exceptions. You pick one platform per layer, write down what it is for, and require a written case before anything else gets bought or built.
| Layer | The choice | What it locks in |
|---|---|---|
| Cloud | One primary provider, or several | Skills, pricing, exit cost |
| Core applications | Buy or build | Process shape and upgrade pace |
| Data | Warehouse, lakehouse or both | Reporting speed and tooling |
| Integration | Point to point or a hub | How fast you can add a system |
| Identity | One directory or many | Access control and audit effort |
Start by writing down what you already run. Most organisations find more platforms than they expected, because every team that quietly bought a tool created one.
Most organisations hang the decision off an enterprise architecture framework, which gives you a standard place to record the choice and the reasoning behind it.
Exceptions need a route, not a ban. Give people a short form, a named approver and a review date — otherwise the exception becomes a permanent shadow platform nobody maintains.
Platform strategy is one chapter of a wider information technology strategy. The wider document sets goals and budget; this chapter picks the ground you stand on.
Functions get their own version of the same exercise. A martech stack strategy is a platform strategy for marketing, asking the same questions about defaults and exceptions.
The data layer moves fastest. A modern data stack usually means a cloud warehouse with separate tools for loading, transforming and serving what sits in it.
Running more than one provider is a real option with a real bill. A multi cloud strategy buys negotiating room and resilience, and costs you depth in both.
Exit cost is the number most strategies skip. Ask what it would take to move off each platform in three years, then record the answer next to the choice itself.
Skills follow the platform. Every default you set is a hiring and training commitment — which is why two platforms in one layer usually costs more than twice as much as one.
Sunset the systems you displace. A strategy that names a new default without funding the retirement of the old one has simply added another platform.
Keep the document short. A platform strategy that runs past a few pages stops being read, and a default nobody has read is the same as no default at all.
Shared definitions still matter when you compare offers. The US National Institute of Standards and Technology (NIST) published a cloud computing definition in September 2011 setting out five essential characteristics, three service models and four deployment models.
Public sector choices carry extra requirements before features are even discussed. The US General Services Administration (GSA) states that new or redesigned federal digital services must be accessible, mobile friendly, searchable and securely hosted.
Examples
Platform strategy looks different by sector, but the pattern holds: name the default, fund the migration, and make exceptions prove themselves. Banks, agencies and outsourcing providers all run some version of the same exercise.
Government digital services. Federal agencies in the United States work to a published set of requirements for new and redesigned services, which narrows the shortlist before anyone compares vendor features.
Regulated industries. A bank picking a core banking platform is choosing something it will still run long after the people who chose it have left — so the comparison weighs exit terms and regulatory evidence as heavily as function.
Outsourcing providers. A provider serving many clients standardises on a small set of platforms so staff move between accounts without retraining. Client exceptions are priced separately, which keeps the default attractive.
Outsourced technology functions. When a provider takes over an application estate, the platform strategy becomes contractual: which platforms they must keep, which they may consolidate, and who pays for each migration.
Related terms
- Cloud strategy roadmap: the sequenced plan for actually getting onto the chosen cloud.
- Enterprise integration platform: the hub layer a platform strategy usually has to choose.
- Information technology strategy: the wider plan this decision sits inside.
- Multi cloud strategy: the option of running more than one provider on purpose.
- Modern data stack: the data layer version of the same decision.
FAQ
What is a platform strategy?
It is the decision about which technology platforms your business builds on, plus the rules for departing from them. It names defaults, owners and exceptions.
How is platform strategy different from a platform business model?
A platform business model is a commercial structure that intermediates between two sides of a market. A platform strategy is a technology choice made inside any business, including ones that sell nothing online.
Who owns the platform strategy?
Usually the chief information officer or an architecture board, with named business sponsors per layer. Ownership without a budget is the common failure.
How many platforms should you have?
As few as the work allows. Each extra platform adds skills, contracts and integration points that somebody has to maintain for years.
How often should a platform strategy be reviewed?
Review it annually, and whenever a contract renewal or an acquisition forces the question. A strategy nobody revisits becomes a list of systems you are stuck with.
Find providers who can run your chosen platforms day to day on Outsource Accelerator.
Independent
