Your technology is strong. I help shape it into something the market clearly understands, adopts, and pays for.

Many technical teams build impressive products but struggle to align product decisions with real customer behaviour and commercial priorities.

Teams often continue investing in features and capabilities without enough clarity around what customers actually value, what drives adoption, or where friction exists in the product experience.

Over time, this can lead to slow adoption, unclear priorities, and engineering effort being spread across too many directions. My role is to help teams work out what's actually worth building and why, before more engineering effort goes in the wrong direction.

In most engineering-led teams, roadmap chaos starts when customer requests begin to directly drive sprint priorities without a clear product layer in between.

Individual requests feel urgent, one-off builds accumulate, and over time the roadmap becomes reactive rather than intentional. The team is always busy but progress feels scattered.

The underlying issue is rarely poor engineering. It is usually the absence of clear commercial and customer thinking around what to build, for whom, and why. Until there's a clear framework for what gets built, every request feels equally urgent because nothing has been prioritised against anything that actually matters.

I don't add process. I help teams make better decisions with what they already know.

In practice that means grounding priorities in what customers actually do and what they'll pay for, rather than in whoever asked most recently.

The team keeps working the way it already works. What changes is that people can see why something is on the roadmap, so fewer priorities get reshuffled mid-sprint.

Custom work rarely feels like a problem until it suddenly is. It happens gradually as customer requests begin shaping engineering priorities. Over time, the roadmap becomes reactive rather than intentional.

The goal is not to stop listening to customers. It is to identify the repeatable problems underneath individual requests, then organise development around those patterns rather than one-off implementations.

That usually starts by separating: • what is genuinely unique to a customer • from what could become reusable product capability

I look for patterns across customer behaviour, operational problems, and engineering effort.

The important question is rarely "what features are customers asking for?" It is usually: • which problems keep appearing • which workflows repeat • where engineering keeps solving similar things in slightly different ways • and whether the value extends beyond a single deployment.

Often what's worth turning into something scalable is already hidden inside the customer work. It just has not yet been framed, prioritised, or packaged that way.

I've spent much of my career working with highly technical products including spatial computing, AI, IoT, and developer-focused platforms.

I've always worked closely with the engineers building those products, so I've seen how product decisions land with the people who have to act on them. That shapes how I work. I don't rewrite tickets or add meetings for the sake of it. I take on the customer conversations and commercial questions that otherwise land on engineers, and make sure the team knows why they're building what they're building.

Depending on the situation, that can be a day a week alongside the founders or a closer working relationship with the whole team.

Plenty of the founders I work with do product and want to keep doing it. That's usually the right call, because nobody knows the technology or the customers better than you do.

In that case I don't take product off you. I take on the work around it, such as talking to customers, working out what keeps coming up, and turning your decisions into a roadmap the team can follow. You keep making the calls, with more time and better information to make them.

Other founders are ready to step back from day to day product and spend their time on the business. Then I do the product work itself, and you get someone you can hand it to without losing the thinking behind it.

It's a fair reaction. Most engineers have worked with a product person who added meetings and second-guessed their decisions, and they don't want another one.

I spend the first weeks understanding what the team has already built and why, before suggesting anything. What engineers usually notice first is fewer changes of direction and fewer customer requests landing on them directly.

If it helps, I'm happy to talk to your technical co-founder or lead engineer before we agree anything.

Absolutely. Most of my clients are based outside Ireland. I have worked with teams across Europe, the US, and the UK, working remotely and fitting around their team's working hours and routines. Wherever you are, get in touch.

Working with me on a fractional basis means you get senior product leadership part time, rather than hiring a full-time executive. Some people call this a fractional CPO. At most of the companies I work with, I'm simply the first product person they've had.

Unlike a consultant, I don't write you a report and leave you to implement it. I work inside your team.

I help you clarify product direction, test how your technology resonates with the market, and bring structure and momentum to product decisions.

Because the role is fractional, companies get experienced product leadership without the cost or commitment of a permanent hire. Working part time keeps it affordable, and it means I'm never around enough to get in anyone's way. Most engagements range from a few days per month to a few days per week depending on the stage of the company and the challenges it's facing.