<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Abhishek Siriya: writing</title><description>Notes on GTM and CRM systems, data platforms, AI agents, and the architecture behind them.</description><link>https://sfdcace.com/</link><language>en-us</language><item><title>One create service for every new CRM record, agents included</title><link>https://sfdcace.com/writing/stopping-bad-crm-records-at-entry/</link><guid isPermaLink="true">https://sfdcace.com/writing/stopping-bad-crm-records-at-entry/</guid><description>Every new account and contact, from reps, imports, forms, integrations or agents, goes through one create service that normalizes, scores matches and stamps who made it.</description><pubDate>Fri, 13 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Agents ask the warehouse the same questions all day, in different words</title><link>https://sfdcace.com/writing/agent-queries-and-the-warehouse-bill/</link><guid isPermaLink="true">https://sfdcace.com/writing/agent-queries-and-the-warehouse-bill/</guid><description>Agent queries hide under one service account and miss the result cache. Tag them, fingerprint the history, promote the shapes that repeat, and budget the rest.</description><pubDate>Wed, 04 Nov 2026 00:00:00 GMT</pubDate></item><item><title>Keeping LLM costs predictable as usage grows</title><link>https://sfdcace.com/writing/keeping-llm-costs-predictable/</link><guid isPermaLink="true">https://sfdcace.com/writing/keeping-llm-costs-predictable/</guid><description>The LLM bill that gets a meeting arrives months after launch. Pricing every call in one place, before the provider sees it, keeps that bill from being a surprise.</description><pubDate>Thu, 22 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Finding the CRM integration whose token dies between runs</title><link>https://sfdcace.com/writing/crm-integrations-that-break-when-tokens-expire/</link><guid isPermaLink="true">https://sfdcace.com/writing/crm-integrations-that-break-when-tokens-expire/</guid><description>Keep every CRM integration in a git registry and check it nightly against token history, so a job whose token dies before its next run gets flagged weeks early.</description><pubDate>Wed, 07 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Moving business logic out of the CRM, one capability at a time</title><link>https://sfdcace.com/writing/moving-logic-out-of-the-crm-without-a-rewrite/</link><guid isPermaLink="true">https://sfdcace.com/writing/moving-logic-out-of-the-crm-without-a-rewrite/</guid><description>The strangler pattern for a heavily customized CRM: a thin router, a flag per capability, shadow runs that compare answers, and results written back.</description><pubDate>Thu, 24 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Finding out your LLM feature got worse before your users do</title><link>https://sfdcace.com/writing/testing-llm-features-before-users-notice/</link><guid isPermaLink="true">https://sfdcace.com/writing/testing-llm-features-before-users-notice/</guid><description>A golden set of real inputs, graders from cheap to slow, and a CI gate that can say no: catching an LLM feature getting worse before users do.</description><pubDate>Wed, 09 Sep 2026 00:00:00 GMT</pubDate></item><item><title>Data contracts between teams, and the CI rules that make them stick</title><link>https://sfdcace.com/writing/data-contracts-between-teams/</link><guid isPermaLink="true">https://sfdcace.com/writing/data-contracts-between-teams/</guid><description>A YAML contract in the producer repo, three CI rules, a registry, and a slow lane for breaking changes, so upstream edits stop breaking downstream data.</description><pubDate>Thu, 20 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Catching usage contraction before the renewal, and what the agent may do alone</title><link>https://sfdcace.com/writing/catching-revenue-contraction-before-the-renewal/</link><guid isPermaLink="true">https://sfdcace.com/writing/catching-revenue-contraction-before-the-renewal/</guid><description>Compute usage contraction in the warehouse as dollars at risk, sync three fields to the CRM account, and write down what a renewal agent may do without a named approver.</description><pubDate>Wed, 05 Aug 2026 00:00:00 GMT</pubDate></item><item><title>When RAG gives a wrong answer, check what it retrieved first</title><link>https://sfdcace.com/writing/when-rag-gives-wrong-answers/</link><guid isPermaLink="true">https://sfdcace.com/writing/when-rag-gives-wrong-answers/</guid><description>Wrong RAG answers usually start in the search step. A starting design with hybrid search, reranking, citations and a handoff, plus retrieval tests you can copy.</description><pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate></item><item><title>From the app database to the warehouse in minutes</title><link>https://sfdcace.com/writing/from-database-to-warehouse-in-minutes/</link><guid isPermaLink="true">https://sfdcace.com/writing/from-database-to-warehouse-in-minutes/</guid><description>Streaming changes from an application database into a lakehouse table: read the log, a Kafka topic per table, upsert by key, compact, and count every night.</description><pubDate>Wed, 08 Jul 2026 00:00:00 GMT</pubDate></item><item><title>The architecture of a customer-support AI agent</title><link>https://sfdcace.com/writing/architecture-of-a-customer-support-ai-agent/</link><guid isPermaLink="true">https://sfdcace.com/writing/architecture-of-a-customer-support-ai-agent/</guid><description>A public support agent should answer when it has grounds to and hand the conversation to a person when it doesn&apos;t. What that takes.</description><pubDate>Thu, 18 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Batch data pipelines that survive a bad night</title><link>https://sfdcace.com/writing/batch-data-pipelines-that-survive-a-bad-night/</link><guid isPermaLink="true">https://sfdcace.com/writing/batch-data-pipelines-that-survive-a-bad-night/</guid><description>The night everything works takes care of itself. Scheduled jobs built for the other night, when a broken source should end in a clean rerun.</description><pubDate>Wed, 03 Jun 2026 00:00:00 GMT</pubDate></item><item><title>Split the task before you run coding agents in parallel</title><link>https://sfdcace.com/writing/splitting-work-for-parallel-coding-agents/</link><guid isPermaLink="true">https://sfdcace.com/writing/splitting-work-for-parallel-coding-agents/</guid><description>Before running coding agents side by side, give every file one owner and commit the shared interfaces first. A path check in CI enforces the split, and a baseline prices it.</description><pubDate>Thu, 21 May 2026 00:00:00 GMT</pubDate></item><item><title>Quote-to-cash at a high level: where the time goes and how to get it back</title><link>https://sfdcace.com/writing/quote-to-cash-architecture/</link><guid isPermaLink="true">https://sfdcace.com/writing/quote-to-cash-architecture/</guid><description>A quote takes milliseconds to compute and days to produce. Where catalog, pricing, approvals, contracts, orders, and billing lose time, and how to win it back.</description><pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate></item><item><title>Putting an LLM inside the CRM, where the work already happens</title><link>https://sfdcace.com/writing/putting-an-llm-inside-the-crm/</link><guid isPermaLink="true">https://sfdcace.com/writing/putting-an-llm-inside-the-crm/</guid><description>An LLM feature in its own tab goes unused. Put it on the record the rep already has open, then deal with the permission and review questions that come with that.</description><pubDate>Thu, 23 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Designing a territory assignment engine</title><link>https://sfdcace.com/writing/designing-a-territory-assignment-engine/</link><guid isPermaLink="true">https://sfdcace.com/writing/designing-a-territory-assignment-engine/</guid><description>How I&apos;d design the engine that assigns sales accounts to territories: rules as data, deterministic matching, stored explanations, dry runs, and careful publishing.</description><pubDate>Tue, 07 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Before a second engine writes to your lakehouse table</title><link>https://sfdcace.com/writing/one-writer-per-table-in-an-open-lakehouse/</link><guid isPermaLink="true">https://sfdcace.com/writing/one-writer-per-table-in-an-open-lakehouse/</guid><description>An open table format lets several engines read the same files. It doesn&apos;t decide who commits or who sees which rows, so give each table one writer and define its policies once.</description><pubDate>Thu, 19 Mar 2026 00:00:00 GMT</pubDate></item><item><title>Keeping CRM systems in sync with events instead of batch jobs</title><link>https://sfdcace.com/writing/keeping-crm-systems-in-sync-with-events/</link><guid isPermaLink="true">https://sfdcace.com/writing/keeping-crm-systems-in-sync-with-events/</guid><description>Most sync bugs are ownership arguments nobody had out loud. Settle who owns each field, then move changes through an ordered log.</description><pubDate>Wed, 04 Mar 2026 00:00:00 GMT</pubDate></item><item><title>The pipeline history your CRM doesn&apos;t keep</title><link>https://sfdcace.com/writing/pipeline-snapshots-the-crm-does-not-keep/</link><guid isPermaLink="true">https://sfdcace.com/writing/pipeline-snapshots-the-crm-does-not-keep/</guid><description>A CRM stores the pipeline as it is now, but forecast calls ask what changed. A daily snapshot and day-over-day change facts in the warehouse give the forecast a memory.</description><pubDate>Thu, 19 Feb 2026 00:00:00 GMT</pubDate></item><item><title>Shrinking the blast radius of a coding agent</title><link>https://sfdcace.com/writing/shrinking-a-coding-agents-blast-radius/</link><guid isPermaLink="true">https://sfdcace.com/writing/shrinking-a-coding-agents-blast-radius/</guid><description>If a coding agent&apos;s session leaked tonight, what could someone do with it, and for how long? Five controls that shrink both answers, and what each costs in friction.</description><pubDate>Thu, 05 Feb 2026 00:00:00 GMT</pubDate></item><item><title>A data agent shouldn&apos;t get to guess what revenue means</title><link>https://sfdcace.com/writing/agents-should-not-guess-what-revenue-means/</link><guid isPermaLink="true">https://sfdcace.com/writing/agents-should-not-guess-what-revenue-means/</guid><description>A data agent picks a meaning and sounds sure either way. Make it look up every business term in a small, owned registry before it writes SQL.</description><pubDate>Thu, 22 Jan 2026 00:00:00 GMT</pubDate></item><item><title>Converting CRM automations without changing the order they run in</title><link>https://sfdcace.com/writing/converting-crm-automations-without-changing-the-order/</link><guid isPermaLink="true">https://sfdcace.com/writing/converting-crm-automations-without-changing-the-order/</guid><description>A converted automation usually keeps its logic. Run order, save phase and run-as user are what move, so map every write, replay real saves in two sandboxes and gate on the diff.</description><pubDate>Thu, 08 Jan 2026 00:00:00 GMT</pubDate></item><item><title>Fix your coding agent&apos;s harness before you switch models</title><link>https://sfdcace.com/writing/fix-the-harness-before-switching-models/</link><guid isPermaLink="true">https://sfdcace.com/writing/fix-the-harness-before-switching-models/</guid><description>Before paying for a bigger model, test the harness around your coding agent on your own merged PRs, one change at a time.</description><pubDate>Wed, 17 Dec 2025 00:00:00 GMT</pubDate></item><item><title>Cheap to write, expensive to keep: the data models nobody reads</title><link>https://sfdcace.com/writing/the-data-models-nobody-reads/</link><guid isPermaLink="true">https://sfdcace.com/writing/the-data-models-nobody-reads/</guid><description>A decision brief to merge, a reconcile test to publish, and a usage ledger that retires dbt models nobody reads, judged against each model&apos;s own read cadence.</description><pubDate>Wed, 03 Dec 2025 00:00:00 GMT</pubDate></item><item><title>Analysis of Metadata AppExchange products</title><link>https://sfdcace.com/writing/analysis-of-metadata-appexchange-products/</link><guid isPermaLink="true">https://sfdcace.com/writing/analysis-of-metadata-appexchange-products/</guid><description>Compares three free AppExchange tools for extracting and tracking Salesforce object metadata: EasyDescribe, Object Metadata Snapshot and Config Workbook.</description><pubDate>Fri, 04 Nov 2016 00:00:00 GMT</pubDate></item><item><title>Salesforce SSO Implementation</title><link>https://sfdcace.com/writing/salesforce-sso-implementation/</link><guid isPermaLink="true">https://sfdcace.com/writing/salesforce-sso-implementation/</guid><description>A walkthrough of federated SAML single sign-on for Salesforce: scope, as-is and to-be process, SSO settings, user Federation ID and best practices.</description><pubDate>Fri, 04 Nov 2016 00:00:00 GMT</pubDate></item><item><title>Visualforce Email template with component to render attachment</title><link>https://sfdcace.com/writing/visualforce-email-template-with-component-to-render-attachment/</link><guid isPermaLink="true">https://sfdcace.com/writing/visualforce-email-template-with-component-to-render-attachment/</guid><description>How to build a Visualforce component rendered as a PDF attachment on a Visualforce email template and send it automatically with a workflow rule.</description><pubDate>Thu, 03 Nov 2016 00:00:00 GMT</pubDate></item><item><title>Salesforce Batch class generating results as CSV</title><link>https://sfdcace.com/writing/salesforce-batch-class-generating-results-as-csv/</link><guid isPermaLink="true">https://sfdcace.com/writing/salesforce-batch-class-generating-results-as-csv/</guid><description>A Database.Stateful batch Apex class on Account that collects success and failure records as CSV attachments and emails them from the finish method.</description><pubDate>Mon, 22 Feb 2016 00:00:00 GMT</pubDate></item><item><title>One to One relationship in Salesforce</title><link>https://sfdcace.com/writing/one-to-one-relationship-in-salesforce/</link><guid isPermaLink="true">https://sfdcace.com/writing/one-to-one-relationship-in-salesforce/</guid><description>Shows how to enforce a one to one relationship between two Salesforce objects using configuration only, plus two trigger-based options with sample code.</description><pubDate>Wed, 17 Feb 2016 00:00:00 GMT</pubDate></item><item><title>Difference between Salesforce.com and Force.com</title><link>https://sfdcace.com/writing/difference-between-salesforce-com-and-force-com/</link><guid isPermaLink="true">https://sfdcace.com/writing/difference-between-salesforce-com-and-force-com/</guid><description>A plain-language comparison of Salesforce.com, the SaaS CRM, and Force.com, the PaaS platform it runs on, and what each one offers.</description><pubDate>Wed, 10 Feb 2016 00:00:00 GMT</pubDate></item><item><title>Salesforce Difference between Abstract &amp; Virtual class and Interface</title><link>https://sfdcace.com/writing/salesforce-difference-between-abstract-virtual-class-and-interface/</link><guid isPermaLink="true">https://sfdcace.com/writing/salesforce-difference-between-abstract-virtual-class-and-interface/</guid><description>Explains how Apex interfaces, abstract classes and virtual classes differ, with code examples and the rules for implementing or extending each.</description><pubDate>Fri, 20 Feb 2015 00:00:00 GMT</pubDate></item></channel></rss>