Blog

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

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.