Home/Case studies/

Faster case processing and fewer complaints with Power Apps

Case study

Bouw en installatie

Faster case processing and fewer complaints with Power Apps

For years, a building materials certification body relied on an Access database that nobody could change anymore. Today, a Power App with an external portal supports the entire inspection process, from application to approval.

Ronny Van der Snickt

Founder & Managing Director, Profility

15 May 2025

Download the case study (PDF)
Profility logo with “Faster case processing, no complaints”, case study

On this page

▾

Planning a project like this?

Tell us what you're running into today, and we'll explore what's possible together.

Book an intro call

The case at a glance

ClientAnonymous, at the client's request
IndustryCertification of building materials and construction products
Starting pointAn outdated Access database that didn't fit the inspection process, with no developer to change it
Alternative on the tableFully custom development of the workflow
SolutionPower App for the entire case flow, with a portal for external users
ComponentsCase flow with stages and approvals, pricing, handoff to the translation agency, external portal, API to the public website, complete audit trail

Who is a building materials certification body?

The client certifies building materials and construction products. Every case follows a fixed, rigorous process: application, testing, assessment, pricing, and finally the approval that forms the basis for the certificate. Both in-house staff and external parties contribute to that process.

At the client's request, this case study is anonymous.

What did a building materials certification body need?

All case tracking lived in an Access database that was years old. That created two problems. The system wasn't designed around the process every certification case has to go through, and nobody in-house could make changes to it anymore. So every change to the procedure was handled outside the system, which in practice meant email and Excel on the side.

The company wanted to modernize and simplify its quality procedure, and at first considered a fully custom-developed workflow. A defensible choice, but an expensive one, and with the same risk as before: you're once again dependent on whoever built it.

Our approach

Not starting from scratch. The client was about to have the workflow fully custom-developed. We proposed building on Power Apps instead, because much of what an application like this needs is already there: forms, data import and export, permissions management, integrations, and security are all standard parts of the platform. That cuts development costs considerably, and it also determines where we do spend our time.

Custom-built where it makes the difference. What we built ourselves is the business logic of the case flow: which steps a certification case goes through, who needs to approve at which point, what happens when a case has to go back a step, and how the price of a case is calculated. That's exactly the part that's unique to this organization, and you won't find it ready-made in any standard package.

A portal for people outside the system. People outside the company also contribute to a certification case. They don't have a license and don't belong in the internal app. They log in through a separate portal and see only the cases that need their input.

The public website as the final destination. In the end, the quality data has to be publicly accessible. An API sends that data from the app to the external website, so nobody has to enter it a second time.

What value did Profility add?

One tool for the approval flow. Today, the client has an application that supports its own, highly specific approval flow for construction product cases, instead of a generic system the process has to work around.

Questions, pricing, and translations in the same flow. Questions about a case are tracked and answered within the system, prices are calculated, and cases that need translating go straight to the translation agency. What used to be three separate tracks is now one case with a status.

Access for external stakeholders. External users provide their input through the portal when it's expected of them, without anyone having to chase them for it.

Publicly accessible quality data. Through an API, the quality data lands on the external website automatically. No double entry, no versions drifting apart.

A complete audit trail. Every action and every approval can be traced, including who did it and when.

What was the result?

Case turnaround times have dropped noticeably. Because staff and approvers handle every step in the same integrated workflow, cases no longer sit waiting for someone who doesn't know it's their turn. The number of complaints has also dropped sharply, and cases flow smoothly through to the website.

There's another benefit that got less attention up front but carries a lot of weight in practice: every step can be reviewed afterward. Who took which action at which stage, and who approved what. For a quality procedure, that's not a luxury.

What we took away from it

An outdated system is rarely just a technical problem. The real pain here wasn't that the database was old. It was that nobody could change it anymore, while the procedure kept changing. That's the point where people start working around the system.

First look at what the platform already does. We start every project by asking which part of the request can be solved with standard features. What's left is usually small, and that's exactly where custom-built work adds value. You can see what that looks like for other processes, from sales to job site scheduling, screen by screen in our showcases.

Frequently asked questions

Can you replace an Access database with Power Apps?

Yes, and it's one of the most common reasons organizations come to us. An Access application usually runs on one machine or network drive, is hard to share, and grinds to a halt as soon as the person who built it leaves. On Power Apps, the same logic lives in a managed environment, with user management, backups, and access from any device. In our article on replacing an Access database, we lay out the three possible routes, and also when you're better off leaving your database as it is.

When is a standard platform better than fully custom development?

As soon as much of what you need already exists: forms, permissions, data management, integrations. Then it's a waste to have all of that developed from scratch. Fully custom development only pays off when you need something that's truly beyond what the platform can do.

Can external parties contribute without a license?

Yes, through a portal. External users get their own secure environment where they only see the cases and fields meant for them. The internal app stays reserved for employees.

Will an app like this have to be rebuilt later?

No. Because the app runs on a Microsoft platform, the interface follows the platform's updates. So no development project is needed to keep it current, and that was an explicit requirement for this client.

Want a system like this for your organization?

Tell us about your situation, and we'll look at what's possible for your business together. No sales pitch.

Book an intro call

ABOUT THE AUTHOR

Ronny Van der Snickt

Founder & Managing Director, Profility

View LinkedIn profile