Handling time
From submission to decision or closure.
New or redesigned process
Requests and decisions in one clear process.
I build Power Apps and Power Automate flows when email and spreadsheets are not enough to manage ownership, status, deadlines and the history of a case.
I do not start with the app screen.
First we define who submits a case, who decides, what happens with exceptions and what completion means. Then I choose the form, data source, notifications and automated steps.
Typical scope
- Process map, roles, statuses and decision rules.
- A responsive Power Apps app for intake or queue management.
- Power Automate flows for confirmations, approvals, reminders and error handling.
- Scenario testing, documentation and handover.
Boundaries and costs
Data source and licence choices depend on the client's environment. Premium features, including some Dataverse or AI Builder options, need a separate cost check. I do not assume they are necessary for a simple process.
What to measure
Agree on a baseline first.
We measure the problem to solve, not the number of screens or automations built.
Manual work
Re-entry, reminders and corrections.
Case visibility
Cases with an owner, status and decision history.
My own examples
Purchase Request and Request Intake
My own systems show two approaches: a purchase approval workflow and a request queue with deadlines and error handling. The home page includes real screens and workflow descriptions. A client solution needs adapted rules, data and permissions.
Open the descriptions and screenshots →First step
Describe one case from submission to closure.
I will assess what can be simplified and what is worth automating. If a pilot is needed, we agree on its bounded scope, outcome and quote before work begins.
Before sending personal data, read the privacy policy.