Client preview · updated 25 October 2026
Where we are
PASPRT (working name) is in its first phase: the full concept as a clickable demo with fictional data, built on the architecture the real product will use. Nothing you do in the demo is saved.
Phase 1 · Now
Concept and clickable demo
Phase 2 · Next
Accounts, storage, AI reading
Phase 3 · After
Beta with real users
Ready to look at
- Landing pageAll sections from the brief, with imagery and a looping hero film made for this project.
- The add flowScan a receipt → product identified → warranty → manual → passport ready. Runs on a sample receipt with two products on it.
- Product passportIdentity, purchase, warranty, documents, ownership, product history and a completeness score. Every fact shows where it came from.
- My StuffInventory with totals, search, the filters from the brief and categories.
- AskQuestions answered only from the manual, with page references. When the manual doesn't say, it says so.
- Pass it onThe seller chooses what transfers; the buyer opens a link and accepts. Personal details never move.
- Inventory exportInsurance overview as CSV and print-ready PDF.
- Rebrandable by designName, taglines, colours, domains and assets live in one config file. Passport IDs (like 8X4K-29PM) contain no brand.
- ArchitectureBrand-neutral domain model, database schema with row level security, private storage and hashed transfer tokens, provider interfaces for AI and data sources.
Coming next
- Accounts and real storageSign-up and login, receipts and documents in private storage, opened only through expiring links.
- AI receipt readingReal photo and PDF extraction, several products per receipt, with the user confirming before anything is saved.
- Product matching and manualsCatalogue lookup for model and image, official manual finder, manual indexing for Ask.
- Warranty engine and remindersRules per brand and country, reminders before a warranty ends, notifications.
- Installable app (PWA)Add to home screen, camera-first scanning on the phone.
- AdminSupport view, data quality, usage analytics.
Open questions
- Final brand name and domain (everything is ready to swap).
- Launch market: Netherlands first, or EU-wide? This decides warranty rules and languages.
- Is English the launch language, or Dutch plus English?
- Business model: free with a paid tier (e.g. more products, export, family sharing)?