Understand the working context

A stage, amount and expected date can summarise a potential sale, but they need context behind them. Use the description and linked records to explain the customer’s needs. Review the opportunity after meaningful discussions so that the pipeline reflects current work rather than a collection of old estimates. Closing an opportunity should reflect what actually happened and leave enough information for the team to understand the outcome.

Put it into practice

  • Use a name that describes the potential order or engagement.
  • Keep the amount, currency and expected timing realistic.
  • Update the stage after a meaningful change in progress.
  • Link a next task with a responsible colleague.

A practical example

A renewal opportunity starts with an estimated value. After the customer confirms quantities, the salesperson updates the amount and prepares the quotation. If the customer delays the project, the expected date and next task are changed together. That gives a manager a more useful view than leaving an optimistic date untouched.

HOW THIS RELATES TO ATLAS

In the current workspace

Atlas supports opportunity records, sales stages, amounts and linked tasks. Advanced forecasting and configurable opportunity-product workflows are outside the current release.

Explore the product

Atlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.