Over the past few months, I’ve been spending a lot of time getting to know people working in what is broadly being called AI-assisted process development.
That phrase alone gives you a sense of the challenge. It can mean so many different things, depending on who you talk to. For some, it’s automation using existing tools. For others, it’s building custom applications. For others again, it’s strategy, data, security, or integration across systems.
And that’s exactly why I’ve been leaning into building relationships rather than trying to solve everything myself.
A Familiar Feeling
Interestingly, this all feels very familiar.
I’m reminded of the early days of web development — when businesses knew they probably needed a website, but had very little clarity on what “good” looked like. There were no real qualifications, pricing varied wildly, and it was surprisingly easy to spend a lot of money without getting meaningful results.
There was also a lot of noise. Everyone had an opinion. Everyone sounded confident. And it wasn’t always easy to tell what was right, what was hype, and who to trust.
AI feels quite similar right now.
It’s early. It’s moving quickly. And while there is real value available, there is also a real risk of going down the wrong path, overinvesting too soon, or building something that doesn’t actually solve the problem.
Why I’m Not Doing This Alone
One of the things I’ve become very clear on is that this is not an area to try to cover on your own.
Even within my own work — where process improvement and systems are a core focus — the technical depth, range of tools, and pace of change means it’s far more effective to work alongside specialists.
That’s led me to focus on building a small, trusted network of people who I can confidently bring into the right situation.
What matters to me is not just capability, but fit. Do they understand real business workflows? Can they communicate clearly? Are they realistic about what is possible and what is not?
What I’m Seeing Locally
One of the more encouraging aspects of this journey has been discovering just how much capability exists locally.
Through my BNI network, I’ve connected with someone who is both technically capable and, importantly, proven to be trustworthy. Their model is practical — working on a set monthly basis to gradually build solutions over time, rather than trying to do everything upfront. That structure feels well suited to a space that is still evolving.
I’ve already recommended them to a local trades business that is growing quickly but struggling with the day-to-day load of emails and quoting. The suspicion — and it’s still a working hypothesis — is that AI will be able to take on a significant portion of that workload with the right design and oversight.
What also stood out with this contact is the breadth of knowledge. Alongside AI-assisted development, they also work with tools like HubSpot and Zapier, which are often part of the bigger picture. After searching for a solid HubSpot contact for quite some time, that alone was a valuable connection. They are even offering a free HubSpot review, which is a low-risk way for businesses to start exploring what’s possible.
Beyond that, I’ve met others working at very different ends of the spectrum.
One has worked at a high government level and brings a much stronger focus on strategy, structure, and security — the kind of thinking that becomes critical as organisations grow or deal with more sensitive data. Interestingly, they work primarily in environments like Claude Code rather than the more familiar user interfaces many of us are starting with.
Another local business has built a rapidly growing team in this space but doesn’t actively advertise their AI process work. They simply don’t need to. Demand from existing clients is already enough to keep them busy. They come from a CRM and systems background (particularly Zoho), which is often where these process improvements naturally start.
There are others again who sit closer to the IT and Microsoft ecosystem, where tools like Copilot are starting to change how everyday work gets done. Their focus is less about building from scratch and more about improving efficiency within tools businesses are already using.
And then there are smaller, highly specialised operators — including one local contact focused on helping small businesses and individuals build practical solutions using tools like the Claude web interface, particularly in marketing contexts.
Even looking slightly further afield, I’m seeing similar patterns. Teams that started in websites or CRM are now pivoting toward AI-assisted process solutions, simply because that’s where the demand is shifting.
What This Means in Practice
All of this reinforces one key point for me.
There is no single “AI solution.”
What matters is understanding the problem first, then matching it to the right approach — and the right person.
In some cases, that might be light automation inside existing systems. In others, it might be a custom-built process. In others again, it might simply be better use of tools already in place.
The risk comes when those distinctions are not clear.
A Practical Role Going Forward
For my part, I’m becoming increasingly comfortable with the role I naturally sit in.
Not as the person building everything, but as the one who understands the business processes, asks the right questions, and connects the client with the right specialist at the right time.
If that helps avoid a poor decision, wasted spend, or a solution that looks good on the surface but doesn’t actually work in practice, then that’s already a valuable outcome.
There is still a lot to learn. Many more conversations to have. And no doubt a few wrong turns along the way.
But I do feel confident about one thing.
Building the right relationships now will make a significant difference — not just in what is possible, but in making sure it is done well.