RentalOS
by
- Category
- Operating system for rental businesses
- Status
- In development
- Built by
- HAYKALI
RentalOS is a vertical operating system for businesses that rent out physical assets. It is built around the rental cycle itself, rather than a generic booking tool with rental bolted on.
Product screens are not shown here because none have been approved for release yet. They will be added to this page when they are. Details on this page are being confirmed with the product team.
What using it looks like
The views this product is organised around, built from its model. Sample data, not a product screenshot.
The day as the team sees it: handovers, returns and what needs attention.
Concept interface, sample data
The operational problem
What usually goes wrong before a system like this exists.
Availability lives in someone's head
It sits in a shared sheet or a chat thread, so the same asset gets promised twice.The paper trail is scattered
Contract, handover condition and return notes are kept in different places, so disputes are settled from memory.Invoices are rebuilt after the fact
Finance reconstructs what was rented, for how long and at what price from bookings and messages.Maintenance is tracked apart from bookings
An asset that needs service is still bookable because nothing connects the two.
What the system is organised around
The areas of the operation it covers.
Assets and availability
One register of what you rent out, and a single answer to whether it is free for given dates.
Reservations
Quotes and bookings that check availability as they are made, not afterwards.
Contracts and documents
The agreement for each rental, tied to the customer, the asset and the period.
Handover and return
Condition and accessories recorded when an asset leaves and when it comes back.
Billing
Charges derived from the rental record instead of retyped from it.
Maintenance and condition
Service and repairs recorded against the asset, so availability reflects reality.
One rule, enforced by the system
Illustrative model of how RentalOS treats a booking. It is not a product screenshot. Product screens will be added when they are approved for release.
One rule, enforced by the system
A booking cannot overlap another booking, or a service job, for the same asset.
Asset B is already booked on days 4 and 5, so the new booking cannot be saved.
- Booked
- In service
- Blocked
Records the system holds
- Customer
- name
- contact
- Asset
- type
- status
- Booking
- asset
- customer
- dates
- state
- Contract
- booking
- terms
- Invoice
- contract
- total
- Service job
- asset
- work
- dates
- A customer places bookings.
- A booking reserves an asset for dates.
- A confirmed booking becomes a contract.
- A contract produces an invoice.
- A service job takes an asset out of availability.
The rental cycle RentalOS is organised around
Every rental business runs some version of this sequence. The product is structured so each stage hands a complete record to the next.
Enquiry
A customer asks for an asset and dates.
Reservation
Availability is checked and the booking is held.
Contract
Terms and price are agreed and recorded.
Handover
The asset leaves with its condition noted.
Return
The asset comes back and is inspected.
Invoice
Charges follow from the rental record.
Turnaround
Cleaning or service before it is available again.
Built for
Owners and managers of rental businesses
Operations and fleet or inventory managers
Front-desk and dispatch teams
Finance staff who invoice rentals
Interested in this product?
Tell us about your business and what you rent out, and we will tell you where the product stands and whether it fits.