Buyers ask the same construction questions again and again because the answer lives in someone's inbox. Publishing it once, where buyers can open it themselves, changes what a customer advisor's week looks like.
A question that keeps coming back is rarely one the developer cannot answer. The delivery date, the tile deadline, the revised plan: in the residential projects Ziggu works in, that answer already exists, and it usually exists in writing.
It sits in a sent folder. Or on a drive nobody outside the office can open. Or in the head of the one colleague who happened to be on that call.
So the buyer asks the only party who can look it up. That is not a difficult buyer, that is a buyer with no other route to the information. Publish the answer once, somewhere they can open themselves, and the weekly question stops being weekly.
Keep buyers informed by publishing the answer where they can reach it, and by letting the project send the update instead of a person. A customer portal gives every buyer the same project record: progress, documents, deadlines and the choices still open to them.
Four kinds of question come back in almost every residential project, and each of them has a published form.
Where is the project now? One project update reaches every buyer the same day, with the milestone timeline showing what is done and what comes next. No update gets retyped per buyer, and nobody has to guess who was told what.
Where is my document? Contracts, plans and specifications live in the project record, always at the latest version, and stay reachable for years after completion. Nobody searches a mailbox on someone else's behalf.
When do I have to decide? The kitchen, the floor tile, the bathroom: each choice carries its own deadline, and the reminder goes out on that deadline without anyone scheduling it. When the buyer signs off, the record shows who approved what, and when.
Who picks this up now? An approved choice reaches the contractor and the showroom with the signed version attached, through the partner side of the portal, instead of a forwarded mail carrying an attachment three versions old.
None of that removes the customer advisor from the project. It removes the part of the job that is retyping.
Buyers judge the sale and the build separately, and they judge the build far more harshly. In the Belgian Homebuyer Survey 2017, 242 qualified buyers of new-build homes in Belgium rated both phases: 76% were satisfied with the sales approach, and 55% with the follow-up during the works. Same people, same projects, a drop of 22 points.
That survey also split those buyers by whether their developer ran a digital environment where they could follow the build. The two groups sat furthest apart in the construction phase, further than in sales or in the choices around it. Read that as an association and not a cause: the smaller group counted 40 buyers, and developers who already ran a digital environment in 2017 were probably better organised in other ways too.
The direction still says something about where the questions land. During the sale there is a salesperson in the room and a reason to be there. After signature the project keeps moving for two years and the buyer has no window on it, so they open one themselves: a phone call, an email, a message on a Saturday.
The change shows up in a customer advisor's calendar before it shows up anywhere else. The work does not disappear. It moves from answering to publishing, and publishing happens once.
| Recurring question | Answered by hand | Published once |
|---|---|---|
| Progress of the works | The same update retyped per buyer | One project update, visible to everyone the same day |
| A document request | Searching a mailbox and a drive per request | Every plan and contract in the project record, latest version |
| A deadline for a choice | Reminders mailed buyer by buyer | An automatic reminder tied to the deadline itself |
| An approved choice | Forwarded to contractor and showroom by hand | Routed to the partner with the signed version attached |
| A snagging point | A spreadsheet only the office can open | A report both sides can see, with an owner and a deadline |
Automation earns nothing on its own. It earns something when the hours it frees go back into the part of the job a buyer actually notices. CAAAP, a property developer in Ghent, went through that shift and described both halves of it.
“We had been struggling with the abundance of information shared between customer and developer”
Stefanie Vanden Broucke, ex-CEO of CAAAP
Finding one document for a client, she said, was sometimes like looking for a needle in a haystack, and mapping a project's history became a puzzle whenever a support colleague left the team. Centralising the communication and the documents solved that half.
What the team did with the time it got back is the more interesting half. “For us, it's not just about customer satisfaction; it's also about customer experience,” Vanden Broucke said. Updates about the building location, get-to-know-the-team posts, good places to eat near the site: small things that build a bigger story around the project. Her customers responded well to it, and some of them became ambassadors.
That is the trade worth making. Not fewer buyers to look after, but a week spent on the parts of a project only a person can do.
Publishing answers once holds up while the pipeline is stable. Add projects and a second question arrives: what breaks first when the same team carries twice the work. That is a capacity question, not a communication one, and it is covered in what has to change first when the pipeline grows.
