Quick answer. The one number that matters is the single metric your product must move to prove it's working — not a vanity metric like downloads, but something tied directly to real value, like "quotes accepted per week" or "repeat bookings in month two." First-time founders often try to track ten metrics at once and end up steering by none of them. Picking one number before you design or build anything forces every decision — what to build first, what to cut, what to test with users — to serve a single, honest measure of progress. Get this wrong or skip it, and you can ship a product that "works" perfectly while not actually moving the thing that determines whether the business survives.
Key takeaways
- The one number that matters is a single metric tied to real value — like "bookings completed per week" — not a vanity metric like downloads or signups.
- A good one number is tied to real value exchanged, repeatable, measurable within the first few weeks, and singular — track other things, but let only one number decide what gets built.
- Applying the "does this move the number" filter honestly to a feature list typically shrinks it by about a third.
- Pick the one number before you design or build anything, ideally in the same week you map your process and test a clickable prototype.
- The number should evolve as the product matures — from an early signal like a completed booking toward revenue or retention measures once that signal is reliably strong.
Why Most First-Time Founders Track the Wrong Things
Most first-time founders track the wrong things because their analytics dashboard rewards activity, not value: total downloads, total signups, total screen views, total time in app — numbers that can all go up while the business quietly fails.
A number is only useful if moving it means something real happened for a real customer. Downloads mean someone tapped a button in an app store. They don't mean anyone found value, came back, or would pay. Signups are the same — free to get, easy to inflate, and disconnected from whether the product actually solves the problem it promises to solve.
This is why we insist on agreeing the one number that matters in week one of design, before a single screen gets built, alongside testing a clickable prototype with real users. If the number is wrong, everything built to move it is aimed at the wrong target.
What Makes a Good "One Number"
A good north star metric has a few specific properties. It should be:
- Tied to real value exchanged, not activity. A booking completed, not a screen viewed.
- Something a user does repeatedly if the product works. One-off actions are weaker signals than repeat behaviour.
- Measurable early, ideally within the first few weeks of launch, not only after twelve months of data.
- Singular. One number, not a dashboard of five. You can track other things, but only one number should be allowed to decide what gets built next.
A number that fails these tests — total registered users, total app opens, total pageviews — might look impressive in an investor update, but it won't tell you whether the business is actually working.
Examples by Business Type
Abstract advice is easy to nod along to and hard to apply. Here's what the one number that matters looks like for different kinds of first-time founder products.
| Product type | Weak metric (avoid) | Strong metric (the one number) |
|---|---|---|
| Trade booking app (e.g. a Sydney mobile mechanic marketplace) | Total app downloads | Bookings completed per week |
| SaaS tool for small accounting firms | Free trial signups | Trials that reach a second billing cycle |
| Two-sided marketplace (e.g. a Brisbane freelance trades marketplace) | Total listings created | Jobs where both sides transact and return within 60 days |
| Consumer subscription app | Total registered accounts | Subscribers still active at day 30 |
| B2B workflow tool for NDIS providers | Logins per week | Care plans completed end-to-end without manual workaround |
Notice the pattern: the weak metric measures whether someone showed up. The strong metric measures whether the product actually did its job, more than once, for that person.
How to Actually Choose the One Number That Matters
Start by finishing this sentence honestly: "My product has succeeded for a user when they have ______." Not signed up. Not opened the app. Done something that means the underlying problem got solved — booked the job, closed the sale, filed the return, found the tradesperson.
Then ask: if that number went up every week for the next three months, would the business clearly be working? If the answer is "sort of, but I'd want to see other things too," you've picked the wrong number, or picked it too early in the funnel.
A first-time founder building a subscription meal-planning app for busy Melbourne parents initially tracked "recipes viewed." It looked healthy — the number climbed every week. But subscriptions weren't renewing. The real number that mattered turned out to be "meal plans actually used to do a grocery shop" — a much smaller, much harder number to move, and the one that actually predicted renewal. Once that became the number the team designed around, the onboarding flow, the notifications, and even the pricing page changed to push toward that single action.
What Changes Once You Have It
Picking the one number that matters isn't a reporting exercise — it changes what gets built. Once it's agreed:
- Every proposed feature gets one question: does this plausibly move the number, or is it a nice-to-have? Most feature lists shrink by a third once this filter is applied honestly.
- The prototype testing plan is built around it. Rather than showing users a tour of the app, you give them the task that produces the number and watch whether they complete it.
- The build sequence follows it. The flow that produces the number gets built and refined first — everything else, including sign-in polish and settings screens, comes later.
- Post-launch ongoing optimisation has a clear target. Instead of guessing what to improve after launch, every experiment is judged against whether it moves the one number.
When the Number Should Change
Your one number won't stay the same forever, and it shouldn't. Early on, it should be the smallest, fastest signal that the core loop works — a completed booking, a returned user. As the product matures and that early signal is reliably strong, the number should mature too, moving toward revenue or retention measures that reflect a sustainable business, not just an interested user.
The mistake is changing it too early, before the first number has actually been proven, which usually means chasing a more "impressive-sounding" metric before the product has earned the right to be measured by it.
FAQ
What's the difference between a vanity metric and the one number that matters?
A vanity metric measures activity — downloads, signups, pageviews — that's easy to generate but doesn't confirm real value was delivered. The one number that matters measures an outcome tied directly to the problem your product claims to solve, ideally something a user does repeatedly only if the product is genuinely working for them.
Can I track more than one metric?
Yes, and you should keep a small dashboard of supporting metrics. But only one metric should be allowed to override a product decision. Trying to optimise for several "most important" numbers at once is how teams end up building a bit of everything and moving nothing meaningfully.
How soon should I pick the one number that matters?
Before you design or build anything, ideally in the same week you map your process and test a clickable prototype. Choosing it after the build starts means you've already made feature and flow decisions without a clear target, which usually has to be partly undone later.
What if I'm not sure what the right number is yet?
That's normal for a genuinely new idea. Start with your best guess at the smallest action that proves the core problem is solved, test it with real users on a prototype, and be willing to revise the number itself in the first few weeks based on what you learn — the number is a hypothesis too, not just the product.
Should the one number that matters replace revenue as a goal?
No. Revenue is usually the eventual number that matters most, but very early on it's often too slow or too noisy a signal to design around directly. A good early number is a strong leading indicator of revenue — repeat bookings, retained trials, completed transactions — that you can observe within weeks rather than quarters.
Next step
Not sure what your number should be yet? Run your idea through our free Idea Reality Check — it's a fast way to pressure-test the assumption underneath your product. If you're ready to map your process and agree your number properly, that's exactly what week one of Sketchli's product strategy and management work does, or book a free 30-minute call to talk it through.
Want to bring your idea to life? Contact us or chat on WhatsApp.