A platform company is the business at the centre of a portfolio: the one whose systems, shared services, cadence and reporting other businesses join. The word is used loosely to mean any business that makes acquisitions. It is more useful to define it by capability. A platform company is one that can absorb another business without its own operations breaking. That is an operating test, and many businesses that are large enough to buy others would fail it.
Signals that a business is ready
- The close holds. Books closed on a fixed business day for at least twelve months, reconciled, with a management pack nobody has to rebuild.
- Shared services exist. Finance, people operations, procurement and customer operations run centrally with controls, so a new business has something to join.
- Owners are named. Every core workflow has a single accountable owner who is not the founder, and the weekly review runs whether or not the founder attends.
- Margin is visible by unit. Gross margin by product, location and channel is reported monthly, so the platform knows what an acquisition would add and what it would cost.
- Systems carry the workflow. Ordering, fulfilment, billing, people and reporting run on systems that a second business could be migrated onto, with a documented path.
- The founder governs rather than runs. The founder's week is spent on plan, capital, key relationships and people, not on exceptions.
Signals that it is not yet ready
The inverse of each item above, plus a few specific warnings. The close slips when volume rises. A significant share of process lives in one or two people. The last system implementation was abandoned or is used partially. Management accounts and annual accounts disagree materially. The founder is the sales team. Any one of these means an acquisition would land on a foundation that is already at capacity, and the acquired business would inherit the platform's problems rather than its strengths.
What changes when a business becomes the platform
Three things change. First, the operating layer becomes a product in its own right: it has to be documented, repeatable and transferable, because it will be installed in businesses whose people did not build it. Second, reporting becomes consolidated: one chart of accounts, one close calendar, one management pack across all units, with unit-level detail underneath. Third, the founder's job changes from running a business to governing a system. Capital allocation, integration decisions, leadership of acquired founders and the discipline to say no to available but wrong acquisitions become the work.
The third change is the one to think about hardest. Some founders find governing a system more satisfying than running a business; others find it hollow. It is far better to discover which before the first acquisition than after. The Portfolios page describes the model and its trade-offs.
A platform without acquisitions
It is also possible, and often better, to build a platform company that never acquires anything. The LACQ case study describes a business whose platform is an integrated data and workflow layer running from factory to salon, with three products and a physical operation functioning as one company. The value sits in the integrated network, and growth comes from new stores, regions and product lines joining that network. That is a platform in the sense that matters: an operating layer that can absorb growth without rebuilding process, whether the growth is bought or built.
In the formula this site uses, enterprise value equals sustainable EBITDA multiplied by a market multiple, a platform company is the shape that moves the multiple most. It is larger, more diversified, better reported and less founder-dependent than any of its parts, and it has demonstrated that it can grow. Reaching that shape is the work of the Operating Platform; the decision to use it for acquisitions is separate, and should be made only once the platform is real.
