Power Platform automation, live dashboards, and a tenant that's genuinely ready for Copilot rather than merely licensed for it. We find the processes eating your team's week and take them off the list.
The per-user rate falls as your headcount rises. Set yours below to see the exact figure.
No asterisks. This is the scope of the engagement — anything outside it gets quoted separately rather than quietly absorbed.
We sit with your team and find the repetitive work: approvals chased by email, data retyped between systems, reports rebuilt every Monday.
The approvals, notifications and hand-offs automated, with proper error handling so a failed run gets noticed rather than silently skipped.
Purpose-built internal apps for the jobs a spreadsheet has outgrown — site inspections, asset registers, request forms.
Live reporting from the systems you already run, so the numbers in the board pack are the same numbers on the floor.
The unglamorous prerequisite: permissions cleaned up and oversharing closed, so Copilot surfaces what people should see and nothing else.
The point of the work, stated as what's different afterwards rather than what we did.
And it's right, because nobody is copying figures between spreadsheets.
Requests route themselves, chase themselves, and record who approved what.
Rather than an expensive way to surface documents nobody was meant to find.
Set your headcount, pick the options you need, and see what it costs. No account, no card — you'll get a firm proposal from a human.
You move between bands automatically as your headcount changes — there's no renegotiation and no penalty for growing mid-term.
| Band | Headcount | Per user / month |
|---|---|---|
| Starter | 1–10 users | £30 |
| Growth | 11–50 users | £26 |
| Scale | 51–250 users | £22 |
| Enterprise | 251+ users | £19 |
A one-time onboarding fee of £3,500 covers the initial build and handover, waived entirely at 300 users and above.
The questions that come up on almost every first call, answered here so you don't have to book one to get them.
By hours saved against effort to build. We map your candidate processes on both axes in discovery and start with the top-right corner. You'll see that map before anyone writes a flow.
Every flow we build has error handling and alerting, and they're monitored under the same agreement as the rest of your environment. A failed run raises a ticket with us, not a mystery for you.
Probably not yet — most aren't. The usual blocker is oversharing: files and sites open to 'everyone' that nobody notices until Copilot starts citing them. That cleanup is included here.
Configure your team size and tell us your biggest time sink — we'll come back with what we'd tackle first.