Skip to content

Power Pages with React.

David Göschel. Architecture and development for enterprise portals.

I build business-critical workflows in Power Pages when low-code is no longer enough.

Request a workflow review View my work

Project experience for companies such as

  • ECE Marketplaces GmbH & Co. KG Logo
  • BAKS Büro-Automatisierungs- und Kommunikations-Systeme GmbH Logo
  • Deutschen Anwaltsinstituts e. V. Logo
  • ait-deutschland GmbH Logo
  • Bode Chemie GmbH Logo
  • Deutscher Verein des Gas- und Wasserfaches Logo
  • Horsch Maschinen GmbH Logo
  • Pax, Schweizerische Lebensversicherungs-Gesellschaft AG Logo
10+
Years of experience
AZ-204
Microsoft certification
10+
Enterprise projects

Extend where it matters

Power Pages remains the foundation. I extend the areas where standard features no longer fit the business process.

  • Limited user guidance

    Standard forms and lists are not enough for complex business processes. Users get lost in confusing interfaces.

  • Limited extensibility

    Low-code tools cannot deliver every custom feature. Workarounds quickly become difficult to follow and unstable.

  • Lack of transparency

    No insight into user behaviour, click paths or errors. Business teams make decisions without a sound data foundation.

  • Inconsistent user experience

    Design requirements cannot be fully implemented. Portals look dated and do not match the corporate design.

  • Complex data logic cannot be represented

    Queries across multiple entities, intelligent filters and batch operations exceed the capabilities of standard features.

  • Growing technical debt

    Platform workarounds accumulate. Maintainability declines, and changes become risky and time-consuming.

Start with the five-day Decision Sprint

Before a major rebuild becomes necessary, we clarify the architecture, security boundary, technical spike and implementation scope for your blocked workflow within five working days.

More project insights

Complex data entry, continuing education and e-commerce. Different challenges, clearly documented architecture.

Consumption reporting in the German-language ECE portal

ECE portal with React

Consumption reporting connects React interfaces and Excel workflows with Power Pages.

View project
Continuing education programme in the German-language DAI portal

DAI Service Portal

Taxonomy filters enable targeted searches across the continuing education programme.

View project

From interface to operations

Targeted development instead of more workarounds. The service follows your workflow, not a fixed technology package.

Interfaces that support the work

  • Extend Power Pages with React

    Custom feature development with React, TypeScript and JavaScript. Clean frontend architecture instead of isolated scripts for complex search, filtering and configuration features.

  • UI/UX and design systems

    Implementation of modern Figma designs. Consistent UI components with HTML, CSS and Bootstrap. A focus on making complex business processes usable.

  • Multilingual content and content strategy

    Scalable multilingual concepts for Power Pages. Manage hundreds of content snippets with a clear separation of logic, content and translations.

Connect data and processes

  • Data logic and integration

    Query and transform Dynamics 365 data through Web API and FetchXML into JSON. Intelligent search, filtering systems and batch-editing functionality.

  • Excel integration and hybrid workflows

    Structured Excel templates for bulk and offline editing. Automated processing through Power Automate flows with validation and synchronisation to Dynamics 365.

  • Power Automate integration

    Design and development of flows for validation, processing and storage. Direct calls from the frontend with a clear separation between logic layers.

Responsibility through to operations

  • Payment integration and e-commerce

    Connect payment providers such as Stripe and Secupay to Power Pages and custom web applications. Secure payment processing, shopping carts and seamless Dynamics 365 connectivity.

  • Monitoring and analytics

    Implementation of GDPR-compliant monitoring solutions with Azure Application Insights. Analyse user behaviour, click paths and performance to support data-driven decisions.

  • Technical responsibility

    Frontend leadership in complex projects. Architecture decisions for maintainable extensions, stakeholder communication and quality assurance throughout the lifecycle.

Your workflow. The next step.

Choose your area. See the typical platform limit, the proven architectural approach and relevant reference projects.

Choose the affected area

Search and filters

Typical limit
Standard lists fall short when auto-suggest, combined taxonomy filters and URL state are required.
Architecture in practice
React controls filters and browser history, while Server Logic validates parameters and calls Dataverse Custom APIs.
Decision Sprint approach
In the Decision Sprint, we define the search contract, OData security boundary and a quick search spike.
Discuss your workflow

Bulk data entry and Excel

Typical limit
Individual forms slow down business teams when hundreds of records need updating per reporting period.
Architecture in practice
React tables with batch editing and structured Excel uploads work together with Power Automate validation.
Decision Sprint approach
In the Decision Sprint, we clarify the data model, validation pipeline and the best mix of tables and Excel.
Discuss your workflow

Multilingual content

Typical limit
Content snippets scattered across scripts and templates create high maintenance effort across many languages.
Architecture in practice
A clear separation of UI logic, structured Web Templates and centrally managed translations for all roles.
Decision Sprint approach
In the Decision Sprint, we design a maintainable language and configuration model between Liquid and React.
Discuss your workflow

Payment

Typical limit
Payment processes and shopping carts require secure server-side confirmation outside the browser.
Architecture in practice
A multi-step portal checkout combined with Stripe integration, Azure Functions and Dataverse synchronisation.
Decision Sprint approach
In the Decision Sprint, we define the payment flow, webhook security and Dataverse status transitions.
Discuss your workflow

Integration and monitoring

Typical limit
Without telemetry and controlled consent, portal errors remain invisible or pose GDPR risks.
Architecture in practice
Consent-controlled services, Azure Application Insights and server-side API integrations with clear contracts.
Decision Sprint approach
In the Decision Sprint, we define the security boundary, consent controls and monitoring events.
Discuss your workflow

For Microsoft partners

Specialist delivery capacity for ongoing Power Pages projects. Support for sold or active projects that need additional frontend, security or integration expertise.

  • Clearly scoped support

    Take ownership of a risky workflow or technical area without competing with your existing customer relationship.

  • Collaboration with your team

    Coordination with practice leads, solution architects, delivery teams, product owners and backend developers.

  • Confidence in your decision

    The Pro-Code Decision Sprint clarifies architecture, security boundaries, the spike, scope and risks in five working days.

  • Implementation with handover

    Documented architecture, traceable contracts and a clear transition to joint or internal implementation.

Practical insights

On my blog, I regularly share insights, best practices and technical deep dives on extending Power Pages through professional web development.

View all posts

Frequently asked questions

Answers about architecture, platform limits, collaboration and long-term technical support.

When is custom development worthwhile?

When your portal is in production and you encounter functional, visual or analytical limits: complex user journeys, custom business processes, modern UX requirements or insufficient visibility into usage and errors. Custom development makes sense when low-code workarounds become unstable and you want to use Power Pages for the long term.

Does custom code replace Power Pages?

No. Power Pages remains your foundation for authentication, permissions, forms and Dynamics 365 integration. I extend specific areas where low-code ends through ReactJS components, modern UI frameworks, intelligent data logic and monitoring. The result is a hybrid solution that protects your platform investment and prepares it for future needs.

Which technologies are used?

Depending on your requirements: JavaScript/TypeScript for logic, ReactJS for complex components, HTML/CSS/Bootstrap for design systems, Dynamics 365 Web API and FetchXML for data queries, Power Automate for business processes and Azure Application Insights for monitoring. All extensions are cleanly embedded in Power Pages.

How does collaboration work?

After a free initial conversation, we develop a frontend architecture suited to your requirements. Implementation follows an agile approach in two-week sprints with regular demos. I work independently or join your existing Scrum teams. You receive continuous visibility and can provide feedback at any time. After go-live, I remain available as your technical contact for maintenance and further development.

What sets you apart from other developers?

I combine a deep understanding of Power Platform with professional web development and UX design. Unlike traditional consultants, I build clean frontend architectures instead of low-code workarounds. Unlike purely web-focused developers, I understand Dynamics 365, Power Automate and the platform limits. And unlike agencies, I support portals over the long term with technical responsibility beyond go-live.

Who maintains the portal after go-live?

I offer long-term support, from bug fixes and functional adjustments to strategic further development. Having developed the systems, I know their architecture, data models and business logic in detail. This provides continuity, avoids knowledge-transfer risks and enables quick responses to change requests.

What should your portal do?

Describe your workflow. Together, we will identify the right next step.

Discuss your workflow