Power Apps development
Build canvas or model-driven apps for tasks such as requests, inspections or internal operations. Choose the interface and data model around the people who use them.
Replace manual requests, spreadsheets and email approvals with apps and workflows your team can maintain. AURUM helps you choose the right Microsoft Power Platform tools, check licences and manage deployment and handover.
Microsoft Solutions Partner for Business Applications · Based in Nuremberg since 2014 · About AURUM
We work with IT and business process owners on new solutions and existing environments. You can start with a process, a licence review or an assessment of existing apps and flows.
Build canvas or model-driven apps for tasks such as requests, inspections or internal operations. Choose the interface and data model around the people who use them.
Automate routing, notifications and approvals. Plan exception handling, ownership, and how the process continues when a flow fails.
Evaluate SharePoint lists, Dataverse or an existing system as the data source. Check relationships, permissions, available connectors and duplicate records before integration.
Plan where makers can develop and test apps, how solutions reach production, and which connectors can be used together under your data policies.
Assess an agent for a bounded business task when it adds value. Agree what data it can use, what actions it can take and which decisions need human review.
Document dependencies, ownership and deployment. Train the people who will maintain the solution and agree how to handle changes and incidents.
Licensing depends on the app or flow, its data sources, who uses it and where it runs. Confirm the design before committing to a plan.
Some Microsoft 365 plans include limited Power Apps and Power Automate rights for scenarios using Microsoft 365 data and standard connectors. Verify the plan and connector for the actual design.
Premium or custom connectors, full Dataverse scenarios and certain automation capabilities need additional licensing or qualifying rights. Check users, app or flow context and environment requirements.
Compare custom code or Nintex where the requirements go beyond the platform or existing tools already cover part of the process. Explore custom software development.
See Microsoft’s Power Platform licensing FAQ and data policies documentation for the official rules.
These published customer references describe work AURUM has done with business applications, modernisation and governance.
AURUM worked on applications for logistics, safety and HR, plus Dataverse architecture and governance. Read the Röchling case study (German).
AURUM helped modernise existing SharePoint applications and replace legacy forms with Power Apps and Power Automate. Read the Epson case study (German).
For your project, we agree who owns the solution and how changes move from test to production. Microsoft documents this approach in its Power Platform solutions overview.
We check licences early and test the workflow with its users before it goes live.
Discuss your requirementsMap the triggers, decisions, data and exceptions. Identify who uses the process and who will own the result.
Try the key steps with representative data and users. Check connectors, permissions, licences and how the design will be deployed.
Implement the agreed app or flow, test normal and failure scenarios, then review the result with users and administrators.
Document the solution, train owners and agree who handles updates, failures and support.
Answers on choosing an app or flow, checking licences and keeping solutions maintainable.
Power Apps provides an interface for people to enter, view or edit information. Power Automate runs steps triggered by an event, a schedule or a user. A solution can use both.
Some Microsoft 365 plans include limited Power Apps and Power Automate rights for defined scenarios. The required licence depends on the connectors, data, environment and how the app or flow is used.
The initial consultation is free. Build costs depend on workflow complexity, integrations, testing and handover. Licence and support costs depend on the setup, active users and the agreed operating model.
Yes. We can review ownership, connectors, environments, dependencies and how users report problems. We then prioritise fixes and agree which solutions to keep, modernise or retire.
Yes, with a design that matches their skills and access. We agree ownership and document connections, deployment and what to do when something fails.
Compare the workflow, existing licences, integrations and support skills. The best fit varies by process. We can review your requirements and compare viable approaches.
Bring a description of the current workflow, its users and the systems it touches. We’ll help you identify a practical first step and the licensing questions to resolve.

Mustafa Yaylak
Managing Director, AURUM GmbH