The Last Meeting That Pays: Turning Project Handovers Into Introductions

The ask that arrives too late

There is a familiar pattern in owner-managed UK firms. A project lands well, the client is pleased, and everyone moves on to the next thing. Three months later, with the pipeline thinner than expected, someone picks up the phone and asks whether the client knows anyone who might need similar work. The reply is warm and entirely useless: leave it with me, I will have a think.

Nothing about that exchange is dishonest. It simply asks the client to do unprompted work: recall your capabilities, scan their network, judge who might be a fit, and then compose an introduction. That is a marketing task, handed to someone who did not volunteer for it.

The alternative is to make the referral a finishing step of the project rather than a separate favour. For service and project businesses, the handover is the natural place to do this. The work is fresh, the outcome is measurable, and the client has just spent weeks or months thinking about what you actually do.

Why the handover is the right moment

Referrals fail for three ordinary reasons. The client cannot articulate what changed, because nobody agreed the outcome in plain terms. They cannot picture the ideal next client, because the request was left open-ended. And they have no convenient artefact to pass on, because the case study or summary never got written.

The handover meeting fixes all three, provided it is treated as a scheduled part of delivery rather than an optional courtesy. Book it in the same way you book a kick-off. Give it thirty minutes and a small agenda. The purpose is not to extract a favour; it is to close the project properly and, in doing so, make an introduction easy.

Move one: capture the outcome in the customer's words

Do not describe your own work. Ask the client to describe it. A useful prompt is: if you had to explain to a peer what changed here, what would you say?

Write down their phrasing exactly. Clients use plain language that prospects recognise, and it is almost always more persuasive than the language in your service page. A client who says we stopped losing quotes in the post is giving you better copy than anything produced in a planning session.

Move two: agree the measurable win

The second move is to put a number or a defined state on the outcome, with the client, before the file closes. That might be a reduction in processing time, an increase in quote conversion, the removal of a recurring error, or the completion of a regulatory step ahead of a deadline.

Be disciplined here. If the client cannot or will not attach a measure, do not manufacture one. Record the qualitative outcome instead and note that no metric was agreed. Invented figures in a case study are a reputational risk and experienced buyers spot them quickly.

Move three: ask for one named introduction

This is the part most firms get wrong, usually by asking for too much. A request for one specific introduction is easy to answer; a request for anyone who might be interested is easy to defer.

Make the ask concrete by describing the ideal next client in operational terms: sector, size, and the trigger event that usually brings them to you. Then narrow it further with a single question.

Of the people you work with, who is the one most likely to hit the same issue in the next six months?

If the client names someone, ask whether they would be comfortable sending a short note, and offer to draft it for them. Supplying the draft turns a task into an approval. If they hesitate, accept it immediately and move on; a pushed introduction is worth very little and can cost you the relationship.

Move four: package the story before the file closes

While the meeting is still running, agree what can be written up and who approves it. Under UK GDPR, a case study naming a client or containing identifiable details needs their consent, and consent is much easier to obtain in the room than by email in six weeks.

Aim for a single page: the situation before, what was done, the agreed outcome, and a line from the client. Keep it in a folder you can attach to an email without editing. Reusable proof is the compounding asset here; the introduction is a one-off, but a signed-off case study keeps working.

A short handover checklist

• Handover meeting booked at kick-off, not improvised at the end
• Outcome written in the client's own phrasing, verbatim
• Measure agreed, or explicitly recorded as absent
• Ideal next client described by sector, size and trigger event
• One named introduction requested; drafted note offered
• Case study scope and approval agreed, with consent recorded
• Testimonial requested in the same conversation
• Referral noted in the pipeline record with source and date

Scripts that keep it short

Opening: we have thirty minutes; I want to close this properly, agree what we can write up, and ask you one question at the end.

On measurement: what would you tell a peer this changed, and is there a figure that would make that credible?

On the introduction: is there one person you would be comfortable sending a two-line note to? I can draft it now and you can approve or drop it.

On the case study: would you be happy for me to write a one-page summary using these numbers, sent to you for sign-off before we use it anywhere?

Tracking referral value without another CRM

Most SMEs do not need new software for this; they need one consistent field. If you already run a pipeline sheet or a simple deal list, add three columns: source, named referrer, and value at twelve months.

For firms working from an accounts package and a spreadsheet, the same principle applies in the invoice ledger. Tag each new customer record with the referrer's name where one exists. Once a quarter, total the invoiced revenue against each referrer. That single figure answers the question that matters: who is actually sending us work, and is it the work we want?

A quarterly review of that list also tells you something less comfortable. Referrers who send small, demanding or slow-paying work are still referrers, and the pattern is worth a conversation about the brief you gave them.

A habit, not a campaign

The value of this ritual is not the first introduction. It is that every completed project ends with a written outcome, a named prospect and a usable case study, which means the marketing function of the business is being fed by delivery rather than by the founder's memory. Do it four times and you have a referral habit. Do it for a year and you have a body of proof that sells without you in the room.