What the price covers
One process that costs a team hours every week, on one site, measured before and after. The scope and the price are agreed in writing after a discovery call, so you know both before anything starts.
- Week 1 · Capacity audit: sit with the team, map where the hours go, agree the measure.
- Weeks 2 and 3 · Build in accounts you own, tested on real cases with the people who do the work.
- Week 4 · Live for one team with daily checks, then the before-and-after report and handover.
That is about five days of James's time, spread over four weeks on purpose. The gaps give your IT team time to grant access and check the setup, and your team keeps doing its job. A bigger process takes about ten days over six weeks.
What you get at the end
A working system in accounts you own, the documentation to run it without Mavraq, and a training session for the team that uses it.
You also get a one-page report you can take to group: the number before, the number after, the hours saved at your own cost per hour, and whether the people using it want to keep it, in their words. If the number did not move, the report says so and says why.
The way out after week one
Week one is the capacity audit, and stopping there costs €2,500. If the audit finds nothing worth building, you choose: stop there and keep the report, or move the pilot to another team, and the first week counts towards it.
What you need from your side
- A sponsor who owns the number and can say yes to the process being changed.
- About two hours a week from the team doing the work, mostly in weeks one and four.
- An IT contact in week one, for the accounts and the sign-off on the data.
- The baseline, measured before the build starts by the people who do the work.
What it costs to run afterwards
The running costs are billed to you by the vendors, in your name, and none of it goes through Mavraq. Nothing is charged per person or per site. The automation runs either on n8n, installed in your own cloud account (the Community edition is free), or on tools you already pay for, such as Power Automate or Azure Logic Apps under your Microsoft agreement. The AI model is charged by how much text it reads and writes, at the rates Azure and AWS publish, in your own account.
Matching one supplier invoice to its order and delivery note comes to around a cent of AI time. That is James's estimate, not a vendor's price, and the pilot measures the real figure.
After the pilot
You decide whether to go on. If you do, it continues by the month as a set number of days: Advisory at 2 days a month, Build at 6 to 8 days a month, or Embedded at 12 or more days a month. Thirty days' notice, and what was built keeps running if you stop.
Before you pay anyone for AI, get three things in writing: the one process, how it will be measured, and the price.