Proofs sat in a shared folder for four days. The photographer thought the producer was sending them. The producer thought the photographer already had.
Nobody was lazy. Nobody was wrong about the work itself. Two people each believed the other owned the next decision, so the decision never moved.
That pattern shows up more often than missing samples or a bad crop. Small ecommerce studios run lean on purpose. The same three or four people wear overlapping hats, and titles stop telling you who is actually accountable for the open handoff.
When two people each thought the other owned it
An ownership gap is not a skill gap. The brief was written. The shot list had rows. The files existed. What was missing was a named human whose job it was to move the work to the next stage.
Studios feel this as stalled approvals, delivery that waits on a "quick check," or a client who hears different answers from two people on the same job. Fixing it does not require a Hollywood crew chart. It requires writing down who owns each handoff on the jobs you actually run.
What team roles means in a 3–10 person ecommerce studio
Product photography team roles, in this context, are the standing accountabilities for moving a client job from request to released files — not job-board titles and not a film set roster.
A commercial advertising shoot may list a producer, digital tech, stylist, and first assistant as separate people. A five-person ecommerce studio shooting packshots and detail rows for Shopify and Amazon often has one person covering two or three of those functions in the same week. The useful question is not "what is our org chart." It is "for this job, who owns the next decision if something stalls."
That question sits next to the product photography workflow itself. The workflow names the stages. Roles name the humans who cannot leave a stage ownerless.
The six handoffs that need a named owner
Most ecommerce jobs share the same six places where work either advances or dies in a shared inbox. Name an owner for each one, even when the same person owns more than one.
- Intake and brief lock — who confirms SKUs, required views, deadline, and output specs are complete enough to start.
- Samples — who records what arrived, condition, and where the tray lives until shoot day.
- Shoot-day decisions — who decides setup order, skips a missing variant, or stops a row that does not match the brief.
- Post and retouch queue — who prioritizes the edit list and decides when a file is ready for internal review.
- Client proofing and approval — who sends the current version, consolidates feedback, and records the decision.
- Final release and delivery — who confirms the released set matches what was approved and that the client can access it.
The day-of instance of shoot ownership already has a home on the call sheet. This list is the recurring map that sheet assumes exists.
Producer, photographer, retoucher, QC — and the hats people actually wear
In a small studio, role names are useful shorthand, not permanent silos.
- Producer / lead: owns client communication, brief lock, schedule, and usually the final release decision.
- Photographer: owns capture against the locked shot list and the style rules for that set.
- Retoucher / post lead: owns the edit queue and whether a file is ready for review.
- QC reviewer: owns the internal pass before the client sees proofs — crop, color, naming, missing rows.
Combining hats is normal. A photographer who also retouches is fine. A producer who also shoots packshot days is fine. The blind spot is combining hats that remove the second set of eyes: the same person who shot the set doing the only QC pass with no second reviewer, or the same person who promised the client Friday delivery also being the only person who can release files while they are on set all day.
When the bottleneck is floor time or edit time, production capacity planning tells you whether to add help. Roles tell you which accountabilities stay named after that help arrives — a second shooter without a named QC owner just moves the stall downstream.
Write the ownership line on the job, not in a dusty org chart
An org chart that lived in a slide deck last spring will not save Thursday's stalled proof set. Put three fields on the job record where the team already looks:
- Current owner — the person accountable for the open handoff right now.
- Open decision — what has to be true before the job can move (brief locked, samples complete, proofs sent, approval recorded).
- Due — the date that decision needs by, not the client's final delivery date alone.
If those three fields are blank, the studio workflow diagnostic ownership questions will score exactly how that feels: the job lives in one person's memory.
Client-facing roles stay few on purpose
Internally, several people may touch a job. Externally, the client should know who speaks for the studio on that project.
Name one primary contact for questions. Name who consolidates feedback when three stakeholders reply in different channels. Keep online proofing as the review source of truth so comments do not scatter. When the job needs a connected brief, proof, approval, and release record, the client approval portal conversation is about the tool shape — roles still decide who is allowed to hit send and who is allowed to mark approved.
Internal quality control should happen before that client-facing send. The QC owner and the client-facing sender can be different people. When they are the same person, build in a short second-pass rule for catalog jobs where a missed variant is expensive.
Seats are not roles
Software permissions and operational ownership are easy to confuse. Lenso team roles and seats (Owner, Admin, Member) control what someone can change inside the product. They do not automatically mean that person owns brief lock, shoot day, or final release on a given client job.
A Member can own QC for the week. An Owner can still leave shoot-day decisions unnamed. Map seats so people can do the work; write the job ownership line so people know who must move it.
Copy-ready team roles checklist
Use this on the next active job, not as a hiring exercise:
- List the six handoffs for this job and write one current owner next to each.
- Mark any handoff where the owner is also the only reviewer — add a second pass or accept the risk in writing.
- Name the single client-facing contact and the person who consolidates feedback.
- Confirm who may send proofs and who may record approval.
- Confirm who releases final files and who verifies the delivery set matches the approved version.
- Put current owner, open decision, and due on the job record where the team already looks.
- If a freelancer or second shooter joins this week, assign which of the six handoffs they own — and which they do not.
- Re-check ownership when the job moves from shoot to post, and again before client proofing.
When those owners need to sit on the same record as the brief, samples, proofs, and delivery, see Lenso for studios. The software does not invent accountability. It makes the missing owner harder to hide.
FAQ
What are the responsibilities of a product photographer?
In an ecommerce studio, the photographer owns capture against the locked shot list and style rules: correct views, consistent setup, and flagging a missing sample or brief conflict on the floor. They do not automatically own client approvals, final release, or the only QC pass unless the studio has explicitly assigned those hats too.
What is a shoot producer, and how is that different in an ecommerce studio?
On a larger commercial set, a producer often coordinates crew, schedule, and logistics as a dedicated role. In a 3–10 person ecommerce studio, "producer" usually means the person who locks the brief, keeps the schedule honest, owns client communication, and drives the job to release — often while also shooting or editing other days. The title matters less than whether those accountabilities have a name on each job.
Who should approve proofs before the client sees them?
Someone other than the person who just finished the work whenever the job size makes a miss expensive. A named QC owner runs the internal pass for crop, color, naming, and missing rows. The client-facing sender then shares only the version that cleared that pass. Solo operators can still separate the tasks in time: finish the set, step away, then review against the shot list before sending.
Can one person own both shoot day and final QC?
Yes, and many studios run that way. The risk is blindness to your own habits — a consistent crop that drifts, a skipped variant, a background that does not match the style guide. If one person owns both, add a short second-pass rule or a checklist tied to the shot-list rows so QC is not "does this look fine to me."
How do Lenso team seats relate to studio roles?
Seats control product permissions. Studio roles control job accountability. An Admin seat does not make someone the producer of record. Use team roles and seats so people can access what they need, and keep the ownership line on the job for who must move each handoff.