<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Gayle Nelson</title>
<link>https://gayle-nelson.com</link>
<atom:link href="https://gayle-nelson.com/feed.xml" rel="self" type="application/rss+xml"/>
<description>Essays on ERP architecture and finance systems by Gayle Nelson, CPA.</description>
<language>en-us</language>
<item>
<title>You Don&#x27;t Get a Mulligan: How to Choose the Firm That Will Implement Your ERP</title>
<link>https://gayle-nelson.com/writing/choosing-an-erp-implementation-partner</link>
<guid isPermaLink="true">https://gayle-nelson.com/writing/choosing-an-erp-implementation-partner</guid>
<description>Companies spend months evaluating ERP software and a few weeks evaluating the firm that will implement it. That is backwards.</description>
<dc:creator>Gayle Nelson</dc:creator>
</item><item>
<title>Automating Crap Is Still Crap: What a CFO Should Actually Do About AI</title>
<link>https://gayle-nelson.com/writing/what-a-cfo-should-do-about-ai</link>
<guid isPermaLink="true">https://gayle-nelson.com/writing/what-a-cfo-should-do-about-ai</guid>
<description>Boards are demanding an AI strategy. Finance teams are buying tools that sit unused. The sequence that works is unglamorous and it is not optional.</description>
<dc:creator>Gayle Nelson</dc:creator>
</item><item>
<title>The Devil Is in the Data: Why Integrations Fail Before They Are Built</title>
<link>https://gayle-nelson.com/writing/why-integrations-fail-before-they-are-built</link>
<guid isPermaLink="true">https://gayle-nelson.com/writing/why-integrations-fail-before-they-are-built</guid>
<description>Integrations don&#x27;t break on the software. They break on master data and on the order you load it in.</description>
<dc:creator>Gayle Nelson</dc:creator>
</item><item>
<title>Design Backwards From the General Ledger</title>
<link>https://gayle-nelson.com/writing/design-backwards-from-the-general-ledger</link>
<guid isPermaLink="true">https://gayle-nelson.com/writing/design-backwards-from-the-general-ledger</guid>
<description>Decide what has to hit the GL, when, and at what level of detail. Then architect every upstream system to deliver exactly that.</description>
<dc:creator>Gayle Nelson</dc:creator>
</item><item>
<title>The Operator Test: Your Consultant Should Have Done Your Job</title>
<link>https://gayle-nelson.com/writing/the-operator-test</link>
<guid isPermaLink="true">https://gayle-nelson.com/writing/the-operator-test</guid>
<description>Platform expertise is table stakes. The question is whether the person designing your revenue recognition has ever survived a month-end close.</description>
<dc:creator>Gayle Nelson</dc:creator>
</item><item>
<title>Wanting a New System and Being Ready for One Are Different Things</title>
<link>https://gayle-nelson.com/writing/ready-for-an-erp-implementation</link>
<guid isPermaLink="true">https://gayle-nelson.com/writing/ready-for-an-erp-implementation</guid>
<description>Three signals tell me whether a company will actually finish an ERP implementation. Missing one is the reason most projects stall, not the software.</description>
<dc:creator>Gayle Nelson</dc:creator>
</item><item>
<title>Everyone Has Admin Access: How Companies Quietly Break the System They Just Bought</title>
<link>https://gayle-nelson.com/writing/everyone-has-admin-access</link>
<guid isPermaLink="true">https://gayle-nelson.com/writing/everyone-has-admin-access</guid>
<description>Most ERP damage happens after go-live, from the inside — over-provisioned access and ungoverned configuration changes. The fix is a permissions model and a change process.</description>
<dc:creator>Gayle Nelson</dc:creator>
</item><item>
<title>Scale Without the Swivel Chair: The Case Against One Platform to Rule Them All</title>
<link>https://gayle-nelson.com/writing/scale-without-the-swivel-chair</link>
<guid isPermaLink="true">https://gayle-nelson.com/writing/scale-without-the-swivel-chair</guid>
<description>Best-of-breed beat the all-in-one platform. But the win only holds if you enforce one rule: enter data once, then let it flow downstream.</description>
<dc:creator>Gayle Nelson</dc:creator>
</item>
</channel>
</rss>