I spent Sunday learning growth from someone who has launched 15 apps. My own analytics couldn't count to 2,085.

Hey Builder 👋

This week I did something I should do more often: I read one expert properly instead of skimming twenty threads, then ran his playbook against my own product. This one is what he teaches, what it found in Careerkit, and how I'll use it.

This week:

  • Careerkit: 2,085 real signups in the last 30 days. All 25 free tools now run on one page pattern.

  • ReplyBoss: a quiet week, no code shipped.

  • HelloBuilder: the website is on pause. This newsletter is the product for now, and it goes to 103 people.

How do you grow an app nobody invites their friends to?

Nikita Bier has a blunt answer for founders building social apps for adults: "adults have no friends." Careerkit isn't even social. Nobody shares their resume builder with friends. So I wanted to know what he teaches that doesn't depend on invites.

Some context on why he's worth listening to:

  • He built tbh, the #1 free iOS app in the US in 2017, which Facebook bought.

  • He built Gas, 7.4 million installs per Sensor Tower, which Discord bought in 2023.

  • He ran product at X from June 2025 to August 2026.

  • And on Lenny's Podcast he said "14 of the apps that we launched were basically duds." The playbook comes from the misses too.

Ayush Garg collected his interviews and posts into an open playbook, every claim cited. On Sunday I read it and turned it into a Claude Code skill that audits Careerkit. Its first run, on Monday, found my analytics had missed more than half of my signups.

Below: five of his rules that carry over to a small product, what each one found in Careerkit, and what I'm doing about it.

1. Read your own funnel, because it's probably lying

He says founders who ask him about growth almost always fall into one of three traps:

  • an "onboarding problem" that is really the team's own debugging sessions;

  • onboarding that looks fine because logged-out users aren't tracked;

  • sharing that counts attempts, "not the final send events."

Careerkit had all three:

  • 8,376 events in my production analytics came from my own machine.

  • Google sign-ups never fired the signup event. My analytics counted 948 signups in 30 days. The database had 2,085. I'd been reading every funnel off 45% of the people.

  • "Copy link" counted the share before the copy happened.

All three fixes went live this week. The honest numbers land next Tuesday.

Check yours tonight: count signups in your analytics and in your database for the same 30 days. Then sign up once with every method you offer and watch which event fires.

2. Share the result, not the app

He has a name for the one-off viral moment: "Spotify Wrapped syndrome. You might top the charts for a day but that is only going to create phantom validation." Real product-led growth, in his words, is "where the mechanics of the product are actually driving the acquisition."

  • Careerkit's career test ends on a result card people can share. In 5 days, the 261 people who started the test shared it 15 times.

  • That's small, but it happens every session, not once on launch day.

For you: list everything your product produces in one session. Pick the one someone would screenshot, and make it one tap to share with a tagged link.

3. Show value in three seconds

"If you can't demonstrate value in the first three seconds, it's over."

This is where I'm actually losing people:

  • 87% of visitors to the career aptitude test never press start.

  • The RIASEC test page runs the identical component and only 5.8% start. Same code, different words, different searchers. So it's copy and intent, not layout.

He also says "there's crazy places that users drop off that you wouldn't ever anticipate," and his fix is to walk every step of the funnel yourself. I've queued 12 recordings of people who left. My plan is to watch them before I change a pixel.

4. Charge for what support keeps asking for

At tbh, "the number one support message we received was can I pay to reveal who sent me polls?" Gas later sold a subscription that hinted at who sent the compliments.

I ranked about 200 written feedback comments on Careerkit from the last 60 days:

  • Nobody asked to pay for anything.

  • The #1 ask was more templates.

  • The #1 anger was the limit on free downloads that nobody had been told about. One comment: "Surprise charge for a free site."

So this week I shipped the boring fix: the download menu now shows how many free downloads are left. Next I'll test whether templates, the thing people actually ask for, should be the paid part.

He also splits apps into two kinds: durable apps, and "paywall-ad arbitrage" apps that live on people forgetting to cancel. That's a good question to ask about your own churn.

5. Do one thing at 100%. Half-ass the rest.

"Execute at 100% for the thing you're trying to validate at that specific stage of the product development cycle. And then you can kind of half-ass the rest just so you can get 100% signal on that one part."

This is the rule I'm applying to my own week, not just to Careerkit's funnel. Three products, one founder, and too many things to do. That's founder life, and when everything feels urgent, nothing gets 100%.

So:

  • Careerkit gets the 100%. It's the one with users.

  • HelloBuilder is this newsletter for now. The website stays as it is: no fixes, no new features.

  • I said it last week and it's still true: this newsletter is "a good exercise for me to learn what's going on, and sharing it is no cost." That makes it the part of HelloBuilder worth doing well.

If you take one thing away: before you trust any growth number, count your signups twice, in your analytics and in your database. If they don't match, fix that first. Then pick the one thing you'll do at 100%.

🧠 What I Learned on X

📰 AI News

🛠 Tools to Try

⚡ Skills to Try

📈 Growth & Money

💬 Builder Discussions

Reply with your question. I answer one every week. And if you've ever compared your analytics signups with your database, tell me how big the gap was.

Keep shipping,

Nishant