Workbench notes for CRM systems engineering: routing, hygiene, integrations and the automations that hold a stack together.

Routing04.11.2026Olu Fadipe

Trial a PR-gated AI change tool: five checks before the first production deploy

The short version

A trial should end with three records that agree: the sandbox run, the pull request diff and the audit log. Here is what to check in each, and what to do when they disagree.

Routing12

Hygiene04

Approval gates for CRM-writing AI agents: what runs unattended and what waitsField enrichment and dedupe suggestions can run unattended. Customer-facing sends, deletes and ownership changes cannot. Here is the split, the payload shape and the retry rules.

Systems03

Salesforce Flow drift and the automation nobody remembers buildingBoth systems reported success. Only one of them wrote what it meant to. A constructed trace of Salesforce Flow drift, the reconciliation bill, and when to delete the automation.

Playbooks01

Does your Salesforce change history survive a reorganisation?When an admin leaves or a team is reorganised, the receiving role inherits the Salesforce change history only if it lives somewhere that role already has access to. Here is how to test that before the reorg.

Data pipeline security review: what to ask before a tool moves PIIA security review fails when the acceptance condition is unwritten. Six evidence items define data pipeline security for a tool that moves PII, and Extract publishes answers to most of them. Approval gates for CRM-writing AI agents: what runs unattended and what waitsField enrichment and dedupe suggestions can run unattended. Customer-facing sends, deletes and ownership changes cannot. Here is the split, the payload shape and the retry rules. The owner-assignment rule behind HubSpot lead routing trustOne owner-assignment rule decides whether reps believe the CRM. A bench note on round-robin ties, records that match nothing, and how an embedded partner audits the rule before a migration. Data pipeline observability: what a readable sync run actually showsThe table is stale and the dashboard is green. Data pipeline observability comes down to whether the failing call, its retries and the schema change can be read before the page. How do we fix lead handoff and attribution between marketing and sales? Write the contract firstBoth reports were internally consistent. The handoff failed because a rejection was written as a lifecycle edit. ELT and reverse ETL: follow one record across the vendor boundaryTwo vendors can each report success while the audience that left the warehouse was yesterday's. A trace of one record shows why ELT and reverse ETL belong on one engine. Separation of duties Salesforce teams can keep through a reorganisationWhen an AI agent drafts Salesforce changes, separation of duties lives or dies at one handoff. A worked example shows how a reorganisation quietly turns approvers into authors, and the signal that warns you first. Salesforce Flow drift and the automation nobody remembers buildingBoth systems reported success. Only one of them wrote what it meant to. A constructed trace of Salesforce Flow drift, the reconciliation bill, and when to delete the automation. Monthly active rows pricing versus a bill finance can forecastA pipeline budget handoff only works if finance can write down a worst case. Monthly active rows pricing makes that hard; published credit tiers make it a lookup. Bring your own AI Salesforce tooling: the one rule that decidesSort Salesforce change tools by one rule: who chooses the AI. The vendor pages, a constructed four-admin case of a model switch, and when a hosted agent is the easier answer. Does your Salesforce change history survive a reorganisation?When an admin leaves or a team is reorganised, the receiving role inherits the Salesforce change history only if it lives somewhere that role already has access to. Here is how to test that before the reorg.