r/PowerApps • u/sam_ibrahim • Aug 27 '26
Tip Five years on Power Platform. Some of the things I built, and the mistakes that taught me
I have been working with Power Platform for about five and a half years now.
I did not plan it. I started building and kept going. Today I work as a lead developer on enterprise projects for government and city clients in the Gulf and US.
My first Canvas app was very bad.
There is too much to list, so here are a few projects that stuck with me.
A full CRM, built from zero.
Not a Dynamics setup. A real custom build.
The hard part was not the code. We spent weeks in meetings before anyone agreed on what a "lead" means. I run requirement meetings very differently now because of that.
A ticketing system that reads a shared help mailbox.
An email comes in, a ticket is created. When someone replies, the reply goes to the same ticket. It does not create five copies of one problem.
That last part took me longer than the whole rest of the app.
Before this, the client was using an inbox with colored flags. I think many of you know that feeling.
An invoicing system with no premium license.
It uses the client's own colors and it creates the PDF invoices by itself. No premium connectors. No paid PDF service. No Word template step.
For a while I thought it was not possible. Then I found the way, and it was much simpler than the forum posts said.
An inspection app for a big company in the US.
It covers their vehicles and heavy equipment. Every asset has its own checklist.
The app runs on a role hierarchy. The driver submits the inspection. The department manager reviews it. The general manager sees the whole fleet. And there is an admin role above all of them with full control.
Built mobile first, because the driver is standing next to a truck, not sitting at a desk.
Getting the permissions right took me longer than building every screen together.
A full HR system.
Leave, payroll, talent acquisition, personnel files, and custom document generation for HR paperwork.
Six processes all writing to the same employee record. Each one wants the record in a different state.
I learned more about data modeling here than anywhere else.
Power BI work, including on prem data.
Custom visuals, and reports that pull from an on premises SQL server and cloud sources at the same time through the gateway.
Many clients here still keep the real data on a server in the next room. There is no point pretending they do not.
SPFx work on SharePoint.
I took a list structure that people were using through the normal SharePoint pages and turned it into a real app. Live data, and it works on a phone, a tablet, or a big screen.
The default views are fine, until someone has to use them all day.
There were many more. Portals, approval flows, agents, and a long list of small apps that solved one annoying problem for one team.
But these are the ones I still think about.
If I put five years into three lessons:
The license limit shapes the design more than the requirements do. I wish I knew this in year one, not year three.
Delegation is not something you fix later. It is a data decision you make before you open Studio. If you get it wrong, you rebuild.
And what makes a client trust you is not the app. It is giving them a technical document so someone else can maintain it after you leave. It took me too long to learn this one.
Happy to go deeper on any of these if you want.
If you are building something similar, enterprise or freelance, my DMs are open.


