Power Apps articles
What drives the cost of a Power Apps development project?
A Power Apps development cost is really three numbers, not one: a one-time build fee set by scope, a recurring Microsoft licence fee set by which connectors the app touches, and a run cost for changes and capacity after go-live. Most confusing quotes are simply those three bundled differently.
Three costs hiding inside one quote
Separating the three is the single most useful thing you can do before reading any proposal. Build cost is one-time and set by scope. Licence cost is recurring, set by Microsoft, and identical whoever builds the app. Run cost is irregular and depends mostly on how well the app was built in the first place.
| Cost type | What it covers | Shape | Who sets it |
|---|---|---|---|
| Build cost | Requirement mapping, data model, screens and forms, permissions, integrations, testing, deployment, training and documentation | One-time, scope-driven | Your consultancy or internal team |
| Licence cost | Power Apps and Dataverse entitlements for each person who opens the app | Recurring, per user per month | Microsoft, at published list prices |
| Run cost | Change requests, storage above your included capacity, environment and release housekeeping, support | Recurring but irregular | Shared — driven by build quality |
Most of the confusion in this market comes from vendors answering a different question than the one you asked. A page titled “Power Apps pricing” usually means licensing. A page written by a development shop usually means the build. They are not substitutes, and a budget built on one of them alone will be wrong by the size of the other.
The scope drivers behind a build quote
Five factors explain nearly all of the spread between a small app and a large one, and none of them is visual design. Ranked by how much effort they typically add: the data model, the number of screens and roles, integrations, offline capability, and migrating the data you already have. Ask any vendor to price them as separate lines.
| Scope driver | Keeps the quote lower | Pushes the quote higher |
|---|---|---|
| Data model | One or two SharePoint lists with simple columns | Many related tables, lookups and business rules in Dataverse |
| Screens and roles | A handful of screens, one user role, one approval path | Dozens of screens, several roles, conditional routing per department |
| Integrations | Stays inside Microsoft 365 — SharePoint, Outlook, Teams | ERP, CRM or line-of-business APIs, each with its own auth and edge cases |
| Offline capability | Users always have a connection | Field crews capturing data offline, with sync and conflict handling |
| Existing data | Starts empty, or a clean export | Years of spreadsheet history to de-duplicate, map and migrate |
| Compliance and security | Ordinary business data, tenant defaults | Row-level security, audit trails, data-loss-prevention policies to satisfy |
The data model is where budgets quietly double. A request phrased as “just a form” often turns out to need customers, sites, assets, jobs and photos as related tables before a single screen is worth building — and Microsoft's own guidance on Dataverse security roles and privileges (opens in new tab) shows why the permission layer is engineering work rather than configuration. When the data layer is the substantial part of the job, we scope it separately as Microsoft Dataverse consulting services so you can see what you are paying for. The shape of the build moves the quote as much as the table count does, and in opposite directions for build cost and ownership cost — canvas apps vs model-driven apps explains which processes justify a generated model-driven interface and which are a single canvas screen.
Offline is the other driver that surprises people. An app that must keep working in a basement or on a rural site needs local caching, sync logic and conflict rules — a genuinely different build from the same screens online, as Microsoft's guidance on building offline canvas apps (opens in new tab) makes clear. If that is your situation, our page for a Power Apps consultant for construction companies covers those field builds in detail.
What Microsoft charges once the app is live
Licensing is the one part of the number that does not depend on who builds the app. The rates below are Microsoft's own published list prices, not ours. The single most important thing to know is that many apps need no incremental licence at all: if the app stays on standard connectors, most Microsoft 365 business plans already include the rights to run it.
| Plan or add-on | Microsoft list price | What it is for |
|---|---|---|
| Standard connectors only | No incremental cost | Apps on SharePoint lists, Outlook, Teams and Office 365 users, running on rights seeded in most Microsoft 365 business plans |
| Power Apps Developer Plan | Free | Individual, non-production environments for building and learning |
| Power Apps Premium | $20.00 per user/month, paid yearly | Production apps that use Dataverse or premium connectors |
| Power Apps Premium (2,000-seat minimum) | $12.00 per user/month, paid yearly | The same rights at large deployment volumes |
| Dataverse Database Capacity | $40.00 per GB/month, paid yearly | Storage beyond the capacity your tenant already includes |
Prices above are Microsoft's, taken from Microsoft's Power Apps pricing page (opens in new tab) and checked on September 11, 2026; Microsoft changes them without reference to us, so confirm the current rate before you build a budget on it. One correction worth making loudly: Microsoft's pricing page no longer offers a per-app plan, so any cost guide still quoting a $5 per-app option — and there are many — is working from a retired price list. For how entitlements map to environments and capacity, Microsoft's licensing and billing reference (opens in new tab) is the source of record. The per-app picture is channel-dependent rather than simply closed — Microsoft withdrew the SKU from new customers in January 2026 but left CSP purchasing intact — and we work the rules and the break-even through in Power Apps licensing for small business, which covers the recurring per-user side of this page in full.
Run cost: what continues after go-live
Three things carry on. Licensing continues for as long as people use the app. Storage becomes a line item only if the app outgrows the Dataverse capacity your tenant already includes — Microsoft documents how that capacity is measured and reported (opens in new tab), and it is worth checking before assuming an add-on is needed. And change work continues, because processes change.
Change work is the item you can actually influence, and you influence it at build time. An app shipped with a sane data model, solution files under Power Platform application lifecycle management (opens in new tab), and written documentation costs a fraction to modify compared with an app assembled directly in production by someone who has since left. That is the honest argument for paying for build quality: it is a purchase of cheap future changes.
Why two quotes for the same app look nothing alike
Compare deliverables, never headline numbers. The cheapest quote usually excludes the parts you only miss later: the data model, the security roles, the test pass, the documentation, the training session, and a defined support window. It may also assume your data is clean, which is a change order waiting to happen. Location matters too — US, nearshore and offshore rates differ several-fold for the same hours.
The billing model matters as much as the rate. A fixed fee forces the vendor to scope precisely before starting and puts overrun risk on them; hourly suits genuinely open-ended work. We wrote up the trade-off in full in fixed fee versus hourly consulting, and the same reasoning drives our Power BI equivalent of this page, what a Power BI dashboard costs.
The rival-platform argument, answered honestly
Several low-code vendors bid on this exact search term to argue that Power Apps gets expensive at scale. The fair part of that argument: if every user of your app needs Dataverse or premium connectors, per-user licensing does add up, and the jump from standard to premium connectors is a real cliff rather than a gentle slope. Worth knowing before you design the app, not after — our guide to Dataverse vs SharePoint lists for Power Apps covers which requirements genuinely push a build over that line, and which do not.
The unfair part: those comparisons usually price Power Apps Premium against their own subscription while ignoring the Microsoft 365 rights you already pay for, the tenant your data already lives in, and the identity, security and backup story you would have to rebuild elsewhere. The build-versus-buy question deserves its own framework rather than a vendor's arithmetic — ours is in Power Apps versus buying software, which covers when a packaged product is genuinely the better call.
Getting to a number you can actually approve
Bring three things to a scoping conversation and almost any competent consultancy can price the work: a walkthrough of the process as it runs today, a list of the systems the app must talk to, and a decision on who needs access. That is usually enough to settle the data model, the connector tier, and therefore both the build and the licence line.
That is how our own fixed-fee Power Apps consulting works — a free scoping conversation, one written price with the deliverables listed, senior US-based engineers, typical 2–4 week delivery, and 30 days of hypercare after go-live. You own the app, the solution files and the data outright. See how the engagement runs if you want a scoped number for your own process.
FAQ
Budget questions people ask before they build
Because the same two-word request — “an inspection app” — can mean six screens on a SharePoint list or forty tables in Dataverse with offline capture. Scope, not the platform, sets the fee. A short scoping call converts the request into a countable list of screens, tables, roles and integrations that can be priced honestly.
No. Apps built only on standard connectors — SharePoint lists, Outlook, Teams, Office 365 users — run under rights already seeded in most Microsoft 365 business plans, so the incremental licence cost is zero. Paid licensing starts when the app uses Dataverse or premium connectors; Power Apps Premium lists at $20 per user per month.
Not on Microsoft's current pricing page. Older cost guides still quote a per-app plan, and budgets built on it will be wrong. As of September 11, 2026 Microsoft lists a free Developer Plan for non-production work and Power Apps Premium for production apps. Always confirm the rate on Microsoft's page before budgeting.
Five things, roughly in order: how many tables and relationships the data model needs, how many screens and roles exist, how many systems the app integrates with, whether it must work offline, and how much existing data has to be cleaned and migrated. Visual polish is the cheapest part.
Three: Microsoft licensing for whoever uses the app, Dataverse storage if the app outgrows the capacity your tenant includes, and change work as the process evolves. There is no mandatory maintenance retainer. A documented app with clean solution files keeps that change work small, which is why build quality is a cost decision.
Related reading
Before you request quotes
Build vs buy
The decision framework that comes before the budget: when a packaged product genuinely wins.
Fixed-Fee Power Apps Service
One written price, senior US-based engineers, typical 2–4 week delivery, 30 days of hypercare.
What a dashboard costs
The same cost breakdown applied to Power BI reporting, with the drivers that move the number.
Book a free consultation
Get more from the Microsoft tools you already pay for
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
- Fixed-fee scope agreed before any work starts
- Senior, US-based Microsoft engineers — no handoffs
- Typical 2–4 week delivery
- 30 days of post-delivery hypercare included
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.