Software architecture and reviews
Map business requirements, data flows and system boundaries. We compare feasible options and document trade-offs, effort and operating costs. You can commission an architecture review as a standalone engagement.
AURUM builds business applications, extends Microsoft 365 and SharePoint, and connects them to the systems you already use. We compare built-in features, low-code and custom development before recommending a solution.
Microsoft Solutions Partner · Based in Nuremberg since 2014 · About AURUM
Bring us a process you want to improve, an integration you need to build or an application you already run. We can start with a review and help you decide how much development the project needs.
Map business requirements, data flows and system boundaries. We compare feasible options and document trade-offs, effort and operating costs. You can commission an architecture review as a standalone engagement.
Build internal web apps, services and tools around a specific workflow. We use technologies such as C# and .NET, TypeScript or Python according to the task and what your team can maintain.
Connect Microsoft 365 and Azure to ERP, CRM or specialist systems where supported interfaces allow. We agree who owns the data and plan for access controls, duplicate records, failed transfers and monitoring.
Extend SharePoint with custom web parts and interfaces using the SharePoint Framework (SPFx), React and TypeScript. We assess the standard features first and document what your admins will need to maintain. Explore SharePoint consulting.
Replace emailed forms and approvals with structured workflows using Power Apps, Power Automate or Nintex. We check how exceptions are handled and which licences and connectors the workflow needs. Explore our Nintex partnership.
Review an existing application and decide what to keep, replace or migrate. For a rollout, we agree how to test with users, document the solution and train its owners. Ongoing support can be scoped separately.
Compare each route against your workflow, integration needs and the skills available to run it after launch.
Choose this when built-in lists, libraries or collaboration features cover the process. Check whether teams can work within the standard behaviour and who will manage the configuration.
Use Power Platform or Nintex when your main need is a form, approval or straightforward business app. Check connector availability, licence requirements, exceptions and ongoing ownership.
Consider custom development when the workflow needs specialised business rules, a tailored interface or integration logic. Budget for testing, deployment, documentation and maintenance.
During scoping, we check potential costs for licences, connectors, hosting and support. For platform-specific details, see Microsoft’s Power Platform licensing FAQ and Microsoft’s SharePoint Framework overview.
These published projects show how AURUM has contributed to business applications, integrations and workflow modernisation.
Industry-specific apps for logistics, safety and HR, plus work on Dataverse architecture and governance.
As part of the Devoteam Alegri team, AURUM helped extend a validated SharePoint document management system and integrate it with Polarion.
SharePoint and Nintex process applications, information protection, and migration work on existing Nintex and InfoPath workflows.
We agree on what to build, how your team will test it and who will operate it after launch.
Discuss your requirementsIn a free initial consultation, we discuss what users do today, where they get stuck and which systems are involved. Then we agree what needs a closer look.
We review requirements and dependencies, propose a target design, and outline alternatives, assumptions and estimated effort so you can decide how to proceed.
We show working increments and test representative scenarios with your users. Together we agree how to handle errors, permissions and acceptance before rollout.
We document how to deploy and operate the solution, train its owners and agree who handles fixes and enhancements after launch.
Find out what affects cost, when to use low-code and what a handover can include.
The initial consultation is free. Implementation costs depend on scope, interfaces, user roles and testing. When we scope the work, we also review likely licence, hosting and maintenance costs so you can compare the options.
Yes. We can review a proposed or existing application, map risks and dependencies, and provide a recommendation you can use to decide whether to proceed.
Power Apps can suit internal forms and apps. Nintex can suit workflow and forms projects, particularly if you already use it. SPFx is a development framework for extending the SharePoint interface. We choose based on the process, available licences, and the skills of whoever will maintain it.
We first check whether your systems provide a supported API or connector. We then assess how data should be mapped, which system is the source of truth, and how to control access and handle failures.
Yes. We review the code, integrations and operational constraints, then identify what can be retained and what needs replacement. For critical processes, we agree a rollout and validation plan with the teams that use the application.
As part of the agreed handover, we can provide documentation and training for the people who will run the solution. If you need ongoing support, we agree its scope and responsibilities separately.
Yes. Our Nuremberg team offers initial consultations in English. We can discuss your systems, intended users and delivery needs before suggesting a next step.
Share a short description of the process, who uses it and which systems are involved. In a free initial conversation, we’ll help you work out whether to start with an architecture review, an integration or an application.

Mustafa Yaylak
Managing Director, AURUM GmbH