Skip to content
Neurally

For product and technology leaders.From AI features to an AI-era product organisation.

You are being asked for an AI roadmap, a faster team and a view on every vendor, all at once. The useful question underneath is how the product organisation should work now, and what it should build first.

If you run product or technology, this is probably your week.

  • “The CEO wants an AI strategy. I have forty ideas and no order.”
  • “My engineers are faster. My roadmap isn't.”
  • “Every squad is experimenting. Nothing is joined up and nobody is measuring.”
  • “I need someone senior who has done this, for six months, not a slide deck.”

Faster engineers, same roadmap

It is common now for a product organisation to report that individuals are quicker and that delivery feels about the same. Both can be true, because writing code was rarely the constraint. Deciding what to build, agreeing it across functions and getting it safely to customers were.

So the gain from AI in a product organisation depends on redesigning the lifecycle around it: how discovery runs, where decisions are made, what a team needs to hand off and what it no longer does. Stuart led that redesign in-house before starting Neurally, and it is the work he is most often asked about.

The decisions on your desk.

  1. 01

    What to build first, and why

    A short list of AI bets ranked by what they would earn or save, each with a value case, assumptions and the measures it will be judged by.

  2. 02

    How the product lifecycle changes

    Discovery, design and delivery look different with AI in the toolkit. Decide the new lifecycle on purpose, including what stays with product managers, designers and engineers.

  3. 03

    Which functions you need

    Whether to stand up a Product AI or Product Operations function, what each owns, and how roadmaps, commitments and dependencies become visible in one place.

  4. 04

    Who builds it

    Your own teams, a partner or both. We help you choose and brief build partners and write pilot specifications and acceptance criteria.

What tends to go wrong.

  • Tool adoption mistaken for transformation

    Coding assistants raise individual output. Without a change in how work moves through the organisation, customers see little of it.

  • A roadmap of features with no owner for the result

    Things ship. Nobody is accountable for whether they moved revenue, retention or cost.

  • Pilots that never end

    Without agreed success measures and a proceed, adapt or stop decision, a pilot becomes a permanent experiment.

How the four stages apply to a product organisation.

  1. Stage 01

    Decide

    Rank the opportunities across product and the organisation. Put a value case and measures behind the few worth funding.

  2. Stage 02

    Design

    Redesign the lifecycle, the roles and the decision rights. Define the functions and the operating rhythm.

  3. Stage 03

    Deliver

    Specify pilots, brief partners and work alongside product and engineering on first releases.

  4. Stage 04

    Embed

    Name owners, train teams on the new lifecycle, and track value until your leaders run it.

Where this comes from.

50%
reduction in discovery-to-development time reported after the product lifecycle was redesigned around AICompare the Market, before Neurally
~50
people given a single view of roadmaps, commitments and dependencies by new Product AI and Product Operations functionsCompare the Market, before Neurally
46
people led across London, Warsaw and Kosovo, with profit-and-loss accountabilityFresha, before Neurally

These are outcomes from roles Stuart held before founding Neurally. They are not Neurally client results, and the wider commercial figures reflect the work of whole teams, not AI alone.

Start with a week on the area under most pressure.

The Diagnostic looks at one or two priority areas, such as your product-development lifecycle or a single product line. You get prioritised opportunities, an initial value hypothesis with its assumptions, a readiness, risk and dependency view, and a recommended next step. If what you need is a senior owner for the change, Transformation Leadership provides one for a fixed term.

Engagement 02

AI Advantage Diagnostic

£6,0001 week

  • Prioritised opportunities for the areas in scope
  • An initial value hypothesis, with its assumptions stated
  • A readiness, risk and dependency view
  • A recommended next step

Also worth a look: Transformation Leadership (quoted after scoping).

Questions we hear.From this seat.

Are you a peer or a consultant?

A peer who now advises. Stuart was Head of Product for Data, AI, Apps and Operations at Compare the Market and Head of Product for Banking and Payments at Fresha. He has run the function you run.

Can you join as a fractional or interim leader?

Yes. Transformation Leadership is embedded, fractional or interim leadership of the change, for a fixed term, typically three to six months, and a fixed outcome. It ends with capability handed to your team.

What was the 50% figure?

At Compare the Market, a 50% reduction in discovery-to-development time was reported for the product lifecycle after it was redesigned around AI. It is a reported outcome from a role Stuart held before Neurally, not a promise about your organisation.

Will you tell us which model or vendor to use?

We help you choose and brief partners and have no commercial tie to any of them. The choice follows from the work you have decided to do.

Do you work with the CEO or with me?

Either. Product and technology leaders are a first-class buyer. The work goes better when the CEO sponsors it, and scoping confirms that before any fee.

Start with a conversation.Thirty minutes, free.

Tell us what you are trying to decide. If we can help, we will say how and what it would cost. If we can't, we will say that too.