Method
How we build
Every system kaysera builds is drawn along one line: the parts that have a correct answer, and the parts that need judgment. Almost everything that goes wrong with AI in property work is something placed on the wrong side of it.
§ 01
Rules become tested code
If a regulator publishes it, it is not a prompt. It is a function with a test and a citation.
- Written from the source, not from memory
- A duty band, a servicing ratio, a contribution rate: each is implemented straight from the published rule, and the code records which document it came from and the date that document was read.
- One test per rule
- Tests are written against worked examples from the regulator's own material wherever they exist. A rule with no test is treated as a rule that is not implemented.
- Changes announce themselves
- When a threshold moves, the test that encoded the old one fails. The failure names the rule and the source. Nobody has to notice that a number on a page went quietly out of date.
In practice: on the REDEMPTION engine this came to 266 tests, covering IRAS, MAS, CPF and HDB rules with a dated check on each.
§ 02
Figures carry their provenance
A number a client can act on has to answer two questions without being asked: where did this come from, and when was it last true.
- Stated, not implied
- Rates and thresholds are published alongside their source and an as of date. A figure that cannot say where it came from does not go on the page.
- Read again, not remembered
- Where a benchmark is published on a schedule, the system reads it on a schedule. A default interest rate that was correct at launch is not a default interest rate a year later.
- One canonical copy
- Every headline figure has exactly one definition, and every surface renders from it. Numbers drift when they are retyped. A website and three decks quoting the same statistic four different ways is the normal outcome, not an unusual one.
§ 03
Where AI belongs
Reserving AI for judgment is not caution. It is what makes the AI worth having: the model is asked for the things it is genuinely better at than a person with a spreadsheet.
- Reading what people actually send
- Statements, valuations, letters, screenshots. Pulling structure out of documents that were never designed for a machine to read is exactly the problem models are good at, and the extracted values are still validated against the rules before anything is computed.
- Explaining a result
- The arithmetic is deterministic. The paragraph that makes it land with a client is not. Narrative, framing and tone are drafted, then reviewed by the person whose name is on the document.
- Exploring the space
- Which scenarios are worth modelling at all is a judgment call. Proposing them is useful. Deciding them is not delegated.
§ 04
How it lands in a firm
The agent goes first. The agency follows, on one licence.
- One agent, one workflow
- The agents who go first are the ones whose pitch is the analysis rather than the listing. They start with the workflow that costs them the most hours, in their own branding, on their own client fact sheets.
- Then the desk next to them
- Nothing about ABSD or TDSR changes from one salesperson to the next. What holds up for one holds up for the rest of the office without being rebuilt for them.
- Then the agency, on a single licence
- One licence covering every salesperson in the firm, with the rules maintained centrally, so no two desks are quoting a client different numbers off the same regulation.
- Shaped to the firm, not the other way round
- Every agency runs its own way. kaysera is small enough and fast enough to build around how a firm already works, rather than asking it to change to suit the software.
§ 05
What we do not do
- We do not give the advice
- kaysera is a software company. It builds the system. The advice, and the responsibility for it, stays with the CEA registered professional whose name is on the document.
- We do not advise consumers or handle client money
- No recommendations to a buyer, no products sold, no funds touched. Every document belongs to the licensed professional who signs it.
- We do not put an unchecked model in front of a client
- Anything a client sees passes through rules that can be tested, or through a person, or both.
- We do not sell seats we have not built
- A demonstration is running software or it is not a demonstration.
§ 06
Working together
The first conversation is short: what your proposals look like today, how long they take, and which part of that is worth handing over.