Litmus / FAQ
Litmus FAQ
Is it right for us
Can we test our product idea before we spend money building it?
Yes. You get a clear go, no-go or iterate verdict before you write code or commit budget. Litmus is a Mantle workshop that tests your idea against customer, market and technical evidence. The reasons behind the verdict are recorded.
Is Litmus a fit if we need evidence before we fund a product bet?
Yes. You see the evidence before you fund the bet. Litmus is built for teams with a product idea or bet who want that evidence first. If the bet came out of North Star, our product strategy framework, it moves straight into Litmus with nothing lost in translation.
How it works
Will Litmus test the market and technical side, not just customer interest?
Yes. Your idea is tested on customers, market and technology before you commit. First we sharpen the idea, surface hidden assumptions and agree what would kill it. Then we gather customer evidence from interviews, calls, intent data and churn drivers. Next we test the market, the competition and technical feasibility. Finally, we weigh the evidence and give the verdict.
Will Litmus show us how hard our idea would be to build?
Yes. You see the build risk before you commit. The technical feasibility review covers build complexity, dependencies, integration debt and scaling unknowns.
Will we see who else is in the market and where our idea wins?
Yes. You see the field before you commit. A competitive teardown shows who else is there, what they miss and where your bet wins, alongside market sizing.
Will the verdict show how each kind of evidence was weighed?
Yes. Your verdict is explained, with the reasoning on record. Customer, market and technical evidence is weighted explicitly, and the rationale behind the go, no-go or iterate verdict is recorded.
Your systems and data
Will the verdict rest on real customer evidence, not internal opinion?
Yes. Your verdict rests on customers, not stakeholder confidence. Evidence is gathered against your hypothesis through structured interviews, calls, intent data and churn drivers.
Getting started
Can we book a Litmus workshop for our idea?
Yes. Use the form on our contact page, and our team will be in touch.
Can we start Litmus with just a hypothesis, before any code?
Yes. You start with your idea as a stated hypothesis. Litmus sharpens it, brings the hidden assumptions into the open and agrees kill criteria at the start, before evidence can bias the team.
Pricing and support
Can we get a price for Litmus that fits our scope?
Yes. Pricing depends on scope. Use the contact form and our team will be in touch.
Will we know exactly what to do next, whatever the verdict?
Yes. Each verdict comes with a clear next step. A go hands the idea, evidence and build target to Spark, our next step for building an MVP. A no-go sets out where the budget and team go next, and records the lessons. An iterate lists the specific changes and the conditions for a re-test.
If the verdict is iterate, can we test the idea again?
Yes. An iterate verdict lists the specific changes to make and time-boxed conditions for a re-test, so your team knows what to change before the idea is tested again.