Guide · Dubai · MENA

From MVP to product-market fit: what to measure and what to ignore

A founder emails me two weeks after launch with a screenshot of the signup graph, climbing, and a question underneath it: are we there yet. The graph answers nothing. Signups measure curiosity. Demo requests measure curiosity. A feature request list measures how many people were polite enough to reply to your onboarding email. Across engagements in Dubai and MENA I keep seeing founders build the next quarter's roadmap on this kind of activity, then wonder why usage does not catch up to the chart they showed their board.

Product-market fit sits one layer under activity, in whether the people who tried your product kept using it and whether some of them would pay for more of it. That layer takes longer to read and it rewards patience you do not feel entitled to right after launch.

How to find product-market fit: the three metrics that matter

Three numbers hold up under scrutiny once the launch excitement fades.

Activation rate. The share of new signups who reach the moment your product solves their problem, not the moment they create an account. For a workflow tool that might be the first completed task. For a marketplace it might be the first transaction, not the first browse. Set this threshold before launch, because defining it after the fact lets you move the goalposts to match whatever number you already have.

Retention curve shape. Plot weekly active users against the week they signed up, cohort by cohort. A flattening curve, one that drops and then holds at some floor, points at a core group who keep coming back. A decaying curve, one that keeps sliding toward zero, means you are refilling a leaky bucket with acquisition spend. The shape matters more than the week-one number.

Willingness to pay. Not a survey answer. A real card charged, a pilot invoice sent, or at minimum a specific price stated out loud by a prospect who then asked a follow-up question about terms instead of walking away. Rough benchmarks vary by product type: a B2B tool can show fit with a handful of paying pilots and strong activation among them, while a consumer app needs a retention curve that flattens before payment signals mean much at all.

Press mentions, investor enthusiasm, and a competitor copying a feature measure your visibility. None of them measure your fit.

A weekly operating loop between MVP and PMF

Run this loop each week rather than reorganizing around it once a month.

1. Talk to five users who used the product this week, not five who signed up this week. Usage is the filter. A person who created an account and did not return has nothing to tell you about your product, only about your landing page.
2. Ask what they did right before and right after they used it, not whether they like it. Liking a product and routing their workflow through it are different claims, and only the second one predicts retention.
3. Decide one change based on this week's conversations, and ship it before the next five calls. A backlog that only grows produces a founder who has listened without shipping anything.
4. Test price with at least one real prospect on a two-week cadence, even informally. Waiting until the product feels finished to ask about money means you find out your pricing was wrong after you built around the wrong number.

The loop stays the same regardless of product type, but the signal you weigh most changes: a workflow tool leans on activation and retention, a marketplace leans on repeat transaction rate on both sides, and a service-heavy product leans on whether a pilot renews without a discount.

Reading the retention curve: flattening versus decaying

Most founders stare at week-one retention and miss the part of the chart that matters most. Week one tells you whether onboarding worked. Week four through week eight tells you whether the product earned a place in someone's routine.

A curve that flattens, even at a modest level, says a core group found enough value to keep returning without you pushing them back in. Build the next quarter around understanding that group: who they are, what separates them from the users who churned, and how to find more people who match.

A curve that keeps decaying past week eight says the current version has not found its core user yet. Spend the next stretch on conversations with the cohort that stuck longest before it fell away. They came closest, and something specific stopped them.

One path from launch to acquisition in 14 months

A Dubai venture studio I worked with went from a blank canvas to an acquisition in fourteen months, with the first version built in six. The retention curve for that first version flattened at a level too thin for an investor deck, low enough that a pure numbers read said to keep iterating on growth. The conversations said something different. The users who stayed were using the product for a narrower job than the one it was built to do, and they kept doing it weekly without being asked.

The team rebuilt the next version around that narrower job instead of the original vision, cut the features that sat unused in that cohort, and watched the retention curve flatten again, this time at a level worth building a business around. Growth spend started only after that second curve held for two consecutive cohorts, not after the first one looked promising. That ordering, evidence before spend, is the part of the story a founder can copy even without copying the product.

Before you spend on growth: the premature-scaling checks

Pass these checks before you put a dirham behind acquisition.

• Retention has flattened for at least two consecutive cohorts, not one. One flattening cohort can be a fluke of timing or a single good customer segment you happened to reach first.
• At least a few users are paying, or have stated a specific price and kept engaging after hearing it. Growth spend on an unpriced product scales confusion, not revenue.
• You can describe the user who stays in one sentence, built from actual usage data rather than the persona slide from your deck.
• The team can name the feature that would break retention if removed. If the team cannot answer that, you do not yet know which part of the product to protect while you scale the rest.

A regional marketplace I worked with skipped straight to paid acquisition after a strong first month of signups, before any of these checks passed. The team spent six weeks and a real budget acquiring users who churned at the same rate as the unpaid ones, because the product itself had not changed. Going back to the retention curve, finding the segment that already stuck, and building the credit-financing and reconciliation workflow that segment needed fixed it. No ad spend did.

FAQ

What counts as product-market fit for an early-stage startup? A flattening retention curve across at least two cohorts, combined with a specific group of users who would pay, or already do, for the product to keep existing. Nothing short of actual repeat usage and real willingness to pay qualifies, whatever the vanity metrics say.

How long does it usually take to reach product-market fit after an MVP launch? There is no fixed timeline. Some products find it in a single rebuild cycle of six to eight weeks. Others take several quarters of narrowing the user and the job before the curve holds. The team's consistency in running the weekly operating loop predicts the outcome, not the number of months that have passed.

Should I raise a seed round before or after product-market fit? Raise on the evidence you have. A flattening retention curve with early paying users supports a stronger seed conversation than a signup chart alone, and most investors at that stage will ask for the curve, not the chart.

What is the biggest mistake founders make between MVP and PMF? Spending on growth before the retention curve has flattened. Acquisition amplifies whatever the product already does, including the part where most users leave, so it turns a quiet problem into an expensive one.

Book a call

If you have launched and the chart is going up while usage is not, book an intro call for a second read on the evidence before you spend on growth. For weekly writing on AI and product from zero, read the Scalable newsletter.