The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
loading…
sales, gtm & revenue framework
Estimate revenue velocity using opportunities, deal value, win rate and sales cycle.
quick answer
Sales Velocity Formula is a structured table for Sales metrics. It turns the decision into named fields, evidence, and a visible sales velocity formula worksheet / visual.
The output should make the tradeoff visible enough for someone else to inspect, challenge, and act on.
Estimate revenue velocity using opportunities, deal value, win rate and sales cycle.
Use BANT when its output is closer to the conversation you need: Qualify opportunities by budget, authority, need and timing.
worked example
A filled example is easier to understand than a blank template. Use it to see the shape before applying the framework to your own case.
A filled example so you can see the shape before applying Sales Velocity Formula to your own context.
A filled example so you can see the shape before applying Sales Velocity Formula to your own context.
generate yours
Start Ask PL with the framework, required inputs, and your context. It will ask for missing details, render the structured table, and explain what decision the output should change.
Apply Sales Velocity Formula to my situation. Context: [Decision, audience, options, evidence, and constraints.] Use the Sales Velocity Formula structure: - Columns and rows as needed: - labels: - optional notes: Ask only for missing inputs that would change the output. Then render the structured table and name the decision it should change.
how to use it
Use the framework to change a decision, not to fill a worksheet. Start narrow, add evidence, then inspect what the sales velocity formula worksheet / visual makes clearer.
Write the concrete sales metrics choice, tradeoff, or conversation the framework should change.
Fill the important slots: Columns and rows as needed, labels, optional notes.
Mark what is measured, what comes from customers, and what is still judgment.
End with the next move, the riskiest assumption, or the evidence that would change the sales velocity formula worksheet / visual.
quality check
Use this check after the artifact is filled. Blank fields are not failure; they are the next research question. Look for concrete evidence, missing constraints, and assumptions that would change the next move.
The framework needs a concrete decision. Broad intent turns it into a worksheet, not a decision aid.
Good framework output makes assumptions visible enough for someone else to challenge.
The diagram is useful only if it changes the next product conversation.
common mistakes
Do not use Sales Velocity Formula as a worksheet. Name the choice, conversation, or tradeoff the output should change.
Separate measured facts, customer evidence, and leadership judgment so weak assumptions stay visible.
If the diagram does not match the decision, switch frameworks instead of stretching the boxes.
The framework should clarify the next move. It should not replace strategy, sequencing, or judgment.
use something else when
Qualify opportunities by budget, authority, need and timing.
Qualify metrics, economic buyer, decision criteria, decision process, identify pain and champion.
Compare weighted/unweighted pipeline to quota by period.
faq
Estimate revenue velocity using opportunities, deal value, win rate and sales cycle.
Business context; objectives; available evidence; stakeholder judgment
Sales Velocity Formula worksheet / visual
Use Sales Velocity Formula when the decision matches this job: Estimate revenue velocity using opportunities, deal value, win rate and sales cycle.
Avoid it when you need BANT's output instead: Qualify opportunities by budget, authority, need and timing.
It is both: a structure for thinking and a visible structured table that makes the decision easier to inspect.
A good input names the real decision, uses concrete evidence, and separates facts from assumptions.
Use the sales velocity formula worksheet / visual to choose the next move, name the riskiest assumption, or decide what evidence would change the call.
Use BANT when the real output you need is closer to: Qualify opportunities by budget, authority, need and timing.
Yes. Describe your context and Ask PL can ask for missing inputs, render the structured table, and explain what decision it should change.