TechniquecurrentGTM data

Agents need the business clock in the answer instead of an optional tool

Fiscal years and as-of dates belong in every response the agent reads.

SymptomAnswers about "this quarter" use calendar quarters for a company whose fiscal year starts in another month, and date windows drift from the data.

Many companies run a fiscal year that doesn't start in January, and some datasets are pinned to an as-of date rather than today. An agent doing date math from the wall clock and calendar quarters gets both wrong.

A fiscal calendar kept in free-text instructions reaches only the interface that reads them.

Agents don't reliably call an optional tool, and a separate tool helps only when the agent thinks to ask. Putting the values in tool responses, or on the records themselves, works better.

The wall clock is also the wrong anchor for an organization whose data is frozen at a past date, because windows measured from today slide past the data and recent history drops out of answers.

In a synthetic test set of 1,000 activities pinned to a past as-of date, windows anchored on today's date returned no rows for "last 90 days" or "this quarter"; windows anchored on the as-of date and the fiscal calendar returned 118 and 11. The set shows the mechanism, not how common it is.

Check your setup read-only

Find the last 5 agent answers in your transcripts that name a quarter, a week or "today". For each answer, compare the dates it used with the CRM's fiscal calendar. Read the transcript before the answer for a read of the fiscal calendar and of the data's as-of date. Any date mismatch is a gap. An answer given without reading both dates is also a gap.

Passes ifIn all 5 sampled answers the dates match the fiscal calendar, and each transcript shows both reads before the answer.

Access needed:agent-transcriptscrm-read

If it fails: changes to make later (not part of the check)
  1. 01Return timezone, as-of date and fiscal-year bounds in the tool responses the agent already reads.
  2. 02Tell agents to read those values from the tool responses before any date math.
  3. 03Anchor every relative window on the organization's as-of date, not the server clock. Relative windows include "last 30 days" and "this quarter".
  4. 04Store the fiscal calendar as structured fields, never only in free-text instructions.
Applies ifYour agents or digests answer this-quarter or last-week questions, and your CRM's fiscal year starts outside January or data is pinned to a past date.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.