Blog

Title Icon

The Stale-Baseline Trap: Why AI-Authored Salesforce Delivery Keeps Building on a Fake Org

We recently audited an entire Salesforce delivery stream — 149 merge requests across a single client engagement, start to finish — and asked one question the usual retrospective never asks. Not what shipped, but where a later change had to revert, re-cut, or re-baseline what an earlier one got wrong. About a quarter of the merge requests were rework. And when we grouped that rework by root cause, one pattern sat underneath almost all of it, surfacing in cluster after unrelated cluster.

Title Icon

Agentic Salesforce Development for Healthcare — Building Compliant, AI-Augmented Health Orgs

For a large share of healthcare organizations, Salesforce Health Cloud has quietly become the system of record for everything that is not the EHR: care coordination, patient and member outreach, intake, eligibility, prior authorization, referrals. It is the connective tissue between clinical systems and the humans who run operations around them. And in 2026, two separate AI questions are landing on the same desk at the same time.

Title Icon

The Seven Shapes of Rework in Agentic Salesforce Work

Rework rarely announces itself. It shows up disguised as productivity — a revert here, a "fix:" follow-up there, a branch quietly closed and re-cut on a new base. Each looks like a small course correction. In aggregate, they are the single largest tax on a delivery stream, and in an agentic one — where an AI author ships fast and there is no default human reviewer standing between the model and the merge button — they compound faster than anyone expects.

Title Icon

High-Capability, Low-Control: A Maturity Model and Governance Spine for Agentic Salesforce Teams

The most dangerous Salesforce delivery team is not the one that lacks skill. It is the one that has plenty of skill and no brakes.

Title Icon

Agentic Development for Salesforce: Capability Is Cheap, Ground Truth Is Expensive

Something quietly inverted in Salesforce delivery over the last year, and most teams haven't repriced their work to match. An agent can now author a permission set, refactor an Apex batch class, write the test coverage, generate a data-migration script, and open a clean merge request — in minutes, without complaint, at a level of craft that would have been a mid-level developer's afternoon. The bottleneck everyone spent a decade optimizing — can we build it fast enough? — has largely dissolved.

Title Icon

Production Guardrails for AI Tooling — The SF CLI Example

In July 2025, an AI coding agent deleted a live production database during what was supposed to be a frozen, read-only session. The agent had been told — repeatedly, in all caps — to make no further changes.

Title Icon

The Architecture Quality Checklist for AI-Built Salesforce Orgs

Every prior generation of advice about Salesforce technical debt described the same disease: years of accreted clicks-not-code, orphaned fields, a trigger per object, and a cleanup project nobody funds. That framing is now obsolete. In an org where agents author most of the metadata, debt no longer accumulates slowly over five years of admin drift — it can accumulate in an afternoon, at production quality, with passing tests. The cleanup metaphor breaks because there is no lull in which to clean up.