Workshop notes / 01

Compare the assumptions behind your next revenue forecast.

For IT service providers, a signed opportunity is only part of the story. Use these notes to examine how a CRM could connect pipeline expectations with the realities of client onboarding.

Explore CRM workflows

Inside the guideStages, start dates, ownership and forecast views

Margin note / 01A close date is not a service start date.

Illustrative example / handoff map

From a promise to a plan

Sales viewExpected close and scope

Delivery viewReadiness and start date

Question to carry forward

Which date is your forecast actually using?

01 / Follow the handoff

Trace one opportunity, not just its total.

A forecast is built from individual decisions. Follow a potential client across these three moments to see where assumptions can drift.

Shape the opportunity

Record the expected service scope, estimated value and likely close date. Note whether the amount is recurring service revenue or a one-time project estimate.

Test the transition

Before a deal moves to committed, ask who owns onboarding and whether the proposed service start date is realistic. Keep uncertainty visible rather than treating a sales date as delivery readiness.

Review the forecast

Compare the original assumptions with the current stage, amount and start date. Discuss changes in the next forecast review and identify who should update the record.

02 / Set the table

Give each assumption an owner.

Use these roles as a starting point. In a smaller provider, one person may wear more than one hat.

Commercial

Sales lead

Explain why an opportunity is in its current stage, what is included in the value and what still needs a client decision.

Operational

Delivery lead

Review the proposed start date and onboarding dependencies. Flag capacity or scope questions before they become forecast assumptions.

Financial

Forecast owner

Agree on which amounts and dates belong in the projection, then ask for a consistent explanation when those inputs change.

03 / CRM evaluation

Choose views that answer a management question.

When evaluating CRM software, bring a real handoff example. Ask to see how each view is built and which underlying records it uses.

What is likely to close, and on what basis?

Explore a pipeline view grouped by stage and expected close period. Ask whether stage definitions and probability assumptions can be inspected, and whether the view can separate a large uncertain deal from several smaller opportunities.

When might service revenue begin?

Look for a way to compare expected close dates with planned service start dates. Discuss how recurring service estimates and one-time project amounts would be distinguished before they enter a projection.

What changed since the last review?

Ask how a team could identify movements in value, timing or stage and trace them to the relevant opportunity. A useful review starts with the reason for a change, not just a different total.

Where is the handoff incomplete?

Explore whether a view can surface opportunities without an onboarding owner, a proposed start date or an agreed scope. Check who can update those details and how sales and delivery would use the same information.

04 / Try this together

A short forecast review exercise.

Bring one opportunity that is approaching a client handoff. The aim is to expose assumptions your team can discuss, not to produce a perfect prediction.

Write down the current story. List the expected close date, proposed service start date, estimated amount and what the amount covers.
Compare perspectives. Ask sales and delivery which details are confirmed, which are estimates and what could change the start date.
Revisit the projection. Discuss how a later start or a different scope would affect the forecast. Identify the record and owner responsible for each update.
Take the questions to your CRM evaluation. Request a walkthrough using similar data. Check whether the views make missing information and changed assumptions easy to investigate.

Leave with a shared definition of what “ready to forecast” means for your team.