TINMUG

Product thinking. Useful by design. Things that ship.

Simple. Useful. Ready for whatever needs solving.

Sound familiar?

Problems teams bring us, and what we’d do about them.

  • Product Consulting

    We built our app with AI. None of us is a product person.

    What we’d do

    Review it the way a new user meets it: the value proposition, the UX and the UI, screen by screen.

    What you get

    A prioritised list of improvements, clear enough to hand straight to your AI tools.

  • Product Building

    Our business works. We know AI could make one part of it much better.

    What we’d do

    Pick the part where AI pays off first, design it with the people who do that work and build it into the tools you already use.

    What you get

    One part of the business running better with AI, and a team that knows how to use it.

  • Product Consulting

    People sign up, then never come back.

    What we’d do

    Find the exact moment new users stall, talk to the ones who left and test small changes to the first steps.

    What you get

    A clear picture of where the value gets lost, and fixes ranked by impact.

  • Product Building

    We have an idea. And a deck. That’s it.

    What we’d do

    Turn it into a working prototype and put it in front of real users in weeks, not quarters.

    What you get

    Proof before budget. Something to test instead of something to argue about.

  • Product Consulting

    The roadmap is full, but nobody can say why.

    What we’d do

    Trace each item back to evidence, flag the bets with nothing behind them and reframe the plan around the problems that matter.

    What you get

    A roadmap you can defend, with the evidence to back it.

  • Product Building

    We want an AI agent for our customers. Not a chatbot that embarrasses us.

    What we’d do

    Define what the agent should and shouldn’t do, prototype it on real conversations and test it before any customer sees it.

    What you get

    An agent that actually helps, with clear limits and evidence that it works.

  • Product Consulting

    We have tons of data and no answers.

    What we’d do

    Pick the few questions that matter, set up the metrics that answer them and pair the numbers with real conversations.

    What you get

    Metrics the team actually uses to decide.

  • Product Building

    We need an internal tool, and IT’s queue is a year long.

    What we’d do

    Build it with AI-native tools in weeks, test it with the people who will use it and hand it over documented.

    What you get

    A working tool your team uses, without waiting for the roadmap.

  • Product Consulting

    Every release takes months, and we still don’t know if it works.

    What we’d do

    Find the riskiest assumption behind the release, test it with users in days and cut the scope to what the evidence supports.

    What you get

    Shorter cycles, and a clear call on what to build next.

  • Workshops & Training

    The team wants to talk to users, but doesn’t know how.

    What we’d do

    Run hands-on training on your own product, with real interviews and tests from day one.

    What you get

    A team that runs its own research after we leave.

  • Workshops & Training

    We need a talk people actually remember.

    What we’d do

    Shape a hands-on session around your audience, with real cases from product, research and AI.

    What you get

    A talk people bring up afterwards, and ideas they can use on Monday.

  • Not on the list?

    Bring the problem anyway. That’s what the first call is for.

How we work

  1. Talk

    Bring the problem, not the brief.

  2. Read

    Talk to users, look at behaviour and find the signal behind the assumptions.

  3. Frame

    Turn what we learn into a decision about what actually needs solving.

  4. Make

    Prototype, test, build or ship whatever moves it forward.

  5. Leave it useful

    You keep the evidence, the decisions and the know-how. No dependency.

Got a product problem? Let’s talk.