For operations, finance and purchasing
Business process automation: approvals based on predefined rules, documents filed automatically.
On Microsoft 365 and Power Platform, connected to your ERP and to e-signature. Where a system has no API, we use RPA robots. Every step has an owner, and every decision is recorded in the history.
- Process automation since 2016on Microsoft platforms
- Approval workflows deliveredin manufacturing, healthcare and services
- BPMN 2.0the standard notation, on request, as the process specification
One process, end to end
What an automated process looks like: approving a contract
Approving a contract, from draft to archive. Each lane is a role, each box a step. Select a step to see what happens there and what it runs on.
- Author
Process starts
An employee needs a new contract with a supplier, a customer or a partner.
- Author
Draft from template
The contract is generated from the company template. Partner and value are taken from the app, not typed.
- Legal
Legal review
Legal receives the contract in Teams. Comments are saved on the contract, not in emails.
- Legal
Approved by legal?
If not, the contract is sent back to the author with the requested changes. If yes, it is sent to finance for review.
- Finance
Finance check
Finance checks the value and payment terms and approves from a card in Teams.
- Finance
Above the value threshold?
You set the threshold. Below it, the contract goes straight to signing; above it, management approves it.
- Management
Management approval
Management opens the contract and the previous approvals in a single card, and approves or rejects from it.
- DocuSign
Signing in DocuSign
The approved contract is sent for signing automatically, first to the partner, then to management.
- SharePoint
Filing by partner
The signed copy and the signing certificate are saved automatically in the partner folder, with metadata and retention.
- SharePoint
Contract concluded
The contract can be found by partner, value or date. Before the expiry date, the app sends an alert.
·
Which business processes we automate
The process stays yours. Approvals, documents and signatures are handled in one application, with a history, instead of emails and spreadsheets.
Multi-step approvals
By role and value threshold, with a full history, up to six steps in a workflow delivered in manufacturing. Approved from a card in Teams.
Documents filed automatically
Every document is saved next to its record, with metadata and retention.
Data between systems
ERP, e-invoicing, DocuSign, your bank. The integration validates before it writes.
Agents that fill in requests
The agent fills in the request from Teams; a person confirms before anything is saved.
Deadlines and alerts
For whatever is expiring or running late, its owner gets an alert before it becomes a problem.
RPA robots for systems without an API
UiPath or Power Automate Desktop enter data in the screens of legacy applications, like an operator, with no manual typing. We use them only where there is no other way to integrate.
How we automate a process, step by step
We start from the current process, with its steps and exceptions.
- 01
We describe the process
With the people who run it, step by step, with its exceptions.
Teams
- 02
We model it
If you need formal documentation, we model the process in BPMN 2.0.
- BPMN 2.0
- 03
We build it
The rules in the app, the integration between systems, RPA robots where there is no API.
Power Apps
Power Automate
- 04
We test it with you
On real data, with the people who will use it.
- Teams
- 05
We hand it over
Documented, so your team can run it. Or we keep running it, with support and an SLA.
SharePoint
Pick a process. Follow it from request to archive.
For each process: the steps, the systems involved and the screen at each step.
Purchase approvals
Teams to AI agent
Step 1: Request
Someone writes in Teams what they need: 500 blue pens, by the end of the month. The agent asks only for what is missing.
AI agent to Process app
Step 2: Search
The agent looks up the item in your catalogue, by name and by code, and proposes only items found there.
Process app to Teams
Step 3: Proposal
The agent shows the proposal in Teams as a card, with the item, the quantity and the deadline. The deadline can be changed.
Teams to Process app
Step 4: Purchase request
The person clicks Create. Only now is the purchase request saved, as a draft.
Process app to Teams
Step 5: Approval
Sent for approval: the application picks the approvers by category and value.
Process app to Teams
Step 6: Approved
The approved purchase request stays in the application, with its approvals and history. The requester receives the decision in Teams.
Common situations
- Purchase requests are approved by email, with each approver separately.
- E-invoices are compared by hand with the order and the delivery note.
- Contracts are sent to legal and finance as separate versions by email.
- The same order is entered once in an application and again in the ERP.
- The only way to know where a request stands is to ask someone.
- Insurance, inspection and service deadlines are tracked in a spreadsheet.
If at least three of these sound familiar, those processes can be automated in the Microsoft 365 you already have.
Discuss your processQuestions about business process automation
Our teams run on spreadsheets. Do they have to give them up?
No. Spreadsheets stay for analysis and reporting. The process data is recorded in an application, with validation rules and a history, and it can still be exported to Excel.
Our ERP is old and has no API. Can the process still be automated?
Yes. Where a system has an API, Power Automate flows call it directly. Where it has none, an RPA robot enters the data in the system's screens, the way an operator would. Both can run in the same process, and every run is recorded in the history.
We use local accounting and ERP systems. Can you connect them?
Yes, through an API, through import files or through an RPA robot. Our accounting automations on SAGA, a Romanian accounting system, run in production.
Do we have to replace our ERP to automate?
No. The ERP stays the system of record. The process sends it the data and gets the record number back.
People will not adopt yet another system.
Approvals happen in Teams and Outlook, where people already work. The process is tested on real data, with the people who will use it, before go-live.
Can we start with a single process?
Yes. The two-day hackathon starts from a process you choose, on your own data.
Examples of automated processes
Purchase approvals
From one sentence in Teams to an approved purchase order.
Contract approvals
From draft to DocuSign signature and the archive.
Supplier invoices
From the e-invoice to a payment prepared in your bank.
IT tickets
From chat to resolution, with the team and the SLA chosen automatically.
Leave and timesheets
The employee requests leave, and working days are calculated from the work schedule, minus public holidays.
Asset management
Insurance, inspections, servicing and warranties, with an alert in Teams before the deadline.
How we work
No hidden risk: what you know from the start.
The estimating risk is ours. Your data and your plan stay yours.
Your data stays in your tenant
The solution runs in your own Microsoft 365 and Azure. There is no separate platform to license or maintain.
Fixed price, fixed scope
We price the work before we start. The scope is written down before the first line of code, and any change is priced and agreed in the open.
The written plan is yours to keep
Our proposal comes in writing, with the scope and the steps. Keep it and use it, whether you work with us or not.
Pick the process that costs you the most. That is the one we automate first.
In 30 minutes we go through the process and agree what to prepare before the project.
Thank you.
We will reply within one business day.