On discovery, back offices, and where AI actually helps.
We don’t publish often — only when there’s something concrete to say. What’s here tends to cluster around a few threads: finding out what to build before anyone writes code, putting AI inside real workflows (inboxes, order desks, quotes), connecting the systems you already pay for, and the build-or-buy calls operators face every month. Written for people who run the work, not for developers chasing trends.
Showing 7–8 of 8 in strategy
If what you're doing is repetitive, there is a better way
The biggest cost in most businesses is people — and too much of their time goes on moving data between systems. Automation isn't usually about cutting headcount; it's about not needing to hire another three people when you grow.
Read post
You vibe-coded a prototype. Now it has to work on a Tuesday morning.
What happens when the thing you built on an AI coding site needs to plug into Xero, survive real users, and not fall over in March. How to decide whether to fix, integrate, or rebuild — without throwing away what you learned.
Read postLet’s talk about your back office
Start with a free 30-minute discovery call. No slides, no sales pitch; just a real conversation about where your business is and where it could be.