Taking an estate of ungoverned apps and flows and making it something you can support.
Illustrative. This is a walkthrough of how we run this kind of engagement, not an account of a specific client project. It carries no client and no results, because none are being claimed. Delivered work, with measured outcomes, is on the work pages.
Several years of citizen development. Nobody knows how many apps exist, several are business critical, and at least one is owned by somebody who has left.
Every app, flow and connection is listed with its owner, its usage and what it touches. Most estates split cleanly into a few that carry real load and a long tail that can be retired.
What you get
Environments get separated, policies applied, and the apps worth keeping get rebuilt properly on a designed Dataverse schema.
What you get
The point is not that we govern it. The point is that your team can, including a route for a citizen developer to get something reviewed rather than blocked.
What you get
Nothing is retired on usage data alone. Low-usage apps get an owner check and a notice period, because the monthly regulatory report is a low-usage app.
If the process is slower than the workaround, people will use the workaround. The review route is designed to be faster than building it in a spreadsheet, or it has failed.
The process is documented and the review is a scheduled task rather than a person's habit. That is the difference between governance and a bottleneck with a name.
Other shapes
