By project or Managed Power BI: choosing how to work with a partner

Once you have decided to invest in Power BI, the next question is how to actually work with whoever builds it. The engagement model shapes everything that follows: how you budget, how you measure progress, and who is responsible for the reporting a year from now. A good boutique partner keeps this simple. There are two ways to work, by project or on a monthly subscription, and the right one depends on the shape of the work rather than the size of your company.

The two models, plainly

Stripped of jargon, here is the difference.

By project is a fixed-scope build. You agree on what gets delivered, the governed model, the dashboards, a migration, whatever the scope is, with acceptance criteria for each piece and milestone billing. It has a clear start, a clear end, and a clear definition of done. You know what you are getting, when, and how to check it.

Managed Power BI is a monthly subscription. Instead of a defined endpoint, a senior team runs and evolves your Power BI on an ongoing basis: watching refreshes, keeping governance and row-level security current, building new reports as needs change, bringing in Copilot and AI as it matures, with a named point of contact. It is a partner on call rather than a one-off build.

Neither is a premium or a budget option. They are answers to different situations.

When a project fits

A fixed-scope project is the cleaner choice when the outcome is well defined. You can describe what you want, you know roughly which sources are involved, and the work has a natural finish line. Typical cases:

• You need a specific set of executive and operational dashboards built on a governed model.
• You are migrating off spreadsheets or a legacy BI tool and want the reporting rebuilt and reconciled.
• You have a defined analytics gap and want it closed, not an open-ended relationship.

The advantage of a project is predictability. The scope, the acceptance criteria, and the billing are agreed up front, so you know what you are committing to. A dedicated squad working against a backlog you control is a flavor of this model for a larger, evolving build, but it is still fundamentally scoped and milestone-driven.

The limitation of a project is that reporting is rarely finished. The business changes, new questions appear, data sources move, and a build that was perfect at handover slowly drifts out of date if nobody owns it. That is where the second model comes in.

When Managed Power BI fits

Managed Power BI is the better choice when the work is ongoing rather than one-off. The tell is that you do not have a fixed scope so much as a standing need: someone has to keep the reporting current, trustworthy, and growing with the business.

Signs you are in subscription territory:

• Refreshes and governance need watching, and right now nobody owns them.
• New report requests arrive regularly and queue up because there is no capacity to build them.
• Your Power BI estate has grown and needs someone to keep it governed as more people and data come on.
• You want Copilot, AI, and new capabilities adopted as they mature, not left on the shelf.

The value of the subscription is that it treats reporting as the living system it actually is. A named senior team runs it, improves it, and advises on where to take it, so your Power BI gets better every month instead of decaying between projects. It is closest in spirit to having a Power BI team on subscription, with the senior experience of a boutique and without the overhead of hiring and retaining that team yourself.

An important point: this is not a help desk. A support contract waits for tickets. Managed Power BI is active, the team is building and governing, not just answering questions. That distinction is what separates a subscription that compounds value from one that just keeps the lights on.

The path most companies take

In practice the two models are not a one-time fork. The common path is a project, then a subscription. A by-project build gets the reporting estate in place, the governed model, the core dashboards, the migration done right. Then Managed Power BI runs and grows it, because the moment the build lands, the business starts asking for the next thing.

Because the work and the ownership stay in your tenant throughout, moving from one model to the other is a change in how you engage, not a technical migration. Nothing gets rebuilt. You are deciding how to keep working, not redoing the work.

The thing both models share: you own it

Whichever model you choose, one principle holds: everything is built in your own Microsoft tenant, and you own it. The semantic model, the reports, and the data are yours, documented and handed over. Access follows your identity provider. You keep operating with or without the partner.

This matters most for the subscription, because a monthly relationship only stays honest when you are free to leave. Managed Power BI is a monthly term you can adjust, and the fact that you own everything means the subscription has to earn its place each month by being useful. It is a partnership, not a dependency. A partner who builds on their own platform, or who holds your model so you cannot operate without them, is offering a worse version of both models.

How to decide

If you want a quick heuristic:

• Can you write down what you want built, and would you know when it is done? Lean toward a project.
• Is the real need to keep reporting current and growing, with no natural endpoint? Lean toward Managed Power BI.
• Not sure? Start with a short assessment. Two weeks inside your real data usually makes it obvious how much ongoing change the environment needs, and therefore which model fits.

The point of keeping it to two models is that the decision stays legible. You are not choosing from a menu of packages designed to be confusing. You are answering one question, is the work defined or ongoing, and the model follows from the answer. Either way, the work is yours, in your tenant, built by the same senior team.