Skip to content

Microsoft Power Platform

Power Platform apps that do a real job and continue to work.

Power Apps development is quick to start and easy to get wrong at scale. Blacklight delivers Power Apps, Power Automate flows and Power BI reporting that are governed, supportable and still in service in three years. And because full .NET systems come out of the same studio, you get told when low-code is the wrong tool.

What Blacklight delivers on Power Platform

Power Apps: line-of-business applications

Inspection forms, approvals, asset registers and field data capture: the small, specific applications your teams now run on spreadsheets and email. We build them model-driven or canvas, as the job demands, on a data model designed to outlive version one.

Power Automate: workflow automation

The handoffs between systems that people now do by hand: notifications, approvals, document routing and data sync. We scope each flow so it has an owner, an error path and a reason to exist.

Power BI: dashboards and reporting

Reporting on governed data, not exported spreadsheets. We delivered Power BI analytics as part of Wandle Housing Association's Dynamics 365 estate: individual and team dashboards that give staff immediate analytics over live case data. Do you need reporting across several systems? That work lives on our integration, data and AI page →

Power Pages and Dataverse portals

External-facing portals on Dataverse: customer, supplier and resident. We design the data model, security roles and licensing before we build the first page.

Did you inherit too many Power Apps?

It is the most common way organisations arrive here. Someone enabled Power Platform. Forty apps appeared. Three of them now run something important, and no one knows which. Citizen development did its job: it proved demand. Then it outgrew its governance.

We audit the estate: which apps are used and by whom, where the data sits, what breaks under licence or platform changes, what each app costs to keep, and which apps to consolidate, rebuild or retire. You get a written picture of the estate and a prioritised plan, with governance, ALM and environment strategy included.

There is no gated form and no obligation to remediate with us. It starts with a conversation, like everything else.

Get in contact →

Proof

Reporting and case queues over live housing data

  1. Problem

    Wandle Housing Association has more than 7,000 homes across nine south London boroughs. Staff and managers needed to see case workloads and performance as they happened, not in month-end spreadsheets.

  2. Build

    As part of Wandle's Dynamics 365 implementation, we delivered Power BI analytics with individual and team dashboards. Case queues let staff pick up work and progress it. All of it integrates bi-directionally with the existing Housing Management System.

  3. Result

    Every team has immediate analytics across anti-social behaviour, complaints, fraud, repairs, estate management and income. There is one live view of work, not six departmental versions of it.

Where Power Platform ends and a bespoke build begins

Low-code has a ceiling. If you pretend it does not, your estate becomes unsupportable. Complex data models, high-volume transactions, demanding integrations, external users at scale, and licence costs that climb past the cost of a build: these are the signals that a custom .NET build is the cheaper, stronger answer.

We build both, so the recommendation is not rigged. Sometimes the answer is a Power App on Dataverse. Sometimes it is a bespoke system with a Power BI layer on top. Sometimes, as at Wandle, where Dynamics 365 and Power BI run beside a bespoke .NET resident portal, it is both.

When low-code is not enough: bespoke software →

Frequently asked questions

What does Power Platform licensing cost?

It depends on three things: whether apps are standalone or use licences you already hold, how many users touch premium connectors, and whether Dataverse is involved. Licensing is the first thing we model in scoping, because it changes the build recommendation, sometimes decisively.

How do you handle governance and ALM?

We separate environments for development, test and production. We deploy apps through pipelines, and we do not edit them live. Policy controls the connectors. Every app has a named owner. This is heavier than "citizen development". It is what keeps app forty-one from stopping app three.

Our Power Apps estate is a mess. Can you save it?

Almost always, partially. That is the honest answer. In most unmanaged estates, some apps are unused, and you can retire them. Most of the rest need consolidation or a move to a proper data model. A small core deserves a full rebuild. The audit tells you which is which before you spend.

Talk to us

Thirty minutes, one estate, straight answers.

For a new build or an estate that needs control, we tell you what to keep, what to repair, and what it costs to know for sure.

Get in contact