Product Photography Proposal Template for Studios

Use a product photography proposal structure covering countable scope, assumptions, exclusions, schedule, price, client responsibilities, review, delivery, and the handoff into the working brief.

A product photography proposal explains what the studio is offering before the work becomes a live client job.

It should help the client understand:

the studio's current understanding of the need;
the products and outputs included;
the assumptions behind the price;
the schedule and dependencies;
the commercial next step;
what remains outside the offer.

The proposal is not the same as the project request, quote, client agreement, working brief, change record, or invoice.

Scope and legal boundary: This is a commercial proposal structure, not a contract or legal template. Whether a proposal, estimate, email, signature, or click creates a binding agreement depends on the wording, acceptance method, governing law, and surrounding facts. Use qualified counsel for the studio's client agreement.

Keep each document in its own role

Project request

The initial information a prospective or returning client submits before the studio decides whether to create the job.

Estimate or quote

The current price expectation or stated price for a defined scope under stated conditions.

The legal meaning of these terms can vary.

Proposal

The client-facing explanation of the proposed goal, scope, price, assumptions, exclusions, schedule, and next step.

Client agreement

The counsel-reviewed contract or accepted terms controlling the legal and commercial relationship.

Working brief

The current operational record used after the studio decides to proceed.

Change record

The approved record of a changed scope, price, schedule, product, output, or assumption.

Invoice

The request for payment of an amount due.

A studio can combine some of these documents deliberately.

Do not combine them by accident.

Do enough discovery before writing the offer

The studio does not need every production detail before the proposal.

It does need enough information to stop guessing about the commercial scope.

Review:

Client and decision maker
Job goal
Products or SKUs
Relevant variants
Required output groups
Likely shot rows
Setups or looks
Styling, props, talent, or location
Retouching treatment
Destinations
Review process
Delivery package
Schedule dependencies
Rights or usage topic
Client responsibilities
Known exclusions

When a fact remains unknown, label it as an assumption, allowance, option, or exclusion.

Do not hide uncertainty in a fixed total.

Put a countable scope near the beginning

The client should not need to read the whole document to discover what is included.

A countable scope can use:

Product group
Maximum or confirmed product count
Relevant variants
Required output package
Setup or look
Retouching treatment
Destination outputs
Optional items
Excluded items

Example:

Product group:
Three serum products and the current retail cartons.
Included output package:
One front, one back, and one dropper-detail file for each serum.
One collection image for the three products together.
Creative treatment:
Current account style guide, one approved tabletop setup.
Retouching:
Temporary dust and fingerprint cleanup.
Keep label text, product geometry, color, and material texture accurate.
Destination:
Client-owned product page under the current approved output specification.
Not included:
Lifestyle images, model work, packaging redesign, marketplace upload, or additional destination files.

The example is fictional.

It is not a market package or price recommendation.

Use the shot-list model without turning the proposal into a shot list

The proposal can state the included output package.

The working shot list later expands the package into one row for:

one product identifier or SKU
one relevant variant
one independently required view or asset
one delivery output

Do not paste a large production spreadsheet into the proposal unless the client needs it to understand the offer.

Reference an approved scope attachment when appropriate.

State the assumptions behind the price

An assumption describes what must remain true for the offer to apply.

Possible assumptions include:

The client provides the final product list by the stated date
Products arrive in usable condition
One named person consolidates client decisions
The current style guide remains in effect
The listed destinations remain the only required destinations
The listed products use the stated setup groups
Client-provided claims, labels, and product information are accurate
The current location or studio remains available

An assumption is not a hidden condition.

Make it visible.

When an assumption changes, use the current change process.

State exclusions directly

An exclusion identifies work that is not part of the offer.

Possible exclusions include:

Additional products or variants
Additional views or destinations
Model or talent fees
Prop sourcing
Location fees
Product shipping and return
Special handling
Packaging or label design
Copywriting
Channel upload
Raw or layered files
Long-term source-file storage
Contract or legal services

Do not rely on:

Anything not mentioned is excluded.

as the only explanation.

The client should be able to recognize the important boundaries.

State the client responsibilities

The studio's schedule and scope can depend on client actions.

Record the relevant responsibilities:

Provide product data
Provide usable samples
Provide current references
Identify decision makers
Review the proposal and agreement
Provide consolidated feedback
Approve or request changes
Pay amounts when due
Own destination upload when the studio is not responsible
Provide legal or product claims
Arrange return or disposal instructions

Do not assign a responsibility the client cannot reasonably perform.

Use a schedule with dependencies

A proposal can show:

Expected acceptance date
Product or sample arrival
Pre-production review
Capture window
Proof target
Client decision window
Final-file target

Use:

Target
Expected
Subject to
Dependent on

when the date is not fixed.

Do not guarantee a final date that depends on an unconfirmed product arrival or client decision.

The agreement should explain delay, rescheduling, and cancellation treatment.

Present the price without exposing the private model

The proposal can show:

Project fee
Unit-based fee
Setup or look fee
Time-based fee
Optional item
Client-approved expense
Tax when applicable
Payment schedule
Currency

The studio's private labor, overhead, capacity, and contribution model can remain internal.

Do not call a total `fixed` when the scope still contains unresolved quantities without a change process.

Choosing which of those items to show, and which pricing unit to build the number from in the first place, is covered in the full product photography pricing guide.

Keep optional items separate

An optional item should explain:

What it adds
Its price or pricing method
The decision deadline
The schedule effect
Whether it changes another part of the job

Examples can include:

Additional destination package
Additional setup
Additional variant coverage
Additional retouching treatment
Layered file handoff
Rush scheduling when available
Extended retention or support under the agreement

Do not make an optional item look included through visual hierarchy.

Define the review path

Record:

What the client reviews
Where comments belong
Who consolidates comments
Who can make the current decision
How a requested change is recorded
How a new requirement is handled
What proof or version is in scope

Do not prescribe a universal number of review rounds.

The agreement and studio service model control what is included.

A comment is not automatically a requested change.

A requested change is not automatically new scope.

Keep approval, payment, and release separate

The proposal can summarize the intended sequence.

Example:

The client reviews the named proof or set.
The current agreement controls approval and changes.
The current invoice schedule controls payment.
The studio releases final files under the agreed release policy.

Do not say:

Approval means paid
Payment means approved
Either action always releases the files

Route rights and usage to the client agreement

The proposal can state the intended use in plain language.

Examples:

Client-owned ecommerce product pages
Named marketplace listing
Paid social campaign
Packaging
Print catalog
Internal sales use

The counsel-reviewed agreement should define:

copyright ownership;
license;
territory;
media;
term;
exclusivity;
sublicensing;
work-made-for-hire status when applicable;
credit;
portfolio use;
transfer;
client-supplied rights.

In general United States context, the Copyright Office says the person who takes a photograph is generally the initial author and owner, except in qualifying work-made-for-hire situations.

A transfer of copyright ownership generally requires a signed writing under Title 17.

Do not turn that summary into a contract clause.

Other jurisdictions differ.

Keep cancellation, rescheduling, liability, insurance, and disputes in reviewed terms

These topics can have serious legal and financial consequences.

Do not copy a clause from this Blog article.

Use counsel-reviewed terms for:

Cancellation
Rescheduling
Kill fee or cancellation fee
Product loss or damage
Insurance
Indemnity
Liability
Force majeure
Dispute process
Governing law
Confidentiality
Data and privacy

The proposal can reference the applicable agreement.

Make acceptance and next steps explicit

The proposal should state what the client must do next.

Possible steps include:

Approve the commercial proposal
Sign the client agreement
Issue a purchase order
Pay the required amount
Provide the final product list
Ship or deliver products
Complete the operational intake
Attend the brief review

Do not use:

Reply looks good

as the entire acceptance process when the studio requires another document or payment.

Move accepted commercial scope into the working job

After the commercial relationship is accepted under the studio's process:

preserve the accepted proposal or scope record;
create the working job;
move the current products and output package into the brief and shot list;
identify assumptions that still need confirmation;
identify the client decision maker;
preserve exclusions;
record later changes separately.

Do not rewrite the job from memory.

The proposal and brief can describe different layers.

They should not contradict each other.

When they do, resolve the conflict under the current agreement before production continues.

Copyable product photography proposal structure

Use this as an editorial and commercial outline.

It is not legal boilerplate.

PRODUCT PHOTOGRAPHY PROPOSAL
Studio:
Client:
Proposal title:
Proposal version:
Proposal date:
Current acceptance or validity period:
Currency:
Prepared by:
Client decision maker:
1. UNDERSTANDING
The studio's current understanding of the client's goal:
Products or collection:
Intended destinations:
Current timing:
What success means operationally:
2. PROPOSED SCOPE
Product groups:
Confirmed or maximum product count:
Relevant variants:
Included output groups:
Likely shot-row count:
Setups or looks:
Styling, props, talent, or location:
Retouching treatment:
Destination outputs:
Delivery package:
3. OPTIONAL ITEMS
Optional item:
What it adds:
Price or pricing method:
Decision deadline:
Schedule effect:
4. ASSUMPTIONS
Product-list assumption:
Sample-arrival assumption:
Product-condition assumption:
Reference or style-guide assumption:
Decision-maker assumption:
Destination assumption:
Other:
5. EXCLUSIONS
Products or variants not included:
Outputs not included:
Production services not included:
Post-production services not included:
Destination upload not included:
Source or layered files not included:
Retention or support not included:
Other:
6. CLIENT RESPONSIBILITIES
Product information:
Products or samples:
References:
Decision makers:
Feedback:
Payment:
Destination upload:
Return or disposal instructions:
Legal or product claims:
7. SCHEDULE
Acceptance target:
Product or sample arrival:
Pre-production:
Capture:
Proof target:
Client decision target:
Final-file target:
Dependencies:
8. INVESTMENT
Pricing model:
Base price:
Included units:
Optional items:
Client-approved expenses:
Tax treatment owner:
Currency:
Payment schedule:
Price-change process:
9. REVIEW AND CHANGES
Review file or set:
Comment location:
Feedback owner:
Decision maker:
Requested-change process:
New-requirement process:
Schedule-change process:
10. DELIVERY
Final outputs:
Delivery filenames:
Manifest:
Delivery method:
Recipient:
Release policy:
Access expiry or revocation:
Retention reference:
11. RIGHTS AND AGREEMENT
Intended use summary:
Applicable client agreement:
Counsel-reviewed rights provision:
Confidentiality reference:
Cancellation and rescheduling reference:
Liability and insurance reference:
Dispute and governing-law reference:
12. NEXT STEPS
Proposal action:
Client agreement:
Purchase order:
Payment:
Product list:
Intake:
Brief review:
Studio contact:

Proposal review checklist

Before sending, confirm:

The client and decision maker are correct
The scope is countable
The output package is understandable
Assumptions are visible
Important exclusions are visible
Client responsibilities are realistic
Dates show dependencies
The price matches the current scope
Optional items look optional
The change process exists
Rights language is routed to reviewed terms
The acceptance process is explicit
The working-brief handoff is possible

What not to put in a generic Blog template

Do not provide universal clauses for:

Copyright assignment
Work made for hire
Model or property release
Indemnity
Liability cap
Cancellation fee
Kill fee
Late payment
Interest
Tax
Governing law
Dispute resolution
Confidentiality
Data processing
Insurance
Product loss or damage

Use qualified counsel.

How this fits in Lenso

Lenso can begin before or after the studio's commercial decision, depending on the entry path.

A project request can provide initial facts.

The studio still reviews the request and uses its current proposal and agreement process.

After the studio decides to proceed, Lenso can keep the working brief, products, shot rows, client review, optional invoice, and final-file handoff connected.

Lenso does not currently create proposals, contracts, legal terms, or electronic signatures.

Questions

Is a proposal the same as a contract?

Not necessarily. The result depends on the document, acceptance, law, and facts. Use counsel.

Is a proposal the same as a quote?

A proposal can include a quote or estimate. The studio should define the terms it uses.

Should the proposal contain the full shot list?

Only when needed to understand the offer. A scope summary or approved attachment can be enough.

How many revisions should the proposal include?

Use the studio's service model and counsel-reviewed agreement. There is no universal count.

Should copyright be transferred?

That is a business and legal decision. Use counsel-reviewed rights language.

Can Lenso send the proposal for signature?

Not under the current product described in this brief.