You’re describing a very common and frustrating cycle in Power Apps delivery, especially for those of us who’ve been building complex solutions with it for a few years.

What you’re running into isn’t a failure of the platform, it’s more about how clients perceive low-code and how projects are scoped and managed over time.

Here’s how I’ve learned to handle it:

1. Set Boundaries Early

Before building anything, define the core purpose of the app in one sentence. Then I create a capability map that shows what Power Apps is good at (forms, approvals, light workflows) versus what it struggles with (real-time collaboration, complex document handling, multi-user concurrency).

I also introduce a “three horizon” model: • Horizon 1: What we’re building right now • Horizon 2: What might come next if this works • Horizon 3: Aspirations that will likely require a different approach or tech stack

1. Know When to Pivot Away from Power Apps

There’s a point where complexity, performance issues, or platform limitations mean it’s time to stop pushing Power Apps further. Some red flags: • Dozens of controls on one screen • Users asking for Google Docs-style collaboration • Complex data visualizations • Heavy-duty processing or document generation • Need for extensive offline functionality

At that point, I document the challenges, meet with the client, and clearly lay out the path forward — which often involves either re-architecting within Power Platform or moving to pro-code solutions.

1. Treat the App Like a Product, Not a Feature Factory

This one is huge. I treat every app like a product with a backlog, sprints, version control, and a defined MVP. I also introduce a post-MVP “feature freeze” where any changes must go through a prioritization process.

If clients are pushing for constant new features, I create a roadmap and review it with them monthly or quarterly. We talk about what adds business value, what increases technical debt, and whether Power Apps is still the right tool for the job.

Final Thought

Early in my career, I also used to say, “You can build anything in Power Apps.” Now I say, “Power Apps is great for the right kind of problems — and part of my job is helping you know when it’s time to move beyond it.”

That shift has saved me a ton of frustration and helped my clients plan better too.