Shoebox
Point it at a folder of receipts and invoices and ask questions in plain language. Built for Receipts — build something that makes a messy pile of documents answerable. PDF and image ingestion, extraction, and natural-language query. The interface is deliberately narrow: one path, done properly, rather than a broad surface that half-works at the deadline.
Gallery
Screens
Shoebox — main view
Shoebox — result state
On the clock
What shipped, what didn't
Completed in time
PDF and image ingestion, extraction, and natural-language query.
Unfinished / faked
Handwritten receipts are close to useless.
Obstacles
Lost four minutes to an auth redirect loop that turned out to be a trailing slash.
Lessons learned
Boring, well-understood tools beat interesting ones when there's no time to debug.
Process
Prompting approach
Started from a single system prompt describing the user and their constraint, then iterated with the assistant on the Shoebox data model before writing any interface code. Full prompt log is in the repository under /prompts.
Fairness
Disclosures
Declared by the builder at submission time, visible to judges before scoring.
Judging
Public feedback
Judges' private notes stay private — this is what they chose to say publicly.
Elena Voss
VP of Engineering, Harbor Compute
Genuinely useful. I would install this. The limitations section is honest, which makes me trust the rest of the submission more.
Claudia Reyes
Staff Engineer, Vantage Analytics
The scope discipline here is the whole story. One path, finished, demoed without a stumble. That is what a 30-minute build should look like.
Hana Kobayashi
Principal Research Engineer, Independent
Genuinely useful. I would install this. The limitations section is honest, which makes me trust the rest of the submission more.
Discussion
0 comments
No comments yet.