For Microsoft 365 teams
Automation for companies that run on Outlook, Excel, SharePoint and Teams.
Most Microsoft 365 companies already pay for more than they use. Power Apps and SharePoint lists sit there while the real work happens in an Excel file on someone’s desktop and a chain of Outlook replies. We build in your tenant, with your IT team’s rules, and use what you already licence before adding anything new.
For operations, finance and IT leads at companies of 5 to 1,000 people whose processes live in Outlook, Excel and SharePoint.
Before and after
What changes in a normal week.
Today
- Requests arrive in a shared Outlook mailbox and are forwarded around until someone picks them up.
- The tracker is an Excel file on SharePoint that two people cannot safely edit at the same time, so copies appear.
- Approvals happen in Teams chats and nobody can find them three months later.
- A Power Apps form was started once, got halfway, and the person who built it has left.
After the build
- Each request in the shared mailbox becomes a record with an owner and a due date, and the sender is told who has it.
- The tracker becomes a SharePoint list or a small database, with Excel kept for the reports people like to read.
- Approvals go through a defined step in Teams, and the decision, the approver and the time are stored on the record.
- The Power Apps form is finished or rebuilt, documented, and handed to someone on your team who can maintain it.
What we build
The systems behind the change.
Built in your accounts, at a fixed price agreed after the audit. Builds start at $1,500.
- Shared mailbox triage
Emails to a shared Outlook address sorted by type, logged as records and assigned, with anything unclear sent to a person to decide.
- Approval workflows in Teams
Purchase, leave or quote approvals with set approvers and limits, posted in Teams and recorded on the request.
- Excel trackers moved to lists or apps
The spreadsheet everyone shares turned into a list or internal tool with roles, with exports back to Excel for reporting.
Proof
A team that has already made the change.
How it starts
Three steps, each with a price.
- 01Discovery call
Thirty minutes on the work your team does by hand. Free, and you leave with a yes or no on fit.
- 02Automation Audit, $500
One to two weeks with the people who do the work. Each fix gets hours saved and a fixed price. Credited to the build.
- 03Build, from $1,500
Two-week sprints in your accounts, then 60 days of hypercare by the same engineers.
Questions
What people ask first.
Our IT team controls the tenant. Will they allow this?
We expect them to be involved. We set out what each build needs, which app registrations and permissions, before anything is created, and we work to their policy on connectors and data location.
Why not use Power Automate, since we already pay for it?
Where it does the job, we use it. Some steps, such as reading unstructured emails or calling an AI model, are easier and cheaper outside it, and we will say which and why in the audit.
We already have a half-built Power App. Can you pick it up?
Yes. The audit looks at what exists and whether finishing it or starting again is cheaper. Either way you get documentation so the next person is not stuck where you are now.
Microsoft 365
Bring one process your team still runs by hand.
On a discovery call we look at how it runs today and tell you what it would take to change it, with a price. The call is free.
Book a discovery call