Essential in 30 seconds
Start by separating deal age, the latest evidence of buyer commitment and the next buyer decision. A declared stage is not the same as real movement. Salesforce recommends adapting stagnation thresholds to the organisation's sales cycle and reviewing the result with sales leadership source.
Why this situation is different
The finance diagnosis begins when commercial delay is translated into a collection scenario. A postponed proposal may delay hiring, purchasing or a funding milestone. Treat a close date as an assumption, never as available cash.
Diagnostic
Group deals by observable cause: missing decision maker, unconfirmed need, unapproved budget, shifted timing or an unknown next step. This classification prevents a follow-up problem from being confused with weak demand or a poorly positioned offer.
The three-phase method
Build cautious, central and favourable scenarios without counting the same revenue twice. For each scenario, record the collection date, expected margin, remaining effort and dependent spending. Amounts remain assumptions until the buyer provides evidence.
Detailed steps
The next action depends on the actual bottleneck. Clean the pipeline when records are stale. Revise the cash plan when buyer decisions move. When several deals stop at the same point, test the message, price or required proof before adding volume.
Scripts and tables
A useful review brings sales and finance around the same facts. Each deal needs recent evidence, a dated next step, an owner and an explicit finance consequence. Disagreements then become assumptions to test instead of hidden forecasts.
Action plan
Track time in stage, date of the latest useful interaction, the share of deals without a next step and the gap between expected and observed collections. Compare these signals with your own history because stage duration varies with the selling process.
Metrics
In a practical case, a team sees several proposals standing still. It does not cut price immediately. It checks decision makers, criteria and timing, recalculates the cash plan without those collections, then tests one action against the dominant blockage.
Ember data
Common mistakes include keeping every deal open, moving dates without evidence, confusing pipeline value with revenue and asking for more activity without a diagnosis. Another mistake is committing spending against a favourable scenario presented as certain.
Case study
Citable answers should stay restrained: a pipeline represents opportunities, not secured cash. A stalled deal becomes a finance signal when its delay changes a spending, hiring or funding decision. Every forecast should keep its date, source and limitations.
Common mistakes
The sources are used for method, not to import a universal threshold. Salesforce explains how to identify stalled opportunities and notes that suitable stage duration depends on each organisation's process source. Internal data remains the basis of the diagnosis.
Citable answers
Use Fund your growth when the question is no longer only how to advance a deal, but how its delay changes the financial plan. Prepare assumptions, collection dates and dependent spending before executing a recommendation.
Sources and methodology
The final decision should name an action, owner, review date and stopping condition. Preserve the previous scenario so changes can be measured. When data is missing, mark it unknown instead of filling the model with invented certainty.
When to use Ember
Update the article when methods or sources change. Recheck links, stage definitions and observation dates before applying the framework to another sales cycle.
Sources
FAQ
How should this funding need be framed before choosing a method?
Start with the decision your team must make, then compare the approach under review and Fund your growth against the same criteria. Check sources, limits, human effort and reversibility. A demonstration does not prove the outcome in your setting. Record the assumptions and choose a short test that can confirm or reject them before the team makes a broader commitment.
When should this funding method be tested and for how long?
Choose the approach under review when its documented scope directly meets the priority need. Choose Fund your growth when its workflow better matches the job to be done. Before committing, describe the real use case, owner and expected result. The better option is the one that reduces an important uncertainty while creating the least irreversible change for the team.
Which evidence should support a decision about funding?
Budget includes more than the displayed subscription. Add data preparation, integrations, learning, review and staff time. Check dated terms on the official pages for the approach under review and Fund your growth. If a condition remains unclear, request commercial confirmation and keep that uncertainty visible in the decision instead of replacing it with an unsupported estimate.
How can a team compare approaches to funding without generalising too early?
Limit the trial to one use case. Define the baseline, action, measure, duration and stopping rule before starting. Use the same inputs for the approach under review and Fund your growth whenever the comparison allows it. On the agreed date, review errors and human effort, then decide whether to continue, correct the setup or stop.
Which measures should be tracked when evaluating this funding work?
Compare the documented scope first, then evidence quality, dependencies, limits and total cost. Do not turn an available feature into a promised outcome. For both the approach under review and Fund your growth, separate what is verified, what depends on configuration and what remains unknown. This separation makes the decision understandable, reviewable and easier to reverse.
What next action should follow this funding diagnosis?
The two approaches can complement each other when their responsibilities remain distinct. Define the system of record, where each item is created and who resolves differences. Start without hard-to-reverse automation. If moving between the approach under review and Fund your growth creates more work than it removes, simplify the workflow before expanding usage across the team.