In short

Product strategy is the work of deciding what to build, for whom and in what order, before any code is written. At Fat Elephant it covers discovery, user research, roadmapping and MVP planning, and it ends with a plan the same team can build.

What We Do

What we do: Product Strategy

Six pieces of work, used together or on their own. Most projects start with the first two and finish with the last.

Product discovery workshops

Short, focused sessions with your team where we pull the idea apart: who it is for, what problem it solves and what has to be true for it to work. You leave with shared language and a short list of the riskiest assumptions, not a binder nobody opens.

User and market research

We talk to the people you want to serve and look honestly at what already exists. The aim is to find out early whether the problem is real, how people cope today and where existing products leave a gap.

Product roadmapping

A roadmap that says what comes first, what comes later and what we are deliberately not doing. We write it in plain language, so a founder, an investor and an engineer can all read the same page and agree on it.

Feature prioritisation

Every idea arrives with a long wish list. We rank features by the value they give users and the effort they cost, then cut until what is left can actually ship. Small and true beats big and hollow.

Technical feasibility

Our engineers look at the plan early. We flag what is hard, what is cheap, what needs a third party and what could turn into a trap, so the roadmap matches what can really be built.

MVP planning

We turn the shortlist into a scoped MVP: the smallest version that tests your main assumption with real users. It comes with a build plan, so the next step is clear and the first version can start moving.

The Process

How it works

Three phases, one team, no handoffs lost in translation. The people who scope the work are the people who build it.

  1. Discover

    We start by listening. Workshops and research with your team and your future users, so we understand the problem properly before we touch a solution. Honest feedback on your idea beats polite silence, even when it is not what you were hoping to hear.

  2. Define

    We turn what we heard into decisions: who the product is for, what it does first, what it leaves out and what could stop it working. Meetings end with decisions, not homework.

  3. Plan the MVP

    We scope the first version, check it with our engineers and write the plan down. You leave with something you can act on straight away, whether the next step is building, testing with users or talking to investors.

Honest Fit

Who it's for, and who it isn't

A good fit if you are

  • Founders with an idea and no technical team yet
  • Teams with a long wish list and no clear first version
  • Companies adding a new product who want to test before they invest
  • Anyone who would rather learn early than build the wrong thing

Probably not for

  • Teams that want a polished deck and don't plan to act on it
  • Projects where the scope is already fixed and just needs building. For that, head straight to our Engineering work
  • Anyone looking for a promise of success. We'll tell you when the smaller version is the right version, and sometimes that the idea needs more work
FAQ

Questions we get asked

What is an MVP?

A minimum viable product is the smallest version of your product that lets real users do the one thing it exists for. It lets you learn whether the idea works before you invest in everything else.

Do we need a finished idea before we start?

No. A rough idea and a clear sense of the problem are enough. Discovery is where we sharpen the idea, test it and decide what the first version should be.

Who needs to be involved from our side?

You, and anyone who can make decisions about the product. Because the people who scope the work are the people who build it, you are not passed between teams or asked to explain the idea again.

Can you keep working with us after the strategy phase?

Yes. The plan is written so design and engineering can start straight away, and our team can carry on from there if you want us to.

How is this different from a strategy deck from a consultancy?

Our strategy work is built to be used. It ends in a scoped MVP and a build plan, not a slide deck, and the engineers who check feasibility are the same people who may end up building it.

How long does it take, and what does it cost?

It depends on the size of the idea and how much research it needs. Tell us what you are trying to build and we will suggest the right starting point, with a clear scope agreed before any work begins.

Have an idea worth building?

Tell us what you are trying to build, and we will suggest the right place to start.