Why Do Clients Take My Work and Never Come Back?

A Story About the Difference Between Delivering Work and Being Worth Returning To

Why Do Clients Take My Work and Never Come Back?
A Story About the Difference Between Delivering Work and Being Worth Returning To

Why do clients take my work and never come back? Often because they got exactly what they commissioned, and nothing more happened. The work was right, the invoice was paid, and there was no reason to think of you again. Being good isn’t what brings people back. Being in the thinking is. 

Let me tell you a story about a woman whose reports were faultless, and whose phone stayed quiet.

Inga is a character I created — her situation will be familiar to anyone whose work is delivered, paid for, and never leads anywhere.

Commissioned, Delivered, Filed

Inga was fifty-two, a structural engineer, and had spent twenty-six years being right.

She worked from a small consultancy, mainly on existing buildings: assessments, load calculations, remedial schemes. A developer would send a brief, she would survey the building, do the work, and produce a report. Her reports were exemplary — clear, thorough, honest about uncertainty, never padded. Contractors trusted them. Building control rarely queried them. She had never once been wrong about something that mattered.

And when a report was delivered, that was the end of it. The invoice was paid promptly. The client said thank you. And then nothing, until the next time somebody needed the same thing done, which might be with her and might be with whoever came up first in a search.

She was fifty-two, she had twenty-six years of judgement in her, and she was still being commissioned task by task, the way she had been at twenty-eight.

It had begun to wear at her. Not the money, which was adequate. It was that she watched buildings get done badly — sensible things not done, expensive things done that needn’t have been — and she was never in the conversation where any of it was decided. She’d be asked to assess whether a wall could come out. She would answer whether the wall could come out. And nobody ever asked the question underneath, which was whether taking the wall out was the right idea at all.

She had come to assume this was simply what consulting engineering was. You are handed a question. You answer it accurately. That is the service.

The Report She Talked Through

What changed it was a delay, and a client who had time to fill.

Inga had assessed a Victorian warehouse a developer was converting into flats. Her report went in as usual — the structure was sound, one particular alteration they’d proposed would need substantially more work than they’d assumed, and there was an alternative that achieved much the same thing.

The developer rang her, not to query it, but because a planning meeting had been pushed back and he had an hour. “While I’ve got you — how did you land on that alternative? It wasn’t in the brief.”

And Inga, who had never been asked that in twenty-six years, told him.

She told him about the way she reads an old building: that you look first for what it was originally doing, because a building has a logic in it, and the alterations that fight that logic are the ones that get expensive. She told him she’d stood in the warehouse for twenty minutes before opening her tape, working out where the loads had originally travelled, and had seen that the wall they wanted to remove wasn’t just structural but was the thing holding a whole sequence together. And she told him about a conversion years earlier where nobody had looked for the building’s original logic at all. A wall had come out easily and cheaply, and eighteen months later the floor above it had begun to move, and putting that right had cost four months and a great deal more than the wall had saved.

“So the alternative isn’t a compromise,” he said. “It’s what the building was already telling you.”

“More or less.”

There was a pause, and then he said: “Can I ask you something else? We’ve got two other buildings under offer. Would you look at them before we buy?”

Nobody had ever asked Inga to look at a building before they bought it.

Why Good Work Doesn’t Bring People Back

Here is the mechanism, and it catches thorough, self-contained professionals hardest.

A report answers the question you were asked. It reveals nothing about the questions you could have answered. Inga’s clients received twenty-six years of accurate documents. Every one of them was the finished product of a way of thinking they never saw: the twenty minutes standing still, the reading of the original logic, the pattern from a job eight years earlier. All of that happened before the document existed, and none of it was in the document.

So when a client had a different kind of question — a harder one, an earlier one, a should we rather than a can we — they didn’t think of Inga. Not because they doubted her. Because they had no evidence she did that kind of thinking. They had only ever seen her answer what she was asked.

This is why doing better work never changes it. A more thorough report is still a report. What changes it is letting someone watch you think: what you look at first, what you noticed that wasn’t in the brief, what you’ve seen go wrong before and how you recognised it.

You don’t get called back by being more right. Inga had been right for twenty-six years. You get called back when someone has seen how you arrive at things, and wants that mind on their next problem.

What Inga Recognised

That evening, Inga sat with the strange feeling of having been asked to look at two buildings that hadn’t been bought yet, and found three things she’d never named.

A success. The hour on the phone. Not her best report — the report was ordinary, and she’d written a hundred like it. What made the difference was that she’d described how she reads a building, including the twenty minutes of standing still and the job that went wrong years before, and let the developer see the thinking rather than the conclusion. He’d reached the point himself: it’s what the building was already telling you.

A failure. Twenty-six years of exemplary work that never grew into anything. Nothing had gone wrong. Not one report she’d want back, not one client who felt let down, not one mistake that mattered. That was exactly what had concealed it: from the outside it was an unblemished career. It wasn’t a failure of engineering. It was that her judgement had stayed entirely inside her own head, and every relationship had ended at the invoice.

A passion. When she looked at what actually drove her, it was old buildings and the people who would work and live in them. She minded, genuinely, when a good building was handled carelessly — not out of sentiment, but because the mistakes are paid for twice, first in money and then by whoever lives with the result for the next forty years. That was why being handed narrow questions had worn at her. She wasn’t being kept out of the money conversations. She was being kept out of the ones where buildings got decided.

Three things. None of them a calculation. All of them the difference between being commissioned and being consulted.

The Practice That Changed

Inga didn’t change her reports. She changed what she let clients see of the thinking behind them.

With the developer, she told her success story — the reading of a building’s original logic, the twenty minutes before the tape comes out. He asked her to look at the two buildings under offer. She advised him against one of them, which cost her a job and won her a client, because he bought the other and used her on all of it. And on that one, she wasn’t handed a brief. They worked out the scheme together, because he had seen how she thought and wanted that thinking in the room while the decisions were still open.

With a small housing association she’d worked with for years, she told her failure story: twenty-six years of answering exactly what she was asked, and watching decisions get made upstream that no one had thought to ask her about. Their surveyor said, quite mildly, that they’d assumed she wouldn’t want to be bothered with the early-stage discussions. She was in the next one.

With a new architect who briefed her on a difficult extension, she told her passion story: why old buildings matter to her, and who pays when they’re handled badly. They ended up redesigning the scheme together, and the architect has since brought her three more.

And with a contractor she’d worked alongside for a decade without ever really talking, she told the same success story she’d told the developer. He started ringing her from site — not with problems, with questions, before things were built rather than after.

She wasn’t a better engineer that year than she’d been the year before. She was exactly as good as she’d always been.

She’d simply stopped delivering only her conclusions, and started letting people see how she got to them.

Within two years, more than half of Inga’s work came before the brief rather than after it — because the people who commissioned her had discovered there was a mind behind the reports they’d been filing for years. Her work no longer arrived and stopped. It was something clients built on with her, and came back to her for.

Why Clients Don’t Come Back: What Inga’s Story Shows

A report answers what you were asked, and reveals nothing else. Your clients have seen your conclusions, never your judgement. So they bring you the same narrow question, or they bring it to somebody else.

Being more right won’t change it. A more thorough report is still a report. Inga was right for twenty-six years. Accuracy was never the missing thing.

Show what you looked at first. The twenty minutes before the tape comes out is the thing worth sharing — not the answer, but how you knew where to look.

Include what you’ve seen go wrong. Inga’s story worked because it carried a job that failed years earlier. The wrong turn is what makes a journey real enough for someone to enter.

Tell the story the conversation needs. The developer heard her success. The housing association heard her failure. The architect heard her passion. Three stories, chosen for the person in front of her.

Your three stories hold the whole of it. A success that shows what happens when your thinking is visible, a failure that shows the cost of keeping it private, a passion that shows why the work matters to you.

You Already Have More Than the Answer They Asked For

Everything Inga needed was already in twenty-six years of work. She hadn’t been failing anyone — she’d been answering faultlessly and privately, and privately is what ended every relationship at the invoice. The success that showed what one visible thought could do. The failure that looked exactly like a spotless career. The passion, and the reason she’d cared about old buildings in the first place.

Yours are there in the same way — in every question you answered precisely, while the better question went unasked.

Continue the Work

And if you want to go deeper — recognising your three stories and the journey inside each; telling them so people enter your thinking rather than receive your output; and turning the same questions outward, to draw out the thinking of the people you work with — that is what my new Professional Self-Coaching resource is for. The thinking, the sequence, the questions and the frameworks a coach would bring to hours of one-to-one work, placed in your hands, to work through in your own space and time.

Get the Partnership — Professional Self-Coaching for Turning Your Expertise Into Genuine Working Relationships Tell the Three Stories That Make Your Insight Land, So People Engage With It, Not Just Receive It

Work With Me: Individual WorkLife Coaching, Commissioned Learning Resources, Speaking Engagements and Organisational Partnerships.

Support This Work: Your support makes a difference and helps me to continue creating resources that are accessible to everyone. Thank you. Carmel

Listen to the audio version here:

Share These Learning Resources 

These resources are designed as short, effective learning experiences—for individuals managing their own development and companies supporting their people’s growth.

If you think this learning resource story would be helpful to others, share it forward.


Discover more from schoolofworklife.com

Subscribe to get the latest posts sent to your email.

Published by Carmel O' Reilly

I'm Carmel O'Reilly, founder of School of WorkLife. I use story-based learning — characters in real WorkLife scenarios — to help people develop their working lives, through Story Lessons, Guided Programmes, and Professional Self-Coaching resources, and the WorkLife Stories podcast. Irish, London-based, and endlessly drawn to a good story.