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 1–4 of 4 in discovery
Why we spend a whole week on discovery before quoting
The two-week discovery sprint isn't a sales tactic. It's the only honest way to estimate a bespoke software project — and the reason our final invoices are within 10% of our estimates.
Read post
Build vs buy: the question we get asked the most
After 20 years of these conversations, here's the honest framework we use to help businesses decide whether to build something bespoke or live with off-the-shelf software.
Read post
The most useful sentence in any discovery
The companion piece to the Tuesday-morning post — the actual craft of getting people to tell you what's really going on. Anchored in a real story about a warehouse picker, a print button that logged her out, and a twenty-minute fix that earned us more trust than any deliverable.
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.