Power Platform: routines that run on their own.
We build approvals, forms and recurring workflows with Power Automate and Power Apps. Connected directly to Business Central. Fewer follow-ups, less manual work.
Starting point
Today, the process depends on reminders.
An order waits for approval because the email gets lost in the inbox. Leave requests lie around as PDFs. Excel lists are reconciled by hand. Everyone knows the process, but no one sees where things stand.
01
Approvals by email
No one knows where a case is currently stuck.
02
Paper and forms
Entries are retyped and changed along the way.
03
Excel as the control centre
Lists drift apart as soon as two people maintain them.
04
Manual reminders
Deadlines and follow-ups depend on individual people.
05
Media breaks
Data travels from email via Excel into Business Central.
06
Knowledge in one head
When that one person is away, the process stops.
Building blocks
What we build for you with the Power Platform.
We start small, with the workflow that costs the most time today. Then the solution grows.
01
Approval workflows
Purchase order Invoice Leave Budget
Multi-level approvals with deputies, deadlines and reminders. Every decision stays traceable.
02
Forms and requests
Power Apps Forms SharePoint
Entries made directly on a tablet or phone. Required fields and picklists prevent typos.
03
Business Central connection
API Webhooks Connector
Orders, master data and postings flow between Business Central and your workflow, without retyping.
04
Business apps
Power Apps Dataverse
Small apps for field sales, warehouse or service. Tailored to your day-to-day work, without major development.
05
Notifications
Teams Outlook Adaptive Cards
The right person learns at the right time what needs to be done. Directly in Teams or by email.
06
Scheduled workflows
Schedule Trigger Recurrence
Month-end closing, dunning runs and reports start on time, even if nobody thinks of them.
07
Data storage in Dataverse
Dataverse SharePoint SQL
Structured data with roles and permissions instead of scattered Excel files.
08
Process documentation
Flowchart Roles Owners
Every workflow has a plan and an owner. That keeps it understandable and easy to change.
How we work
Six rules for every workflow.
Automation should take work off your plate, not create new questions. That is what we stick to.
Rule 01
Understand the process first
We first look at how things work today. What is unnecessary is not automated but dropped.
Rule 02
Standard before custom build
We use existing connectors and licences. Custom development only where it is needed.
Rule 03
Plan for exceptions
Every workflow knows the case where something is missing or rejected. Then it goes to a person, not into the void.
Rule 04
Assign permissions properly
Access runs via Entra ID and roles. Everyone only sees what they need for their task.
Rule 05
Make errors visible
If a run fails, the person responsible gets a notification. Nothing is left lying around unnoticed.
Rule 06
Handover without dependency
You get documentation and training. Your key users make small changes themselves.
Process
Four steps to a workflow that runs.
System Audit
½-day workshop
We capture workflows, systems and licences. You receive a prioritised list with a clear effort estimate.
Prototype
Duration: 1 to 2 weeks
The most important workflow runs as a prototype with real data. Your team tries it out.
Implementation
Duration: depends on scope
We build, test with the users and connect Business Central. Changes are incorporated continuously.
Operations
Duration: ongoing
Monitoring, adjustments and support. New workflows are added as needed.
Results
We measure before. And after.
Together we define how you will recognise success. Before the start we measure the current state, afterwards we compare using the same yardstick.
Lead time
Metric 01
From request to decision, in hours instead of days.
Follow-up questions
Metric 02
How often a case is chased up or entered again.
Manual work
Metric 03
Time per week your team spends transferring data.
For IT managers
Technology that doesn’t add to your IT team’s workload.
- Platform
- Power Platform in your M365 tenant, separate test and production environments.
- Development
- Solutions packaged as Power Platform solutions, versioned and transportable.
- Connectivity
- Business Central via API and connectors, other systems via HTTP.
- Integration
- Dataverse, SharePoint and Teams as data storage and user interface.
- Operations
- Error monitoring, an owner for each workflow, support with response times.
- Security
- Entra ID, roles, data loss prevention policies. EU data centers only on request.
- Quality
- Testing in a separate environment, acceptance by the business team.
- Handover
- Documentation, key-user training, licence overview.
Getting started
Start with the System Audit.
½-day workshop. Fixed price. A clear result. If you then commission the implementation, we credit the full price.
€2,999net
Audit deliverables
List of your workflows by time spent- The three best candidates for automation
- Overview of Power Platform licences and permissions
- Roadmap with effort and sequence
No. The Power Platform is designed for business teams. We build the complex parts. After training, your key user can make small adjustments themselves.
That depends on users and workflows. Much is already included in Microsoft 365. In the System Audit we review your licences and state what you need.
Yes. There are standard connectors and the Business Central API. We check in advance which version and which extensions you use.
The person responsible gets a notification with the cause. The case is not lost; it waits for clarification.
In your Microsoft 365 tenant. On request, we use data centers in the EU exclusively.
A first prototype is usually ready after one to two weeks. The scope determines when it goes live.
Then we adapt the workflow. It is documented and versioned. Your team can make smaller changes themselves.
No. Business Central remains the leading system. The Power Platform handles the workflows around it that the ERP does not cover.