Lettings
One workspace for the tenancy lifecycle.
2026
Development recorded in the project repository. Earlier work may predate this history; this is not a confirmed launch date.Business systems
Inside Lettings
The live Lettings product website.
The problem
A letting agency needs one operational view from first enquiry through property, applicant, tenancy, documents, maintenance, communication and client money. When those stages live in separate products, staff spend the tenancy reconciling people, properties, tasks and balances by hand.
For a platform serving several agencies, the same broad workflow must remain strictly inside the correct agency's records. External messaging, payment and property providers add integrations without changing that boundary.
The solution
The platform in development connects CRM, properties, applicants, tenancies, documents, maintenance and client-money workflows in one agency workspace. Each domain remains a clear module while shared relationships make the full tenancy visible to authorised staff.
Agency-scoped database rules and audit history separate customers of the platform. Provider adapters add messaging and external services without embedding a single supplier throughout the application. The platform and integrations remain in development.
The decisions behind it
- One tenancy, several responsibilities
- The people, property, maintenance and money records have different lifecycles, but must still refer to the same tenancy.
- Separation beneath the interface
- An agency boundary has to apply to data access, including requests made outside the normal screens.
- Agency-separated records
- Tenancy and maintenance workflows
- Accounting and communication adapters