Stop losing damage charges because the proof is on someone's phone.
ReturnProof turns each checkout and return into a timestamped condition packet so small rental operators can recover valid damage costs, catch missing accessories, and avoid redeploying broken gear.
Return inspection packet
Mixer kit #A-17 · 4 flags
hold
before redeploy
Setup
one item class
Cadence
every return
Goal
recover valid charges
Narrow customer
Small rental operators with 50-1,000 rentable items and a busy check-in counter.
Best fit: tool libraries, AV rental shops, camera rentals, event gear, party rentals, and light-equipment yards that are not ready to migrate to a heavyweight rental suite.
Paid problem
Disputed damage, missing accessories, and accidental redeployment leak cash and availability.
The cost is unrecovered repair bills, delayed invoices, lost rental days, customer disputes, and staff time spent reconstructing what happened from paper sheets and phone photos.
Landing-page validation
One redacted return workflow in. One proof packet out.
The waitlist tests whether operators will share a sample checkout/return flow and ask for a condition-evidence packet before a full system is built.
Day-in-the-life pain
The customer is waiting, the next booking is coming, and the damaged gear needs a decision now.
A staff member receives a returned mixer, camera kit, pressure washer, projector, or party tent. The customer says it was already like that. The next reservation may need the same item tomorrow. The owner needs to know whether to charge for damage, hold for maintenance, swap accessories, or redeploy. The current stack can be a spreadsheet, paper form, phone camera, inbox thread, and memory.
Input
Scan a QR code on return, select the reservation, and capture quick photos of the item, accessories, meter/usage notes, and customer-visible damage before the gear goes back on the shelf.
Checks
ReturnProof compares checkout vs return state, requires missing accessory evidence, routes maintenance holds, and drafts a customer-facing damage or no-charge explanation.
Output
A timestamped return packet: photos, accessory checklist, repair decision, hold/redeploy status, billing note, and proof link for customer disputes or insurance follow-up.
Why the workaround breaks
A spreadsheet can say the item returned. It cannot prove the condition.
ReturnProof starts as a narrow evidence layer around the rental workflow that already exists. It does not replace reservations, payments, or accounting on day one. It closes the expensive gap between physical return, repair decision, and billable proof.
Checkout-to-return photo pairing
Match today's return photos against the checkout packet so staff can show what changed without hunting through phone galleries or paper folders.
Accessory and consumable checklist
Cables, cases, batteries, stands, blades, bits, remotes, and manuals get checked before the customer leaves the counter.
Maintenance hold lane
Items with damage, usage overage, safety concerns, or missing parts move into hold status instead of being accidentally redeployed for the next booking.
Billing-ready dispute note
Generate a plain-language repair or replacement charge note with linked proof so the owner can invoice confidently and respond to disputes.
Spreadsheet-safe export
Early users can keep their current booking or inventory sheet while ReturnProof adds the missing condition-evidence layer.
Evidence, not proof
Public threads point to a narrow operations gap around rental inventory, check-in/out logs, maintenance, and damage proof.
Reddit / r/selfhosted · small equipment rental operator
A small equipment rental business for tools and AV gear wants to move away from spreadsheets and manual tracking for inventory, check-in/out logs, maintenance scheduling, billing, and reporting.
Open source →
GitHub public problem issue · rental yards miss damage proof
Rental operators lose recoverable repair costs when return inspections rely on paper sheets, phone photos, handwritten notes, counter conversations, and manual billing follow-up.
Open source →
GitHub issue · realistic rental inventory quantities
A rental-system issue calls out that real rental businesses track multiple units of the same item, availability, and pricing rather than treating every rentable object as a disconnected one-off record.
Open source →
Related equipment-cost issue · freelancers renting vs buying gear
Freelancers making gear decisions currently use ad-hoc spreadsheets and peer advice; this reinforces that tool and AV gear workflows carry real cashflow and utilization consequences.
Open source →
Objections
This is not another generic asset tracker.
The first validation offer is deliberately concrete: one return-inspection workflow becomes a customer-dispute-ready packet with photos, accessory status, maintenance decision, and billing note.
Why not a full rental-management suite?
Many small rental shops only need one painful wedge fixed first: return proof, accessory checks, maintenance holds, and charge recovery. A full suite migration is too heavy for the validation step.
Will staff actually use it at the counter?
The first workflow is intentionally mobile and short: reservation, photos, checklist, hold or redeploy. If it takes longer than the paper sheet, the landing test should fail.
Is this only for heavy equipment?
No. The narrow target is tool, AV, camera, party, and light-equipment rental operators where missing accessories and disputed damage are frequent enough to cost margin.
Is public evidence proof of demand?
No. It is directional. Demand is validated only if real operators join the waitlist and share a redacted return-inspection or inventory sample.
Early waitlist
Send one messy return. Get the packet your paper sheet should have produced.
Early users get a human-reviewed sample packet, a 20-minute workflow review, and a say in whether ReturnProof should start as a mobile checklist, QR-code add-on, spreadsheet companion, or lightweight micro-SaaS.