Work · 003 · Product
deskless
The compliance and evidence layer for UK letting agents. Repairs, complaints, documents and money on one statutory clock.
01 The problem
The deadline is the product.
A letting agent's exposure is not that a repair is slow. It is that when an ombudsman asks what happened and when, the answer lives across an inbox, a spreadsheet and somebody's memory. Section 11 and Awaab's Law both run on clocks with legal consequences, and neither clock is in the software the agent already pays for.
deskless puts repairs, complaints, documents and money on that one clock, and produces a record built to be handed to a redress scheme rather than reconstructed for one.
02 Where it does not compete
Knowing what not to build was the design work.
The incumbent ships AI repair triage in the UK at around £1 per property, with distribution through property management systems and a training set of tens of thousands of labelled repairs. deskless does not beat that on triage and does not try.
It wins on the statutory and evidence layer, which the incumbent does not do: redress-scheme complaint handling with an evidence pack, on the same timer engine as the repair obligations.
It is also not an emergency line. Email is the only channel and nobody reads email at 2am, so the product handles everything that is not a 999 call. For a genuine emergency it does exactly one thing: shows the tenant a hardcoded safety instruction and flags the ticket. No escalation chain, no AI-mediated emergency response. Pretending otherwise would be the dangerous feature.
03 Build
- Core
- A single timer engineSection 11, Awaab's Law and redress-scheme windows are all the same primitive
- Output
- Evidence packsAssembled continuously, not generated in a panic
- Channel
- Email in, structured record out
- Front end
- React, Vite, TypeScript
- Data
- Supabase, Postgres, row-level security