Gorilla Dash

Help Centre

Guides for every part of Gorilla Dash

Step-by-step how-to guides written by the team that builds the product. Read them here, or download any guide as a PDF.

CRM Pipeline

Expected close dates and your pipeline months

Download PDF

What the close date drives, why a deal can land in a month you did not expect, and how your tribe's timezone comes into it.

Last updated September 2, 2026


The expected close date is what puts a deal in a month. It drives the closing-soon list, the pipeline by period, and every forecast anyone builds from them.

Keeping it honest

  • Put in when the customer will decide, not when you would like them to.
  • When a date passes, move it and say why in a note — a pipeline full of last month's dates is the clearest sign nobody is maintaining it.
  • A deal with no close date sits outside every period report. It is in the pipeline but not in any month.

Month boundaries and timezones

Periods are worked out in your tribe's own timezone, so a deal dated the last day of the month belongs to that month for the tribe that owns it — not to whichever month it happens to be at head office.

CHECK THE TRIBE TIMEZONE ONCE
A tribe whose timezone was never set can have its month-end deals fall on the wrong side of the boundary, which is maddening to debug at quarter end. It is a one-off setting on the tribe and worth confirming before your first quarter.

Closing a deal

When a deal is won or lost it also gets a closed date — when it actually finished, as opposed to when you thought it would. The gap between the two, across many deals, is the honest measure of how well your team forecasts.

Next · CRM PipelineWinning and losing an opportunity