Process description
In one or two meetings we write down the process as it is: who starts it, who approves, what data is needed and where it must end up. Most often it turns out that half the steps are unnecessary.
We build business apps and automate processes with Microsoft Power Platform tools, most of which are already in your Microsoft 365 licence. From leave requests to SAP Business One and Business Central integrations, with governance so it does not turn into chaos.
Built for ISO 27001NIS2 DORA
Almost every company has processes that never got a system of their own: leave requests travel by email, supplier invoices are approved by forwarding PDFs, the equipment register is an Excel sheet on a shared drive, and site inspections are filled in on paper. Each of these processes costs employee time and breeds errors, and a separate system for each would be too expensive. At the same time, most of these companies already have Microsoft 365, which includes Power Platform tools, but nobody uses them, or IT does not know what runs where.
We do two things. First, we build specific solutions: a Power Apps app with a form on a phone, a Power Automate flow that starts an approval in Teams and writes the result to SharePoint or Dataverse, a Power Pages portal for customers or partners, a Copilot Studio agent that answers employees' questions from your documents. Where needed, we connect SAP Business One, Business Central or another accounting system through an API or an intermediate database. Second, we put governance in place: separate environments for development, testing and production, DLP policies that stop business connectors from mixing with external services, licence control and a solution register, so that a year later it is clear what runs, for whom and why. We tell you what is included in Microsoft 365 and what needs a premium licence before we start, not after the invoice.
Solutions, and the governance around them.
Canvas apps for phone and browser: forms, registers, inspections. Model-driven apps on Dataverse when you need relationships between tables and roles.
Cloud flows for approvals, notifications and moving data between Outlook, Teams, SharePoint and accounting. Desktop RPA for legacy applications without an API.
External portals for customers or suppliers: submitting requests, order status, document exchange, with sign-in through Entra ID or email.
Agents in Teams and on your website that answer from your documents, log a request in the helpdesk system or start a Power Automate flow, with clear boundaries.
A data model in Dataverse or SharePoint lists, depending on scale, role-based permissions, auditing and backups. SQL or API connections to existing systems.
Reading and writing invoices, customers and balances: Business Central through standard connectors, SAP Business One through its API or an intermediate SQL database in an ERP hosting environment.
Development, testing and production environments, DLP policies for connectors, and moving solutions through solutions packages so the production version does not change with a single click.
We assess what works with Microsoft 365 and what needs a premium licence, monitor flow errors and maintain the solutions.
What each is for, which licence it needs and a typical example from our practice.
| Power Apps | Power Automate | Power Pages | Copilot Studio | |
|---|---|---|---|---|
Who it suits | internal forms, registers and inspections on a phone | approvals, notifications and moving data between systems | external portals for customers and partners | agents in Teams and on a website that answer from your data |
Licence | Microsoft 365; Dataverse and premium connectors need a separate licence | Microsoft 365; premium connectors and desktop RPA need a separate licence | separate, by number of users | separate, by number of messages |
Example | equipment register with a QR code and an on-site inspection form | supplier invoice from email to SharePoint, approval in Teams, entry in Business Central | customer portal with order status from Business Central | agent that answers questions about procedures and logs a request to IT |
Data location | SharePoint, Dataverse, SQL | any connector, SAP Business One through its API | Dataverse | SharePoint, websites, Dataverse |
Typical duration | 1–3 weeks | from a few days to 2 weeks | 2–6 weeks | 1–3 weeks |
From describing the process to a solution in production.
In one or two meetings we write down the process as it is: who starts it, who approves, what data is needed and where it must end up. Most often it turns out that half the steps are unnecessary.
We build a working version in the development environment and show it to the people who will use it. Changes at this stage are cheap, so we keep adjusting until the process feels comfortable.
We connect accounting and other systems, set permissions and DLP policies, test with real data in the test environment and train users.
We move the solution to production through solutions packages, monitor flow errors, manage licences and make changes when the process changes. We keep the solution register up to date.
When a process needs to understand free text or answer from documents, Power Automate is not enough. We build Copilot Studio agents as a separate service.
Partly. Power Apps and Power Automate with standard connectors (SharePoint, Outlook, Teams, Excel) are included in Microsoft 365 business plans. Dataverse, SQL, API and other premium connectors, desktop RPA, Power Pages and Copilot Studio require separate licences. Before we start, we tell you what fits within your current licence.
Yes. We reach SAP Business One data through its API or directly from the database in an ERP hosting environment, where Power Automate writes to it or reads from it. Typical cases: registering supplier invoices after approval in Teams, and customer balances in a salesperson's app.
Power Automate executes precisely defined steps: an event happens, take these actions. Copilot Studio builds agents that understand a question in free text, find the answer in your documents and, when needed, start a Power Automate flow. An agent is added where people ask questions rather than fill in forms.
They can, and for small solutions that is often best. We prepare the environments, DLP policies and rules, train people and review what has been built, so that no flow that sends data to a personal mailbox ends up in production. We build the solutions that involve integrations.
This is the most common Power Platform problem: flows belong to a personal account and stop working when it is disabled. We keep solutions in a solutions package with a service account as the owner, document them in the register and maintain them.
We take over the day-to-day administration of your Microsoft 365 tenant: users and licences, Teams and SharePoint permissions, mail rules, Secure…
We select and supply Microsoft 365 licences as a Microsoft CSP partner: Business Basic, Standard, Premium and Enterprise plans and the Copilot add-on.
We turn on and configure Microsoft Viva apps in your Microsoft 365 tenant: an employee portal in Teams, communities, learning, surveys and…
This service is delivered by specialists with valid international certifications. Their expertise is confirmed by independent organisations, not by us.
Cloud security is managed following ISO/IEC 27017 and 27018 practices.
AI systems are deployed with protection against data leakage and model abuse.
We reply within 1 business day