A rental business lives on two questions: where, and in what state
An equipment renter — construction, events, tools, farm machinery — manages a fleet where every item is either available, out, or in maintenance. The spreadsheet tracking those states expires at every movement: one unrecorded checkout, and you promise a client a machine that's already gone.
Add equipment condition (the damaged return discovered three rentals later), deposits to track, and the preventive maintenance that drives fleet lifespan — three trackings shared calendars can't hold.
Your fleet, your rental rules, your application
Describe your business: “We rent construction equipment. Each item has a reference, a daily rate, a condition. A rental has a client, dates, equipment, a deposit and a status: reserved, out, returned, inspected. I want availability, today's returns and deposits to give back.”
The generated application materialises that register: the fleet and its states, rentals linked to clients, deposits tracked from intake to refund, and a dashboard of the day's movements.
- Equipment fleet: references, rates, conditions
- Rentals: client, dates, equipment, deposit, status
- Checkouts and returns with condition checks
- Maintenance and downtime
- Dashboard: availability, returns, deposits
The return inspection, finally traced
Paper tracking's weak point is the return: equipment comes back hand to hand without a trace, and damage is discovered at the next checkout — too late to attribute. With a “returned” status distinct from “inspected”, the application materialises the verification step, and each item's history remembers its conditions.
Generated demo data simulates an active fleet — varied equipment, ongoing rentals, expected returns — to evaluate the tool on something concrete.
The fleet register, a company asset
Rental and maintenance history drives per-machine profitability and the fleet's resale value: that register belongs to the company. Code ZIP export, GitHub push, free hosting or the included dedicated URL.
Free Discovery plan for the first application; Pro (€25/month) and Max (€149/month) to iterate, with the cost shown before each generation.
Typical generated entities
- Equipment
- Rental
- Client
- Deposit
- Maintenance
Generated screens
- Fleet with availability and conditions
- Rental record: equipment, dates, deposit
- Today's checkouts and returns
- Equipment record: full history
- Fleet dashboard
Dashboard indicators
- Equipment out / available
- Returns expected today
- Deposits to give back
- Utilisation rate per item
Frequently asked questions — equipment rental
Can we manage degressive rates (day, weekend, week)?
Yes: describe your rate grid and it structures equipment records and rentals. Specific calculations can then be refined on the exported code.
How do we avoid double-renting the same item?
The register is central: an item that's out is visible as such to everyone. Upcoming reservations appear on the item's record and in date-filtered lists.
Can we track preventive maintenance (hours, servicing)?
If your description provides for it, maintenance becomes an entity attached to items, with deadlines visible on the dashboard.
Can the return inspection happen on a phone?
Yes: it's a responsive web application — inspection status and remarks are entered at the depot as equipment comes back.
What do we need to start?
Describe your fleet and rules in plain language, validate the proposed plan, generate with the Discovery plan (€0). The application arrives deployed with demo data.