Operations · App Starter
A working rental system — availability calendar, checkout and return desk, late fees, utilization — generated into a codebase you own.
Describe what you rent and how you charge, and Dual7 generates this rental system around it: six connected entities, a date-range availability calendar, and a checkout desk, shipped as a real full-stack app. Change the fee rules, add delivery, rename anything — it's your code, not a per-asset subscription.
01 · Data model
Double-bookings and unbilled late returns are schema problems before they're process problems. This starter generates six connected entities, and every calendar, desk screen, and report below reads from them.
| table | what it holds |
|---|---|
equipment | Individual rentable units — serial number, condition, rates by day and week, and current status: available, reserved, out, or in maintenance. |
categories | Fleet groupings (generators, trailers, speakers) carrying default rates, deposit rules, and turnaround buffers new units inherit. |
customers | The people and businesses renting from you — contact details, ID on file, rental history, and any outstanding balance at a glance. |
reservations | Future holds on a unit or a category for a date range — the rows the availability calendar blocks before anything leaves the building. |
rentals | The active ledger: checkout time, due date, actual return, condition notes, and every charge — base, late, damage — on one record. |
maintenance_logs | Service and repair records that take a unit off the calendar, so a machine in the shop can never be promised to a customer. |
02 · Screens
Every reservation and open rental blocks its unit's calendar, with a configurable turnaround buffer between bookings. Conflicts surface when the booking is made, not when two customers arrive for the same trailer on Saturday morning.
One counter screen runs the handover: pull up the reservation, record condition, collect the deposit, and the unit flips to out with a due date. Return reverses it — condition check, charges settled, unit back on the calendar or routed to maintenance.
Due dates drive fee accrual automatically, using rules that live in your code — a grace period, a daily rate, a cap, whatever your policy actually is. Damage and cleaning charges attach to the rental record, so the final invoice writes itself.
Time-on-rent versus time-available, per unit and per category, alongside revenue per unit. It's the report that says which fleet to expand and which idle assets to sell — computed from your live tables, not a spreadsheet you rebuild monthly.
03 · Process
Tell Dual7 what you rent, how you price it — hourly, daily, weekly — your deposit policy, and how returns work. Plain language is enough; the starter supplies the structure.
Get the working system in minutes, then shape it conversationally: add a delivery option, change the late-fee grace period, split a category. Every change lands in real code you can inspect.
When the counter staff are ready to use it, run it through Dual7's approval gates to production — audit trail included, deployed on your infrastructure, data in your database.
04 · Fit
The wall calendar works until the person who understands it takes a day off. This starter is the whiteboard made durable: the same bookings, visible to everyone, with conflicts caught at reservation time instead of at the counter.
Rental platforms tend to bill by fleet size, so growing the business grows the software bill in lockstep. Generate the system once, run it on your infrastructure, and adding the hundredth unit costs a database row.
A tool crib at a contractor, a gear room at a studio, a loaner pool at a dealership — internal rental operations rarely justify a dedicated vendor. A generated system sized to the desk does, because there's no recurring bill to justify.
If rental is the business, the operational core shouldn't be rented from someone else. Start from working checkout, calendar, and fee logic, then build your edge — routing, pricing, a customer portal — into code you control.
05 · Yours
The starter is a floor, not a ceiling. Rename entities to your trade's vocabulary — units to machines, rentals to hires — and the screens and reports follow. Add fields in Vibe mode as your operation needs them: a delivery-address field on reservations, a fuel-level field on returns, a customer credit limit.
Structural changes are still just changes to your code: add a delivery-scheduling module, put an online reservation page in front of the calendar, or wire card payments into the checkout flow. The output is a normal full-stack codebase with no runtime dependency on Dual7, so your team can also edit it directly.
Rental software subscriptions charge you monthly for screens around your own fleet data, and the price climbs with every asset you add. This starter generates the schema, screens, and fee rules as source code in your repository, deployable on your infrastructure. No per-asset tiers, no export project when you switch — switching away from code you own isn't a thing.
The honest trade-off: you're operating an app, not renting a service desk. Dual7's governed pipeline exists to make that safe — approval gates before changes reach the counter, an audit trail, and regeneration when you want to restructure rather than patch by hand.
06 · Industries
A rental system that thinks in event weekends — quantity inventory, packages, and delivery runs — generated into code you own.
A rental system built for iron — open-ended billing, hour meters, jobsite delivery, off-rent calls — generated into code you own.
A rental system that speaks production — kits, insurance certificates, prep checks, weekend rates — generated into code you own.
A working full-stack rental system generated into a codebase you own: six connected entities (equipment, categories, customers, reservations, rentals, maintenance logs), a date-range availability calendar, a checkout and return desk, automatic late fees, and utilization reporting. It runs on your infrastructure with your data in your database.
Both. Reservations hold a unit or a category for a date range in advance; a walk-in is a rental created straight from the desk against whatever the calendar shows as free right now. Either way the unit is blocked the moment the record exists, so the two paths can't collide.
Deposits are collected at checkout and reconciled at return against any damage or cleaning charges. Late fees accrue from the due date under rules you define — grace period, daily rate, cap — and because those rules are code in your project, an exception for a good customer is an edit, not a support ticket.
Yes — each piece of equipment is its own row with a serial number, condition history, and rental history. If parts of your inventory are bulk-counted instead (cables, pads, sandbags), add a quantity-tracked entity alongside; the schema is yours to extend.
The starter ships desk-first, and adding a public reservation page is a natural extension: a form that reads the same availability calendar and writes the same reservations table. In Vibe mode that's a conversational change; it lands as normal code in your repository.
Dual7 App Starters
A working rental system — availability calendar, checkout and return desk, late fees, utilization — generated into a codebase you own. Describe your version to start — the output is a project you own.