Skip to content

Forecasting

A forecast with a method behind every row

A forecast should explain its source records, allocation method and exceptions. Client financial data remains private.

Published
26 August 2026
Reading time
2 min
Written by
Elliot Saha

A forecast is easier to review when every row carries the method that placed it. The design can be explained without publishing client financial data.

Preserve the source

Use stable keys to join historical and current records. Keep a reference to the source beside the derived row so authorised reviewers can trace it.

Name the allocation method

Store the method used to place each row in a period. Make date assumptions and rounding rules explicit.

Make exceptions reviewable

Route missing dates, duplicate records and ambiguous mappings to an owned review queue. Keep the supporting client records within the authorised system.

Written by

Elliot Saha

Co-founder and Chief Technology Officer

Elliot owns Salesforce platform architecture at ShareCo. He spent the last year embedded as sole architect, administrator and developer on a single enterprise org, and most of what he writes here came out of that.

Read next
  • AI architecture

    When to move AI off the Salesforce platform

    Calling a model from Apex is the right first move and the wrong last one. Three platform limits decide when the work has to leave, and one rule keeps the two paths from drifting.

    • 5 August 2026
    • 5 min read
  • Revenue operations

    Define the denominator before reporting a win rate

    Count-based and value-based measures answer different questions. Define the submitted bid, deduplicate projects and separate open work from closed outcomes.

    • 14 July 2026
    • 2 min read
Bring us the hard one

Bring us your hardest Salesforce problem

Tell us what is failing and who it affects. Start with a free fit conversation; any diagnostic or implementation work follows an agreed scope and fee.

  • Free fit conversation
  • Vancouver, British Columbia