# The FM back office, and what it actually costs you

> The FM back office is where margin is won or lost. What it covers, why cost scales with volume, and what changes when AI runs the loop. 500k+ work orders in.

Source: https://tyten.ai/guides/fm-back-office  
Published: 2026-08-07  
Last updated: 2026-11-07

---

Guide

Every FM operator knows the back office is where the money goes, and almost nobody can say how much. This is what it covers, why it grows in step with contract volume, and what changes when an AI workforce runs the loop instead of a growing team.

Published August 2026 · Updated 7 November 2026

## What the FM back office is

The FM back office is everything that happens around the work, rather than the work itself. An engineer fixes a fault in an hour. The back office spends considerably longer raising the job, finding a compliant contractor, agreeing a price, booking the visit, chasing the paperwork, checking the supplier bill and raising the client invoice.

It is administrative, it is repetitive, and it is where FM margin is won or lost. It is also the part of an FM business that grows in direct proportion to contract volume, which is why it becomes the constraint on growth.

## The five loops it runs

| Loop | What it involves | Where it breaks |
|---|---|---|
| Intake | Requests arrive by email, phone and portal and have to become structured work orders. | Requests sit unread; the same fault is raised twice; urgency is misjudged. |
| Dispatch | Finding a contractor who is available, priced and compliant right now. | Work goes to whoever answers, including suppliers whose insurance has lapsed. |
| Chasing | Quotes, job sheets, certificates and remedials pursued until they arrive. | Nobody owns it, so it happens when someone remembers or when a client asks. |
| Documentation | Reading what came back, checking it is complete, filing it against the job. | Paperwork is filed unread, so failures surface at audit rather than on the day. |
| Billing | Checking the supplier bill against the job, then invoicing the client. | Overpayment on unproven work; revenue sitting uninvoiced until month end. |

Each loop maps to an AI worker: [reactive helpdesk](https://tyten.ai/platform/reactive-helpdesk), [PPM chasing](https://tyten.ai/platform/ppm-chasing), [document tracking](https://tyten.ai/platform/document-tracking), [accounting](https://tyten.ai/platform/accounting) and the [voice agent](https://tyten.ai/platform/voice-agent) on the phone.

## Why it scales with headcount

More than 500 hours of shadowing UK FM back offices produced a blunt finding: roughly 95% of the work is manual, repetitive and fully automatable, and it is still done by hand. That has three consequences that compound.

|  | What happens |
|---|---|
| Headcount tracks volume | Back-office headcount grows in line with contract volume, because there is no other way to absorb the work. |
| Pressure creates errors | High-volume, high-pressure work burns people out. Staff leave months after being trained, and the errors rise with the workload. |
| The cause is structural | It is not a training problem or a software problem. The work itself is repetitive, so adding people scales the cost without removing the cause. |

## What changes when AI runs it

Live in production since November 2025, TYTEN's AI workforce has run more than 500,000 work orders end to end across UK FM clients. Between November 2025 and July 2026 it also processed £4.1M of accounts payable and chased 7,144 job sheets. At Penguin FM, a subcontractor network of around 250 suppliers, the first three modules produced a 40% increase in available helpdesk capacity, a 5x increase in work order volume handled, and cleared 100% of the backlog.

The pattern is consistent: headcount stays flat while volume grows, invoices leave the day the job completes rather than at month end, and compliance gaps surface before they reach the client. Read the [full account](https://tyten.ai/insights/penguin-fm-ai-helpdesk-transformation) of how that was built.

## Automate it, offshore it, or build it

|  | What you get | What it does not fix |
|---|---|---|
| Hire more coordinators | Immediate capacity, and judgment on day one. | Cost scales with volume, and the repetitive work remains repetitive. |
| Offshore the helpdesk | A lower hourly rate for the same tasks. | The same manual loop, now with a time zone and a handover in the middle. |
| Build it in house | Complete control of the roadmap. | An integration treadmill across every CAFM, mailbox and accounting system you touch. |
| An AI workforce | The loop itself is done, with every action logged against the work order. | Judgment, exceptions and relationships stay with your team, by design. |

The longer arguments: [versus hiring a coordinator](https://tyten.ai/guides/tyten-vs-hiring-a-coordinator), [versus offshoring](https://tyten.ai/insights/offshore-helpdesk-vs-ai-fm-cost-comparison), and [versus building it yourself](https://tyten.ai/insights/build-in-house-fm-back-office-software).

## Working out your own number

The honest way to size this is against your own volumes rather than a case study. The [ROI calculator](https://tyten.ai/roi-calculator) takes your work order volume and the areas you would automate, and returns hours saved, full-time equivalent freed and annual cost saving. No email required.

## FM back office FAQ

### What counts as the FM back office?

Everything around the work rather than the work itself: raising jobs, dispatching contractors, agreeing quotes, chasing job sheets and certificates, checking supplier bills and invoicing clients.

### Why does back-office cost grow with contract volume?

Because the work is manual and repetitive, so the only way to absorb more of it is to add people. Roughly 95% of it is fully automatable, which is why headcount and volume have historically moved together.

### Will automating it mean redundancies?

It takes the routine loop of raising, chasing, checking and filing. In production the pattern has been more capacity from the same team rather than a smaller team, with people moving to exceptions and client relationships.

### Do we have to replace our CAFM to automate the back office?

No. The AI workforce sits on top of the CAFM you already run and writes back to it, and it also works across the mailbox, phone line and accounting system where much of the back office actually happens.

### How is this different from offshoring the helpdesk?

Offshoring changes who does the manual loop and what they cost. It does not remove the loop. An AI workforce does the loop itself and logs every action against the work order.

### How long before it is running?

Typically 4 weeks to go live with the first module, and faster for each one after because the integration is already established.

## See your back office run itself

30-minute demo. We run real scenarios from your own operation end to end and show the audit trail behind every action.

[Book a Demo](https://cal.com/tyten/30min)