Your RevOps team knows that a Stage 3 deal without a mutual close plan isn’t real pipeline. They know the renewal date lags a day, and that “Partner” means reseller in your org. The agent your sales team wants to use with Salesforce knows none of that. And the people who know it aren’t allowed to tell it, because changing the AI agent context in Salesforce means a developer changes a prompt, an Apex class or a Flow, behind a release process.
Today that knowledge lives in the standard places. The methodology deck. A Confluence page. A Slack thread from two years ago. The heads of the people who have been there longest. None of those is a place an agent looks, and the one place it does look, its prompt, is owned by whoever built it.
The knowledge never reaches the agent
What qualified means, how a deal review is run, which amount field finance uses, the rule that a renewal isn’t at risk until the health score has been low for two weeks. If any of that reaches an agent, it reaches it as a ticket, and it comes back six weeks later. Each agent gets its own prompt, and each one carries a slightly different reading of the same business.
What the business team should be able to change themselves
Three things, and none of them should need a developer.
What the agent is told about a record. For an opportunity, which 22 of the 212 fields it receives, in what order, what each one means and how to use it. Your RevOps lead decides that, starting from the page layout your team already uses.
The guidance every agent gets. Enablement writes the methodology once. Finance writes how revenue is recognized once. Marketing writes the voice once. Every agent working in that area gets it, and nobody answers the same question in Slack again.
The steps for a job. How a deal review is run. How a renewal is prepared. Sales ops writes it once, and every agent that does that job does it the same way.
Each team owns its own definitions. Sales owns the pipeline set, customer success owns renewals, and finance keeps its own reading of the same amount field. Change a definition and the next request uses it. No ticket, no deploy.
What security still controls
Who sees what. Every request runs as the signed-in user, and Salesforce field-level security and sharing rules apply to the query itself. Your RevOps lead can put the margin field in the opportunity definition. A rep who couldn’t see that field on the record still won’t receive it from the agent.
This is not a setting someone could get wrong. There is no screen where the author decides who sees a field. The worst thing your RevOps lead can do is write a definition nobody finds useful. They cannot expose a field to someone who couldn’t already see it, because Salesforce decides that, not the person writing the definition.
What this looks like day to day
At 2pm your RevOps lead changes what the renewal agent is told about the health score. By 2:01 every agent working on renewals reads the new instruction. Security can see the change, who made it, and what the agent now receives for any customer. If it was wrong, it is one click back. Nobody filed a ticket. Nobody got access to anything they didn’t already have.
ContextWorks is built so both sides get what they need. The business team changes what the agent is told, themselves, the day they learn something new. Security and governance keep control of who sees what, see every change as it happens, and can undo any of it in one click. You don’t have to choose between the people who know the business and the people who own the risk.
