Topic
Software and integration
Build against buy, integration that survives both ends changing, automation designed around the exception, and system selection.
7 articles
AI that acts, not just answers
An assistant that drafts is one thing. An agent that sends the email, updates the record or raises the purchase order is another, and the question stops being whether its output is good and becomes what it is allowed to do on its own.
Read it →
System selection when every vendor demos well
Demonstrations are performed by people who know the software, using data chosen to suit it. Judging a system on one is like judging a car by watching someone else drive it around a car park.
Read it →
Why everyone still exports to Excel
You implemented an ERP with reporting built in, and the finance team still exports to a spreadsheet every month. That is not resistance to change. It is feedback.
Read it →
What "we will integrate it" actually costs
Integration is quoted as a task and behaves like a relationship. The build is the cheap part; the price is paid every time either system changes.
Read it →
Automation that survives contact with the exception
The happy path is the easy part. What decides whether an automation is still running in a year is what it does when the input is wrong, and whether anybody finds out.
Read it →
Build or buy, and the honest test between them
We write software, so treat our answer with suspicion. The test we use is whether the process is a genuine competitive difference or just the way you happen to do something ordinary.
Read it →
When the stock figure depends on which screen you are looking at
Most businesses running several systems do not have a data problem so much as a disagreement problem. Everyone has quietly learned which screen to trust, and that knowledge is not written down anywhere.
Read it →
Next step
Recognise any of this? Let's talk.
We respond within one business day.