Power Apps development for businesses that have outgrown the spreadsheet
When a shared spreadsheet is doing the job of a system, a Power App gives your team a proper one: a form on their phone instead of a row in a file, data in one place, and rules that stop the wrong thing being entered.
How the work goes
Power Apps is Microsoft's low-code platform, and it sits inside the Microsoft 365 licence most businesses already pay for. That makes it the natural next step for a process that has outgrown Excel: a job log, a CRM, a stock check, an inspection form, a quoting tool. I build canvas apps for the front end and model-driven apps where the data is the point, on Dataverse or SharePoint depending on what you have and what you need.
I run my own business on a CRM I built this way, and that case study is on this page, so you can see what a working app looks like rather than a mock-up. Every build starts with a short conversation about what the spreadsheet is really for, then a written scope and a fixed price.
You own the app and the environment it lives in. I hand over with documentation and a walkthrough, and I'll say so plainly if a simpler tool would do the job.
One honest difference from a spreadsheet fix: an app is a living thing. Microsoft updates the platform, your business changes, someone wants one more field. Power Apps clients stay on an ongoing arrangement after handover, typically around £200 a month, so there is always someone who knows the build and can make the change the same week.
What it tends to cost
I won't pretend there's a price list for this; it depends on what the app has to do. As a rough guide, a single-list app on SharePoint usually lands in the low thousands, and a full multi-screen system on Dataverse is a five-figure project. What I can promise is that you'll know the number before I start: one call, a written scope, a fixed price. After handover, keeping it running is around £200 a month.
How I price, fixed or hourly, and where scope tends to creep →
What clients said
Thompson was fantastic to work with. He gave me a very clear idea of what his plan was to solve my problem, the timeline and cost. He also insured the code behind his solution, was neat and optimal, not just thrown together. I also booked an additional call with him, in which he very patiently explained his code and logic in great detail, so that even a total novice could understand it. The solution does what i want, and is flexible, so would highly recommend!
This is my third hire now of Chris and I can't speak highly enough of him. He is great at communicating, works very quickly and finds solutions to absolute everything you can think of. Hire Chris if you want a true professional.
Questions people ask
- Do we need extra licences?
- Often not. Apps on SharePoint lists run on standard Microsoft 365 licences. Dataverse and premium connectors need a Power Apps licence per user; I will tell you which applies before you commit.
- Canvas or model-driven?
- Canvas when the screen layout and mobile use matter most; model-driven when it's about managing related records with views and forms. Plenty of jobs use both, and the choice is part of scoping.
- Who owns the app?
- You do. It is built in your tenant, in your environment, with you as owner. Nothing sits in my account.
- What happens after handover?
- You get documentation and a walkthrough, then an ongoing support arrangement: typically around £200 a month, agreed at handover, covering platform updates, small changes and questions. Bigger additions are scoped and quoted separately. It runs month to month, so there is no lock-in.
Tell me what's slow
A sentence or two about the job is enough to start. I reply personally, usually the same day.
Start a project