What a Copilot Studio Agent Build Actually Costs a 30-Person Firm in Year One

Nobody publishes an all-in number for a first agent. Microsoft publishes credit rates. Consultancies publish day rates or a build fee. Resellers publish licence prices in a currency that moves with the exchange rate. The firm that wants to know what its first agent will cost in year one is left adding up five things it does not fully understand, and the partner who has to sign it off gets a range too wide to be a budget.

This post adds them up. It follows one imaginary firm through twelve months, with the numbers landing where they would land on real invoices: ours, Microsoft’s and the Azure bill nobody expected. The honest finding is that the build fee is the smallest surprise. The lines firms miss are Copilot Credits, premium connectors and what happens after launch.

Every Microsoft price below is the US dollar list price at September 2026, with an approximate sterling figure. Microsoft sets prices in dollars and converts them per product and per month, so check Microsoft’s UK pricing page or your reseller before a figure reaches a spreadsheet. FiveForward prices are in sterling, exclude VAT and are the ones published on our pricing page.

The firm

Thirty staff. A professional firm, accountancy or legal, it makes no difference to the sums. Business Standard or Business Premium already in place. No IT team: the office manager is the Microsoft 365 admin because somebody had to be. Ten of the thirty hold a Microsoft Copilot licence, the partners and the people who draft most.

They want one agent to start. It answers staff questions about internal procedures from the SharePoint library where the procedures already live, drafts standard client letters from a short form and posts each draft to a Teams channel for a person to review before it goes anywhere. It is built on the standard harness in Copilot Studio, for a reason that becomes a budget line at invoice four.

That shape is deliberate. It keeps most of the agent’s running cost inside the licences the firm already pays for.

Invoice one: Discover and Design, £1,500

The year starts with the only FiveForward invoice that is not tied to a build. Discover maps the firm’s workflows, finds the agent opportunities and, with Design, produces the roadmap, the workflow map, the recommended build route and a fixed price for that route, played back in a session of about an hour. Two stages, one fee.

The fee is credited back in full once follow-on spend reaches £3,500 before VAT within 90 days of the roadmap. For any firm that goes on to build, this line is a deposit rather than a cost, and it comes off the build invoice. It appears in the totals below as £1,500 out in month one and £1,500 back in month three.

Invoice two: the build

The Design playback ends with a choice between two routes, and the firm’s second invoice depends on which it takes.

Route one, FiveForward builds. Typically £5,000 to £15,000, fixed at Design with the specification included. Three things move the price: how many agents, how many systems they connect to and the state of the source data. The imaginary firm’s first agent connects to SharePoint and Teams and its procedures are in reasonable shape, so it sits at the low end. Call it £7,000, with £6,000 to £8,000 as the honest range.

Route two, the firm’s own people build. £3,950 fixed: two delivery days, two build reviews and 90 days of async support answered within two working days. Cheaper on paper. What it costs the firm is two people’s time across the delivery days and the weeks between them, plus a champion who keeps going after the 90 days end. On its own, route two triggers the Discover credit, because £3,950 clears the £3,500 threshold.

The Automate page describes what route one delivers and the standard route two builds are held to. Both routes end with the same thing: an agent in the firm’s tenant, documented, with a named owner.

Invoice three, from Microsoft: Copilot licences

Now the invoices come from Microsoft, and the first is the one the firm already understands. Copilot Business, the licence for organisations up to 300 users, is $21 per user per month on an annual plan at September 2026 list, about £16. Microsoft has been running a promotional $18 rate during 2026. It is time-limited, so budget at list and treat the promotion as a bonus if it still applies when you buy.

Ten licences at list is about £160 a month, or £1,930 a year.

Two things about this line matter more than the number. First, the licence is what makes agent use free of credits for those ten people. On the standard and Copilot Chat harnesses, internal users with a licence do not draw credits when they talk to the agent, within fair use. For the people who hold it, the licence is the agent’s running cost. Second, not everyone needs one. There is no minimum seat count, and a background automation nobody chats to needs credits or Power Automate licensing, not user licences. Our Copilot Basic vs Premium post covers who should be licensed and who is fine on the included tools.

Invoice four, from Microsoft: Copilot Credits

The second Microsoft invoice is the one firms do not see coming, because until this year most of them had never bought a credit. Copilot Credits are Microsoft’s usage currency for AI work the licence does not cover. They pool at tenant level, are bought on a pay as you go meter at $0.01 a credit and are billed monthly in arrears. Our Copilot Credits reference has the full picture. What matters here is what this one agent draws.

The ten licensed users draw nothing. The other twenty pay per response: 12 credits for an answer grounded on the firm’s Microsoft 365 content, 2 credits for an answer from uploaded files or a website and 5 credits for each tool the agent calls, such as the flow that posts a draft letter to Teams.

Rough it out. Twenty unlicensed staff at 15 conversations a month is 300 conversations. Say half use the procedures library, and half of those pull from SharePoint at 12 credits while the rest answer from files at 2. The other 150 conversations each fire one tool at 5 credits. That is about 1,800 credits a month. Allow for conversations that run to two or three exchanges and it still sits around 5,000 credits, about $50, under £40 a month. Under £500 for the year.

At that volume the firm should never start on the 25,000 credit capacity pack, which is what the product Microsoft calls the Copilot Studio licence actually is: $200 a month, about £150, resetting monthly with no carry-over. Below roughly 20,000 credits a month, pay as you go is cheaper. A first agent belongs on the meter, with a spend cap set in the Microsoft 365 admin centre before it is published. The three numbers to check before an agent goes live walks the office manager through exactly that.

Now the contrast that makes the harness choice a budget line. Build the same agent on the GitHub Copilot harness, the new default in Copilot Studio, and the per-response rates no longer apply. Every run is metered against Microsoft’s planning bands from the September 2026 guide: 100 to 300 credits for a light run, 300 to 500 for a medium one, more than 500 for a heavy one, licence or no licence. Run a medium-weight automation once a day and that is 9,000 to 15,000 credits a month, $90 to $150, roughly £70 to £110, before anyone has asked it a question. The imaginary firm’s agent answers frequent, low-value questions from licensed and unlicensed staff alike, which is precisely the work the licence already covers on the standard harness, and that is why it is built there. Our guide to which harness an agent belongs on works through the decision properly.

Invoice five, from Microsoft: premium connectors

This is the invoice that arrives mid-build if nobody checked. The agent’s flows post to Teams and read from SharePoint, both standard connectors, included with Microsoft 365. Nothing extra.

The moment a flow touches SQL, an HTTP call, Dataverse or a non-Microsoft system, it is using a premium connector, and every user who runs that flow needs Power Automate Premium at $15 per user per month on an annual plan, about £11. The alternative is pay as you go at $0.60 per premium flow run, about 45p. Neither is large. Both are a surprise if the budget had no line for them.

We have watched this happen. A firm’s build got underway, the team discovered that the connector to the system they needed was premium, and the whole thing paused while someone found out what a Power Automate Premium licence was and got the spend approved. Nothing was wrong with the design. The connector tier had not been checked. The fix is to check it at Design, which is one of the things the specification is for. Our Copilot Studio vs Power Automate post explains where flows sit in an agent build in the first place.

Invoice six, from Azure: consumption

The imaginary firm’s first agent has no Azure line. Scenario two, below, does, so it is worth knowing what the line looks like.

Document-processing builds, the pattern behind our post room case study, use Azure AI Document Intelligence to read scanned pages: $1.50 per 1,000 pages for OCR, $10 per 1,000 for layout or prebuilt models and $30 per 1,000 for custom extraction, at September 2026 list. An Azure OpenAI step is billed per token on top of Copilot Studio credits, and it is the line firms discover a few months in. Functions, Storage and Logic Apps are pennies to a few pounds a month at a 30-person firm’s volumes.

Add it up and a post room style pipeline runs £10 to £200 a month in consumption, depending on page volume and model choice. Small, but it is a separate line on an Azure bill and someone has to own it.

Invoice seven: Embed

The last invoice is the one that decides whether the agent is still working in month twelve. Embed is the retainer: Starter at £750 a month for up to two production solutions with questions answered within two working days, Growth at £1,500 for up to ten with a one working day response and Enterprise scoped individually. Three month minimum, reviewed quarterly, so £2,250 is the smallest commitment and £9,000 covers a full year on Starter.

What it covers is agent operations, optimisation and new use cases, and async support: prompt tuning, knowledge sources kept current, connector troubleshooting, authentication renewals, fixes to what exists and usage reviews. What it does not cover is anything new: new agents, new workflows, new integrations, new Azure services. Those are scoped separately, always. Route two firms have 90 days of the same support included in the build price and then choose whether to continue on Embed. What happens after the agent is built explains what that month of running actually contains.

Three year-one totals

Put the invoices in a column and the year looks like this for scenario one, with the Discover fee shown as it lands and as it comes back.

The ranges move with the build. Put the route one build at £8,000 and the typical year is closer to £19,500. Add a workshop cohort to route two and the lean year touches £7,000.

Then scenario two, on top. The same firm wants a document-processing pipeline: scanned post read, matched to clients and filed, with Azure Document Intelligence doing the reading and an Azure OpenAI step doing the understanding. More systems connected, so the build sits at the upper end of the range. The post room case study is the kind of build that lands at £10,000 to £15,000. Add £120 to £2,400 a year of Azure consumption, then the same licence, credit and Embed lines as before. Two solutions in production still fit Embed Starter.

One observation to close the numbers. In the typical scenario the recurring lines, licences, Embed and credits, pass the build fee inside the first year. Even on the lean route they catch it within two. So the decision in front of the partners is not really whether the firm can afford a build. It is whether this is a capability the firm wants to run. Firms that answer yes budget for the running from the start. Firms that answer no should not build yet.

What it replaces

The other side of the ledger is the work the agent takes on, and here the inputs are more useful than a conclusion. In builds we have delivered for firms of this size, a work in progress report that took managers up to 30 minutes became a five-minute conversation with an agent. Letters of engagement and letters of representation went from 30 to 60 minutes each to filling in a form and reviewing the output. Post handling that took up to two hours a day now takes a person’s attention only for the exceptions that need judgement.

We are not going to claim a payback period, because it depends on how many letters your firm sends and what your managers’ time is worth. Put your own volumes against those figures and the sum is yours. The work does not disappear. It moves, the time comes back and the judgement stays with the person who reviews the draft.

If the pace of Microsoft’s pricing changes is what is holding the decision, we have written separately on whether waiting for it to settle is the right call.

The one thing to do next

Every figure above is an illustration for a firm that does not exist. The version with your firm’s name on it comes out of Discover: £1,500, credited back once the build starts, ending with a fixed price for your specific first agent, the harness it belongs on, the connector tiers checked and the running costs modelled. That is the number to put in front of the other partners. If you would rather talk it through first, book a free consultation.

Sources checked

Last checked: 12 September 2026. Microsoft prices are US dollar list at September 2026 and subject to change. Sterling figures are approximate.

• Microsoft, Copilot Credits Guide, September 2026
• Microsoft Learn, standard harness licensing in Copilot Studio
• Microsoft, Copilot pricing
• Microsoft, Microsoft 365 business plans and pricing, UK
• Anders Jensen, Copilot Studio pricing 2026, including per-feature rates
• FlowForma, Power Automate pricing, August 2026
• Citizen Development Academy, Power Automate pay as you go rates, June 2026
• DocuOCR, Azure Document Intelligence pricing, July 2026
• FiveForward pricing