+ case study
Snapose
Photobooth studio platform
- year
- 2025
- type
- Client product
- role
- Problem structuring, architecture, build, training
- status
- shipped
Competitors sell software. We shipped the operation around it: auto finance with waste analysis, offline-first with Drive sync. Five apps became one.
01+ the problem
What they came in with
A photobooth studio ran each event across five or more apps, and every one of them assumed the venue had internet. They asked for photobooth software.
02+ what we found
What it actually was
Competitors already sell photobooth software. The real constraints were connectivity, because a crowded venue is where the internet fails first, and reconciliation, because five apps meant five versions of the books.
03+ the build
- 01
Offline first
The booth runs without a connection and syncs to Google Drive when one returns. Data is backed up by default.
- 02
Shared across laptops
Sync goes through the studio’s own Drive, so every laptop on that Drive sees the same data instead of one device holding it.
- 03
Books that close themselves
Finance is captured as the booth runs, with waste analysis, so reconciliation stops being a monthly fire.
04+ architecture
Written down, so your team can extend it
05+ the result
- 5 to 1
Apps a venue runs
Photobooth operators, before and after Snapose
Operator workflow audit, 2025
06+ in their words
gw baru dikasih liat flow yang pake snapose software yang kalian bikin and gw masih amazed padahal kita udah rehearse sebelumnyaI was just shown the flow running on the Snapose software you built and I am still amazed, even though we had already rehearsed it.
07+ handover
What the client owns at the end
- Source code and infrastructure access, in your accounts
- Architecture documentation, the diagram on this page included
- Operating documentation written for the people who run it
- Training sessions until your team runs it without us
Every engagement ends with handover. That is not an upsell, it is the definition of the work.