Assembly or acquisition

The equipment was standardized. What the company sold alongside it was not.

An 8 to 10 week sprint, August 2025. A global machinery company, around €5B revenue. Part 4 of 4 in Assembly or Acquisition. Parts 1, 2 and 3 were assembly problems. This one is not, and it looks identical from the outside.

The record is direct. There was no consolidated view of existing consulting services. Offerings were created ad hoc and varied across regions, and leadership lacked visibility into which services customers valued or how they should be priced.

Parts 1 to 3 dealt with variation in how a company operates. This one deals with variation in what it sells, and the commercial cost is higher, because customers see it directly and compare one region against another.

For scale, the record describes a growing market of more than €300m for these consulting services. That is the size of the market the engagement brought into view. It is not revenue the client won, and we do not present it as a result of the work.

Almost everything a service catalogue needs comes from outside the company building it

The stated constraint matches the other three engagements: service teams were fully occupied with daily mill projects. That explanation is accurate here and still misleading, because capacity is the smaller of the two problems.

A service catalogue needs four inputs. The company holds one of them.

Give a service team six protected months clear of mill projects and they still would not hold three of the four, because the company has no route to them. No amount of workshop time produces a competitor price list. That is the whole difference between this engagement and part 3, which produced a similar deliverable entirely from material the client already had.

A second condition applies only here. A company builds a service catalogue roughly once in a career. A regional service lead may have delivered several hundred mill projects and never built a catalogue, so the company has no view on how many packages is too many, or where a standard offer ends and a bespoke engagement begins. That is not a point about machinery expertise. It is a point about having run this particular exercise before and knowing which of the obvious options turn out badly.

A catalogue, and the only engagement in this series whose record carries no outcome figure

This record reports no efficiency figure, no cost saving and no revenue number, and we have not gone looking for one. The record does carry a time-to-market claim, which we have left out of this series because it states no baseline. We would rather publish a shorter outcomes table than a number a reader cannot check.

Regional teams can now sell a defined package, priced against what customers will pay

What that enables. The service business can price against the customer rather than its own cost base, which is the difference between a catalogue that lasts and one rebuilt within a year. It can also put a package into a region without that region inventing its own, which is what turns a set of local practices into a business that scales.

Price against what customers will pay, and standardize the package rather than the conversation

Price against the customer, not your own cost. A catalogue priced from internal cost gets rebuilt within a year, because the first customer who walks away tells you nothing about what they would have accepted. The demand work is what makes the packages last.

Benchmark before drafting, for the same reason as part 1. A standard drafted before anyone maps the current state gets ignored at the second site. A catalogue drafted before anyone benchmarks competitors gets ignored by the second region, which has seen what a competitor offers and will judge the internal document against it.

Ship the buying journey with the packages. A list of services is a price list, and a price list makes the seller build the argument from scratch every time. Packages, the buying journey and sales guidance together are what let a regional team sell an offer it did not design.

Do not assume regional variation was waste. Some of it was a region responding correctly to a different customer base, and standardizing that away costs revenue. Telling that apart from variation that is merely historical is the analytical work.

Two questions you can answer before you scope the programme or call anybody

1. Given six uninterrupted months, would your team have the answer? If yes, you have an assembly problem. You are buying protected time and a method, not knowledge. Say so internally. It is the more defensible position, and it survives the challenge from people who have done the work for years and know they could have done this too, given the time.

2. Does any of the evidence you need come from outside the company? Competitor benchmarks, competitor positioning, what customers will pay, the size of the market. If your answer depends on any of these, no amount of internal time closes the gap, because there is no internal route to the evidence. You have an acquisition problem, and it needs a different scope, a different timescale and a different business case.

The two problems fail in opposite directions, which is why it pays to tell them apart before you scope rather than after.

Sequencing. Where a programme contains both problems, do the assembly work first. The machinery catalogue needed a view of what the company currently sold before anyone could benchmark it. The finance catalogue of 311 tasks in part 3 is exactly the kind of list that has to exist before anyone can judge which 10% belongs elsewhere. Companies usually get this backwards. Competitive pressure arrives, the board commissions the external study, and the findings then sit unused, because the company never built the internal picture those findings would have to be applied to.

The first three are inventories of the company's own behaviour. The fourth is not. Note that the two catalogue engagements, finance and machinery, fall on opposite sides of the line despite producing the same kind of deliverable. A company that scoped the machinery work by analogy to the finance work would have budgeted eight weeks of internal interviews and produced a catalogue describing only what it already sold.

Five boundaries, including one that applies to the whole series

What share of the €300m the client can address. Seeing a market is not holding a share of it. Closing that distance is commercial strategy, not an eight-week engagement.

Whether the packages survive a sales force. A catalogue is a hypothesis about how customers buy, and it gets tested when a regional team has to quote it.

Whether the regions adopt it. The question that closes all four parts. A standard published centrally and ignored regionally is an expensive document.

The sample. Four engagements are a pattern, not a proof. These are the four we have published so far, chosen on that basis rather than sampled, and a fifth might not fall on the same line.

Results after rollout. None of the four records reports one. Every figure in this series describes what an engagement found or delivered, not what the client has since realized. We report what we saw, and we stop there.

Three of the four clients reached for the same word

The Vice President of Services said SprintlyWorks delivered the service catalogue they lacked, and that work which would have taken them more than six months internally was done in weeks.

Head of Operations, fleet: clarity and direction that would have taken internal teams months to establish. Vice President, Finance: clarity and the roadmap they needed. Director, Business Development, pulp and paper: structure and clarity across mills, in weeks.

Three companies, three functions, one word. Clarity is what assembly work produces. It appears when material a business already held finally becomes comparable, and it is worth naming precisely rather than inflating into a claim the records do not support.

How to use this. Put the two questions to whichever standardization programme is on your desk now. The answers tell you whether you need somebody released to assemble what you already have, or somebody sent out to get what you do not.

Four case records, and every figure reproduced with the qualification its record applies

The records. Standardizing Fleet Maintenance and Control Operations, a €1.5 billion logistics company, February 2026. Standardizing Supplier Quality Workflows Across Sites, a €10 billion global pulp and paper producer, September 2025. Standardizing Financial Services Across Business Areas, a €10 billion global forest products group, September 2025. Building a Unified Mill Services Catalogue, a €5 billion global machinery company, August 2025, an 8 to 10 week sprint with more than 10 internal stakeholders.

The qualifications. The €5m is identified, not recovered. The 10% is identified as outsourcing potential. The €300m is the size of a market that came into view, not revenue captured. The 15% is a potential against named levers.

What we leave out. We describe clients rather than naming them, and no detail about any client's suppliers, customers, prices or internal thresholds appears in this series.

About this work. SprintlyWorks runs 8 to 10 week sprints for industrial companies that need a written account of how their sites work today, a single harmonized process, or a service catalogue, and cannot release the people who would build it. We work at the sites, reconcile what we find into one structure, and hand over something the client can act on.

Running a standardization programme, or about to scope one? Answer the two questions above and send us what you get. If it is assembly work, we will tell you what an internal team would need. If it is acquisition work, we will tell you what evidence you are missing.