Loyalty on a construction project comes from clients never having to chase an update, not from a wow moment at the end. What low client effort looks like in practice.
You answer the next question before the client asks it. A daily “any news?” message is rarely impatience. It is a client who cannot see the project and has no other way to check.
Watch what actually triggers those emails. A payment request arrives without the milestone that explains it. A plan is revised and the client hears about it three weeks later, from the kitchen supplier. A delivery date shifts by a fortnight and nobody says why.
Each one creates a question. Each question costs the client a message, a wait and a small piece of confidence. Send the milestone with the invoice, publish the revised plan the day it is signed off, post the reason for the shift: the email never gets written.
That is not a communication style. It is a decision about where project information lives and who can reach it without going through a person.
The Effortless Experience, the 2013 book by Matthew Dixon, Nick Toman and Rick Delisi, makes an argument most service businesses resist: loyalty is built by taking work away from the customer, not by dazzling them. Going beyond expectations, their customer service research found, moves loyalty far less than removing friction does.
At Ziggu we like a wow moment. A photo of the windows the day they go in, an update nobody had to request: keep those. The book is not an argument against them. It is an argument about what they cannot fix.
A perfectly finished kitchen does not undo six weeks of a client wondering whether anyone was working. The build gets judged on the build. The relationship gets judged on how much the client had to do to stay informed about it.
For a project business that distinction weighs more than it does for a call centre, because the exposure lasts longer. A support case runs for twenty minutes. A construction project runs for two years, and the client spends all of it either watching progress or guessing at it.
Client effort on a building project is the number of times someone has to come and get what should have arrived. Not clicks, not screens: chases.
The average buyer barely knows what an energy performance certificate is, let alone how to keep track of the settlements that follow it. That same buyer is then expected to send a quick email whenever something cannot be found. Those two expectations sit badly together, and only the second one is under your control.
Count the chases on one project. The number is usually higher than the team guesses.
The difference is rarely about how hard the team works. It is about where the information sits at the moment the client goes looking for it.
| High-effort project | Low-effort project |
|---|---|
| Updates arrive by email, WhatsApp and phone, in no fixed order | Every update lands in one place, in the order it happened |
| Three versions of the same plan, none of them marked current | One current version, with the earlier ones kept and dated |
| The client emails to ask whether anything has moved | The update goes out before the question is asked |
| An approval given in a corridor or a chat thread | An approval recorded with who signed off, and when |
| Four contacts, and the client guesses which one to use | One thread per project, with the right person pulled in |
Read the left column as a list of moments where the client does work the team could have done once. Each row is a place where a project either answers itself or sends someone hunting.
None of it is a technology question first. The right column describes a habit, and a shared client portal makes that habit cheap to keep where email makes it expensive.
Proactive communication survives a busy month only when it is built into the process. Teams that manage it are not more disciplined than yours. They have fewer decisions to make each time.
Immobel learned that from its own buyers. The residential advisory team was working hard behind the scenes, and the buyers could see none of it. “Behind the scenes we were busy for our clients, but we hadn’t stopped to think that they couldn’t see any of it,” says Valentine Van Malleghem, head of residential advisory. The team rebuilt its procedure around one dossier per buyer, one place for plans and documents, one record of what was decided. The full account sits in the Immobel success story.
What changed afterwards was the volume of questions, not the volume of messages. “We don’t have overflowing mailboxes any more, we have better processes, and we can work proactively by sending newsletters or creating FAQs,” says Marie-Lise Moetwil, senior residential project advisor. “Some things look small, but they have more impact.”
The smallest example in that story is the best one. A site photo, uploaded the day it is taken, answers a question the buyer has not sent yet. “Uploading a site photo to Ziggu reassures our buyers,” Marie-Lise says. “They can see that it’s moving, that we’re on top of the follow-up.”
That is what client updates are for: publishing the thing that pre-empts the question, on a rhythm nobody has to remember.
Removing effort does not remove the relationship. It frees up the part of the relationship worth having.
Keep the site photo, the friendly message, the update that arrives early. Use them to bring clarity, not as a plaster over a process the client cannot follow. Loyalty does not come from a box of chocolates at the key handover. It comes from a client who says, at every stage of a two-year build, that finding out where things stood was easy.
