Insights
Senior thinking on building and connecting systems.
Practical writing on software architecture, systems integration, automation and the enterprise platforms underneath them — written by the people who do the work, not by a content team.
Why finance integrations fail after go-live — and how to spot it early
Most integration failures aren't caused by bad code — they're caused by assumptions that held during testing but quietly broke in production. Here's what to watch for.
The hidden cost of the gap between finance, IT, and your vendors
When something breaks between systems, every party has a plausible explanation for why it's someone else's problem. The cost of that gap is real — and it's usually borne by finance.
A practical framework for AP automation that actually holds up
AP automation is one of the highest-ROI investments a finance team can make — and one of the most common sources of integration failures. The difference is usually in how you handle the exceptions.
Master data: the quiet root cause of most integration failures
Bad vendor records, inconsistent cost centers, duplicate supplier IDs — master data problems don't announce themselves. They just make everything downstream slightly, persistently wrong.
Build vs. buy vs. integrate: choosing the right finance system path
The question finance teams face most often isn't which system to buy — it's what to do with the systems they already have. Here's a framework for making that decision clearly.
What "integration reliability" really means (and how to measure it)
Reliability isn't the same as uptime. An integration can run every day and still be unreliable. Here's what actually matters — and how to know if you have it.
When to rescue an integration vs. rebuild it
The instinct when something is broken is often to replace it. Sometimes that's right. More often, a targeted rescue is faster, cheaper, and less disruptive — if you know what you're looking at.
Giving finance leaders real visibility into operational controls
Most finance dashboards show outputs — balances, totals, variances. What they rarely show is whether the processes producing those outputs are working correctly. That's the visibility gap that matters.
Dealing with something like this?
If any of this matches a problem you are working on, a senior engineer will give you a straight read on it — no obligation and no sales sequence.