Place commercial KPIs by action horizon
Choose CRM, data platform or warehouse from latency and actionability—not from one universal source-of-truth claim.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01Context
Commercial teams need operational prompts, daily management signals and governed historical reporting from the same underlying events.
02Decision drivers
- D01
Decision latency
- D02
Definition governance
- D03
Source-data proximity
- D04
Historical reproducibility
03Options considered
CRM
Immediate record-level actions
Cost: Limited cross-system computationData platform
Near-real-time multi-source signals
Cost: Operational dependencyWarehouse
Governed history and complex analysis
Cost: Higher latency04Decision
Use a tiered model: compute interaction-local signals in CRM, near-real-time prioritization in the data platform, and certified historical measures in the warehouse. Publish definitions through one semantic contract.
05Consequences
- A metric name cannot silently represent different time windows.
- CRM receives decisions and explanations rather than raw analytical complexity.
- Finance-grade reconstruction remains in the warehouse.
06Revisit when
The organization has a single operational store with sufficient controls.
Latency expectations or ownership of semantic definitions materially change.
07Where this decision is applied
Cases that take this decision, and why it matters there.
- Process case / 03Designing a commercial performance recovery processTurning an underperformance signal into an owner, a plan, a review cadence and a recorded outcome.
- Systems case / 04Designing one CRM for multiple commercial motionsA shared opportunity core with motion-specific stages and extensions—so each motion runs its own way while forecasts and reports stay comparable.
- Data case / 02Turning ERP transactions and targets into commercial intelligenceConforming orders, invoices, targets and accounts at a declared grain in the data platform—so one metric definition serves every team, and its result lands in the CRM as a governed signal.
- Data case / 03Writing analytical signals back into operational CRMA writeback contract for derived KPIs and segments: account grain, read-only in the CRM, stamped with freshness and version, reconciled against what was published—and turned into exactly one task per signal.
- Data case / 05Evolving commercial analytics from single-currency to multi-currencyKeeping the original amount as the fact and the reporting amount as a versioned, derived view—with a declared rate policy for actuals, targets and thresholds, and V1 history migrated without restatement.
- RevOps case / 04Designing a target model with explicit period semanticsTargets as governed data—grain, phasing, version, precedence, owner and freeze point—so year-to-date performance means the same thing in every report and every month.
- RevOps case / 05Designing forecast governance and pipeline coverage that trigger actionForecast categories from stage semantics, overrides recorded at the forecast level, one owner of the final number, weekly snapshots—and a coverage contract whose threshold starts pipeline generation.
- RevOps case / 06Running commercial management cadence from the CRMFour forums—daily, weekly, monthly, quarterly—each with participants, evidence, decisions and outputs defined, run from system views instead of exported spreadsheets, and measured by adoption signals that show whether the routine is real.
- AI case / 02Preparing account context before a commercial visitAn agent assembles account, pipeline, order, performance and visit history into a briefing that separates fact from inference, cites every statement and writes nothing back.
- AI case / 04AI-assisted account review with evidenceAn agent prepares each account for the monthly performance review—target, actuals, pipeline, activity, segment, recovery plan and changes since last time—as a cited summary with anomalies and questions. The manager decides.