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 process
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
Built for your Tuesday morning
On why software for businesses needs to be built by people who've felt what it's like when the system isn't there. Not a snipe at developer culture — an observation about whose Tuesday morning the software actually has to survive.
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
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 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.