Most software for small businesses is designed for a desk. Large screen, stable connection, quiet, time.
For a real estate office on Mallorca we built a tool for recording properties. And the place where that happens is not a desk. It is a finca in the interior, at midday, on a half-empty battery and poor reception.
That sounds like a detail. In fact nearly every decision inside the thing follows from it.
Built For The Phone, Not For The Screen#
Input runs step by step rather than as one long form, and it is made for a thumb, not for a mouse.
Photos come straight from the camera. The location is taken from the device rather than typing an address that, for a plot in the interior, often does not exist. Everything saves itself continuously, and a started draft can be picked up later on the same device.
That self-saving is not a convenience but the condition for the tool being used at all. Anyone standing outside who loses half an hour of work because the connection drops does not open it a second time.
What Fits In No Field Still Needs A Place#
The most important part is not a field but a note trail.
Every property carries knowledge that cannot be pressed into categories. The access road is difficult in winter. The neighbour is thinking about selling too. The permit is in progress, but not in the usual way.
A rigid form either forces that into an ill-fitting field or loses it. So a note can be added to any property at any time, without structure, without required fields. That is the catch-all for everything you cannot foresee at design time, and without it the tool would be unusable in practice.
Photos Get Resized, Not Beautified#
A deliberate decision that needs explaining in the age of image generators: the tool resizes and compresses photos, and nothing else.
No brightening, no sky replacement, no removing of objects in the way. Technically that would be easy. It is still wrong, for two reasons. One is legal: showing a property differently from how it is puts you in territory where somebody eventually stands there with a lawyer. The other is practical: the prospect will stand in front of the house at some point. The gap between picture and reality is exactly the moment an appointment falls apart.
The Data Belongs To The Office#
The tool can export the properties as a table and in the exchange format the large property portals read.
That sounds like a side note and is a matter of principle. Anyone maintaining their properties in a system they cannot get them out of again has made themselves dependent. The vendor can then raise the price, and you pay, because moving would cost more.
So for tools we build for clients the rule is: there has to be a way out. Not as a concession but as a design feature. A client who could leave at any time and stays anyway is the only kind of client worth having.
Roles, Because Not Everyone May Do Everything#
A real estate office does not consist only of agents. There are people who find and record properties out in the field, and people who decide what goes on sale.
That separation sits inside the tool. Whoever records creates drafts and sees their own. Whoever is responsible sees everything and publishes. Between them runs a clear path from draft through review to active listing, on to reserved, sold, archived.
Without those stages you immediately get dead entries: half-finished records where nobody knows whether they are still current. With them, everybody sees at a glance where something stands.
Operable From The Chat As Well#
The newer part: the tool can also be operated from an AI assistant. Instead of opening the interface, you can ask which properties are currently in review, or create a new search profile.
The benefit is not the convenience but the distance. An office tool gets opened when you have time. A question gets asked in passing. Anything that lowers the barrier between "I should" and "done" decides whether a system gets used or quietly falls idle.
What I Take From This#
Before designing software for a business, you should know where it will be used. Not what it should be able to do.
A tool for the desk and a tool for outdoors look identical on a requirements list. They get built completely differently. Skip that question and you build something that convinces in the demo and sits untouched in daily work.
