A developer appoints four consultancies on a site. Each is excellent. Three months in, the drainage strategy assumes a level the civils team changed, the structural solution conflicts with the services route, and nobody noticed because nobody was looking across all four.
The fees were competitive. The coordination cost more than the saving.
The decision developers are making
Whether to buy specialism from four firms and manage the gaps, or buy coordination from one and accept whatever depth it has. It is a genuine trade off and it deserves an honest answer.
When a single appointment works better
Sites where disciplines interact heavily, developers without an internal technical team, tight programmes, projects where one gap causes a redesign, and anybody who does not want to chair coordination meetings.
When separate specialists are better
Where one discipline dominates, where specialist expertise genuinely differs, where a client has an internal team to coordinate, and where a particular firm is the acknowledged expert in something unusual.
Explain what coordination actually means
Shared assumptions, consistent levels, a single set of information and somebody checking that one discipline's change reaches the others. It is invisible when it works.
Explain who holds the risk
Under a single appointment, the consultancy resolves internal disagreements and carries the coordination responsibility. Under separate ones, the client does. That is the real difference.
Be honest about your own depth
A multi discipline firm should say which disciplines are its strength and where it would bring in a specialist. Claiming equal excellence in everything is not believable.
Explain the single point of contact
Who the client deals with, what they can decide and how internal disciplines are reached. Developers value this more than almost anything else.
Explain the fee structure
Whether it is one fee or several, how it is broken down and whether disciplines can be dropped. Developers need to compare it against four separate proposals.
Explain what the client still has to coordinate
Architect, contractor, planning consultant and anything outside your appointment. Being clear about the boundary prevents the assumption that everything is covered.
Explain the information flow
How the architect's drawings reach every discipline, how changes propagate and what the client must provide, which is the capture in project enquiries for engineering consultancies.
Explain the programme advantage
That disciplines working alongside each other in one office move faster than four firms exchanging emails. It is usually the strongest argument and it should be quantified.
Explain what happens if one discipline changes
A revised structural solution ripples into drainage, services and sometimes the layout, and developers want to know who notices. Describing how a change is circulated internally, who checks the consequences and how the client is told is the concrete version of the coordination everybody claims to provide.
Publish the disciplines you offer
Named, with what each covers. Developers search for a combination and find lists of services.
Ask what is already appointed
Before proposing anything, because a developer with two disciplines in place needs a different proposal, which relates to feasibility study enquiries from developers and councils.
Handle the complex enquiry properly
These arrive with several questions at once, which is the problem in how AI handles multi part customer questions and the brief taking in garden design enquiries that need a proper brief.
Getting started
Publish your disciplines, where you would bring in a specialist and how coordination works, then capture what is already appointed at any hour. SpideyChat for professional services firms answers from your published pages, plans are on the pricing page, and the chatbot ROI calculator works through the numbers.