Products people come back to, built on evidence.
Discovery, product management, UX and UI, and build, in short cycles tested with real users. So you spend on what people actually want.
Sound familiar?
Four signs your product needs a reset.
Most product trouble starts long before launch. These are the signs we look for first.
You have an idea and a budget, but no proof people will pay.
What we do: find out fast, with real people, before you build all of it.
Your roadmap is a list of requests from whoever spoke last.
What we do: tie every priority to what moves activation, retention or revenue.
People sign up, then disappear.
What we do: find exactly where they drop off, and fix that first.
Every release takes longer than the last.
What we do: smaller cycles, clearer scope and a steady rhythm of shipping.
What we do
Four services, one product.
Take one or take all four. Each one hands the next exactly what it needs, so nothing is lost between research and release.
Discovery and validation
Start here
We test the problem before anyone writes code. Interviews with the people you want to serve, a look at what they use today, and quick experiments to see if they care enough to act.
You get Evidence on the problem and demand, and a clear decision on what to build first.
Product management
Direction
We set the direction and keep it: a roadmap tied to outcomes, the few metrics that matter, and a weekly rhythm your team can run.
You get A roadmap you can defend, metrics that mean something, and rituals that stick.
UX and UI design
Experience
Flows and screens designed around what people are trying to get done, tested as clickable prototypes before they are built.
You get Tested flows, a clickable prototype and a design system your engineers can build from.
Build and growth
Ship
We work with your engineers, or a build partner we bring in, to ship in short cycles. Then we measure what changed and improve what moves the numbers.
You get Working releases, a measured baseline, and a backlog ranked by impact.
How it works
Validate. Build. Grow.
Three stages, in order. Each one ends with something you can see, use and approve before we move on.
Validate
Is it worth building?
We prove the problem is real and worth paying for. Interviews, quick experiments and a prototype people can click, all before engineering commits.
- You get Evidence and a clear go or no-go
- We need Access to the people you want to serve
- You approve What gets built, and in what order
Build
Ship in short cycles
We design and ship in short cycles. Every cycle ends with something working that real users have tried.
- You get Working releases, tested with users
- We need A decision-maker in each review
- You approve Each release, before it ships
Grow
Improve what moves the numbers
We measure what people actually do, then improve whatever moves activation, retention and revenue.
- You get A baseline and a ranked backlog
- We need Access to product data
- You approve The metrics we will be judged on
Ways to start
Starter Fixed scope, fixed fee
Product discovery sprint
The fastest way to know what to build. We test the problem with real people and shape a first version you can click, before engineering commits.
We look at
- Your idea or product, and who it is for
- Interviews with the people you want to serve
- How you will make money from it
- What people use today instead
You get
- Evidence on the problem and demand
- Key flows as a clickable prototype
- A build plan, in priority order
- Findings you keep, whether or not you continue
Free tool
Free check CratX Product
Product readiness score
Five questions. Answer honestly. Your score updates as you go, and nothing is sent anywhere.
- Have you spoken to at least ten people who have the problem you solve?
- Has anyone paid, pre-ordered or committed real time to get it?
- Can you name the one metric that shows your product is working?
- Do you know where most new users drop off?
- Could you ship a meaningful improvement within the next two weeks?
Results by score, from 0 to 5. Only the matching one is shown to visitors.
- You’re guessing. Talk to the people you want to serve before you build more.
- There’s an idea here, but very little evidence behind it yet.
- There’s an idea here, but very little evidence behind it yet.
- Good instincts, real gaps. The gaps are usually where money gets wasted.
- Strong. A few changes would make every release count.
- Evidence-led and moving. Your next step is a rhythm that keeps it that way.
What we believe
Prove the problem before you pay to solve it.
Most products fail because nobody needed them, not because they were built badly. A few weeks of evidence is the cheapest money you will spend.
Prototypes, not slides.
A deck describes an idea. A prototype tests it. You see something you can click early, and decisions get made on evidence.
Programs with Product
When product is part of something bigger.
A product succeeds when the brand makes the promise and the operation keeps it. These programs bring the right practices together.
Program P1
Launch
Name, brand, product and the way you deliver it, built together from day one.
Brand, Product, Process
Program P5
New market
Arrive looking local and running ready, with a product and process built for the new market.
Brand, Product, Process
Product questions
What people ask about product work.
Straight answers before the first call.
Do you build the product yourselves?
Build
We design it, manage it and work hand in hand with whoever builds it: your engineers, or a build partner we bring in. You always know who is writing the code.
How long is a discovery sprint?
Timing
It depends on the question we are answering. We agree the length and the deliverables in writing before we start, and keep to them.
Do we need our own product manager?
Team
Not to start. We can lead product while you hire, then hand over to your product manager with everything they need.
What if the evidence says don’t build it?
Evidence
Then we tell you, clearly. That’s the cheapest outcome you will ever get, and it often points to a better idea.
Can you work with our existing engineers?
Engineers
Yes. We fit into how your team already works, and improve the rhythm only where it slows you down.
Who owns the designs and code?
Ownership
You do: research, designs, prototypes and code. Our methods and frameworks stay ours, and you’re free to keep using them.
The other two practices
Product works best with the rest.
One team runs all three practices, so what your product does matches what your brand promises and what your operation can deliver.
Contact
Tell us where your
product is stuck.
A short note is enough. We’ll reply promptly with a time to talk.
- Product discovery sprint
- Validate an idea
- Roadmap
- UX and UI
- Product stopped growing
- Not sure yet
What’s going on with your product?