Turning a client's idea into something you can quote

StoryFolder — 2026-09-02

Part of: A client sent you a reference video. Now what?

Last updated: 2 September 2026.

A client can approve a feeling in about four seconds. What they have not approved, and usually have not seen, is the set of production choices sitting inside it. Before you can put a number on the job you need those choices written down one by one, with a decision against each: keep it, adapt it, get a specialist to look at it, or drop it. The way to get there is to turn the idea into a list of specific shots, write the production question against each row, take the list back to the client, and only then move the agreed rows into whatever you actually price work in.

StoryFolder is useful for exactly one part of that. It turns the reference into numbered rows with real durations and gives you somewhere to record the decisions, so a 59-second reel becomes 52 things to be agreed rather than one thing to be argued about. It holds no rates, crew model, shoot schedule, or arithmetic connecting a field to money. The pricing happens in your sheet, the way it always did.

What must be true before a client's idea is ready to quote?

Six things, and none of them come out of the reference on their own: the outcome the client actually wants, which parts of the reference are non-negotiable, what may be substituted, the deliverables, who signs off, and every production assumption you have made that would change the number if it turned out to be wrong.

The gap between a reference and a scope is where most of the bad jobs start. On r/advertising in February 2026 somebody put it plainly: "We all have that one client. They send a Super Bowl commercial as a reference but have a budget that barely covers the catering for a real shoot." A commenter on r/cinematography a year earlier reached for the same idea with a different picture: "clients see a Ferrari and want a Ferrari on a 2nd hand Toyota Corolla budget. Unless these guys have the budget you might have to manage their expectations here."

Managing expectations is the part that gets waved at and never described. Here is a version of it that works, because it moves the conversation off the whole video and onto individual shots.

Everything in the left column is a fact you can point at. Everything in the right column is a decision, and a decision needs an owner and a date.

How do you break the idea into decisions the client can answer?

One row per shot, and four things recorded against each: what the client is responding to, what you think it would take, how confident you are in that guess, and who has to answer.

That last pair is the part people skip, and it is what stops a scope document turning into a wish list. A worked row looks like this.

Nothing in that table is computed. The shot number and the duration come out of the reference; the other four columns are you doing the job. StoryFolder's contribution is that the row exists, with the frame beside it, so "the reflection trick" has a coordinate and cannot quietly become three shots later on.

For the Decision column, use a controlled list rather than free text, because free text is how you end up with four spellings of the same status on a 52-row board. On Pro you can create a Dropdown with the four values, which can only ever hold one of its own options, and write it across a multi-selection in one go. On the free plan the Tags field that ships with every board carries the same four labels, one shot at a time. See creating your own fields and applying a value to several shots.

The Confidence column is the one that earns its keep in the meeting. A client will accept "I am not promising this until our VFX supervisor has watched it" far more easily than they will accept a price that quietly includes a contingency for it. Marking the guess as a guess is what buys you the specialist call.

How do you expose the hidden production behind a simple reference?

Interrogate every shot down the same list of departments, in the same order, until it stops producing surprises: location, talent and performance, art and wardrobe, camera and movement, lighting, sound, post and VFX, and transitions. The reason to do it as a fixed list rather than by instinct is that the expensive things hide behind the shots that look easy.

Where you land will be one of three states, and they need to stay separate:

The counter-move that turns this into a productive conversation rather than a list of refusals comes from an r/cinematography thread on 15 October 2023, where someone described how they handle a client whose references outrun their money: "show them comps you feel you can recreate on their budget and see if they bite." Their actual wording to the client is worth stealing: "Love these shots! Here are some more comps that we can achieve on your budget that capture the spirit of these exteriors in the studio, what do you think?"

That reply only works if you can be specific about which shots you are talking about. "Some of the shots" is a negotiation. "Shots 7, 14 and 22, and here is what I would do instead for each of them" is a document.

One way to front-load the whole thing came up on the same thread, where a commenter described sending "a form for someone like this to fill out. Full of questions that if they can't answer then they don't have any clue what they want," with the reasoning underneath it: "If they don't know what they are asking for it's impossible for you to deliver it." A shot-by-shot pass over their own reference is the same filter, run against something they chose themselves, which is usually a shorter argument.

How do you agree what to keep, adapt, or drop?

Present alternatives per shot, not one verdict on the whole video. A client who hears "that is out of budget" hears no. A client who hears "shots 4 through 9 are fine as they are, 14 works if we shoot it here instead, and 31 is the one we should talk about" hears a plan with one open question in it.

On an r/cinematography thread from 4 December 2021, where a client wanted the sinking scene from Get Out on a small budget, a commenter's advice covers almost every adapt: "Keep the shots tight, hide as much as possible, and simplify." Most of the time the thing the client responded to survives that intact, because what they responded to was the beat rather than the budget behind it.

Send the marked-up board and then talk over it. The published board is view-only, so the approvals come back by email or on the call rather than in the page, and you record them yourself. That is worth knowing before you promise a client they can tick boxes in the link you sent.

What goes into the quote after scope is agreed?

The agreed rows, and nothing else from here. Copy them into your own estimating sheet or production system, where rates, quantities, day counts, contingency and tax live, and price them there.

StoryFolder will tell you how many shots there are, and the average, median, longest and shortest duration. On Pro it will also chart how your marked values are distributed, so the number of shots carrying Needs specialist validation is something you read rather than something you count by hand. Those counts are the input to your estimate. They are not the estimate: nothing on the StoryFolder side knows what a crane day costs, how many days the shoot runs, or which of these shots share a setup, and there is no estimate document in the product for it to write that into.

The scope document is worth showing the client because it contains no pricing: they can argue about the work without arguing about the number, and you can change the number later without reopening the work.

When should you charge for discovery?

At the point where you are producing something they could hand to another vendor. Before that, you are qualifying the job. After that, you are doing the job.

Nobody agrees on where the line sits. On an r/Filmmakers thread from 2015, one poster described spending "an hour and a half discussing the project and starting to steer them in the right direction" and treated it as a cost of sale: "This is their freebee. I don't normally consult for free, but in order to land a gig sometimes you have to throw them a bone." Someone else on the same thread was less accommodating: "This ain't your reel, and if they wanted Spielberg they would have paid Spielberg."

Both are defensible and it is your call. The shot-by-shot breakdown does make the call easier to explain, because it is a deliverable with edges. An hour on the phone is hard to charge for. A document listing every shot in their reference, what each would take, and what you recommend instead, is not.

FAQ

What are the four useful scope statuses? Keep, Adapt, Needs specialist validation, and Out of scope. They are an editorial framework, not a StoryFolder feature; you create them as values in a field.

Can I apply one status to several shots at once? Yes, with a Dropdown on Pro, written across a multi-selection from the inspector. The shipped Tags field edits one shot at a time.

Can StoryFolder work out a price from a 52-shot reference? No. It reports the shots, their durations and the values you typed. There are no rates, no day counts and no calculation from a field to a cost anywhere in it.

Who should validate a VFX-heavy reference shot? A VFX producer or supervisor. StoryFolder stores their answer against the shot; it does not produce one.

Can the exported spreadsheet be the estimate? It can supply the rows your estimate is built from. The export contains no pricing, no formulas and no way back in.

Can the client approve shots inside the published link? No. The published board is view-only, so approvals come back through your normal channel and you record them on the board yourself.

← All articles