<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Juan Manuel Garrido</title>
    <description>The latest articles on DEV Community by Juan Manuel Garrido (@juanma_garrido_1974).</description>
    <link>https://dev.to/juanma_garrido_1974</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209026%2F5152cf80-fda7-41ef-826d-434dc8f66d2b.png</url>
      <title>DEV Community: Juan Manuel Garrido</title>
      <link>https://dev.to/juanma_garrido_1974</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/juanma_garrido_1974"/>
    <language>en</language>
    <item>
      <title>When a Salesforce recommendation keeps getting ignored, write the risk down and set a limit</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Mon, 16 Nov 2026 15:28:59 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/when-a-salesforce-recommendation-keeps-getting-ignored-write-the-risk-down-and-set-a-limit-3oke</link>
      <guid>https://dev.to/juanma_garrido_1974/when-a-salesforce-recommendation-keeps-getting-ignored-write-the-risk-down-and-set-a-limit-3oke</guid>
      <description>&lt;p&gt;I wrote today, in Spanish, that it took me more than 30 years to understand that not every table deserves you sitting at it. In a Salesforce org, that idea becomes very practical: your judgment is part of the decision, or you are only there to implement what was already decided.&lt;/p&gt;

&lt;p&gt;This is not a guide to quitting. It is a way to stop explaining the same risk for months, with nothing written down, until you get tired of talking to a wall.&lt;/p&gt;

&lt;p&gt;The Spanish original is here: &lt;a href="https://discover.egafutura.com/no-todas-las-mesas-merecen-que-te-sientes/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;https://discover.egafutura.com/no-todas-las-mesas-merecen-que-te-sientes/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Write the risk where the decision lives
&lt;/h2&gt;

&lt;p&gt;If a validation rule, a Flow or a status change is going to break a process, do not leave the warning in a chat thread. Put it on the record: a comment on the work item, the description of the Flow, or the approval task. Two sentences are enough: what can go wrong, on which object, and what you would test before going live.&lt;/p&gt;

&lt;p&gt;That does not guarantee anyone will listen. It does mean the conversation cannot later restart as if nobody had flagged it. If the same warning came up in three meetings, it belongs on the object or the work item, not only in the memory of the person who raised it.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Record who decided, and what they chose instead
&lt;/h2&gt;

&lt;p&gt;When the recommendation is discarded, write down the decision: who made it, on which date, and which alternative was chosen. In Salesforce that can live in a work-item comment, an approval field, or a short knowledge article tied to the process.&lt;/p&gt;

&lt;p&gt;The point is not to be proven right later. The point is that the team can review the judgment, not only the outcome. If that Flow later fails in production, it will matter that the discarded alternative, and the reason it was discarded, were written down.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Set a personal limit before you keep pushing
&lt;/h2&gt;

&lt;p&gt;The hard part, and the one that took me the longest to learn, is this: not every table deserves another month of your time. If you have documented the risk, explained it, and the answer stays the same, ask whether that table wants your judgment or only your execution.&lt;/p&gt;

&lt;p&gt;Yesterday I published a practical checklist for &lt;a href="https://dev.to/juanma_garrido_1974/review-an-ai-generated-salesforce-change-list-what-else-runs-on-the-same-object-4ejb"&gt;reviewing an AI-generated Salesforce change by listing what else already runs on the same object&lt;/a&gt;. Today's point is the human side of that same craft: knowing when to stop proving your value to people who have no interest in recognizing it.&lt;/p&gt;

</description>
      <category>salesforce</category>
      <category>documentation</category>
      <category>career</category>
      <category>leadership</category>
    </item>
    <item>
      <title>Review an AI-generated Salesforce change: list what else runs on the same object</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Mon, 16 Nov 2026 15:20:33 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/review-an-ai-generated-salesforce-change-list-what-else-runs-on-the-same-object-4ejb</link>
      <guid>https://dev.to/juanma_garrido_1974/review-an-ai-generated-salesforce-change-list-what-else-runs-on-the-same-object-4ejb</guid>
      <description>&lt;p&gt;An AI model can draft a Flow, an Apex class or a validation rule in minutes. In a Salesforce org, that draft still has to live next to everything that already runs on the same object. Today I wrote on LinkedIn that experienced developers, in the teams I have worked with, often solved in 20 minutes a problem that took other people two days. Not because they typed faster. Because they already knew where to look, what to ask, and when to distrust a solution that looked clean.&lt;/p&gt;

&lt;p&gt;This post is a practical way to do the "where to look" part before you ship an AI-generated change. It is not a substitute for a senior review. It is a way to arrive at that review with a list, not with a feeling.&lt;/p&gt;

&lt;p&gt;The Spanish original is here: &lt;a href="https://discover.egafutura.com/la-ia-y-el-developer-con-25-anos-de-experiencia/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;https://discover.egafutura.com/la-ia-y-el-developer-con-25-anos-de-experiencia/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Export the automation that already touches the object
&lt;/h2&gt;

&lt;p&gt;Active flows, with regular SOQL:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sf data query --result-format csv \
  --query &lt;span class="s2"&gt;"SELECT ApiName, Label, ProcessType, Description, LastModifiedBy.Name, LastModifiedDate FROM FlowDefinitionView WHERE IsActive = true"&lt;/span&gt; \
  &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; flows.csv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Active validation rules, with the Tooling API:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sf data query --use-tooling-api --result-format csv \
  --query &lt;span class="s2"&gt;"SELECT EntityDefinition.QualifiedApiName, ValidationName, Active, Description, ErrorMessage, LastModifiedBy.Name FROM ValidationRule WHERE Active = true"&lt;/span&gt; \
  &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; rules.csv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Triggers (Tooling API):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sf data query --use-tooling-api --result-format csv \
  --query &lt;span class="s2"&gt;"SELECT Name, TableEnumOrId, Status, LastModifiedBy.Name FROM ApexTrigger WHERE Status = 'Active'"&lt;/span&gt; \
  &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; triggers.csv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;TableEnumOrId&lt;/code&gt; is the object for a trigger. For flows, the object is not always a dedicated field in &lt;code&gt;FlowDefinitionView&lt;/code&gt;, so you will also scan &lt;code&gt;ApiName&lt;/code&gt;, &lt;code&gt;Label&lt;/code&gt; and &lt;code&gt;Description&lt;/code&gt;. That is imperfect, and it is still better than opening every flow by hand in a large org.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Build a short list in pandas
&lt;/h2&gt;

&lt;p&gt;Say the AI change touches &lt;code&gt;Opportunity&lt;/code&gt;. A few lines of pandas give you a review agenda:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;pandas&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;

&lt;span class="n"&gt;obj&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"Opportunity"&lt;/span&gt;
&lt;span class="n"&gt;flows&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_csv&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"flows.csv"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;rules&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_csv&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"rules.csv"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;triggers&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_csv&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"triggers.csv"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;mask&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;
    &lt;span class="n"&gt;flows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"ApiName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;contains&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;case&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;na&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="n"&gt;flows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Label"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;contains&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;case&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;na&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="n"&gt;flows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Description"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;contains&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="k"&gt;case&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;na&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;flow_hits&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;flows&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;loc&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;mask&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"ApiName"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"Label"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"ProcessType"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"LastModifiedBy.Name"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="n"&gt;rule_hits&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"EntityDefinition.QualifiedApiName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"ValidationName"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"Description"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"ErrorMessage"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"LastModifiedBy.Name"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="n"&gt;trig_hits&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;triggers&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;triggers&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"TableEnumOrId"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="n"&gt;obj&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Name"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"LastModifiedBy.Name"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Flows that may run:"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;flow_hits&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Active validation rules:"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;rule_hits&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"Active triggers:"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;trig_hits&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Paste those three tables into the ticket. The question for the reviewer is no longer "does this Flow work?". It is "what else will run when this record is saved?". A clean-looking change can collide with an old rule, loop with another flow, or overwrite a field that a batch still expects to find empty.&lt;/p&gt;

&lt;p&gt;Managed package automation will also appear in some of these queries. If you only want what your team owns, filter out rows whose name or namespace you do not maintain. Keep the managed ones in a second list: you cannot edit them, but they can still fire after your change and surprise you.&lt;/p&gt;

&lt;p&gt;Write the three tables into the ticket as CSV or as a pasted Markdown table. The next person who reviews the change should not have to run the queries again to see what you already saw.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Add the cases a model usually skips
&lt;/h2&gt;

&lt;p&gt;I still want three tests next to that list, even if this post is about queries:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A record that must be blocked, with a clear error message.&lt;/li&gt;
&lt;li&gt;A record that must go through, even if a field arrives later than the happy path assumes.&lt;/li&gt;
&lt;li&gt;The same change run by a user who is not a System Administrator, so sharing and field-level security show up.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If the change touches a discount, an approval or a status, include the case where the usual approver is away. A process that only works in a demo with an admin will not survive a normal week.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. When to slow down
&lt;/h2&gt;

&lt;p&gt;None of this proves the change is wrong. It does justify waiting a day when:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The new Flow or class has no description, or the description repeats the API name.&lt;/li&gt;
&lt;li&gt;The tests assert coverage, not the business rule (for example, that a discount over a cap is not saved).&lt;/li&gt;
&lt;li&gt;The model invented a field or object for a value that already exists.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The model accelerates the draft. The list tells you where to look. Someone with experience still decides when that draft is not ready.&lt;/p&gt;

&lt;p&gt;If your sales, stock and billing numbers have to come from the same place, that is what a &lt;a href="https://www.egafutura.com/erp/erp-para-salesforce" rel="noopener noreferrer"&gt;native ERP on Salesforce&lt;/a&gt; is for. I also publish a longer Spanish version of the experience argument on &lt;a href="https://discover.egafutura.com/la-ia-y-el-developer-con-25-anos-de-experiencia/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;EGA Futura Discover&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>salesforce</category>
      <category>python</category>
      <category>salesforceflow</category>
      <category>ai</category>
    </item>
    <item>
      <title>Find the Salesforce fields, flows and validation rules only your senior can explain</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Sat, 14 Nov 2026 18:28:04 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/find-the-salesforce-fields-flows-and-validation-rules-only-your-senior-can-explain-1ngg</link>
      <guid>https://dev.to/juanma_garrido_1974/find-the-salesforce-fields-flows-and-validation-rules-only-your-senior-can-explain-1ngg</guid>
      <description>&lt;p&gt;Today I wrote on LinkedIn about something you never forget in your career: the person who knew far more than you and, instead of making you feel it, sat down to teach you.&lt;/p&gt;

&lt;p&gt;Good seniors do that. But in a Salesforce org, a lot of what they teach is never written anywhere. Why does this field exist? Who asked for this flow? What is this validation rule protecting? The answer lives in one or two heads, and the new admin depends on those people having time to explain.&lt;/p&gt;

&lt;p&gt;This post shows a quick way to find those gaps with three Tooling API and SOQL queries and a few lines of pandas. The output is a list of components without a description, grouped by the person who last touched them. That list is a good agenda for a senior and a new admin to sit down together.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Custom fields without description or help text
&lt;/h2&gt;

&lt;p&gt;Run it with the Salesforce CLI against the Tooling API:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sf data query --use-tooling-api --result-format csv \
  --query &lt;span class="s2"&gt;"SELECT EntityDefinition.QualifiedApiName, DeveloperName, Description, InlineHelpText, LastModifiedDate, LastModifiedById FROM CustomField WHERE NamespacePrefix = null"&lt;/span&gt; \
  &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; fields.csv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;NamespacePrefix = null&lt;/code&gt; leaves out fields that come from managed packages, which you do not own. &lt;code&gt;Description&lt;/code&gt; is for admins. &lt;code&gt;InlineHelpText&lt;/code&gt; is what users see next to the field. Both empty usually means the meaning of the field lives in someone's memory.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Active flows without description
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;FlowDefinitionView&lt;/code&gt; is queryable with regular SOQL:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sf data query --result-format csv \
  --query &lt;span class="s2"&gt;"SELECT ApiName, Label, Description, ProcessType, LastModifiedBy, LastModifiedDate FROM FlowDefinitionView WHERE IsActive = true"&lt;/span&gt; \
  &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; flows.csv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A flow nobody can explain is the riskiest item on this list, because it runs on its own.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Active validation rules without description
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;sf data query --use-tooling-api --result-format csv \
  --query &lt;span class="s2"&gt;"SELECT EntityDefinition.QualifiedApiName, ValidationName, Description, ErrorMessage, LastModifiedDate, LastModifiedById FROM ValidationRule WHERE Active = true AND NamespacePrefix = null"&lt;/span&gt; \
  &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; rules.csv

sf data query --result-format csv \
  --query &lt;span class="s2"&gt;"SELECT Id, Name, IsActive FROM User WHERE UserType = 'Standard'"&lt;/span&gt; \
  &lt;span class="o"&gt;&amp;gt;&lt;/span&gt; users.csv
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Read the &lt;code&gt;ErrorMessage&lt;/code&gt; column too. A message like "Invalid value" with no description behind it is what makes a new user stop asking and go back to a spreadsheet.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Build the list
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;pandas&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;

&lt;span class="n"&gt;users&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_csv&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"users.csv"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;users&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Id15"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;users&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Id"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;15&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="n"&gt;names&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kt"&gt;dict&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;zip&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;users&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Id15"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;users&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Name"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;active&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kt"&gt;dict&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nb"&gt;zip&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;users&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Id15"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;users&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"IsActive"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;blank&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;isna&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;|&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;astype&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;strip&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="s2"&gt;""&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;fields&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_csv&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"fields.csv"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;fields&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;fields&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nf"&gt;blank&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;fields&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Description"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&lt;/span&gt; &lt;span class="nf"&gt;blank&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;fields&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"InlineHelpText"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="n"&gt;fields&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"component"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"field "&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;fields&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"EntityDefinition.QualifiedApiName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="s2"&gt;"."&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;fields&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"DeveloperName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="n"&gt;rules&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_csv&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"rules.csv"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;rules&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nf"&gt;blank&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Description"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"component"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s2"&gt;"rule "&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"EntityDefinition.QualifiedApiName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="s2"&gt;"."&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"ValidationName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="n"&gt;out&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;df&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;fields&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;rules&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="n"&gt;ids&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;df&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"LastModifiedById"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;astype&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="kt"&gt;str&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;15&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="n"&gt;out&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;DataFrame&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="s2"&gt;"component"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;df&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"component"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"ask"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;ids&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nb"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;names&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"still_active"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;ids&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nb"&gt;map&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;active&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"last_change"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;df&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"LastModifiedDate"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;flows&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_csv&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"flows.csv"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;flows&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;flows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="nf"&gt;blank&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;flows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"Description"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="n"&gt;out&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;DataFrame&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="s2"&gt;"component"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"flow "&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;flows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"ApiName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"ask"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;flows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"LastModifiedBy"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"still_active"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;None&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="s2"&gt;"last_change"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;flows&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"LastModifiedDate"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;gaps&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;concat&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;out&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sort_values&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"ask"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"last_change"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;gaps&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;to_csv&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"knowledge_gaps.csv"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;index&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;gaps&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;groupby&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"ask"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;dropna&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;size&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sort_values&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ascending&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The CSV headers can vary slightly between CLI versions, so check the column names in your files first. The last line tells you who carries most of the undocumented configuration.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. What to do with the list
&lt;/h2&gt;

&lt;p&gt;Do not turn it into a cleanup sprint for one person. Turn it into pairing sessions:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;What you see&lt;/th&gt;
&lt;th&gt;What to do&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;One name owns most of the gaps&lt;/td&gt;
&lt;td&gt;Book a recurring slot with that person and a newer admin&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Last modifier is an inactive user&lt;/td&gt;
&lt;td&gt;The explanation may have left with them; ask whoever uses the component today&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Flow without description&lt;/td&gt;
&lt;td&gt;Start here: it runs without anyone watching&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rule with a vague error message&lt;/td&gt;
&lt;td&gt;Rewrite the message with the user who keeps hitting it&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;In each session the senior explains, and the newer admin writes the description and the help text. The senior teaches, the junior learns the org, and what was said stays in the org for the next person.&lt;/p&gt;

&lt;p&gt;If your ERP is native to the same org, as with &lt;a href="https://www.egafutura.com/erp/erp-para-salesforce" rel="noopener noreferrer"&gt;EGA Futura ERP&lt;/a&gt;, the same queries cover its custom fields, flows and rules, because it all lives in one metadata model.&lt;/p&gt;

&lt;p&gt;I wrote the human side of this, in Spanish, as &lt;a href="https://discover.egafutura.com/senior-que-se-sento-a-ensenarte-generosidad-para-ensenar/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;why you never forget the senior who sat down to teach you&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Juan Manuel Garrido, founder of EGA Futura.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>salesforce</category>
      <category>python</category>
      <category>documentation</category>
      <category>career</category>
    </item>
    <item>
      <title>Before an AI agent automates your sales process, mine how it really runs: Salesforce OpportunityHistory and pandas</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Fri, 13 Nov 2026 18:40:22 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/before-an-ai-agent-automates-your-sales-process-mine-how-it-really-runs-salesforce-18lm</link>
      <guid>https://dev.to/juanma_garrido_1974/before-an-ai-agent-automates-your-sales-process-mine-how-it-really-runs-salesforce-18lm</guid>
      <description>&lt;p&gt;Every few years a new technology arrives promising to fix how companies work: ERP, then CRM, then the cloud, now AI agents. And in many mid-sized companies the same things keep happening. A manager asks for the numbers in Excel because he does not trust the system. Sales reps keep their own notes. Three reports give three totals. An approval that was supposedly automated ends up in a WhatsApp message.&lt;/p&gt;

&lt;p&gt;An AI agent follows the process you give it. The risk is that you give it the documented process, while the company runs a different one. This post shows a cheap way to see the process as it actually runs, using data Salesforce already keeps, before you automate anything.&lt;/p&gt;

&lt;h2&gt;
  
  
  The data you already have
&lt;/h2&gt;

&lt;p&gt;For opportunities, Salesforce writes a row to &lt;code&gt;OpportunityHistory&lt;/code&gt; every time the stage, amount or close date changes. No setup needed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="nc"&gt;OpportunityId&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;StageName&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;Amount&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;CloseDate&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;CreatedDate&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;CreatedById&lt;/span&gt;
&lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="nc"&gt;OpportunityHistory&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="nc"&gt;CreatedDate&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="no"&gt;LAST_N_DAYS&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="mi"&gt;180&lt;/span&gt;
&lt;span class="k"&gt;ORDER&lt;/span&gt; &lt;span class="k"&gt;BY&lt;/span&gt; &lt;span class="nc"&gt;OpportunityId&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nc"&gt;CreatedDate&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Export it to CSV (Data Loader, a report or the CLI). That is an event log: case id, activity, timestamp, resource. It is the minimum input for basic process mining.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: build the variants
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;pandas&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;

&lt;span class="n"&gt;log&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_csv&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"opportunity_history.csv"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;parse_dates&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"CreatedDate"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;log&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sort_values&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"OpportunityId"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"CreatedDate"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="c1"&gt;# keep only real stage changes (amount or date edits also create rows)&lt;/span&gt;
&lt;span class="n"&gt;prev&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;groupby&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"OpportunityId"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"StageName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;shift&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;log&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"StageName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="n"&gt;prev&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="n"&gt;variants&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;groupby&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"OpportunityId"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"StageName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;agg&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;" &amp;gt; "&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;join&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;variants&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;value_counts&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;head&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The documented process is usually one line. The output is usually many. Look at the top ten and ask which one the AI agent would be told to follow.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: find rework and skipped steps
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;paths&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;groupby&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"OpportunityId"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"StageName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;apply&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;list&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="n"&gt;went_back&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;paths&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;apply&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;lambda&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;!=&lt;/span&gt; &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;set&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;jumped&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;paths&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;apply&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;lambda&lt;/span&gt; &lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="nb"&gt;len&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;s&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;=&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;

&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"went back to an earlier stage: {went_back.mean():.0%}"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"two steps or fewer from creation to last stage: {jumped.mean():.0%}"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;An opportunity that goes from the first stage straight to Closed Won was probably worked somewhere else and updated at the end. That is the CRM nobody fills in, measured.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: find where work waits
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"next_stage"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;groupby&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"OpportunityId"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"StageName"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;shift&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"next_at"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;groupby&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"OpportunityId"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"CreatedDate"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;shift&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"wait_days"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"next_at"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"CreatedDate"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;dt&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;total_seconds&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;86400&lt;/span&gt;

&lt;span class="n"&gt;waits&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;dropna&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;subset&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"next_stage"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
            &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;groupby&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"StageName"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"next_stage"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"wait_days"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
            &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;agg&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"count"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"median"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
            &lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sort_values&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"median"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;ascending&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;waits&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;head&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Long waits between two stages are often a handoff between areas, or an approval that happens outside the system.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: find who moves the work
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;movers&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;log&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;groupby&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"CreatedById"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;size&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sort_values&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ascending&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;movers&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;head&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If one or two users move most of the stages for a team of reps, someone is collecting updates from a spreadsheet or a chat and typing them in. Ask them how the information reaches them.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to do with this before the agent
&lt;/h2&gt;

&lt;p&gt;The numbers do not tell you why. They tell you who to talk to and which questions are still open in the organization:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Signal&lt;/th&gt;
&lt;th&gt;Open question&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Many variants for the same sale&lt;/td&gt;
&lt;td&gt;Which process is the real one, and who decides that?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Skipped stages&lt;/td&gt;
&lt;td&gt;What does the rep get back for updating the CRM?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Long waits between stages&lt;/td&gt;
&lt;td&gt;Which area owns that handoff?&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;One person moving everyone's records&lt;/td&gt;
&lt;td&gt;Where does the information actually live?&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;If you automate before answering these, the agent will do the same things faster, including the wrong ones.&lt;/p&gt;

&lt;p&gt;When the ERP is native to the same Salesforce org, as with &lt;a href="https://www.egafutura.com/erp/erp-para-salesforce" rel="noopener noreferrer"&gt;EGA Futura ERP&lt;/a&gt;, the same approach extends to orders, invoices and payments, because the history lives in one database. That makes the log longer. It does not answer the questions for you.&lt;/p&gt;

&lt;p&gt;I wrote the business side of this, in Spanish, as &lt;a href="https://discover.egafutura.com/por-que-seguimos-pidiendo-los-numeros-en-excel-cuatro-problemas-que-no-arregla-el-software/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;why we still ask for the numbers in Excel with CRM, ERP and AI&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Juan Manuel Garrido, founder of EGA Futura.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>salesforce</category>
      <category>python</category>
      <category>ai</category>
      <category>datascience</category>
    </item>
    <item>
      <title>Reverse-engineer the shadow spreadsheet: turn the Excel your team still uses after go-live into a backlog</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Fri, 13 Nov 2026 18:40:19 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/reverse-engineer-the-shadow-spreadsheet-turn-the-excel-your-team-still-uses-after-go-live-into-a-2m1h</link>
      <guid>https://dev.to/juanma_garrido_1974/reverse-engineer-the-shadow-spreadsheet-turn-the-excel-your-team-still-uses-after-go-live-into-a-2m1h</guid>
      <description>&lt;p&gt;The implementation is done. The consultants closed the project. On Monday, a sales rep opens the same spreadsheet they used before.&lt;/p&gt;

&lt;p&gt;The usual reaction is to ban the spreadsheet. A more useful one is to treat it as the most honest requirements document you have. Somebody keeps maintaining that file because it solves a problem the new CRM or ERP does not. This post shows a small, repeatable way to read it.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: get a copy and profile it
&lt;/h2&gt;

&lt;p&gt;Ask for the actual file, not a description of it. Then look at what is really in it. A few lines of pandas are enough:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="n"&gt;pandas&lt;/span&gt; &lt;span class="k"&gt;as&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;

&lt;span class="n"&gt;df&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;read_excel&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"shadow.xlsx"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;sheet_name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;None&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;  &lt;span class="c1"&gt;# every tab&lt;/span&gt;

&lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;tab&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="n"&gt;df&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;items&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;f&lt;/span&gt;&lt;span class="s2"&gt;"\n== {tab}: {len(data)} rows"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="n"&gt;profile&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;pd&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nc"&gt;DataFrame&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="s2"&gt;"filled_pct"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;notna&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;mean&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;100&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nb"&gt;round&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"distinct"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;nunique&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="s2"&gt;"example"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;apply&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="k"&gt;lambda&lt;/span&gt; &lt;span class="n"&gt;c&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;dropna&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;iloc&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;c&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;notna&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nb"&gt;any&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="kc"&gt;None&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
    &lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;profile&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;sort_values&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"filled_pct"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;ascending&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="kc"&gt;False&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Columns that are almost always filled are the ones the person actually needs. Columns with few distinct values are usually statuses or categories the system may already have under another name.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: map every column to the system
&lt;/h2&gt;

&lt;p&gt;Build a simple table with one row per column:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Spreadsheet column&lt;/th&gt;
&lt;th&gt;Exists in the system?&lt;/th&gt;
&lt;th&gt;Where&lt;/th&gt;
&lt;th&gt;Why they still use the sheet&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Customer&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;Account&lt;/td&gt;
&lt;td&gt;Faster to type than to search&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Expected delivery&lt;/td&gt;
&lt;td&gt;Partly&lt;/td&gt;
&lt;td&gt;Order, but filled by operations&lt;/td&gt;
&lt;td&gt;Rep cannot see it, has to ask&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Paid?&lt;/td&gt;
&lt;td&gt;Yes&lt;/td&gt;
&lt;td&gt;ERP invoice status&lt;/td&gt;
&lt;td&gt;Rep has no access to that screen&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Notes for the boss&lt;/td&gt;
&lt;td&gt;No&lt;/td&gt;
&lt;td&gt;none&lt;/td&gt;
&lt;td&gt;Not a system problem, a reporting habit&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The values above are an example of the format, not a real company. The last column is the one that matters. It usually falls into one of four buckets:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Too many steps.&lt;/strong&gt; The field exists, but entering it takes longer than the spreadsheet.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Not visible.&lt;/strong&gt; The data exists, but this role cannot see it, so they ask someone and write it down.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bad data.&lt;/strong&gt; The migrated data was never cleaned, so the person keeps their own version.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Missing.&lt;/strong&gt; The system really does not cover it.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Step 3: turn buckets into backlog items
&lt;/h2&gt;

&lt;p&gt;Each bucket leads to a different kind of work:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;em&gt;Too many steps&lt;/em&gt;: simplify the layout, remove fields nobody uses, add defaults. This is often a small change.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Not visible&lt;/em&gt;: review permissions and page layouts so the role can see the order, invoice or payment status it needs.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Bad data&lt;/em&gt;: schedule the cleanup that was "left for later", with an owner and a date.&lt;/li&gt;
&lt;li&gt;
&lt;em&gt;Missing&lt;/em&gt;: this is the only bucket that may justify new customization, and it should go through the same review as any other change.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Notice that only one of the four buckets is about building something new. Most of the work is removing friction.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: sit next to the person
&lt;/h2&gt;

&lt;p&gt;None of this replaces a conversation. Three questions are enough to start: show me what you do here, what is missing in the system, and what takes you longer since we implemented it. Often that person already said it during the project and nobody followed up.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where a single platform helps
&lt;/h2&gt;

&lt;p&gt;When the sales team already works in Salesforce, having the ERP native to the same org removes a lot of the &lt;em&gt;not visible&lt;/em&gt; bucket: the rep can check the order, invoice or payment status from the account, based on their permissions. That is why we build &lt;a href="https://www.egafutura.com/erp/erp-para-salesforce" rel="noopener noreferrer"&gt;EGA Futura ERP&lt;/a&gt; natively on Salesforce. It does not remove the other three buckets. If entering an order is painful, someone will still find a way around it.&lt;/p&gt;

&lt;p&gt;I wrote the business side of this, in Spanish, as &lt;a href="https://discover.egafutura.com/equipo-sigue-en-excel-despues-de-implementar-erp-crm/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;why your team is still in Excel after implementing an ERP or CRM&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Juan Manuel Garrido, founder of EGA Futura.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>salesforce</category>
      <category>erp</category>
      <category>python</category>
      <category>productivity</category>
    </item>
    <item>
      <title>Three systems, three numbers: write a metric contract before you put an AI agent on your CRM and ERP</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Wed, 11 Nov 2026 17:12:01 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/three-systems-three-numbers-write-a-metric-contract-before-you-put-an-ai-agent-on-your-crm-and-erp-38on</link>
      <guid>https://dev.to/juanma_garrido_1974/three-systems-three-numbers-write-a-metric-contract-before-you-put-an-ai-agent-on-your-crm-and-erp-38on</guid>
      <description>&lt;p&gt;A sales manager asks for one number. The CRM says 100 sold. The ERP says 80 invoiced. Somebody's spreadsheet says 120. None of them has to be wrong: each system records a different moment of the same sale, entered by different people at different times.&lt;/p&gt;

&lt;p&gt;This is the normal state of many mid-sized companies that run Salesforce next to a separate ERP and glue them together with spreadsheets. It is also exactly the setup where teams now want to add an AI agent that "answers questions about the business". If you do that without fixing the definitions first, the agent inherits the same argument and picks one of the three numbers for you.&lt;/p&gt;

&lt;p&gt;This post shows a small, practical artifact that helps before any agent work: a metric contract.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why the numbers disagree
&lt;/h2&gt;

&lt;p&gt;Take "sales this month". In a Salesforce org alone there are already two valid answers:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight sql"&gt;&lt;code&gt;&lt;span class="c1"&gt;-- Won opportunities closed this month&lt;/span&gt;
&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="nb"&gt;SUM&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;Amount&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="nc"&gt;Opportunity&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="nc"&gt;IsWon&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt; &lt;span class="k"&gt;AND&lt;/span&gt; &lt;span class="nc"&gt;CloseDate&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="no"&gt;THIS_MONTH&lt;/span&gt;

&lt;span class="c1"&gt;-- Activated orders effective this month&lt;/span&gt;
&lt;span class="k"&gt;SELECT&lt;/span&gt; &lt;span class="nb"&gt;SUM&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nc"&gt;TotalAmount&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="k"&gt;FROM&lt;/span&gt; &lt;span class="k"&gt;Order&lt;/span&gt;
&lt;span class="k"&gt;WHERE&lt;/span&gt; &lt;span class="nc"&gt;Status&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'Activated'&lt;/span&gt; &lt;span class="k"&gt;AND&lt;/span&gt; &lt;span class="nc"&gt;EffectiveDate&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="no"&gt;THIS_MONTH&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Both queries are correct SOQL and they can return different totals on the same day. "Invoiced" lives in the ERP and has its own date logic. The spreadsheet usually mixes all of them plus manual corrections. Three sources, three numbers, one meeting to decide which one wins.&lt;/p&gt;

&lt;h2&gt;
  
  
  The metric contract
&lt;/h2&gt;

&lt;p&gt;A metric contract is a short, versioned file that says, for each number leadership asks about, exactly where it comes from and who owns it. YAML is enough:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;metric&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;sales_this_month&lt;/span&gt;
&lt;span class="na"&gt;question&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"How much did we sell this month?"&lt;/span&gt;
&lt;span class="na"&gt;definition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Sum of activated orders by effective date"&lt;/span&gt;
&lt;span class="na"&gt;source_of_truth&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;salesforce&lt;/span&gt;
&lt;span class="na"&gt;object&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;Order&lt;/span&gt;
&lt;span class="na"&gt;filter&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Status = 'Activated' AND EffectiveDate = THIS_MONTH"&lt;/span&gt;
&lt;span class="na"&gt;amount_field&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;TotalAmount&lt;/span&gt;
&lt;span class="na"&gt;owner&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;sales_operations&lt;/span&gt;
&lt;span class="na"&gt;not_this&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s2"&gt;"won opportunities"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"invoices issued"&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="na"&gt;reconciles_with&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;metric&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;invoiced_this_month&lt;/span&gt;
    &lt;span class="na"&gt;expected_gap&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"orders activated but not yet invoiced"&lt;/span&gt;
&lt;span class="nn"&gt;---
&lt;/span&gt;&lt;span class="na"&gt;metric&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;invoiced_this_month&lt;/span&gt;
&lt;span class="na"&gt;question&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"How much did we invoice this month?"&lt;/span&gt;
&lt;span class="na"&gt;definition&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Sum of posted invoices by invoice date"&lt;/span&gt;
&lt;span class="na"&gt;source_of_truth&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;erp&lt;/span&gt;
&lt;span class="na"&gt;owner&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;finance&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The values above are an example of the format, not a real company's setup. What matters is that every metric has exactly one source of truth, one owner, and an explicit list of what it is not.&lt;/p&gt;

&lt;h2&gt;
  
  
  What changes for the agent
&lt;/h2&gt;

&lt;p&gt;With a contract in place, an agent that answers "how much did we sell?" has a single query to run and a documented gap to explain when the invoiced number is lower. Without it, the agent has three sources that disagree and no rule for choosing.&lt;/p&gt;

&lt;p&gt;A few practical rules that follow:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Give the agent the contract as context, not just database access.&lt;/li&gt;
&lt;li&gt;If a metric needs a spreadsheet to compute, the contract should say so. That row is a candidate for removal, not for automation.&lt;/li&gt;
&lt;li&gt;Review the contract when a process changes, the same way you review code.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  When a single data source removes the problem
&lt;/h2&gt;

&lt;p&gt;The contract reduces arguments, but it does not remove the reconciliation work when sales, invoicing and inventory live in separate databases. That is why we build &lt;a href="https://www.egafutura.com/erp/erp-para-salesforce" rel="noopener noreferrer"&gt;EGA Futura ERP&lt;/a&gt; natively on Salesforce: sales, invoicing, inventory, purchasing, treasury and accounting share the same database as the CRM, so the "sold" and "invoiced" metrics in the contract point to the same place. If you are earlier in the journey, the contract is still the cheapest first step.&lt;/p&gt;

&lt;p&gt;I wrote the business side of this, in Spanish, as &lt;a href="https://discover.egafutura.com/salesforce-erp-excel-tres-numeros-dia-de-un-jefe/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;the typical day of a manager reconciling Salesforce, the ERP and Excel&lt;/a&gt;.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Juan Manuel Garrido, founder of EGA Futura and co-founder of Vantegrate.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>salesforce</category>
      <category>erp</category>
      <category>ai</category>
      <category>database</category>
    </item>
    <item>
      <title>Before you estimate an ERP or CRM implementation, trace one real order to cash</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Tue, 10 Nov 2026 17:03:08 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/before-you-estimate-an-erp-or-crm-implementation-trace-one-real-order-to-cash-3ep8</link>
      <guid>https://dev.to/juanma_garrido_1974/before-you-estimate-an-erp-or-crm-implementation-trace-one-real-order-to-cash-3ep8</guid>
      <description>&lt;p&gt;A system can go live on schedule and still leave the finance team invoicing in a spreadsheet the following Monday. When that happens, the cause is usually upstream of the project: nobody walked through one complete, real transaction before the estimate was signed.&lt;/p&gt;

&lt;p&gt;This post is a practical template for doing that walkthrough and turning it into something an estimate can rely on. It applies to ERP, CRM, Salesforce, Odoo or any business system that touches orders, invoices and payments.&lt;/p&gt;

&lt;h2&gt;
  
  
  Pick a messy transaction, not a clean one
&lt;/h2&gt;

&lt;p&gt;Choose a recent sale that had at least one exception: a partial delivery, an off-list discount, a credit note, a split payment. Clean transactions confirm the demo. Messy ones show the scope.&lt;/p&gt;

&lt;h2&gt;
  
  
  Record every step in the same shape
&lt;/h2&gt;

&lt;p&gt;Walk the transaction with the people who actually did it. For each step, capture the same fields. A plain YAML file works fine and is easy to diff later:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;transaction&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Recent sale with partial delivery and a credit note"&lt;/span&gt;
&lt;span class="na"&gt;steps&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;step&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;order&lt;/span&gt;
    &lt;span class="na"&gt;done_by&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;sales rep&lt;/span&gt;
    &lt;span class="na"&gt;recorded_in&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;customer email + spreadsheet&lt;/span&gt;
    &lt;span class="na"&gt;exceptions&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;special&lt;/span&gt; &lt;span class="s"&gt;price&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="na"&gt;approved_by&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;sales manager&lt;/span&gt;
    &lt;span class="na"&gt;outside_system&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;approval&lt;/span&gt; &lt;span class="s"&gt;via&lt;/span&gt; &lt;span class="s"&gt;chat&lt;/span&gt; &lt;span class="s"&gt;message&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;step&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;credit_note&lt;/span&gt;
    &lt;span class="na"&gt;done_by&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;accounting&lt;/span&gt;
    &lt;span class="na"&gt;recorded_in&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;accounting system&lt;/span&gt;
    &lt;span class="na"&gt;exceptions&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;partial&lt;/span&gt; &lt;span class="s"&gt;return&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="na"&gt;approved_by&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;finance&lt;/span&gt;
    &lt;span class="na"&gt;outside_system&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;email&lt;/span&gt; &lt;span class="s"&gt;thread&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
  &lt;span class="p"&gt;-&lt;/span&gt; &lt;span class="na"&gt;step&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;payment&lt;/span&gt;
    &lt;span class="na"&gt;done_by&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;treasury&lt;/span&gt;
    &lt;span class="na"&gt;recorded_in&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;bank + spreadsheet&lt;/span&gt;
    &lt;span class="na"&gt;exceptions&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;paid&lt;/span&gt; &lt;span class="s"&gt;in&lt;/span&gt; &lt;span class="s"&gt;installments&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="na"&gt;approved_by&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;null&lt;/span&gt;
    &lt;span class="na"&gt;outside_system&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;reconciliation&lt;/span&gt; &lt;span class="s"&gt;spreadsheet&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The values above are a format example, not a real case. The interesting fields are &lt;code&gt;approved_by&lt;/code&gt; and &lt;code&gt;outside_system&lt;/code&gt;. That is where unestimated work hides.&lt;/p&gt;

&lt;h2&gt;
  
  
  Classify every gap before anyone estimates hours
&lt;/h2&gt;

&lt;p&gt;Each thing that doesn't map cleanly to the target system goes into one of four buckets:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Bucket&lt;/th&gt;
&lt;th&gt;Meaning&lt;/th&gt;
&lt;th&gt;How to estimate&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;standard&lt;/td&gt;
&lt;td&gt;The product does it out of the box&lt;/td&gt;
&lt;td&gt;Near zero&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;configuration&lt;/td&gt;
&lt;td&gt;Fields, picklists, validation rules, declarative automation, permissions&lt;/td&gt;
&lt;td&gt;Hours, low risk&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;development&lt;/td&gt;
&lt;td&gt;Custom code, UI components, integrations&lt;/td&gt;
&lt;td&gt;Separate estimate, real risk&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;business decision&lt;/td&gt;
&lt;td&gt;Nobody has defined the rule&lt;/td&gt;
&lt;td&gt;Not hours. A meeting with someone who has authority&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The last bucket is the one that blows up projects. "Who approves a credit note above a certain amount?" is not a configuration task. If it gets mixed into the configuration estimate, it comes back later as a change request, a moved date, or a spreadsheet that survives go-live.&lt;/p&gt;

&lt;p&gt;A quick way to make this visible is to count gaps per bucket per step:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;from&lt;/span&gt; &lt;span class="n"&gt;collections&lt;/span&gt; &lt;span class="k"&gt;import&lt;/span&gt; &lt;span class="nc"&gt;Counter&lt;/span&gt;

&lt;span class="n"&gt;gaps&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"order"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"business_decision"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"no backup approver for off-list discounts"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"order"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"configuration"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"discount approval threshold"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"credit_note"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"business_decision"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"no written limit for credit notes"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"payment"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"development"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s2"&gt;"bank file import"&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="n"&gt;by_bucket&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nc"&gt;Counter&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;bucket&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;_&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;bucket&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;_&lt;/span&gt; &lt;span class="k"&gt;in&lt;/span&gt; &lt;span class="n"&gt;gaps&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;print&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;by_bucket&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="c1"&gt;# Any business_decision &amp;gt; 0 means the estimate is not ready to sign.&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Same caveat: the list is illustrative. The rule at the end is the point.&lt;/p&gt;

&lt;h2&gt;
  
  
  Treat every spreadsheet as a requirement
&lt;/h2&gt;

&lt;p&gt;For each spreadsheet in &lt;code&gt;outside_system&lt;/code&gt;, write down what it calculates, where its inputs come from and who makes decisions with it. Some become formula fields or reports. Others hide a business rule nobody wrote down. Either way, they belong in scope, not in a "phase two" nobody funds.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who sits in the room
&lt;/h2&gt;

&lt;p&gt;The people who do the work every day, plus someone with authority to settle disagreements between departments. Without the second one, business-decision gaps stay open and the consultants end up guessing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Use the same trace after go-live
&lt;/h2&gt;

&lt;p&gt;A few weeks after launch, rerun the walkthrough with the same transaction type. If &lt;code&gt;outside_system&lt;/code&gt; is still full, the project is not done, whatever the timeline says. Going live is a date. Closing the month without people staying late to reconcile two sets of numbers is the result.&lt;/p&gt;

&lt;p&gt;I wrote about the business side of this, in Spanish, on our blog: &lt;a href="https://discover.egafutura.com/implementacion-erp-sale-en-fecha-administracion-sigue-en-excel/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;why an ERP implementation can go live on time and still fail&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Juan Manuel Garrido, founder of EGA Futura&lt;/p&gt;

</description>
      <category>erp</category>
      <category>salesforce</category>
      <category>productivity</category>
      <category>management</category>
    </item>
    <item>
      <title>Salesforce Flow: wait for a follow-up request before creating a sales task</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Mon, 09 Nov 2026 16:39:58 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/salesforce-flow-wait-for-a-follow-up-request-before-creating-a-sales-task-4oop</link>
      <guid>https://dev.to/juanma_garrido_1974/salesforce-flow-wait-for-a-follow-up-request-before-creating-a-sales-task-4oop</guid>
      <description>&lt;p&gt;Creating a Salesforce contact should not automatically turn a conversation into a sales task.&lt;/p&gt;

&lt;p&gt;That is a design position, not a statement about a mandatory Salesforce default. If your organization creates tasks whenever a Contact is saved, someone configured that behavior. The entry rule can be reconsidered.&lt;/p&gt;

&lt;p&gt;In a personal post, I wrote: “Human relationships do not work like a CRM.” This is a translation from my Spanish original. The technical question it raises is narrow: what event should authorize an internal follow-up task?&lt;/p&gt;

&lt;p&gt;This article proposes a hypothetical design. It has not been executed or validated in a Salesforce organization as part of this draft. There are no deployment results or customer outcomes to report.&lt;/p&gt;

&lt;h2&gt;
  
  
  Define the event before the field
&lt;/h2&gt;

&lt;p&gt;For this example, the event is an explicit request for commercial follow-up. Merely meeting someone does not satisfy it. The team needs an agreed way to record the request rather than infer it from a pleasant conversation.&lt;/p&gt;

&lt;p&gt;The proposed custom field on Contact is a checkbox named &lt;code&gt;Solicita_seguimiento_comercial__c&lt;/code&gt;. In English, the name means “requests commercial follow-up.” It is not a standard Salesforce field. Its initial value is false.&lt;/p&gt;

&lt;p&gt;This checkbox does not represent legal consent for marketing. A request for a proposal should not silently become permission for unrelated messages. Record only information needed for the commercial purpose, without adding personal details that the process does not need.&lt;/p&gt;

&lt;p&gt;A checkbox is intentionally limited. It represents a current state, not a history of requests. If the process needs to distinguish separate requests over time, consider a model that records them individually before building this version.&lt;/p&gt;

&lt;h2&gt;
  
  
  Configure the proposed record-triggered Flow
&lt;/h2&gt;

&lt;p&gt;Work in a sandbox. Create the custom field using your organization's administration conventions and review field access. People who record requests need an interface that makes the meaning clear. The checkbox should not be preselected as a shortcut for contact creation.&lt;/p&gt;

&lt;p&gt;The variant described here uses Contact creation or update as the trigger. That allows a request to be recorded during initial entry or later. If your business process only accepts requests after creation, narrow that scope and adjust the tests.&lt;/p&gt;

&lt;p&gt;The proposed setup is:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Object: Contact
Trigger: created or updated
Entry condition:
  Solicita_seguimiento_comercial__c Equals True
For updated records:
  Only when a record is updated to meet the condition requirements
Run after save, optimized for actions and related records
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This block describes configuration; it is not deployable metadata. Interface labels may vary with the language of your environment.&lt;/p&gt;

&lt;p&gt;The update option matters. Running whenever the checkbox is true could create a task on unrelated edits. Running when the record moves into the qualifying state targets the transition instead. For creation, a record initially saved with the checkbox true also qualifies in this version.&lt;/p&gt;

&lt;p&gt;The Flow runs after save because it creates another record. Salesforce's &lt;a href="https://trailhead.salesforce.com/content/learn/modules/data-and-actions-in-flows/work-sf-records-flows" rel="noopener noreferrer"&gt;record management material for Flow&lt;/a&gt; explains operations on records. This example does not use a before-save update to change the triggering Contact.&lt;/p&gt;

&lt;h2&gt;
  
  
  Create the internal Task
&lt;/h2&gt;

&lt;p&gt;Add a Create Records element for Task. Associate it with the triggering Contact through &lt;code&gt;WhoId&lt;/code&gt;, using the Contact identifier available as &lt;code&gt;$Record.Id&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Choose the task subject to describe the actual request. Decide who should own the task according to your organization's assignment process. Do not paste user identifiers from another environment. Select status values that exist in your organization rather than assuming every environment uses the same configuration.&lt;/p&gt;

&lt;p&gt;Review required fields and validation rules before testing. The sketch above does not account for every organization-specific constraint. Decide how a creation failure will become visible to the responsible team without exposing unnecessary contact information.&lt;/p&gt;

&lt;p&gt;This design does not send email. An internal task and an outbound message are separate actions. The task should not be treated as permission to enroll someone in a marketing sequence.&lt;/p&gt;

&lt;p&gt;Before activation, inspect existing Contact automation. Another process may already create follow-up tasks. A carefully scoped new Flow does not prevent a different automation from acting on the same record.&lt;/p&gt;

&lt;h2&gt;
  
  
  Test the absence of a task
&lt;/h2&gt;

&lt;p&gt;Start with a Contact whose checkbox is false. The expected outcome is no Task from this Flow. Update another field without changing the checkbox. Again, this Flow should not create a task.&lt;/p&gt;

&lt;p&gt;These are expected outcomes, not results observed during preparation of this article. Confirm them in your sandbox, including whether other automation produces a task independently.&lt;/p&gt;

&lt;p&gt;Next, record a hypothetical follow-up request by changing the checkbox from false to true. The expected outcome is a Task associated with the correct Contact and assigned according to the rule you chose.&lt;/p&gt;

&lt;p&gt;Update an unrelated field while the checkbox stays true. The expected outcome is no second Task from this Flow. This test checks whether the entry configuration actually represents a transition rather than a continuously true condition.&lt;/p&gt;

&lt;p&gt;Also test creation with the checkbox already true. In the creation-or-update variant, the expected outcome is a task. If that should not happen in your process, the proposed scope is wrong for your requirement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Repeated requests are a separate requirement
&lt;/h2&gt;

&lt;p&gt;Set the checkbox back to false and then to true again. The basic design can produce another task because the record re-enters the qualifying state.&lt;/p&gt;

&lt;p&gt;That may be appropriate for a new request. It may be wrong if an earlier task is still open. Make that decision explicit. A separate duplicate check or a request-based data model may be needed. This checkbox alone does not provide global idempotency across other automations.&lt;/p&gt;

&lt;p&gt;Salesforce Architects' &lt;a href="https://architect.salesforce.com/docs/architect/decision-guides/guide/record-triggered" rel="noopener noreferrer"&gt;record-triggered automation guide&lt;/a&gt; provides context for evaluating entry conditions and record changes. It does not validate this hypothetical Flow for your organization.&lt;/p&gt;

&lt;p&gt;Salesforce also describes a Lead as a potential prospect in &lt;a href="https://trailhead.salesforce.com/content/learn/modules/leads_opportunities_lightning_experience/create-and-convert-leads-lightning" rel="noopener noreferrer"&gt;its Trailhead lead material&lt;/a&gt;. That distinction does not decide whether a Contact has asked for follow-up. The request still needs its own representation.&lt;/p&gt;

&lt;p&gt;The technical acceptance condition here is deliberately modest: when no request was recorded, this Flow leaves the conversation without a sales task.&lt;/p&gt;

</description>
      <category>salesforce</category>
      <category>automation</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Your AI agent is a while loop. Your company's approval policy is not</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Mon, 09 Nov 2026 16:31:54 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/your-ai-agent-is-a-while-loop-your-companys-approval-policy-is-not-4bba</link>
      <guid>https://dev.to/juanma_garrido_1974/your-ai-agent-is-a-while-loop-your-companys-approval-policy-is-not-4bba</guid>
      <description>&lt;p&gt;A popular meme says an AI agent is just an LLM inside a while loop. Simplifying a lot, that's fair: the model gets an instruction, decides what to do, calls a tool, reads the result and goes around again. You can build one in about 20 minutes.&lt;/p&gt;

&lt;p&gt;Getting it to work inside a real company can take months. Not because the loop is hard, but because the loop needs answers the company never wrote down.&lt;/p&gt;

&lt;p&gt;This post is about one design decision that makes a big difference: keeping business policy out of the model and putting it in data and deterministic code the agent can only call.&lt;/p&gt;

&lt;h2&gt;
  
  
  The question the model should never answer
&lt;/h2&gt;

&lt;p&gt;Here's a common case. A salesperson needs a 20% discount approved. Their limit is 15%. The manager is on vacation. Who approves?&lt;/p&gt;

&lt;p&gt;In many companies nobody has a clear answer. The agent can query the CRM, run a flow or call an API. But if no one has defined who has authority over that discount, the model should not invent a commercial policy. Any answer it produces is a guess that looks like a decision.&lt;/p&gt;

&lt;p&gt;So the first job is not prompt engineering. It's turning "who decides" into something explicit.&lt;/p&gt;

&lt;h2&gt;
  
  
  Put the policy in data, not in the prompt
&lt;/h2&gt;

&lt;p&gt;An approval matrix is boring and that's the point. It can be a table, custom metadata, or a config file the business owns:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="n"&gt;APPROVAL_MATRIX&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="c1"&gt;# (max_discount_pct, role allowed to approve, backup role)
&lt;/span&gt;    &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;15&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;sales_rep&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="bp"&gt;None&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
    &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;25&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;sales_manager&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;regional_director&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
    &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;40&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;regional_director&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;cfo&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;approver_for&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;discount_pct&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;unavailable_roles&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;max_pct&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;role&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;backup&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;APPROVAL_MATRIX&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;discount_pct&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;=&lt;/span&gt; &lt;span class="n"&gt;max_pct&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;role&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;unavailable_roles&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
                &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;role&lt;/span&gt;
            &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;backup&lt;/span&gt; &lt;span class="ow"&gt;and&lt;/span&gt; &lt;span class="n"&gt;backup&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;unavailable_roles&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
                &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;backup&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;None&lt;/span&gt;  &lt;span class="c1"&gt;# nobody available: escalate, don't guess
&lt;/span&gt;    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="bp"&gt;None&lt;/span&gt;  &lt;span class="c1"&gt;# above any defined limit: out of policy
&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The numbers above are placeholders. The real ones come from whoever owns the commercial policy. If that person doesn't exist yet, you've found the actual blocker, and it isn't technical.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give the agent narrow tools with a gate
&lt;/h2&gt;

&lt;p&gt;The agent loop stays simple. What changes is the tool layer: tools that change money, prices or contracts never execute directly. They return a proposal, and a deterministic gate decides what happens next.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight python"&gt;&lt;code&gt;&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;request_discount&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;opportunity_id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;discount_pct&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="n"&gt;approver&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;approver_for&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;discount_pct&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;unavailable_roles&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;])&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;approver&lt;/span&gt; &lt;span class="ow"&gt;is&lt;/span&gt; &lt;span class="bp"&gt;None&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
        &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
            &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;status&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;needs_human&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
            &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;reason&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;No approver defined or available for this discount&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;status&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;pending_approval&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;approver_role&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;approver&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;opportunity_id&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;opportunity_id&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
        &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;discount_pct&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;discount_pct&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="n"&gt;TOOLS&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;get_opportunity&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;get_opportunity&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;      &lt;span class="c1"&gt;# read only
&lt;/span&gt;    &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;request_discount&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="n"&gt;request_discount&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;    &lt;span class="c1"&gt;# proposes, never applies
&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="k"&gt;def&lt;/span&gt; &lt;span class="nf"&gt;agent_loop&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;llm&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;message&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;max_steps&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
    &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;_&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="nf"&gt;range&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;max_steps&lt;/span&gt;&lt;span class="p"&gt;):&lt;/span&gt;
        &lt;span class="n"&gt;reply&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;tool_calls&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;llm&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;message&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;tools&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nf"&gt;list&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;TOOLS&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
        &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="n"&gt;tool_calls&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;reply&lt;/span&gt;
        &lt;span class="n"&gt;results&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;[]&lt;/span&gt;
        &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;call&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;tool_calls&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
            &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt; &lt;span class="ow"&gt;not&lt;/span&gt; &lt;span class="ow"&gt;in&lt;/span&gt; &lt;span class="n"&gt;TOOLS&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
                &lt;span class="n"&gt;results&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;({&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;error&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sa"&gt;f&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;tool &lt;/span&gt;&lt;span class="si"&gt;{&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="si"&gt;}&lt;/span&gt;&lt;span class="s"&gt; not allowed&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;})&lt;/span&gt;
                &lt;span class="k"&gt;continue&lt;/span&gt;
            &lt;span class="n"&gt;results&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;append&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;TOOLS&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;name&lt;/span&gt;&lt;span class="p"&gt;](&lt;/span&gt;&lt;span class="o"&gt;**&lt;/span&gt;&lt;span class="n"&gt;call&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;args&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="n"&gt;context&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt;
        &lt;span class="n"&gt;message&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;results&lt;/span&gt;
    &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;status&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;needs_human&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;reason&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="s"&gt;step limit reached&lt;/span&gt;&lt;span class="sh"&gt;"&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A few things that are easy to skip in a demo:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;A step limit.&lt;/strong&gt; &lt;code&gt;while True&lt;/code&gt; is fine in a meme. In production, the loop needs a budget and a defined way out.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;An allowlist.&lt;/strong&gt; The model can only call tools you registered, and each tool has the smallest scope that works.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;"needs_human" as a first-class result.&lt;/strong&gt; Stopping is a valid outcome, not a failure. The agent should say why it stopped and who should look at it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read tools and write tools are different things.&lt;/strong&gt; Reading an opportunity is cheap to get wrong. Changing a price list linked to active contracts is not.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Not everything needs an agent
&lt;/h2&gt;

&lt;p&gt;If a decision fits in an &lt;code&gt;if&lt;/code&gt;, a rule engine, a flow or plain code will do it faster, cheaper and the same way every time. In Salesforce, that's still Flow and Apex territory. Agents earn their place where you need interpretation: free text, messy context, choosing between paths you can't enumerate.&lt;/p&gt;

&lt;p&gt;Mixing the two up is expensive in both directions. Use reasoning where you need reasoning. Use rules where you need the system to do exactly what it should.&lt;/p&gt;

&lt;h2&gt;
  
  
  The takeaway
&lt;/h2&gt;

&lt;p&gt;Building the engine of an agent can be surprisingly simple. The hard part starts when you connect it to a real company: permissions, duplicate data, legacy processes and the exceptions that never show up in demos.&lt;/p&gt;

&lt;p&gt;Solve the process first. Then automate it.&lt;/p&gt;

&lt;p&gt;I wrote the business side of this, with a checklist of what to review before letting an agent work on real Salesforce data, on EGA Futura Discover (in Spanish): &lt;a href="https://discover.egafutura.com/agente-de-ia-en-salesforce-de-la-demo-a-la-empresa/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;Por qué un agente de IA que se arma en 20 minutos tarda meses en funcionar dentro de Salesforce&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Juan Manuel Garrido, founder of EGA Futura and co-founder of Vantegrate.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>salesforce</category>
      <category>agents</category>
      <category>architecture</category>
    </item>
    <item>
      <title>ERP and CRM implementations rarely fail because of the software</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Mon, 09 Nov 2026 16:31:45 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/erp-and-crm-implementations-rarely-fail-because-of-the-software-1l59</link>
      <guid>https://dev.to/juanma_garrido_1974/erp-and-crm-implementations-rarely-fail-because-of-the-software-1l59</guid>
      <description>&lt;p&gt;Most failed ERP or CRM rollouts start the same way. The company decides to “digitally transform.” Budget is approved. A vendor is chosen. The timeline is aggressive. Then comes the real decision: who leads the project.&lt;/p&gt;

&lt;p&gt;That is where many programs break.&lt;/p&gt;

&lt;p&gt;Not business owners. Not the people who know the process end to end. Not someone with digital street smarts. The project is handed to people who think software is screens with data, and that “everything is easy once it is in the system.”&lt;/p&gt;

&lt;p&gt;Day one looks productive. Meetings. Decks. Green status. The hard work is skipped: process discovery, workflow ownership, dependency maps, data model understanding, real testing strategy.&lt;/p&gt;

&lt;p&gt;Without that, the ERP becomes a guessing game. Vague requirements. Rushed configuration. Exceptions swept under the rug. Master data treated as a detail.&lt;/p&gt;

&lt;p&gt;Then teams expect the system to fix broken processes. It does not. It exposes them.&lt;/p&gt;

&lt;p&gt;Blame starts. Tech “makes it complicated.” The implementer is told to go faster. Change requests explode. Patches become the plan. Users are trained at the end, if they are trained at all.&lt;/p&gt;

&lt;p&gt;Go-live arrives. Invoices do not close. Stock does not match. Orders get stuck. Finance cannot close the month. Operations returns to spreadsheets. The conclusion becomes automatic: “the system does not work.”&lt;/p&gt;

&lt;p&gt;Usually the system never got a chance.&lt;/p&gt;

&lt;p&gt;An ERP is not an IT project. It is not a shortcut. It is a mirror. Mirrors are uncomfortable when you do not know what you are looking at.&lt;/p&gt;

&lt;p&gt;Before kickoff, ask:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Who owns each critical workflow, by name, with real time?&lt;/li&gt;
&lt;li&gt;Is there a dependency map across sales, inventory, billing, and finance?&lt;/li&gt;
&lt;li&gt;Who defines and cleans master data?&lt;/li&gt;
&lt;li&gt;How do you test the end-to-end process, not just screens?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If your stack is Salesforce, a native ERP can remove a sync layer. It still cannot replace process ownership.&lt;/p&gt;

&lt;p&gt;Longer Spanish version on Discover: &lt;a href="https://discover.egafutura.com/erp-espejo-liderazgo-del-proyecto/" rel="noopener noreferrer"&gt;https://discover.egafutura.com/erp-espejo-liderazgo-del-proyecto/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>salesforce</category>
      <category>erp</category>
      <category>crm</category>
      <category>leadership</category>
    </item>
    <item>
      <title>From MS-DOS to AI agents: why the generation that adapted the most shouldn't have to prove it</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Fri, 06 Nov 2026 11:25:09 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/from-ms-dos-to-ai-agents-why-the-generation-that-adapted-the-most-shouldnt-have-to-prove-it-4ane</link>
      <guid>https://dev.to/juanma_garrido_1974/from-ms-dos-to-ai-agents-why-the-generation-that-adapted-the-most-shouldnt-have-to-prove-it-4ane</guid>
      <description>&lt;p&gt;I recently read that people over 40 struggle to adapt to new technology. I'm Juan Manuel Garrido, founder of EGA Futura and co-founder of Vantegrate, and that claim doesn't match the history I lived.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick memory check
&lt;/h2&gt;

&lt;p&gt;Many of us started on black screens with no mouse, typing every command by hand. We saved work to floppy disks and hoped they wouldn't fail. Getting online meant waiting until nobody else needed the home phone line. We listened to the modem scream and watched a page load one line at a time.&lt;/p&gt;

&lt;p&gt;Then came Windows and the mouse. We sent our first emails when we still had to explain what the @ symbol meant. We moved from fax to email, from paper planners to phones, from phones that only made calls to smartphones and WhatsApp, which permanently changed how we work. We watched office servers move to the cloud. Every time we finally knew a system by heart, a new one showed up and we started over.&lt;/p&gt;

&lt;p&gt;In 2020, overnight, we learned to work from home, run video meetings, and keep whole teams going remotely.&lt;/p&gt;

&lt;h2&gt;
  
  
  Starting from zero again (on purpose)
&lt;/h2&gt;

&lt;p&gt;Today we're learning to work with AI. Exactly like someone who is 25, who is also starting from scratch. Nobody handed us a manual. We learned by doing, asking, and getting it wrong. Often while raising kids, paying bills, and holding down a job.&lt;/p&gt;

&lt;p&gt;So when someone says people over 40 struggle to adapt, I feel they don't know our story. We're the generation that lived through the most technological change in a single working life. Adapting is what we've been doing since day one.&lt;/p&gt;

&lt;h2&gt;
  
  
  1994 to today
&lt;/h2&gt;

&lt;p&gt;I founded my company in 1994 with software that ran on MS-DOS. Today we build &lt;a href="https://vantegrate.com/agentes-ia" rel="noopener noreferrer"&gt;AI agents for mid-sized companies&lt;/a&gt;. Along the way I reinvented myself more times than I can count, like almost everyone reading this.&lt;/p&gt;

&lt;p&gt;If a recruiter still thinks age predicts the ability to learn, share this with them. Age isn't the measure. The track record of adaptation is.&lt;/p&gt;

&lt;p&gt;Full version (Spanish) on &lt;a href="https://discover.egafutura.com/de-ms-dos-a-agentes-de-ia-por-que-la-generacion-que-mas-se-adapto-no-deberia-tener-que-demostrarlo/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;EGA Futura Discover&lt;/a&gt;. We also run &lt;a href="https://www.egafutura.com/salesforce" rel="noopener noreferrer"&gt;free live Salesforce classes&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>career</category>
      <category>technology</category>
      <category>ai</category>
      <category>ageism</category>
    </item>
    <item>
      <title>AIforce vs Agentforce and the new Salesforce developer role: notes from Dreamforce 2026</title>
      <dc:creator>Juan Manuel Garrido</dc:creator>
      <pubDate>Thu, 05 Nov 2026 17:24:47 +0000</pubDate>
      <link>https://dev.to/juanma_garrido_1974/aiforce-vs-agentforce-and-the-new-salesforce-developer-role-notes-from-dreamforce-2026-k78</link>
      <guid>https://dev.to/juanma_garrido_1974/aiforce-vs-agentforce-and-the-new-salesforce-developer-role-notes-from-dreamforce-2026-k78</guid>
      <description>&lt;p&gt;AIforce does not replace Agentforce. Developers are moving from writing every line of code to giving agents guidelines, reviewing their output and setting guardrails. And the real story of Dreamforce 2026 was MCP and skills, not a single vendor.&lt;/p&gt;

&lt;p&gt;I'm Juan Manuel Garrido, founder of EGA Futura and co-founder of Vantegrate. On September 17 we streamed our weekly masterclass live from floor 61 of Salesforce Tower with Alba Rivas from Salesforce, right after the developer keynote. These are her three clarifications.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. AIforce is not a rebrand of Agentforce
&lt;/h2&gt;

&lt;p&gt;Start with the Headless Toolkit (formerly Headless 360, introduced at TrailblazerDX):&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Piece&lt;/th&gt;
&lt;th&gt;What it does&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;MCP Servers&lt;/td&gt;
&lt;td&gt;Expose business logic to any agent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Headless Experience Layer&lt;/td&gt;
&lt;td&gt;Renders components and interfaces dynamically inside agents&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Multi framework&lt;/td&gt;
&lt;td&gt;Build with Angular, React or another framework, not only Lightning Web Components&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;AIforce is the layer that uses those technologies to open Salesforce to any MCP client or agent, plus partnerships with agent vendors. Agentforce remains Salesforce's own AI. The idea that one replaces the other is, in Alba's words, a misconception that may have been poorly communicated.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. From code to guidelines
&lt;/h2&gt;

&lt;p&gt;Creating the object, writing queries, the class, the tests and deploying: according to Alba, that classic workflow doesn't have much time left. The role shifts and expands:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Design:&lt;/strong&gt; ask the agent for a solution that follows your guidelines, technologies and criteria.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Review:&lt;/strong&gt; check that what was built matches what was asked, because AI makes mistakes too.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Guardrails:&lt;/strong&gt; give the agent knowledge and limits.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Anyone can ask an agent to build an app. Not everyone can build one that works in production in an enterprise environment.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. The Dreamforce of MCP and skills
&lt;/h2&gt;

&lt;p&gt;The Claude relationship continues (there's already a Salesforce plugin for Claude), but OpenAI and NVIDIA were also on stage, and AIforce is meant to work with everyone. MCP is becoming a universal protocol, and business users use it too. Skills are written in Markdown and can be shared across a team.&lt;/p&gt;

&lt;p&gt;Full recap of the session on &lt;a href="https://vantegrate.com/pulse/dreamforce-2026-aiforce-agentforce-developer" rel="noopener noreferrer"&gt;Vantegrate Pulse&lt;/a&gt; (Spanish). Version with FAQ on &lt;a href="https://discover.egafutura.com/aiforce-reemplaza-a-agentforce-tres-aclaraciones-de-dreamforce-2026-sobre-agentes-mcp-y-el-nuevo-rol-del-developer/?utm_source=devto&amp;amp;utm_medium=referral&amp;amp;utm_campaign=amplify" rel="noopener noreferrer"&gt;EGA Futura Discover&lt;/a&gt; (Spanish).&lt;/p&gt;

</description>
      <category>salesforce</category>
      <category>ai</category>
      <category>mcp</category>
      <category>career</category>
    </item>
  </channel>
</rss>
