Orchestration without the friction

A customer calls their managed service provider with a simple question: was last Tuesday’s work done, and was it done to the standard in the contract?

Answering it is rarely simple. The MSP sold the service and owns the outcome, but a regional partner took the job and one of their engineers did the work. So the account manager messages the partner, the partner messages the engineer, and the photos come back through a chat app two days later, without the test results the customer actually asked about.

Nobody in that chain has done anything wrong. The engineer did the job. The partner passed the message on. The MSP chased it. This is simply the everyday friction of orchestration: the work moves through several businesses, and the record of it does not.

Accountable for work you don’t see

Most MSPs deliver some field work with their own people and a good deal more through others: subcontractors, specialist partners and independent engineers. It is a good model. It lets a provider cover more ground and more skills than it could ever employ directly.

But it puts the MSP in a demanding position. It is accountable to the customer for every job, while seeing clearly into very few of them.

Where the friction builds up

Every handoff in the chain is a place where something can be lost:

1. The requirement gets thinner. The customer’s acceptance criteria are detailed in the contract. By the time they reach the engineer, they may be a line in an email or a quick call from the dispatcher.
2. The status says more than it knows. “Complete” tells you the engineer believes the job is finished. It does not show what was tested, what was photographed or whether it matches what the customer asked for.
3. Changes are agreed in passing. An extra hour on site, a different cable route, a second visit. Agreed on the phone, remembered differently when the invoice arrives.
4. The money waits on the slowest answer. The partner waits on the MSP, the MSP waits on the customer, and everyone waits for someone to find the evidence. That is the done-to-paid gap, and every business in the chain carries its share of it.

Each of these costs a little. Together they are why delivering through partners can feel harder than it should, for the MSP and for the people doing the work.

Transparency is not sharing everything

The usual response is more updates: status calls, weekly spreadsheets, a shared folder of photos. It adds effort without adding much confidence, because each update is someone’s summary rather than the record itself.

Useful transparency is narrower than that. It means the people who have to make a decision can see the same facts at the moment they need them:

• the customer sees the evidence laid out against their acceptance criteria;
• the MSP sees progress and exceptions across every job, whoever is doing it;
• the partner and engineer know exactly what is expected before they travel, and can point to the record if the work is ever questioned.

It also means some things stay private. Partners should not see each other’s jobs or rates, and engineers do not need the commercial terms between the MSP and its customer. Transparency that works gives each business the right view of one shared record.

How FortyFive takes the friction out

We built FortyFive because we kept meeting this problem in 18 years of running field delivery through partners. It is a field service orchestration platform for the business accountable to the customer, and it is built around one record per job:

• The requirement travels intact. Scope, acceptance criteria and agreed rates are set once and carried in a runbook to whoever takes the job.
• One way to offer work. Offer jobs to your own teams first and preferred partners next. Offers, counter-offers and responses are all recorded.
• A status you can see behind. Follow each job live. Engineers capture evidence step by step against the runbook, with the time and location on every answer, plus photos and signatures.
• Changes approved as they happen. Scope changes are approved live and kept with the job, so the conversation happens before the invoice, not after it.
• Acceptance on the record. Each site report is sealed when it is submitted, and the decision sits with it. The result is a proof of delivery you can share with your customer.
• Invoices from accepted work. Accepted work, agreed rates and approved changes become the invoice, instead of a reconstruction at the end of the month.
• Each business sees its own view. Each customer’s data is kept separate, so competing partners can work on FortyFive without seeing each other’s jobs, rates or records.

FortyFive runs standalone from the first job, with no integration required, so there is no systems project before you start. Ticketing and finance systems can be connected later. There is more detail on our page for managed service providers.

Where to start

Pick one customer contract: the one with the most queries, or the strictest acceptance criteria. Run its next month of jobs through one record, and count how many follow-up calls you no longer need to make.

We are at MSP Global in PortAventura, Tarragona, on 21–22 October. If any of this sounds familiar, come and talk to us there, or book a walkthrough and bring a recent job.

Less friction. More flow.