Enterprise and institutional operators
Thousands of homes, and a regulator who does not accept “the system did it”. Tekniti runs the operational layer, and shows its working.
Every enterprise engagement runs against a plan like this one, with named owners on both sides and a go-live gate per branch. Nothing goes autonomous until you have watched it work with approvals on.
- Approvals on by default, relaxed only where you decide
- Branch-by-branch rollout, reversible at any stage
- Security questionnaire, DPA and sub-processors up front
Bespoke work
Built around the systems you are not replacing.
The question is never whether it has the feature. It is whether it fits what you already run — and who does that work.
Sits alongside your PMS
Nobody rips out the system of record on day one. Tekniti reads from it, writes back to it, and takes the operational work in between.
Connectors we build
If the system has an API, a feed, a mailbox or a nightly export, it can be connected. Where it has none, we build the bridge as part of the engagement.
Custom workflows
Your approval thresholds, escalation paths, service standards and contractor panels, configured as the way work actually moves.
Your own agents
A domain we have not built for — arrears policy, licensing regime, a reporting pack — can be added as an agent with its own scope and audit trail.
API and events
Read the portfolio, push events, subscribe to what changed. Your data science team gets the same record the product runs on.
White-label
Your brand in front of landlords and residents, with branch-level separation underneath.
No API? A nightly export and a monitored mailbox are enough to start.
Model Context Protocol
Ask it from the assistant you already use.
Every tier exposes the portfolio over MCP. Enterprise engagements get the connector built into your own deployment, with your access controls in front of it.
ClaudeClaude, and Claude for Work
ChatGPTChatGPT, and ChatGPT Enterprise
GeminiGemini, and Gemini Enterprise
Which of our buildings has an EICR expiring this quarter?
9 across three branches — two have no contractor assigned.
Draft the board note on compliance exposure.
Drafted from the live record, with the eight properties listed.
Read-only by default. Anything that changes a record still goes through the same approval gate as the rest of the product.
Beyond lettings
Other buildings. Same engine.
An obligation with a date, an issue with a timescale, a resident with a contract, an approval with a name. Change the rules and the vocabulary, not the architecture.
Residential lettings
LiveSame engine underneath every one of these — the rule set and the vocabulary are configuration, not a rebuild.
Scale
One system from ten homes to ten thousand.
The interface gets denser and the controls get deeper. It does not become a different product, and you do not migrate to get there.
10 properties
Self-managing landlord
Compliance dates, tenant replies, repairs and rent in one place.
100 properties
Portfolio landlord
Portfolio-wide exposure, spend patterns, year-end figures.
1,000 properties
Letting agency
Branches, teams, routed approvals, client reporting.
10,000 properties
Institutional operator
Custom workflows, integrations, API, dedicated support.
Control
Autonomous where it should be.
Accountable where it matters.
Autonomy is only worth having if you can see where it stopped, and who said yes.
- 1
Identify
A report, a date, a payment, a message.
- 2
Reason
It reads the property, tenancy and history behind it.
- 3
Prepare
It drafts the reply, the job, the notice, the quote.
- 4
Approve— human in the loop
Anything material waits for a named person.
- 5
Execute
Carried out, and the parties are told.
- 6
Record
Written to an append-only, hash-chained log.
Trust
Built for work you can’t afford to lose track of.
Compliance work has consequences. The system that does it has to show its working.
Append-only audit trail
Every compliance-relevant action is hash-chained, so the record can be shown to be untampered.
Approval gates you define
Material actions wait for a named person. The decision and the decider are part of the record.
Hosted in London
The platform and its data run in AWS eu-west-2 (London).
Separated by account
Every query is scoped to the account, branch and role that issued it.
Two-factor sign-in
TOTP second factor for staff accounts, with managed session control.
Answers on the record
Security questionnaire, DPA and sub-processor list on request.
Each line carries the hash of the line before it. Change one and every entry after it stops matching.
Partners
Tekniti is part of Bayseian Ltd — an OpenAI Select Partner and a member of the Claude Network.
Your portfolio can run better.
Ten homes or ten thousand — know what is happening, and act on it.
No setup fee. Cancel any time. Live in minutes at app.tekniti.ai.