The catalogue is only the visible part. Underneath sit the agency, its agents and a partner network — each with their own access and their own share of the deal. Nothing off the shelf covers that.
The task
A property agency is not a shop window, it is a structure. There are the properties, the agents who work them, and the partner network that brings in both clients and new agents.
Catalogue plugins solve only the first part: show a property attractively. Everything else — whose client is whose, who works with whom, how the network is shaped — falls outside their scope.
The approach
Our own data structure. A property is described the way the agency describes it, not the way a plugin author once imagined it. That sounds like a small thing right up until the first property that does not fit the imported schema.
The partner network is in the foundations, not bolted on. A branching structure means a participant can bring in not only a client but the next participant, and the system has to understand that.
No licensing strings. The plugin belongs to the company: no annual fee, no risk of the author abandoning the project, no update that one day breaks the feature you depend on.
The result
The agency runs properties, agents and the partner network in one system rather than three spreadsheets and an inbox.
This is what separates “build a website” from “build a system”. A website you can order anywhere. A system has to be designed around how a particular business actually works.