This is a submission for the Hacktoberfest Open-Source AI Challenge Week 2: Side Hustle
What I Built
<!-- What does it do, and who would pay for it? What problem does it solve for them? -->Every quarter, freelancers dig through a folder of blurry receipt photos and PDF invoices to work out what they spent and what they can deduct. It's tedious, and the paperwork is full of client names, amounts, and addresses they'd rather not hand to a cloud service.
ReceiptDesk is a local app. You drop in a folder of receipts and invoices, and it:
- extracts vendor, date, total, tax, and currency
- assigns a category (software, travel, equipment, meals, etc.)
- flags duplicates and receipts with missing fields
- exports a clean CSV for your accountant
It's built for solo freelancers and tiny studios. I think they'd pay a small one-time fee or a cheap yearly licence, because the alternatives are either manual work or uploading client data to a SaaS.
Demo
Code
How I Built It
<!-- Which open-source AI did you use (open-weight models, agent harnesses, frameworks, local inference), and how is your project built around it? -->- Model: Gemma, an open-weight model, running locally through Ollama. [Name the exact size and variant you used.]
- Pipeline: [OCR step / vision input, whichever you chose] → the model returns structured JSON → validation → categorisation → CSV export.
- Validation layer: the model's output is checked against a schema. Totals must parse as numbers, dates must be real, and anything that fails is flagged for human review instead of guessed.
- Stack: [Language, UI framework, storage.]
- What I tried that didn't work: [One honest failure, such as a model size that was too slow or a prompt that hallucinated totals, and how you fixed it.]
Why Does Open Innovation Matter?
<!-- Why does open innovation matter for what you built? What did it make possible that a closed API wouldn't? -->- Privacy is the product. Receipts and invoices expose clients, income, and locations. With an open-weight model on the user's own machine, I can truthfully say nothing leaves the laptop. That claim is hard to make with a closed API.
- The economics work. There's no per-document API bill, so a cheap one-time price still leaves margin. A freelancer with 2,000 receipts a year costs me nothing to serve.
- No lock-in. If a better open model appears, I swap one config line. I'm not exposed to someone else's price change or deprecation.
- Room to specialise. [If you fine-tuned or prompt-tuned for a niche, say how it did against a general baseline. Only include numbers you measured.]
My Agent Session
My First User
Prize Categories
<!-- Which partner categories are you entering? List every one that applies, or remove this section. -->- Best Use of Gemma
- Best Use of a .tech Domain (only if you deployed a landing page on a claimed .tech domain)
<!-- Team Submissions: Please pick one member to publish the submission and credit teammates by listing their DEV usernames directly in the body of the post. -->N/A
Top comments (0)