August 2026

After a couple crazy weeks of travel, I’m settled back in Suffolk, with my Beach Buggy, for a bit of rest before IMTS. The only way I’ve been able to stay on top of what’s going on in the big project I alluded to is with an internal development I led. 

I’ve been experimenting with vibe-coding for a while and have created dozens of tools – some more helpful than others. But this one takes the cake, primarily because it builds on a tool I’ve spoken about before: Whisper.

In the background, Whisper collects all the information that matters. In this case, that’s: Slack, email, documents, development tickets (we use Shortcut), and conversations on Threads. It then makes that data available to queries using any Large Language Model. 

The project we’re running has more than a dozen artefacts that it has to keep up to date: Risk Matrix, Issue and Change Logs, Action list, Stakeholder and Dependency Registers etc. What I’ve now built is a Control Tower that links those artefacts with the underlying data that Whisper unearths. It then makes suggestions on how those artefacts need to be updated: Add an action, update the due date, update the completion score, etc. 

That means I have updated artefacts whenever they’re needed, not least when it’s time to get paid 🤑 The tool can also create reports or meeting agendas based on templates I’ve created

I won’t be running the project for much longer (others are taking over) but at least now I have a single point to check that all is as it should be (or not). 

What I’ve built here isn’t unique. It’s just one of many effectors that people are building on top of Whisper data. Unlocking that data is the crux. We believe it will help in hundreds of situations: Technical Data Package generation, CRM updates, intent capture, even in maintenance. 

Maybe on reading this the team will hook Whisper up to our new Equipment Maintenance Module. That’s made some amazing final progress this month (see below), but wouldn’t it be cool if a sidebar conversation about a defect automatically identified the fault and led to a maintenance event being scheduled? 

That’s just one of the things I’ll be talking about on stage at IMTS. If you’ll be there, ping me! 

See you in Chicago!