Most digitisation projects do not fail on the technology. They fail because somebody is supposed to open a new application and stops doing it after three weeks.
That is not laziness. A new interface costs attention, and attention is the scarcest resource in daily business. If the new tool does not give back more than it costs immediately, habit wins. Every time.
So for a rental office we deliberately built nothing new.
The Constraint Was The Most Interesting Part#
The brief was: no second program, no new vendor, no training. The assistant application that is open all day anyway stays the interface.
That sounds like a restriction and is in truth a good requirement. It forces the question to be asked differently. Not: which interface do we build. But: what is the existing one missing so it can carry the working day.
The answer was access. The application could talk, but it knew nothing. No memory, no client data, no inbox.
Connected Rather Than Rebuilt#
So we connected the existing assistant application to what was missing. For a while now that runs over an open standard for attaching such applications to external tools. The user notices none of it. To them it is the same application as before, it can just suddenly do more.
Four things were attached.
A memory that keeps tenants, property histories, ongoing cases and agreements over the long term. In rentals that is the actual lever, because almost every case here has a backstory. Who has moved out before, which property had trouble with the heating, what was agreed last time.
A contact system where contacts, enquiries and statuses are maintained straight out of the conversation. Not in a second window, but in the one you are already typing in.
The existing inbox, from which incoming messages are read and draft replies prepared. Approval and sending remain exclusively with the office.
And an image generator for property visualisations and listing graphics, in the same session where the matching copy is written. That is one of the few places where text and image genuinely belong together: whoever is phrasing the listing knows which picture fits it.
The Configuration Is The Difference#
On top comes something that sounds like a detail and tips the balance: a base instruction tailored to the business.
An assistant without a role answers generically. It does not know this is about rentals rather than sales, that certain phrasings are house standard and others are not, that an enquiry follows a fixed process. It cannot know, it is written nowhere.
Written down, the quality of answers changes noticeably without anything about the technology being different. In setups like this that is regularly the most effective hour of work in the entire project.
Where Things Sit#
Memory and contacts run on our servers in Europe, with a separate data space per client. The credentials for the inbox live exclusively in the local configuration on the work machine, not centrally with us.
Each of the four connections can be switched off individually without the application itself noticing. That is a side effect of the open standard and practically more important than it sounds: whoever no longer wants something takes it out, and the rest keeps running.
Why This Route Is More Often The Right One#
There are cases where a dedicated build makes sense. When many people work in it, when specific processes have to be mapped, when the data may not leave the house.
In all other cases the existing application plus a few connections is the faster and more durable route. No training effort, no second interface, no migration. And the business is productive the next day rather than in six weeks.
The best workplace is rarely the one you build. Usually it is the one somebody already opens every day.
