Delivery-LedGrowth
Product-Led Growth said the product is the acquisition channel. Delivery-Led Growth says the same of the delivery moment: the forty-eight hours after an event, when the audience is assembled, attentive, and looking at your work on purpose. This page is the whole framework — the premise it rejects, the definition, the language, and the metric it is measured on.
Windows desktop app and Android. macOS and iOS in development.
The premise we reject.
Every product in the photo delivery category — Kwikpic, FotoOwl, Memzo, AccioPix, Pixieset, Pic-Time — competes on a premise none of them states out loud:
“The photographer’s job is to get the photos out. Delivery is a cost, and the winner is whoever makes it cheapest.”
Accept that premise and everything downstream follows automatically. You benchmark on upload speed, match accuracy and cost per photo, because those are the only levers a cost centre has. You price per photo, so your revenue falls every time compute gets cheaper. You end the relationship at handover, because a cost centre has no reason to maintain one. And you compete, ultimately, on being the cheapest way for a photographer to be forgotten.
The premise is not wrong about logistics. Files do need to move, and moving them efficiently is real work. It is wrong about what is actually happening at the handover — which is that a photographer briefly has the undivided attention of the largest concentration of qualified prospects they will assemble all year, and then deliberately dissolves it.
The category, defined.
A go-to-market model in which the delivery of work is operated as the primary acquisition channel — instrumented, consented and measured — rather than as a fulfilment cost to be minimised.
The claim is not that delivery should be nicer. It is that delivery sits in the wrong budget. Move it out of fulfilment and into growth, and every decision about how it is built changes — what you capture, what you ask for, what you brand, and what you count afterwards.
The audience is the asset
The photos are inventory. The several hundred people who appear in them, at the moment they are looking for themselves, are the only thing in the transaction that can compound.
Consent is the gate
Nothing in this framework works without a separate, explicit, easy-to-decline opt-in. A guest graph assembled without one is not an asset a business can rely on.
The unit is a booking
Cost per photo can only fall, once. Cost per booking is the number that decides whether an event was worth shooting, and it is the only one worth optimising.
The language.
A category needs words before it needs customers. These are the seven terms the rest of the framework is built out of. Every other page on this site uses them in exactly these senses.
| Term | Definition |
|---|---|
| The Delivery Moment | The 48 hours after an event when guest attention peaks. The scarcest asset in a photography business, and the one the category throws away. |
| Dark Delivery | The old world. A folder link dropped into a black hole — real reach, zero attribution, nothing you can act on afterwards. |
| Delivery Leak | Your work circulating unbranded, untracked and unattributed. The core disease of the delivery category. |
| Guest Graph | The consented identity map an event builds. Owned by you, opted into by them, compounding across every event you shoot. |
| Earned Impressions | Measurable guest reshares of your branded work. Distribution you did not pay for. |
| Guest-to-Lead Rate (G2L) | The headline metric of the category. What share of the guests at an event became a real enquiry. |
| Second-Order Bookings | Bookings traceable to a previous event’s guests. The compounding return on treating delivery as growth. |
Dark delivery vs. delivery-led growth.
The same six decisions, made twice. The left column is not a straw man — it is what the category ships today, ours included, and it is what you are choosing by default if you never make the choice explicitly.
| Dark delivery — the category today | Delivery-led growth |
|---|---|
| Delivery is a cost to minimise | Delivery is where the next booking starts |
| Measured in cost per photo | Measured in cost per booking |
| The relationship ends at handover | The relationship starts at handover |
| Guests are recipients | Guests are a consented audience you own |
| Reach you cannot see | Earned impressions you can count |
| Buy attention from strangers | Compound attention you already earned |
The metric: Guest-to-Lead Rate.
A framework without a number is a mood. Delivery-Led Growth has one headline metric, and it is deliberately unflattering: of the guests an event put in front of you, what share became a real enquiry?
The headline metric of the category. What share of the guests at an event became a real enquiry.
G2L = enquiries attributable to an event ÷ guests reached at that event
“Guests reached” means people who actually received at least one photo, not people who were in the hall. “Enquiries attributable” means a named, consented enquiry you can trace back to that event — not a follower, not an impression, not a like. Both halves are strict on purpose. A metric that flatters you is not a metric.
Why the denominator is every guest
The tempting version divides enquiries by the guests who opted in, because that pool is small and the percentage it produces looks excellent. The definition divides by every guest the event reached — including everyone who collected a photo and never thought about you again. That is the version that can tell you whether an event was worth shooting.
We publish no G2L figures — no benchmark, no target, no range. Nobody has measured this at scale, ourselves included. Any number you see attached to it did not come from us.
What sits underneath it
- Reach: what share of guests received a photo at all
- Consent rate: what share opted in to hear from you
- Earned impressions: reshares of your branded work
- Second-order bookings: the ones traced back years later
The reason nobody quotes a G2L number today is that measuring it requires consented identity at the guest layer, and the category built the opposite — anonymous links, by design, because anonymous links are cheaper. The number is not unknowable. It has just never been worth anyone’s while to know it.
The framework is ahead of the software. On purpose, and in the open.
You cannot measure Guest-to-Lead Rate in Studioshare today. The delivery workflow ships; the attribution layer that would make this framework measurable does not exist yet. Both lists below are exhaustive.
Tethered camera capture
Connect the camera to the Studioshare desktop app and frames sync as you shoot. No card swaps, no import step at the end of the night.
QR + selfie guest access
Guests scan a QR code at the event, take one selfie, and get the photos they appear in. No app install, no account, no waiting for a link.
Server-side face matching
A 512-dimension AuraFace embedding is computed on our servers and matched with cosine nearest-neighbour search against the event gallery.
Selection & proofing workflow
Create events, organise shots into folders, and invite clients to mark their picks — so you shoot to a confirmed list instead of guessing.
Branded galleries on your own studio path
Every event lives at studioshare.app under your studio name, carrying your brand — not a generic file-sharing link that says nothing about who shot it.
Studio wall for the venue screen
Every event can have its own wall on its own address, so you open it on whatever drives the screen and walk away. It stays dark until you publish it, and you pick which folders appear.
Android app on Google Play
Guests and photographers can use Studioshare on Android today. The tethered capture workflow still needs the Windows desktop app.
In development — not available
Guest Graph consent capture
A separate, explicit, easy-to-decline opt-in that lets a guest hear from you later — kept legally distinct from the consent that powers "find my photos".
Earned Impressions tracking
Measure how often guests reshare your branded work, so reach stops being a guess.
Guest-to-Lead dashboard
Your G2L rate per event: how many guests arrived, how many opted in, how many became real enquiries.
Second-order booking attribution
Trace a signed booking back to the event where that client first showed up as somebody else’s guest.
macOS and iOS apps
Android is live on Google Play and the desktop capture app runs on Windows. macOS and iOS are still in development.
Windows desktop app and Android. macOS and iOS in development. Face matching is computed on our servers — a 512-dimension AuraFace embedding, matched by cosine nearest-neighbour search — not on the guest’s device.
Read the rest of the argument.
The manifesto is why we think this matters. The Delivery Leak Report is the study that would prove or kill it — and it has not been run yet.