What do I do about my legacy APIs?

Dear Uncle Bill,

I’m the IT manager at a mid-sized CPG company. Over the past decade, our production systems have expanded significantly - starting with our ERP system, and now including Commerce, Supply Chain Management (SCM), Human Capital Management (HCM), and an EDI solution. Each of these systems requires APIs to exchange data. However, each integration was implemented using custom code at the time, and we now face a major challenge: there are no consistent standards for the code, security, or performance across these APIs.

My team has been maintaining these integrations individually, and most of them remain undocumented. Compounding the issue, we’ve developed a range of additional APIs over the years to accommodate our customers and vendors, which has only increased the complexity. I now see this as a serious “business continuity risk” due to the lack of transparency, scalability, and security.

I need to approach our CFO to request funding for a solution that can standardize, secure, and streamline our API management. However, I’m unsure of the most effective solution or how to frame this request in a way that will clearly demonstrate the urgency and long-term value. Could you offer some guidance or talking points to help me present this to leadership?

Best regards,?

Hard-Coding in Des Moines, IA

?

Dear Hard-Coding in Des Moines, IA,

First off, congratulations on building a digital spaghetti monster! It sounds like your API architecture has evolved into its own chaotic universe, fueled by custom code and the wild energy of just-get-it-done development. But now, it’s time to pull the ripcord before it becomes a business continuity issue of mythic proportions.

Here’s how to pitch it to your CFO—because let’s face it, they need to understand why this is more urgent than upgrading to the latest model of espresso machine.

1. Present the Risk Like a True CFO Whisperer

?? CFOs are allergic to risk, and lucky for you, that’s your lead argument. Frame the issue as a business continuity threat. Explain that this house-of-cards API strategy is one minor failure away from a complete collapse. Highlight the lack of documentation, making it clear that if your key developers were to leave (or get abducted by aliens), you’d be stuck with a system no one understands. This is the digital equivalent of keeping your passwords on sticky notes—minus the charm.

2. Performance and Scalability Concerns

?Custom code works like a charm...until it doesn’t. Over time, as your API ecosystem has expanded, the cracks have likely begun to show in performance and scalability. System slowdowns, failed integrations, and bottlenecks are signs your digital duct tape is peeling. Explain that by centralizing your APIs with a modern solution, the business can support growth, reduce downtime, and improve operational efficiency.

?3. Security: The Silent (but Dangerous) Time Bomb

?You’ll want to emphasize that security standards are a patchwork, leaving your system vulnerable to cyberattacks. Custom code can leave behind gaping holes for hackers to waltz through. And with compliance mandates tightening up (thanks, regulators!), the risk of a data breach or failing an audit can lead to huge financial penalties. How would you like to explain that to the board? is the question you leave hanging in the air.

4. The Tech Debt Analogy

?Describe your current system as technical debt - the coding equivalent of putting off cleaning your garage. Sure, it works for now, but over time, the costs of maintaining it only increase. Centralizing API management would be like a one-time spring cleaning, rather than a constant struggle against digital entropy.

5. Modern Solutions That Solve These Problems

?Now that you’ve scared the CFO sufficiently, drop in the solution. Mention API management platforms like Azure API Management, Apigee (Google Cloud), MuleSoft (Salesforce) or Boomi. These platforms offer standardized methods for connecting systems, providing centralized monitoring, security protocols, and performance management. They also make life easier with features like “automated documentation” and “scalable architecture”. No more custom code nightmares, just a clear, manageable framework.

6. ROI: The Magic Words

?? It’s time to talk dollars. API management platforms provide cost savings in the long term by reducing the labor hours spent on patchwork fixes and increasing efficiency. Not to mention, it minimizes downtime that could disrupt business operations—another CFO nightmare. You could frame it as a strategic investment, emphasizing that while there’s an upfront cost, it will prevent future headaches and pave the way for scalability and agility.

Bonus Tip:

?Throw in some humor! When discussing the undocumented APIs, maybe say something like, "Right now, we’re a resignation letter away from being an unsolvable mystery. It’s like a real-life episode of ‘CSI: Code Edition’ - except no one wins."

Ultimately, frame it as the way forward. Tell the CFO that investing in API governance and standardization isn’t just about avoiding disaster, it’s about future-proofing the company for the next decade of growth.

Good luck! And remember, when it comes to untangling tech messes, even digital spaghetti is better served with structure.

Warm regards,?

Uncle Bill