Home › Bespoke access software
Bespoke access software
Most installers stop at the door. We write the software that runs the locks afterwards, because that is where the work actually is once you have more than a few.
Where the manufacturer's app runs out
Every smart lock ships with an app, and for one house it is fine. It stops being fine at about the point you have several doors, several people, and a reason for access to start and stop on a date somebody else decided.
Then you are typing codes into a phone because a booking came in, or a tenancy started, or a contractor is due on Thursday — and doing it again to take the access away, which is the half people forget.
What we build instead
Access driven by whatever already decides it. A booking system, a tenancy start date, a work order, a staff rota. The code is issued when the thing happens and expires when it stops, without anybody remembering.
Multiple doors and multiple sites in one place, with a record of who was given what. Front door plus room door, where a building needs both. Reporting that answers "who had access to this door in March" without somebody scrolling an app.
This is not a claim we are making up
The founder built and runs tioo.com, a live platform for short-let operators that integrates directly with TTLock — assigning locks to rooms, nominating a shared front door, and issuing and expiring PINs against bookings automatically.
That is his own product rather than a client project, and we would rather say so plainly than dress it up as a delivery history we do not have. It is the reason we can talk about lock APIs from experience instead of from a brochure.
How it is quoted
Not from a price list. Bespoke scope varies too much for one to mean anything. We write a short specification with you, quote a fixed price against it, and if the scope changes the quote changes in writing first.
Got more doors than an app can sensibly handle?
Tell us how access gets decided and we will tell you what is possible.
Request a quote