Articles
Field notes
Deep dives, playbooks, and working notes on GTM Systems.
We Had 282 Automations and Nobody Could Say What Half of Them Did
Five years of "just add one more flow" left an org where a single lead save fired eleven automations and changing anything was russian roulette. Here is how to audit an accreted stack, find the dead weight, and consolidate it without breaking production.
Read the article →Someone Wrote 200 Lines of Apex to Copy One Field, and It Failed a Deploy Two Years Later
The declarative-first rule is not dogma; it is a bet on who can maintain the thing after you leave. Here is the rule, the specific cases that genuinely need Apex, and the honest line between them.
The Integration Dropped 1,400 Records and We Found Out Ninety Days Later
A sync silently failed on a subset of records and nobody noticed until the quarter did not add up. The fix is reconciliation built into every integration so a dropped record surfaces the same day, not next quarter. Here is the pattern and the queries.
The Quote Said $240K, the Invoice Said $261K, and Both Systems Were "Right"
Sales quoted fast and finance could not reconcile a single deal to the penny. The gap was rounding and proration living in two places that never agreed. Here is how to design CPQ so quotes stay fast and the numbers actually tie out to finance.
Forty Flows Fight on Every Save and Nobody Knows Who Wins
A lead score kept reverting to zero seconds after it was set. The cause was two record-triggered flows racing on the same save, and no document said which fired first. Here is how to map the firing order of an accreted automation stack and stop the fights.
We Built the Same Field Twice Because Nobody Drew the Object Model First
A rep found three "Contract End Date" fields on the Account and asked which one was real. None of them were. Here is why you architect the object model before you create a single custom field, and what skipping that step actually costs.