Tom Hundley
Part 1 of 3
The AI is the easy part. The SOAP API from 2008 is the hard part.
In Silicon Valley demos, data lives in clean JSON files or modern Postgres databases.
In the mid-market, data lives in:
If your AI strategy doesnt account for Legacy Integration, you dont have a strategy. You have a toy.
Do not let the AI touch the legacy production database directly.
Legacy APIs are often SOAP, XML, or weird proprietary formats. LLMs hate XML.
Sometimes there is NO API. The only way in is a Windows GUI.
Dont wait for your legacy systems to be modernized before adopting AI. You will be waiting forever. Build the bridges instead.
This article is a live example of the AI-enabled content workflow we build for clients.
| Stage | Who | What |
|---|---|---|
| Research | Claude Opus 4.5 | Analyzed current industry data, studies, and expert sources |
| Curation | Tom Hundley | Directed focus, validated relevance, ensured strategic alignment |
| Drafting | Claude Opus 4.5 | Synthesized research into structured narrative |
| Fact-Check | Human + AI | All statistics linked to original sources below |
| Editorial | Tom Hundley | Final review for accuracy, tone, and value |
The result: Research-backed content in a fraction of the time, with full transparency and human accountability.
Were an AI enablement company. It would be strange if we didnt use AI to create content. But more importantly, we believe the future of professional content isnt AI vs. Human—its AI amplifying human expertise.
Every article we publish demonstrates the same workflow we help clients implement: AI handles the heavy lifting of research and drafting, humans provide direction, judgment, and accountability.
Want to build this capability for your team? Lets talk about AI enablement →
Discover more content:
