All projects

Finny case study

Since 2026Active development

Finny: turning receipts into timely warranty reminders

Finny is a web app for keeping proof of purchase, product details and warranty dates together. It turns receipt input into a record people can check before relying on its reminders.

Visit Finny
From receipt to reminderThe Finny workflow keeps a human review between automatic receipt extraction and the saved deadline used for reminders.
  1. Add receipt
  2. Review OCR draft
  3. Save purchase record
  4. Receive reminder

The problem

A receipt is most useful months after checkout, when a product fails or a warranty deadline approaches. By then, proof of purchase, product details and the relevant date are often no longer in the same place.

Finny brings those pieces into one reviewable record and keeps the saved warranty date connected to the receipt instead of treating the scan as an isolated document.

My role

I am building Finny as an active software project from Bremen. The documented project stack is TypeScript, React and Next.js.

My work covers the web product flow from receipt input and field review to the stored purchase record and the reminder experience.

How the workflow is structured

  1. A receipt enters the web app as a photo or PDF; Pro users can also forward receipts by email.
  2. OCR suggests the retailer, product, purchase date, price and warranty period. The user reviews and corrects those suggestions before saving them.
  3. The reviewed record connects proof of purchase to a saved deadline. Finny then sends email reminders before that date.

Technologies used

  • TypeScript
  • React
  • Next.js

Key decisions

Review before save

OCR output remains a draft. The product asks the user to verify the extracted fields before they become the record used for reminders.

One purchase record

The receipt, retailer, product, price, purchase date and warranty period stay connected instead of being spread across separate tools.

Deadline-led reminders

Reminders are derived from the reviewed warranty date, so the notification flow starts with data the user has already checked.

Implementation challenges

Receipts are inconsistent inputs

Photos and PDFs vary, and extracted fields can be incomplete. The workflow therefore exposes suggestions for correction rather than presenting OCR as certain.

Dates are not legal conclusions

Commercial warranties and statutory rights are different. Finny organizes reviewable dates and reminders without deciding legal questions for the user.

Current outcome

  • Finny is an active project and has been part of the portfolio since 2026.
  • The public product supports receipt photos or PDFs, reviewable OCR fields and email reminders before saved deadlines.
  • Public product information is available in both English and German.