The Problem
The resale value of a well-maintained or heavily modified vehicle is almost never reflected in the sale price, because the documentation doesn't exist in a form a buyer will trust. Service records are in a folder. Receipts are in a glove box. Modification history is in a thread on a forum. None of it transfers cleanly at the moment of sale.
Built by PaddockGavin and powered by Paddock20, iGot Receipts™ closes the gap between "I have the receipts" and "I can show you the receipts." Every mod, service and cost is logged against a VIN, then packed into one file you hand over at the sale, with photos, dates and line items.
The insight was simple: the person who knows the most about a vehicle is its current owner. The platform's job is to turn everything they already know into something the next owner can verify.
How It Was Built
Discovery
Most owners have a system. It is not organized in a way that survives a sale. The research phase mapped the tracking behaviors of enthusiasts and daily drivers: what they save, what they lose, and what they wish they had at the moment of resale. The product was designed around that observed behavior.
Architecture
Every record in the system is anchored to a VIN. That single decision changes the entire data model: records become portable, verifiable and transferable at the moment of sale.
UX
It had to be easy enough to use in the service bay, not two weeks later from memory. So you can shoot a photo, fill a form or say it out loud.
Export
Every feature in iGot Receipts™ points at one thing: a packet a buyer will believe. Dates, photos, receipts and line items, sorted by type, exported as one file.
Architecture
One rule drove the build: the packet has to convince a buyer who has never heard of us. So the dates have to hold up, the photos have to prove where they came from, and the layout has to need no explaining.
The Result
iGot Receipts™ turns ownership history into a transferable asset. The platform is built for the moment a buyer asks "what was done to this car?" and the answer is a document instead of a conversation: VIN-linked, timestamped, photo-backed and exported in minutes.
The receipts were always there. The packet puts them in front of the buyer.
Consumer products live or die on the gap between what users want to do and how fast they can do it. That is an architecture problem before it is a design problem. Start with a Fit Call.
Next Case Study
Paddock Mail™ →
Build With RAIL: Free
Answer three questions, type them or say them out loud, and watch RAIL scope your app in real time. Named app, working interface, and a build blueprint you keep. Before you ever talk to anyone.
A named app. A working interface. A blueprint PDF you keep. Whether we ever talk or not.
