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–2 of 2 in philosophy
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 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.