Video tooling is an annual planning cycle software purchase
Quick answer
An annual planning cycle software purchase is one that has to be written into an operating plan before budget exists for it. Enterprise video tooling works this way, so the real evaluation window opens months before a line item appears and closes when the plan locks.
What makes video an annual planning cycle software purchase?
Video sits with the teams whose entire year is written down in advance. A creative services lead at a global advertising platform described where she was in that process:
We're kind of in this operating plan process right now. I don't know if you know the whole scope of things. We just plan and write docs and do all these things, and then we circle back and do it again. So we have op one planning, which is right now. The TLDR here is that I don't have a lot of definitive answers for you because we're still trying to suss that out ourselves.
She is not stalling and she is not unqualified. She has the pain, she owns the function, and she genuinely does not know yet what next year looks like, because the document that decides it is still being written by her and everyone around her.
A month later that same person may have a number, an owner and a named initiative. The plan changed. The pain was there the whole time.
Why does the evaluation window open before budget exists?
Because a line item has to be argued for before it can be approved. Nobody gets money for video tooling and then goes looking for a vendor. Somebody writes a paragraph in a planning doc about video volume and creative capacity, that paragraph survives a review, and the money follows the paragraph.
Which puts the real decision point months earlier. By the time a request for pricing arrives, the shape of the purchase was set in a document you never saw. The teams that get written into the doc are the ones who were useful while it was being drafted.
What does a creative leader need during planning season?
Ammunition for the document, and nothing that requires a decision. During op one planning the ask is not budget approval. It is help making a case that a function is under water and there is a known way out.
- Numbers they can paste into a plan doc. Six hours per video by hand against thirty to forty five minutes in a template, at 93% lower cost per video, and about 30% of creative time going to tedious tasks.
- Language for the initiative itself, in the words their finance partner already uses.
- A rough volume estimate, so the paragraph has a size attached and survives the first round of edits. The product demo and explainer templates are a reasonable place to start counting.
- Something they can forward without your logo on every page.
What they do not need in that window is a proposal, a security questionnaire or a deadline. Those are evaluation artifacts, and evaluation has not started. Sending them early reads as pressure.
What should you ask for at each stage of the planning cycle?
Match the ask to what the buyer is physically doing that month. The common mistake is asking for a next step from a different stage.
| Stage | What the buyer is doing | What to ask for |
|---|---|---|
| Plan drafting | Writing docs, arguing for headcount and tooling, no numbers of their own yet | Twenty minutes to hear how the function is scoped, and permission to send benchmarks they can paste in |
| Plan review | Defending the paragraph to finance and to a skip level leader | A one page scope with volume, owner and a before number |
| Budget lands | Turning an approved line into an actual purchase | A pilot scoped on the volume of real work due that quarter |
| Plan locked | Executing what was written, with no room for new line items | The date the next cycle opens, and a standing check in before it |
Here is what that looks like end to end. A creative services lead tells you in op one planning that she has no definitive answers. You send three benchmarks and a paragraph she can lift, then go quiet for six weeks. During plan review she comes back asking what a rollout costs for two hundred people, because her paragraph survived and now needs a number. A walkthrough of the templates at that point gives her something concrete to describe, and why IT ends up owning the video timeline tells her what to plan for beyond licenses. When the budget lands, the pilot she asks for is already sized to the work she wrote down. If you had pushed for a signature during the first conversation, the paragraph would have been written about something else.
FAQ
When do enterprise companies buy software?
Most large purchases land inside an annual or semi annual operating plan, which means the decision is shaped months before budget exists and cannot easily be added once the plan locks.
What is an operating plan cycle?
A recurring process where teams write documents proposing what they will do and what it costs, then revise them through review rounds until leadership approves the plan and the budget follows.
How do you sell software during budget planning season?
Give the buyer material for their planning document rather than a proposal. Benchmarks, volume estimates and plain language they can paste in do more than pricing at that stage.
What should you send a buyer who has no budget yet?
Numbers and language for their plan doc, sized to their function. A one page scope with volume and owner is useful. A quote with an expiry date creates pressure they cannot act on yet.