What Microsoft Power Platform Actually Costs a Small Business

Introduction

When founders of small service businesses start looking seriously at the Microsoft Power Platform as the technical foundation for their operational systems, the first question they ask is almost always about cost. What does it cost. What is the licence per user. Is there a cheap version. Is it more or less expensive than the alternatives they have been considering. The questions are reasonable. The pricing is genuinely confusing. And the honest answer is that the licence cost is rarely the cost that actually matters.

This is not because Microsoft licensing is irrelevant. It matters, and there are real differences between the licensing options. But for a small service business considering the Power Platform, the licence is one of three distinct costs that together determine what a Power Platform implementation actually costs. Focusing on the licence in isolation is the same mistake as focusing on the cost of a car’s number plate when deciding whether to buy the car. It is a real cost, it is part of the total, and it is by far the smallest part.

The three costs are the platform licensing itself, the implementation work to build something useful on the platform, and the operational impact the platform has on the business once it is in place. For most growing service businesses, the operational impact is the largest part of the equation by an order of magnitude, in either direction. A well-implemented Power Platform produces operational improvements worth many times the licence cost. A poorly-implemented one produces ongoing operational drag worth many times the licence cost. The licence cost is real, but it is rarely what determines whether the investment was a good one.

This post walks through all three honestly, with ballpark numbers for a small service business, so the actual cost picture is visible rather than guessed at.

The licensing layer

The Power Platform licensing structure has changed multiple times over the last several years, and any specific pricing here may be out of date by the time you read it. The honest move is to give the shape rather than precise numbers, and to recommend checking the current pricing directly with Microsoft or a partner before making any decision.

In broad terms, a small service business looking at the Power Platform is choosing between two main licensing approaches. The first is per-user licensing for Power Apps, where each user has a licence that lets them access the apps you build. The cost is typically in the range of a few pounds to about twenty pounds per user per month, depending on the licence level. For a five to fifteen person service business, the total licensing cost sits somewhere in the hundreds of pounds per month range, which is small relative to most other operational spend.

The second is per-app licensing, where a specific app has a flat licence that covers all users. This works better for smaller businesses with a single core app, but Microsoft has moved away from this model in recent years, so it is less commonly the right choice now than it was. The per-user approach is more common and more flexible for businesses likely to build out across multiple operational systems.

There are also additional costs for Power Automate flows that run frequently, Power BI for reporting, Dataverse for structured data storage, and Power Pages for client-facing portals. Each of these has its own pricing, and for a small business they are often included in bundle pricing or covered by the per-user licence depending on usage levels. The total stack, fully licensed for a ten-person service business, typically lands somewhere in the range of a few hundred pounds per month, depending on what you actually use.

This is the cost most founders focus on. It is real. It is also, for almost any service business considering the Power Platform seriously, the smallest of the three costs in the picture.

The implementation layer

The platform itself does not do anything until something is built on it. The Power Platform is, conceptually, a set of tools for building business applications. The applications themselves still have to be designed, built, configured, and integrated. This is the implementation cost, and for most service businesses it is meaningfully larger than the licensing.

The shape of implementation cost depends heavily on what is being built. A simple CRM system built in Power Apps for a small team might be a project of a few thousand pounds with a small partner or consultancy. A full operational platform covering CRM, project delivery workflows, reporting dashboards, and a client portal might be ten to twenty thousand pounds or more, depending on scope and complexity. The variance is large because the projects themselves vary enormously in what they cover.

Castlane’s own pricing for Power Platform projects, as covered in the Castlane package architecture for the CRM and sales pipeline pillar, illustrates the range. A Gold-tier CRM platform build typically sits between four and seven thousand pounds. A Platinum CRM infrastructure project, which connects to wider business systems, typically sits between eight and sixteen thousand pounds. These are deliberately ranges rather than fixed numbers, because the scope of each project depends on the specifics of the business. The numbers are honest, current, and broadly representative of what a small service business should expect to pay for a Power Platform implementation done properly.

The implementation cost is paid once, although it usually has a small ongoing component for adjustments, refinements, and new features as the business grows. Most service businesses underestimate this layer relative to the licensing layer, which is the opposite of how the maths actually works. The implementation is where most of the spend sits, and it is where the value gets created or lost.

It is worth being honest about something specific here. A Power Platform implementation done badly is genuinely worse than not doing it at all. Many service businesses have bought into the platform, paid for a partial implementation that was never quite finished, and ended up with a system the team does not trust and the founder cannot rely on. The licensing keeps being paid, the implementation cost has been spent, and the value is negative because the system is now a drag rather than an asset. As covered in the piece on what a CRM cannot do for you, the tool is only part of the answer, and a Power Platform without the surrounding operational design is exactly the same problem. The implementation cost is real money, and it has to be spent on a complete and properly-designed implementation, or the money is largely wasted.

The operational impact layer

This is the cost most founders never calculate, and it is almost always the largest number in the picture, in either direction.

A Power Platform implementation that does its job changes how the business operates. The right systems being in place produces real, measurable operational improvements. The pipeline runs more cleanly. Leads do not slip. The team coordinates without the founder being the routing layer. Reporting is current rather than reconstructed. The founder’s time is freed for strategic work rather than operational fire-fighting. The compound effect of these improvements, across a year, is large. For a growing service business, the operational impact of a well-implemented Power Platform is often worth several times the combined cost of licensing and implementation, sometimes by an order of magnitude.

The other direction is also real, and worth being honest about. A poorly-implemented platform, or one bought before the operational maturity to use it is in place, produces ongoing drag rather than improvement. The team works around the system rather than through it. The data is incomplete. The dashboards are not trusted. The founder still does the work the system was supposed to do. The licensing cost continues being paid, the implementation cost has been sunk, and the operational impact is negative because the business is now carrying a system that does not work for them. The cost of this scenario, summed across a couple of years, can easily reach into the tens of thousands of pounds of operational drag, on top of the direct costs.

This is the cost that should dominate the calculation, and almost never does. Founders focus on the licensing because it is the most concrete and the most easily compared. They underweight the implementation because the implementation cost is variable and the value is hard to quantify in advance. And they ignore the operational impact almost entirely, because it does not appear on any invoice. The result is that the largest part of the cost equation is the one founders pay the least attention to, in either direction.

What the honest cost picture looks like

For a ten-person service business implementing the Power Platform properly, the honest cost picture for the first year looks roughly like this. Licensing costs in the range of two to five thousand pounds for the year, depending on the configuration. Implementation costs in the range of five to fifteen thousand pounds, depending on scope. And operational impact, positive or negative, that is likely to be worth somewhere between two and ten times the combined direct cost, depending entirely on whether the implementation was done well.

The decision worth thinking about is not “is the licence fee worth it”. The licence fee is small relative to the impact. The decision is “will the implementation be done in a way that produces operational improvement, or in a way that produces operational drag”. That is the question that determines whether the investment was a good one, and it is much more about who is doing the work, how the operational design is approached, and whether the business is ready to actually use what gets built, than it is about the platform pricing.

This is why the platform-versus-platform comparison, which most founders are inclined to do at the start, is the wrong frame. The Power Platform versus a competing CRM versus a different stack are all fundamentally similar at the licensing level. The differences between them are real but small. The much larger differences are in how the implementation gets done, who does it, and whether the operational design surrounds the platform properly. A well-implemented competing system is much better than a poorly-implemented Power Platform, and vice versa.

What this means in practice

If you are considering the Power Platform for your service business, the operational maths to do first is not the licensing comparison. It is the question of whether your business has the operational maturity to make use of what gets built, and the implementation partner can be trusted to design the platform around your actual operations rather than just install the technology. As covered in the piece on what operational maturity actually looks like, the readiness to use a platform like this is itself a structural condition. A business at the wrong stage will not get the operational impact, regardless of how good the platform or the implementation is.

If those conditions are met, the Power Platform is a strong foundation for the operational infrastructure of a growing service business, and the total cost is small relative to the value. If those conditions are not met, no platform will produce the impact, and the spend would be better directed at the operational design work that creates the readiness in the first place.

The honest answer to “what does the Power Platform cost” is that the licence fee is the small part, the implementation is the medium part, and the operational impact is the part that actually determines whether the investment was worth making. Focusing on the first while ignoring the third is the most common mistake, and it is the one that produces the cases where founders later conclude the platform was not worth it. The platform usually was. The implementation was not.

If you are weighing up the Power Platform for your business and want a realistic picture of what the implementation would look like, what it would actually cost, and whether your operational maturity supports it, book a free 30-minute Systems Consultation. We will work through the honest cost picture for your specific situation. Book a consultation here.