Disclosure and a caveat. We build PSA Hub. This is a vendor comparison and you should weigh it as one.
Microsoft changes Project Operations' packaging and pricing regularly. Figures here reflect publicly reported list pricing in early 2026 — verify current numbers with Microsoft or your partner before deciding anything. The structural argument below outlives the numbers; the numbers do not.
They are not the same category, which is the first thing to get right
Project Operations is Microsoft's first-party project business application, and it ships in three deployment shapes that differ enormously in scope:
| Deployment | Roughly what you get |
|---|---|
| Lite | Project sales and project management on Dataverse, integrating with a third-party ERP for the financial side. Stops short of full project invoicing and accounting. |
| Resource / non-stocked | The above plus project accounting, revenue recognition and full integration with Dynamics 365 Finance. |
| Stocked / production | The above plus inventory, warehousing and production orders, inside Finance and Supply Chain Management. |
PSA Hub compares to the first of those. It runs time, expense, projects, billing, WIP, profitability, resourcing, utilisation and forecasting on native Dataverse tables. It is not an ERP and does not pretend to be: it has no general ledger, no inventory, and no manufacturing.
If your requirement includes stock, production orders or a Microsoft-native general ledger, stop reading. That is Project Operations on Finance and Supply Chain, and nothing on this page changes it.
Where the price difference comes from
Publicly reported list pricing for Project Operations is around $135 per user per month. PSA Hub is $35 (Core) or $55 (Pro) per user per month, billed annually, minimum 15 users.
That gap is not us being clever. It is scope. Project Operations is a first-party Microsoft application with a path into Finance, Microsoft's own support organisation behind it, and a roadmap that is not ours to promise. Those things are worth money and some firms should pay it.
What you are buying at the lower number is a narrower product that does the professional services parts well and stops.
Choose Project Operations if…
- You need or will need Dynamics 365 Finance. The integration path is the whole point of the product and it is not something a third party replicates credibly.
- Procurement requires a first-party vendor. Some organisations cannot buy a business-critical application from a company our size, and that is a legitimate constraint rather than a failure of nerve. We would rather you say so on the first call.
- You want Microsoft's support organisation and roadmap. Ours is one company in Sintra with published response targets. Theirs is Microsoft. Those are different risk profiles and you are allowed to prefer the second.
- Your scope includes inventory or production. Not a close call.
Choose PSA Hub if…
- You are already on Dataverse and the project work is the whole requirement. Time, expense, projects, billing, WIP, margin, resourcing, utilisation, forecasting — and no ledger.
- The screens matter more than the schema. A PSA suite is mostly the things model-driven forms are worst at: a week grid, a planboard, a utilisation matrix, an approval queue. PSA Hub is a Power Apps code app — React and TypeScript over your Dataverse — precisely so those screens behave like an application rather than a stack of forms.
- Per-seat cost at your headcount actually decides it. At 40 users the difference between $55 and $135 a month is roughly $38,000 a year. That is either a rounding error or the entire business case, depending on the firm.
- You want the price before the call. Ours is on the product page with a calculator.
What is the same either way
Both run on your Dataverse, in your tenant, under your Entra ID, administered by your team. Neither is a separate SaaS with a sync job pointed at Microsoft. If you are currently running a standalone PSA tool alongside Dynamics, both options remove the same three things: the second system, the integration between them, and the month-end reconciliation that exists because the two disagree.
Both also leave your Power Platform licensing and Dataverse capacity as a matter between you and Microsoft.
The comparison people get wrong
The mistake is comparing PSA Hub's per-seat price against a standalone PSA tool rather than against Project Operations. Standalone tools are often cheaper per seat, and if you have no Microsoft platform investment they will genuinely cost you less — we say so on the product page.
The comparison only favours us when the platform is already yours, because that is where the integration, the second data copy and the reconciliation stop being free.
How we would run the decision
- Is a Microsoft-native general ledger in scope, now or within two years? Yes → Project Operations. Done.
- Can you buy business-critical software from a small vendor? No → Project Operations. Done, and no hard feelings.
- Do you have 15+ billable people whose time becomes invoices, on Dataverse already? No → neither; a self-serve PSA tool will cost you less.
- Still here? Then it is a genuine comparison, and it turns on whether the screens and the per-seat cost matter more to you than first-party support does.
Send us the four numbers that drive an implementation quote — headcount, your accounting system, migration volume and integration count — and we will tell you which way we would go. Including when it is not us.