ERP Design with Power Pages for Scaling Without Chaos

There’s something I’ve noticed over the years: ERP design with Power Pages usually becomes a topic after a portal grows up faster than anyone expected.

I’ve seen this pattern play out many times. A small portal is built so customers can check order status. That’s the plan.

Then come ship-to changes. Invoice access. Workflow logic. Reporting. Before long, that portal quietly becomes the ERP’s front door... and ERP is doing a lot of heavy lifting it was never designed for.

No alarms went off. No one made a bad decision. But license counts rose, upgrades slowed down, and “just one more change” stopped feeling simple.

That’s when teams realize they didn’t lose control; they slowly handed it away.

This post brings together the full arc of this three-part blog series and shows how connected design avoids that outcome, creating a lower-cost, future-ready ERP without rewinding years of work.

ERP modernization is a design choice

ERP modernization rarely fails because the software can’t keep up. It fails because the design choices around it weren’t made with the long view in mind.

Over time, small decisions add up. Customizations meant to solve real problems start carrying more responsibility than intended. Access expands. Logic creeps in. The core system slowly becomes the place where everything lives — whether it should or not.

That's the common thread: ERP doesn’t become rigid on its own. It becomes rigid when design decisions quietly push more responsibility into the core system than it was ever meant to carry.

Modernization isn’t about replacing ERP. It’s about deciding what ERP should own — and what it shouldn’t.

Why intentional design outlasts good intentions

ERP design choices tend to age quietly... like a “temporary” workaround that’s somehow still in place three upgrades later.

What looks like a small decision early on — where access lives, how workflows are handled, which system owns interaction — often becomes the reason ERP feels heavier years down the road.

This isn’t because anyone made a bad call, but because the design was never meant to carry that much weight.

That’s the true difference between customization and connection. One approach keeps adding responsibility inside ERP. The other keeps ERP focused on what it does best, while letting surrounding systems absorb change.

Once that distinction is clear, the rest of the design conversation gets much simpler, especially when it comes to deciding where interaction should live.

How does Power Pages fit into a future-ready ERP design?

Power Pages plays a specific role in future-ready ERP design: it becomes the interaction layer, not the system of record.

ERP remains the authoritative source for financials, inventory, and operational truth, while Power Pages handles how users interact with that data securely, intentionally, and without embedding logic directly into ERP.

This separation matters. When interaction lives outside the core system, ERP stays cleaner, upgrades stay manageable, and design decisions don’t pile up where they’re hardest to unwind.

That’s the heart of ERP design with Power Pages: protecting the core while still meeting real access needs.

One example where this becomes very real is in eCommerce scenarios.

I’ve seen organizations assume they need a full-scale B2B or B2C commerce platform, even when their model doesn’t quite fit either mold. The result? Expensive licensing, heavy customization, and a lot of effort trying to shoehorn a prebuilt solution into a business process it wasn’t designed for.

Sometimes the requirement isn’t “online shopping cart.” It’s something more specific, like enabling sales reps to configure orders, access customer-specific pricing, or submit structured requests that don’t align with a traditional commerce flow.

That’s when Power Pages becomes a flexible interaction layer.

Instead of customizing ERP to behave like a storefront or over-customizing a commerce platform to behave like ERP, the portal is designed intentionally around how the business actually operates.

ERP stays focused on data and process integrity. The portal handles interaction. Licensing stays controlled. And the architecture remains clean.

That’s the difference between adapting the design and forcing the system to comply.

Can Power Pages reduce ERP customization and licensing costs at the same time?

Yes — and this is where so many organizations see immediate relief.

When users interact through Power Pages instead of directly inside ERP:

• Fewer full ERP licenses are required

• Custom workflows move out of the core system

• Design changes don’t automatically trigger ERP rework

This supports a more intentional ERP user licensing strategy, where ERP access is reserved for users who truly need it, instead of everyone who needs visibility.

Over time, this approach reduces both licensing pressure and the hidden costs tied to maintaining custom ERP logic.

What does a connected ERP architecture actually look like in practice?

In practice, connected ERP architecture looks surprisingly simple:

• ERP stays focused on data integrity and process control

• Power Pages and the Microsoft Power Platform handle interaction

• Each layer has clear responsibility boundaries

Instead of a single system trying to do everything, the architecture becomes modular.

ERP remains stable. Connected tools adapt as business needs change.

This modular approach supports ERP modernization without customization, so companies can evolve access and workflows without rewriting ERP every few years.

Why does a cleaner ERP core make automation and AI easier later?

Automation and AI don’t thrive in tangled systems. They spend more time working around the mess than adding value.

When ERP is overloaded with custom logic, automation becomes brittle. AI becomes disruptive instead of additive.

Clean systems, on the other hand, invite incremental improvement.

This aligns with broader industry guidance. McKinsey emphasizes that scalable AI depends on well-designed ERP foundations where data access and system boundaries are clear rather than tightly coupled.

A cleaner ERP core makes ERP automation readiness and ERP AI readiness practical instead of aspirational.

Why this lowers cost over time

Connected design lowers total cost in ways that aren’t always obvious upfront:

• Predictable license growth

• Easier upgrades

• Reduced dependency on specialized customization knowledge

Forbes found that organizations are increasingly rethinking ERP customization in favor of scalable, connected architectures that support growth without compounding complexity.

The takeaway here is that lower cost doesn’t come from doing less. It comes from doing the right things in the right place.

How should leaders evaluate ERP modernization without triggering disruption?

There’s no need to rip and replace your ERP to modernize it. The most effective changes often present themselves around the edges.

By keeping ERP stable and shifting interaction outward, organizations can reduce disruption while still making meaningful progress. Change becomes incremental instead of risky. Design decisions feel intentional instead of reactive.

That’s how modernization builds confidence rather than fatigue.

Bringing it full circle

Remember that portal from the introduction? It didn’t fail. It simply grew beyond what it was designed to handle.

That pattern shows up more often than most teams expect. Earlier in this series, I talked about how well-intentioned customization decisions quietly compound into long-term cost and risk.

Then we explored how connected experiences can provide access without dragging that complexity directly into ERP.

Instead of letting access, workflows, and interaction pile up inside Business Central, those responsibilities live outside the core — where they can change without everything else breaking. The ERP stays clean. Upgrades stay manageable. And future decisions don’t come with a decade of cleanup attached.

That’s not less control. It’s better control — by design.

If this way of thinking resonates, our upcoming webinar will too. We’ll walk through this design approach and show how connected portal design can lower ERP costs while preparing organizations for automation and AI, without turning ERP into a science project. Register here.

And if you’re seeing these patterns show up in your own environment, feel free to reach out. I’m always happy to talk it through.

About Matt Keyes

Matt Keyes is a visionary leader, founder, and CTO of Key Partner Solutions. With over two decades of experience in Microsoft Dynamics, he is passionate about driving digital transformation for businesses through innovative technology solutions.

His deep technical expertise, combined with a strategic approach to solving business challenges, makes him a sought-after thought leader in the industry.

Today, Matt is focused on empowering companies to unlock new levels of growth and efficiency through cutting-edge software development and consulting.

Connect with Matt on LinkedIn.