<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
  <title>Finu Shaheem — Blog</title>
  <link>https://finushaheem.co/blog/</link>
  <atom:link href="https://finushaheem.co/blog/feed.xml" rel="self" type="application/rss+xml"/>
  <description>Practical notes on product growth — retention, Go-to-Market and community.</description>
  <language>en</language>
  <lastBuildDate>Mon, 16 Nov 2026 00:00:00 GMT</lastBuildDate>
  <item>
    <title>Retention is your best acquisition channel</title>
    <link>https://finushaheem.co/blog/retention-is-your-best-acquisition-channel/</link>
    <guid isPermaLink="true">https://finushaheem.co/blog/retention-is-your-best-acquisition-channel/</guid>
    <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    <description>Why keeping users makes every new one cheaper — and five practical ways to fix a leaky bucket before you spend more on growth.</description>
    <content:encoded><![CDATA[
<p>Most teams reach for acquisition first. A new channel, a bigger ad budget, a launch. But if users leave as fast as they arrive, every new user is poured into a leaky bucket — and you pay for the same growth again and again.</p>
<p>Retention changes the maths of everything else. Users who stay tell friends, leave reviews, renew, upgrade, and pay back what it cost to win them. That is why I treat retention as the first acquisition channel, not the last.</p>

<h2>1. Find your activation moment</h2>
<p>Activation is the first time a new user actually gets the value you promised. For a budgeting app it might be the first category that balances; for a team tool, the first task a teammate completes. Define it as an event you can see in your data, not a feeling.</p>
<p>The quickest way to find it: compare what retained users did in their first week with what churned users did. Then talk to a few of each. The behaviour that separates the two groups is your candidate.</p>

<h2>2. Read retention by cohort, not averages</h2>
<p>An overall “active users” number hides everything. Group users by the week they signed up and plot what share of each group is still active in week 1, 2, 4 and 8.</p>
<ul>
  <li>A curve that keeps falling towards zero means the product is not yet a habit for anyone.</li>
  <li>A curve that flattens means a core group has found lasting value. That flat line is the most honest product–market fit signal you have.</li>
  <li>Newer cohorts sitting above older ones means your changes are working.</li>
</ul>

<h2>3. Shorten time-to-value</h2>
<p>Every step before the activation moment is a place to lose people. Audit your first-run experience and ask of each screen: does this help the user reach value, or does it help us?</p>
<ul>
  <li>Delay sign-up, permissions and profile questions until they are clearly useful.</li>
  <li>Start people with templates or sample data instead of an empty screen.</li>
  <li>Make the first success possible in one sitting.</li>
</ul>

<h2>4. Build the habit loop on purpose</h2>
<p>Habits form around a trigger, an action and a reward. Your job is to attach the product to something the user already does — a morning routine, a weekly review, the end of a shift — and make the reward show up every time.</p>
<p>Notifications are a trigger, but they have to be earned. One useful, well-timed message beats five generic reminders, and users who mute you rarely come back.</p>

<h2>5. Win back with a reason</h2>
<p>Ask churned users why they left, in one question, and listen for patterns. Then reach out to them only when you have actually fixed something they cared about. A win-back message with real news works; “we miss you” rarely does.</p>

<h2>A short checklist</h2>
<ol>
  <li>Write down your activation event in one sentence.</li>
  <li>Plot weekly cohort retention curves and look for where they flatten.</li>
  <li>Remove one step between sign-up and first value this month.</li>
  <li>Pick one trigger in the user’s existing routine to build around.</li>
  <li>Collect the top three reasons people leave.</li>
</ol>
<p>Acquisition multiplies whatever retention you already have. Fix the bucket first, and every channel you add later gets better.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Go-to-Community: launch with people, not ads</title>
    <link>https://finushaheem.co/blog/go-to-community/</link>
    <guid isPermaLink="true">https://finushaheem.co/blog/go-to-community/</guid>
    <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    <description>A practical guide to community-led launches — where to show up, how to give before you ask, and what to measure instead of member count.</description>
    <content:encoded><![CDATA[
<p>Go-to-Market asks “how do we reach buyers?” Go-to-Community asks a different question: “where do our users already gather, and how do we become useful there?”</p>
<p>Working with GTech µLearn, a community of 40K+ learners, made one thing clear to me: people come for the content but stay for other people. Products can grow the same way — through trust that is earned in public, one helpful answer at a time.</p>

<h2>Why it works</h2>
<ul>
  <li><strong>Trust travels faster than ads.</strong> A recommendation from a peer in a group someone already trusts does more than any banner.</li>
  <li><strong>Feedback arrives early.</strong> You hear objections, use cases and bugs before you have spent on paid growth.</li>
  <li><strong>It compounds.</strong> Every answered question, template and guide keeps working long after you post it.</li>
</ul>

<h2>1. Map where your users already are</h2>
<p>Before building your own community, list the places your users gather today: forums, Discord and Telegram groups, subreddits, college clubs, meetups, LinkedIn circles, newsletters. Join, read and learn the norms before you say anything.</p>

<h2>2. Give before you ask</h2>
<p>Teach something, answer questions, share a template or a checklist that solves a real problem — with no link to your product. The goal is to become the person people tag when the topic comes up.</p>

<h2>3. Find your champions</h2>
<p>In every community a small group does most of the helping. Find them early. Give them access before anyone else, credit them publicly, and let their feedback visibly shape what you build. Champions turn a launch into a movement.</p>

<h2>4. Create rituals, not campaigns</h2>
<p>Campaigns end; rituals repeat. A weekly office hour, a monthly challenge, a showcase of what members built. Rituals give people a reason to come back that does not depend on your marketing calendar.</p>

<h2>5. Close the loop</h2>
<p>When the community asks for something and you ship it, say so — and name who asked. Nothing builds loyalty faster than people seeing their ideas become real.</p>

<h2>Measure what matters</h2>
<p>Member count is the easiest number to grow and the least useful. Watch these instead:</p>
<ul>
  <li>Active contributors per week, not total members.</li>
  <li>Share of questions answered by members rather than your team.</li>
  <li>Sign-ups and referrals that name the community as the source.</li>
  <li>Retention of users who joined through the community versus other channels.</li>
</ul>

<h2>Common mistakes</h2>
<ul>
  <li>Using the community as a broadcast channel for announcements.</li>
  <li>Launching your own community before you have earned a place in existing ones.</li>
  <li>Automating the human parts — welcomes, thanks and replies.</li>
</ul>
<p>Go-to-Community is slower to start and harder to fake. That is exactly why it lasts.</p>
]]></content:encoded>
  </item>
  <item>
    <title>A one-page Go-to-Market plan for mobile apps</title>
    <link>https://finushaheem.co/blog/one-page-go-to-market-plan/</link>
    <guid isPermaLink="true">https://finushaheem.co/blog/one-page-go-to-market-plan/</guid>
    <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
    <description>A simple, one-page template for launching a mobile app: who it is for, the first channel, the store listing, the paywall and the metrics that matter.</description>
    <content:encoded><![CDATA[
<p>Long launch decks rarely survive contact with reality. A plan that fits on one page does: everyone can read it, argue with it and update it every week. Here is the structure I use for mobile apps.</p>

<h2>1. Who exactly is it for?</h2>
<p>One sentence, specific enough to picture a real person. “Busy people” is not a segment. “First-year engineering students who want to practise coding interviews on their phone” is.</p>

<h2>2. The problem, in their words</h2>
<p>Write the problem the way your user would say it to a friend. If you cannot, you have not talked to enough of them yet. These words become your store subtitle, your first screenshot and your ad copy.</p>

<h2>3. Positioning in one line</h2>
<p><em>For</em> [who] <em>who</em> [problem], [app] <em>is a</em> [category] <em>that</em> [key benefit]. <em>Unlike</em> [alternative], <em>it</em> [difference].</p>

<h2>4. One primary channel, one experiment</h2>
<p>Pick the single channel most likely to reach your segment cheaply, and one experiment to test alongside it. Common options for mobile apps:</p>
<ul>
  <li>App Store and Google Play search (App Store Optimisation)</li>
  <li>Creators who already talk to your segment</li>
  <li>Communities your users already belong to</li>
  <li>Paid social, once you know which message converts</li>
  <li>Partnerships with products your users already use</li>
</ul>

<h2>5. The launch assets</h2>
<p>For most apps the store listing <em>is</em> the landing page. Prioritise the icon, the title and subtitle, and the first three screenshots — they carry most of the decision. Then a simple website and a short demo video.</p>

<h2>6. Pricing and paywall hypothesis</h2>
<p>Decide what you will test first: free trial or freemium, where the paywall appears, and what the user has experienced before they see it. Show the paywall after the activation moment, not before.</p>

<h2>7. Metrics: one north star, a few inputs</h2>
<ul>
  <li><strong>North star:</strong> the number that rises only when users get value (for example, weekly active users who complete the core action).</li>
  <li><strong>Store conversion:</strong> listing views to installs.</li>
  <li><strong>Activation rate:</strong> installs that reach the first success.</li>
  <li><strong>Day-7 retention:</strong> the earliest honest signal of a habit.</li>
  <li><strong>Trial-to-paid:</strong> if you charge.</li>
</ul>

<h2>8. The next 30 days</h2>
<p>List three experiments, each with a hypothesis, the metric it should move and the date you will decide. Review the page every week and rewrite what you have learned.</p>

<h2>Copy this template</h2>
<pre><code>WHO:        [one specific person]
PROBLEM:    "[in their words]"
POSITION:   For [who] who [problem], [app] is a [category]
            that [benefit]. Unlike [alternative], it [difference].
CHANNEL:    Primary: [ ]   Experiment: [ ]
ASSETS:     Icon · Title · Subtitle · 3 screenshots · Site · Video
PAYWALL:    [trial / freemium] shown after [activation moment]
METRICS:    North star [ ] · Store CVR · Activation · D7 · Trial→Paid
30 DAYS:    1. [ ]  2. [ ]  3. [ ]</code></pre>
<p>A plan this small will be wrong in places. That is fine — it is cheap to change, and changing it every week is the point.</p>
]]></content:encoded>
  </item>
</channel>
</rss>
