Blog

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.

Short answer: Buy an off-the-shelf agent when the job is generic and the data is standard — you'll be live in weeks. Build custom when the agent runs on your proprietary data and workflows and becomes a competitive moat. In practice, most businesses land on a managed middle path: custom where it differentiates, bought where it doesn't, with a partner running both.

We talk to a lot of leaders who have already made up their minds. AI is a fad. AI is garbage. They tried it, it underwhelmed, and they filed it next to every other overpromised technology a vendor once swore would change their business. It is a reasonable conclusion, and most of the time it is an honest report of a real experience.

It is also, almost always, a report on the wrong experiment.

An agentic operating system (agentic OS, or AOS) is the operating model a business runs on when AI agents—not just people or scripts—do the work: a coordinated layer of agents, shared context, guardrails, evaluations, and orchestration that turns one-off AI experiments into a system that ships real business outcomes on repeat.