Introduction

The same small revenue number used to produce completely different conclusions depending on who was reading it. A product earning $9,000 in a month was dying according to one person and doing fine according to another. The disagreement wasn't about standards. There was simply no word for where the product was.

So the meetings kept missing each other. A founder would look at a product two months old and ask why revenue wasn't moving, and the product manager would answer that it was still early. Neither of them could say when early ended or what counted as normal in the meantime, and the same exchange came back every quarter.

Naming the stretch changed that conversation. Calling something the introduction stage fixes what to expect from it and what not to. Low revenue is normal here. What this stage does demand is product-market fit (PMF) — evidence that the thing you built actually matches demand in a specific market. Small revenue is not the problem. Spending months here without that evidence is.

Few people know the product, reaching those few costs a lot, and the ones you reach talk a great deal.

1. Revenue is small, because most of the people who could use the product don't know it exists. Going from $6,000 last month to $8,200 this month is not a 37 percent growth rate worth reporting.
2. Each new user is expensive. Customer acquisition cost (CAC) — what you spend to land one customer — runs highest in this stage. Nobody recognizes the name in an ad, and there are no existing users around to make introductions.
3. The people who show up first are a specific crowd. Early adopters, the ones who spot an advantage before others do and accept the risk that comes with it, are your users here. They use half-finished features, report the crashes, and ask for things that don't exist yet.
4. Feedback is dense. There are few users, but each one carries a lot of information. When thirty people use a product and five say the same thing, that's a signal, and one signal like that can rewrite a whole quarter of work.
5. The product changes often. Changing it is cheap because there are few people to convince. At 30,000 users, moving one screen comes with an announcement and a help article; at thirty teams, a line in a chat channel covers it.

You leave this stage when users stay and keep arriving after you stop paying for them. That is what having product-market fit actually means in practice.

Teams usually read three things together.

1. Where retention — how much of a signup cohort keeps coming back — settles. Take the signup month as 100: if month four holds at 40, month five at 38, and month six at 37, the curve has flattened. Before that shape appears, pouring in more users is filling a bucket with a hole in it.
2. Whether anyone arrives through a channel you didn't pay for. Once word of mouth, the unpaid recommendations users pass along on their own, accounts for part of new signups, the product has started moving under its own power.
3. Whether acquisition cost is falling. If the same ad budget brings in more people than it did last quarter, the market is starting to recognize what this is.

When all three move together, the growth stage has begun. When one looks good and the other two haven't budged, you're still here. The most common misread is signup count alone. Double the ad spend and signups double, but if the retention curve still falls to the floor, everything returns to where it started the day the spending stops.

The further a product sits from how people already do the job, the more likely another gap opens along the way: the chasm, the drop in demand between early adopters and the mainstream market. Thirty teams loving the product while the next 300 never arrive is what that looks like.

"We're in the introduction stage. Holding us to the same CAC target as a mature product means we can't do anything."

A different stage should carry different expectations.

"We're still early, so I'd rather report interview counts than a revenue target this quarter."

Progress here is measured in facts confirmed, not in money collected.

"If you've been in the introduction stage for over a year, you're not in a stage. It isn't working."

A stage is a condition, not a duration, and staying in it without signals is a reason to stop.

Pagedeck's meeting the quarter it spun its document templates out as a separate product went exactly this way. Grace asked what the first month brought in, Mia said $3,600, and Grace's next question wasn't about the number — she asked how many teams were still there in week four. Mia said 11 of the 40 they had invited, and the meeting never went back to revenue.

Mia and Ravi spent the next two weeks finding out why those 11 stayed. Nine of them gave the same reason, and that reason became the plan for the following quarter.

The most common mistake is reading the introduction stage as a span of months right after launch. The stages come in order and each one is named like a period of time, so a calendar reading comes naturally. But stages are separated by the shape of the numbers, not by time. A product three years past launch whose retention still falls to zero and whose signups stop the moment ads stop is in the introduction stage. Read it as a duration and you get decisions like "it's been six months, time to build the growth plan," which stacks hiring and ad budget on top of demand nobody has confirmed.

The other common move is using the phrase as an explanation for having nothing to show. "We're still early" is a convenient sentence that covers every low number at once, so it gets reached for often. But this stage has things worth counting. How many teams you talked to, how many are still active, and what the ones who stayed say they stayed for can all be counted monthly with no revenue at all. Hold on to the stage name without those counts and you lose any way to check whether you've met the conditions to leave — and any way to understand why the next stage never arrives.