Context
In short-term rentals, a booking connects a property, a guest, messages, payments and operational tasks. TSUKA is a SaaS project being developed to bring these parts into a shared management system.
The task
The product’s goal is to help owners and operators understand working context and act on it. Development covers properties and bookings, communications, guest history, finances and automation.
Constraints
The product is in development. Plans, prototypes and released capabilities should not be presented as one promise. Data quality, reliable external integrations and clear automation boundaries matter.
Approach
The operating logic starts with the manager’s task: what is happening with a property and guest, which information is needed now, and what needs action. This frames modules around an end-to-end business process rather than a list of screens.
- 01Process
- 02Problem
- 03Solution
- 04Validation
Implementation
Development areas include a PMS, a shared inbox, guest communications, financial analytics, integrations and operational tools. The project uses AI in development and explores AI agents. This list does not certify that every module is ready.
Current state
TSUKA continues to develop. A verified public feature-availability matrix and measured client outcomes are not presented here. This page focuses on the product’s purpose and the work behind it.
Risks to account for
Design questions include duplicate guest records, inconsistent external statuses, partial integration failures and expanding scope before validating the core workflow. These are issues to consider, not a documented incident history.
Key takeaways
Editorial takeaway: B2B value appears in a connected workflow. Separate features do not establish that an operator can complete the whole task. Further evaluation needs real usage scenarios and verifiable quality criteria.
Quantitative results have not been published. This case describes the starting problem and direction of work.