How Much Does a Power Apps App Cost? The 7 Cost Drivers

"How much does it cost?" is the first question, and it is the right one. The honest answer fits in one sentence: the cost of a Power Apps application depends on what it does, what it connects to and who uses it. That is not a dodge, it is a list. Here are the seven drivers that move the price, then how to read a quote, and why we work at a fixed price, set at scoping.

The seven drivers of a Power Apps application's cost

1. Scope. How many processes does the app cover? A leave request is a form, an approval and a calendar. A sales pipeline is customers, quotes, follow-ups and indicators. Scope is the first multiplier, and it is what scoping freezes.
2. Number and complexity of screens. A list screen and a form cost little. A drag-and-drop schedule, an editable pivot grid or a screen that adapts to three different roles cost noticeably more. Count the screens, but above all spot the ones that are out of the ordinary.
3. Connections to your tools. Sending an Outlook email or posting in Teams is standard. Reading your ERP, your payroll software or an in-house API means a premium connector or custom development, with integration testing. Each connection is estimated separately.
4. Data. Starting from a clean database or from an Excel file full of duplicates is not the same job. Cleaning and migrating existing data is a line item in its own right, and the choice between SharePoint and Dataverse changes both the effort and the licensing.
5. Business rules. A two-level approval chain, different permissions per department, pricing calculations with exceptions: each rule is designed, coded and tested. It is often the most underestimated driver, because the rules live in people's heads.
6. Microsoft licensing. It is not in the vendor's quote, but it is part of the cost. With standard connectors and data in SharePoint, your Microsoft 365 licences are enough. With Dataverse or a premium connector, expect a Power Apps licence per user, around 20 euros (or dollars) per user per month for the full licence, less for a licence limited to one app; check the current Microsoft price list. Our article on what is included and what is premium helps you plan for it.
7. Maintenance. An app lives: Microsoft updates the platform, your processes change, a user finds a case nobody planned for. Plan for either a fixed-price maintenance plan or a trained internal owner.

What costs nothing, or almost

Worth saying too. No hosting to pay for: the app runs inside your Microsoft 365. No server, no backups to organise, no subscription to a third-party vendor. And the data stays with you. That is what often makes a Power Apps application cheaper over three years than off-the-shelf software, especially when it replaces two or three of them.

How to read a Power Apps application quote

A quote is read as a scope, not as a price. Here are the questions to ask.

• Is the scope written down, screen by screen and rule by rule? A quote that says "job management application" with no detail commits to nothing.
• What is excluded? Data cleaning, history migration, training, licences: each item must be named, included or not.
• Who tests? If acceptance rests entirely on you, with no support, budget your teams' time.
• What does the warranty cover, and for how long? A functional bug fixed with no invoice for a set period is the minimum.
• Who owns the app? It must sit in your tenant, under your name, with its documentation. You must be able to change vendor.
• Is it time and materials (days billed as they go) or a fixed price (one price for one scope)?

Time and materials or fixed price: who carries the risk

With time and materials, you pay for days. If the project slips, you pay more. The risk sits with you. With a fixed price, the vendor commits to a price for a written scope. If their estimate was too short, that is their problem, not yours. The risk sits with them.

A serious fixed price therefore requires serious scoping. Nobody can commit to a price without having seen the process, the data and the users. That is why the price is set at scoping, never before. A two- to three-day scoping produces the written scope, the mockup and a firm price for the build. You then decide with a known price, or you walk away with the scoping and have it built elsewhere.

What you can do right now

Describe your need in ten lines: who enters data, who approves, what it connects to, how many people use it. Count the rules you already know. Check whether your data sits in a clean database or in a spreadsheet that has lived a long life. With those elements, a vendor can tell you which family of project you are in, before even pricing it. Our online pre-scoping asks exactly those questions, in a few minutes.