What a digital platform actually is
"Digital platform" is one of those phrases that survives because it is vague. It gets used for a website, for an app, for a spreadsheet with ambitions. Underneath it there is a real and quite specific idea, and it is worth having the plain version.
A platform is software that more than one kind of person logs into, to do different things, with the same underlying information.
That is the whole definition. A brochure site has visitors. A shop has customers. A platform has at least two sides, and the value is in what happens between them.
What that looks like in practice
A recruitment system where candidates apply, employers post and a coordinator manages both. A reporting system where site managers submit numbers and head office reads them. A trade portal where customers order at their own prices and your office sees every order in one queue. Different industries, the same shape: several roles, one set of data, one version of the truth.
The three questions that decide whether you need one
- Does more than one kind of person need in? If only your staff use it, you need an internal tool, which is a simpler and cheaper thing. If customers, suppliers or partners need in too, you are in platform territory.
- Do they need to see different things? This is where the cost lives. Not the screens, the permissions: who can see what, who can change what, and what must never leak from one account to another.
- Is the information currently in several places? If the same fact lives in a spreadsheet, an inbox and somebody’s head, the platform’s first job is to make one copy that everybody reads.
Where these projects actually fail
Not on features. They fail on permissions and on accounts nobody tested properly, which is also where they cause real damage: one customer seeing another customer’s data is not a bug report, it is a phone call you remember.
They also fail by being built for everybody at once. The version that works starts with one role doing one job end to end, in use, before the second role is added. A platform launched with four half-finished sides is four groups of people disappointed on the same day.
What to insist on before anybody builds anything
A written list of roles and, for each, what they can see and what they can do. One page, in plain English, agreed before the design. Every expensive surprise in this kind of project is a line that was missing from that page.
The build side of this is on digital platforms. If what you actually need is one role and one job, that is usually custom software instead, and it costs less.