What Finishing a Contract Reminded Me About Consultancy

Last Friday marked the end of my contract with Motorway.

Ending a contract is always a slightly strange moment. One day you are deep inside the context, the systems, the meetings, the acronyms, the Slack channels, the odd bits of business logic that only make sense once someone explains the historical scar tissue behind them. Then suddenly you are handing things over, closing tabs, and stepping back out of that world.

Over the past few months, I worked as a consultant within the Payments team, helping deliver new payment capabilities and integrations in a complex, business-critical part of the platform.

Payments work has a way of keeping everyone honest. It is not the place for vibes. Money moving through systems tends to have very little patience for “probably fine”.

Good consultancy is not just writing code

The technical part matters, obviously. You need to understand the systems, make good engineering decisions, deliver reliable software, and not create a new problem disguised as a solution. A bold strategy, I know.

But consultancy, at least when it is done properly, is not just parachuting in to write code and disappear.

It is understanding the business domain quickly. It is learning why the process works the way it does, even when the first instinct is to call it mad and replace half of it. It is working with engineers, product managers, stakeholders, support teams and anyone else who has part of the picture.

The job is to create useful outcomes, not just technically satisfying artefacts.

That distinction matters. A clean implementation that misses the business reality is not a good solution. A clever abstraction that nobody can maintain is not a gift. A fast delivery that leaves confusion behind is just technical debt with a nicer hat on.

The best feedback is specific

One of the highlights of the engagement was receiving a recommendation from Mark McCracken, the team leader of the Mobilize project.

He recognised my ability to understand complex business domains quickly, collaborate across teams, deliver high-quality software at pace, and keep looking for ways to improve how the work happened.

That kind of feedback means a lot because it points at the work behind the work.

Not just “Brad wrote some code”. More that I was able to get into the messy middle of a real business problem, understand what mattered, and help move it forward without needing everything to be perfectly neat first.

That is the kind of consultancy I enjoy. Technical enough to be challenging, practical enough to matter, and close enough to the business that the work does not disappear into a backlog-shaped void.

On to the next challenge

I am grateful to everyone in the Mobilize team and across Motorway. It was a pleasure working with talented people inside a platform where the work mattered and the problems were real.

Now the focus shifts again.

I will continue with consultancy, but I am also investing more time into building my own AI products. That balance feels right at the moment: stay close to real business problems, keep delivering useful work, and use what I learn to build better products of my own.

Consultancy gives you a front-row seat to how businesses actually operate. Product building gives you the chance to turn those patterns into something scalable.

The trick, as usual, is doing both without making a complete mess of your calendar.

On to the next challenge.

Draft adapted from Brad’s LinkedIn post from 2026-06-29. Source: LinkedIn post.