A photo studio sells shoots. That is the whole business: a customer books, a photographer shows up, images come back. Every hour of revenue needs a person standing somewhere holding a camera.
But the studio had been making a second thing the entire time, without noticing it was a thing. The look — the colour, the grade, the reason the photos are recognisably ours — lives in a set of presets. They were built for internal use. They were also, it turns out, the only part of the business that can be sold without anyone being there.
What was missing was not the product
The presets already existed and already worked. What did not exist was everything around them: a storefront, product pages, a cart, a checkout, a way to deliver a file after payment, and somewhere to keep the orders. The booking platform covers none of that — it is built for scheduling a person, not for selling a download. The store is live at tettyphotostudiolut.com.
- Storefront with collections and product pages
- Cart and Stripe checkout for a digital product
- Supabase for the product and order data
- Deployed on Vercel and operated after launch
Live
in production at tettyphotostudiolut.com
Stripe
checkout for a digital product
Solo
designed, built, shipped, operated
Why it was worth building
Shoot revenue is bounded by photographer hours. Preset revenue is not bounded by anything except whether anyone wants the look. Those are different shapes, and a company with only the first shape has to grow by hiring.
The general version
If you run a service business, look at what you built to deliver the service. The internal tool, the checklist, the preset, the template — it was produced as a byproduct, it already works, and it is usually the only part you can sell while asleep.