There are two ways to build an AI product. The first is to start with what AI can do and find a commercial problem that fits. The second is to start with what a commercial decision actually requires and ask where AI can genuinely help with that.
Most products being sold into estate agency right now were built the first way. A language model exists that can read text and produce outputs. Seller enquiries are text. Therefore: AI seller qualification. The logic is superficially coherent. The product ships. It does something that looks like what was promised.
But the starting point shapes everything that follows. A system built around what AI can do will optimise for AI performance. A system built around what the decision requires will optimise for decision quality. These are not the same objective, and they do not produce the same system.
I want to be honest about why this distinction matters to us, because it is not an abstract engineering preference. It is the reason Pulsero is built the way it is, and it is the reason the alternative approach produces systems that underperform in commercial settings even when the underlying AI is capable.
What the decision requires
The decision an estate agency makes when a seller enquiry arrives is not a simple one. On the surface it looks like a routing problem: which sellers should we contact first, and in what way. But the decision that needs to support that routing is considerably more demanding.
It requires an accurate reading of what the seller has communicated, including things they have said indirectly or incompletely. It requires placing that reading in the context of what actually predicts instruction likelihood, which is not the same as what sounds most urgent or most motivated in the text. It requires consistent application of that contextual logic across every enquiry that arrives, not just the ones that are easy to read. And it requires producing an output that the agent receiving it can evaluate, act on, and push back on when their own knowledge of the situation suggests a different reading.
That is a demanding set of requirements. Reading the enquiry accurately is one part of it. But accurate reading is the beginning of the process, not the end. What follows — the contextual judgement, the consistent application of logic, the production of auditable reasoning — those are different requirements, and they are not naturally satisfied by the same system that handles the reading.
Accurate reading is the beginning of the process, not the end. What follows requires something different from the system that handles the reading.
Where AI genuinely helps
AI is genuinely good at the reading part. This is not a minor capability. Seller enquiries arrive in every form imaginable — terse portal messages, discursive emails, walk-in conversations reconstructed from memory, forwarded WhatsApp threads. The range of expression, the variation in what is stated directly versus implied, the informal language and incomplete sentences that characterise real human communication: these are exactly the conditions under which large language models outperform every previous approach to text understanding.
A capable language model reading a seller enquiry can surface context that a human would identify but that no keyword system or structured form could capture. It handles the messiness of real communication without needing that communication to conform to a particular format. That is valuable, and it is genuinely difficult to replicate without AI.
The question is what you do with that capability. If you ask AI to read the enquiry and also produce the final classification, you are using a single system for two tasks that have different requirements and fail in different ways. The reading capability is real. But the classification decision needs things that a language model does not natively provide: stable logic that does not drift between enquiries, calibrated uncertainty rather than uniform confidence, and reasoning that can be examined and corrected when it is wrong.
Where it does not
The failure mode that results from asking AI to do too much is not dramatic. The system does not obviously break. It produces outputs that look reasonable, expressed with apparent confidence, at a speed no human process could match. The problem is in what those outputs are actually worth.
A language model making classification decisions will produce different outputs on similar enquiries as the model is updated. It will express the same confidence on a well-evidenced classification as on a poorly-evidenced one. It will produce reasoning that sounds coherent but may not reflect the actual basis for the output. And when it is wrong, the error will often not be visible until its consequences have already arrived.
These are not problems that can be solved by making the model more capable or the prompt more specific. They are structural characteristics of using a probabilistic system for a task that requires deterministic properties. No amount of fine-tuning changes the fact that a language model is optimised for producing plausible outputs, not for applying a defined logic consistently and transparently across every case it encounters.
The agents using these systems sense this even when they cannot articulate it. They learn not to fully trust the output because the output behaves in ways they cannot predict or explain. They use the tool less. The capability that was purchased goes partially to waste because the system was not built with the requirements of the decision in mind.
These are not problems that can be solved by making the model more capable. They are structural characteristics of using a probabilistic system for a task that requires deterministic properties.
The question that matters
The question I find most useful when evaluating any AI system making commercial recommendations is not how capable the underlying model is. It is what the system is asking AI to do, and whether that matches what AI is actually good at.
A system that uses AI for everything it can plausibly handle is not a well-designed system. It is a system that has optimised for the presence of AI rather than for the quality of the output. The presence of AI is not the same as the quality of the decision.
A system that has thought carefully about what each part of the decision process requires, and has matched those requirements to the right mechanism, will outperform a system built around AI capability in commercial settings over time. Not because it uses less AI, but because it uses AI where AI genuinely helps and uses something else where it does not.
This is a harder system to build. It requires being honest about the limits of AI as well as its capabilities. It requires resisting the pressure to let the most impressive technology handle every part of the problem. And it requires designing from the decision outward rather than from the technology inward.
What this means in practice
For us, this design philosophy has a practical consequence that shows up in every output Pulsero produces. The agent who receives a classification can see what the enquiry said, what it suggested, and why the system reached the conclusion it did. They can agree with it, disagree with it, or override it with information the system did not have. The output is not a verdict to be accepted. It is an informed position to be evaluated.
That is only possible because the system was designed around what the decision requires rather than around what AI can do. The reading capability and the classification logic are handled by parts of the system suited to each. The output reflects both, transparently, in a form the agent can work with.
I think this is what commercial AI systems should look like. Not because it is the most technically impressive approach, but because it is the approach most likely to produce outputs that are actually useful to the people making decisions based on them. The technology exists to do considerably more than that. The question is always whether doing more serves the decision or just serves the technology.
For classification decisions with real commercial consequences, the answer is consistent. Design from the decision. Use AI where it genuinely helps. Use something more constrained and auditable where the decision requires it. The result is a system people trust and use, rather than one they tolerate and work around.