Power Platform
Low-code is only cheap if what you build can be maintained by someone who is not us. That is a design decision, and it is easy to get wrong.
What we do
Built to be handed over. Naming, structure and documentation so someone internal can take it on.
Dataverse where it earns it. Not every app needs it. We say when a list is enough.
Governance from the start. Environments, permissions and a route to production, before there are forty apps.
Shadow IT surfaced. The apps people already built in secret are usually the best requirements document you have.
How we work
What exists already, and what people do by hand around it.
Live in weeks, in a real environment with real permissions.
Your people build the next one, with us reviewing.
What a delivery contains
The app or flow that solves the actual task
Storage in Dataverse where it is needed, and in what you have where it is not
Connections to the systems the app must read from or write to
Environment setup: development, test and production kept apart
Governance that holds, who may build what, and where it ends up
Training for the people who will develop it further without us
Documentation and solution packages you own
What it costs
Power Platform is cheaper to start with than Dynamics 365, and that is exactly why the cost spreads. What drives the price of an engagement is three things: how many systems the app has to talk to, whether you need Dataverse or can work with the data where it already sits, and whether this is one app or the start of a portfolio that has to be governed. The last is the one people underestimate, ten ungoverned apps cost more a year than they saved between them.
We do not price what we have not understood, so we give specific numbers after a short scoping call, half an hour is often enough. Ask for an estimate.
How long it takes
| Scope | Time |
|---|---|
| One app or flow, bounded need | weeks, not months |
| App with a couple of integrations | 4-8 weeks |
| Model-driven app on Dataverse | 2-3 months |
| Portfolio with governance and environments | 3 months and up |
Short timelines are the whole point of the platform. If the answer to a need is "six months", we have usually picked the wrong tool, it is then either Dynamics 365 or custom development that the need is really about.
When this fits, and when it does not
Fits when
- A spreadsheet has become a system nobody dares own
- An approval runs over email and stalls when someone is on holiday
- You need a form out in the field that writes straight into the system
- You are already on Microsoft 365 and hold the licences
Does not fit when
- The need is really a full CRM or ERP
- It goes out to customers at volume, look at Power Pages or custom development
- Nobody internally will own the app afterwards
- The requirements are not settled, and the app is being used to discover them
Questions we get
Do we need Dataverse?
Not always. If the data already sits in SharePoint or a system with a usable API, the app can read it where it is. Dataverse earns its place when several apps share the same data, or when you need row-level permissions.
Can our own people build?
Yes, and that is often the point. We set up the environments and the governance first, so what gets built internally lands somewhere somebody has oversight of, not in a personal account that disappears with a resignation.
What do the licences cost?
Much is already covered by Microsoft 365. Premium connectors and Dataverse need their own. We work through the mix with you before you buy, this is often where the money is.
What happens when whoever built the app leaves?
That is why we ship solution packages and documentation, and keep development separate from production. An app that exists only in the production environment is an operational problem waiting to happen.
Shall we talk this through?
Tell us briefly what you need and you get a concrete answer, and an estimate you can plan around.