Most of it is already in the subscription.
A business paying for Microsoft 365 is already paying for approvals, forms, automation, reporting and a document system. Much of the work below is turning on what has been bought and left switched off, and building the few pieces that genuinely are not there.
You buy your own licences, direct, at Microsoft’s published price. We hold no reseller agreement and no Microsoft designation, so nothing here earns us anything except the work itself. Each section below carries the published limit that decides how the job has to be built — the ones we could read off Microsoft’s own documentation, and no others. Every price we charge sits on one page.
Seven pieces, and what each is good for.
Power Automate
A job that runs without anybody starting it — a file arrives, a form is submitted, a date passes, and the next four things happen on their own. This is where most Microsoft 365 automation belongs, because it is already in the subscription.
The published limit. The free licence covers standard connectors only. The moment a flow reaches for a premium or custom connector it needs a paid Power Automate licence on top of Microsoft 365 — which is the cost most often missed when a flow is scoped by somebody counting steps.
SharePoint
Where the documents already are, and where the list somebody built in 2019 is now doing a job it was never designed for. We build the structure, the metadata and the retrieval, and we say when a list has become a database wearing a list’s clothes.
The published limit. The list view threshold is 5,000 items and cannot be raised in SharePoint Online. It counts what a single query has to touch rather than what the list holds, so a list of 200,000 is fine and a careless view over 6,000 is not. The fix is an indexed column and a filter, decided before the list is built rather than after it stops opening.
Power BI
The report somebody rebuilds by hand every Monday. We connect it to the source, model it so the numbers survive a question, and publish it where the people who need it already are.
The published limit. On shared capacity a semantic model gets eight scheduled refreshes a day and each has to finish inside two hours. Premium, per-user or Fabric capacity takes that to 48. If the answer has to be current to the hour, the capacity decision is made on day one and it is a licensing decision rather than a modelling one.
Microsoft 365
The parts of the subscription nobody switched on. Approvals, forms, shared mailboxes, retention, the permissions that were set once and never revisited. Usually the shortest job on this page, because the capability is already bought and only has to be set up.
Azure
Where the work goes when it outgrows a flow — a function on a schedule, a queue, a small service joining two systems that were never meant to speak. Also where a backend belongs when the alternative is a runtime you cannot take with you.
Fabric
One place for the data that currently lives in a warehouse, a spreadsheet and somebody’s laptop. We treat it as the destination for data engineering work rather than as a product to be sold on its own.
Copilot
Adoption rather than another tutorial. What it should be pointed at, what it must be kept away from, who is allowed to see what once it can read everything, and how anyone will know whether it helped. The permissions question is the whole question. Microsoft’s own wording: it only surfaces data to which individual users have at least view permissions — so whatever your sharing settings already allow is what it will find, and that is a tidy-up job before it is an AI one.
True across all seven.
-
You buy the licences, direct
We hold no reseller agreement and no Microsoft designation, so nothing on this page earns us a commission or a tier. It also means we can say the plan you already pay for is enough, and often it is.
-
The licence decision comes before the build decision
Two of the limits above are licensing, not engineering — the connector a flow may use and the number of times a report may refresh. Both are cheaper to settle at the start than to discover in the second month, and both change what gets built.
-
The code stays somewhere you can take it
Where a job can sensibly live outside a vendor runtime, that is where we put it. It runs on any tier, it can be handed to your own developer, and it survives a decision to move.
What the work costs.
The platform changes how a job is built, not what it is worth, so these are the same figures as everywhere else on this site.
-
A flow that starts itself
One job at $2,550, or the whole chain around it at $3,950. Work that runs on its own.
-
Joining Microsoft to something outside it
One connection in one direction at $3,250, or two systems kept in step both ways at $11,500. The integration work.
-
Paperwork that somebody reads and retypes
One kind of document, handled end to end, at $3,650. The paperwork work.
-
Reporting that has to be trusted
A read-only report on what is actually in the data at $390, the cleanup at $2,950, and a move with the count proved on both sides at $4,900. The data work.
-
A written answer before you commit to any of it
What is worth doing, what your licences already cover and what they do not, written down and yours to keep, at $1,350. The written review.
When it is running, somebody has to be watching it.
A build is finished the day it goes live. Keeping it alive is a different job, and on a platform that ships changes to every product above on its own schedule it is not an optional one.
Watch
$549 per month
“It runs. I do not want to be the one who notices when it stops.”
- We are told the moment a run fails, and we tell you
- A written note every month of what ran, what failed and what we did
- Broken things fixed by the next working day
- Your accounts stay yours — we hold access, not ownership
Guard
$849 per month
“I need to know about the runs that finish and quietly do nothing.”
- Everything in Watch, plus:
- We check the runs that finish but do nothing, where there is something to count
- Broken things fixed the same working day
- Changes are unlimited — they join a queue and we work through it in order
Managed
$1,200 per month
“I do not want to run it at all. I want somebody whose job it is.”
- Everything in Guard, plus:
- We operate it, not you
- A named person, and the name of their backup
- Reachable outside business hours when something is genuinely down
- Your changes are worked ahead of everyone else’s
Monthly, in advance. Thirty days’ notice either way, from either side. Offered after a build, never before — we will not sell you a plan to watch something we have not seen.
Tell us which licences you pay for.
The plan, roughly how many people, and the job that is being done by hand. We will tell you whether it is already covered by what you buy, whether it needs one more licence, or whether it is a build. We reply within one business day.