Building in Public with Deven

From: Deven Bhooshan, 52

To: Anyone who remembers what “followers” used to mean

Re: Social media, AI, work, fame — what it all became

A letter from someone who built on you, profited from you, and watched you eat itself.


I am 52. Reeta keeps telling me I've become the kind of man who talks to himself. She is not wrong. But today I want to talk to someone specific — anyone who remembers what it felt like to have followers.

That number. That small, stupid number at the top of your profile. I had 40,000 once. I checked it every morning before I checked on my wife.

I'm writing this on paper, by the way. Reeta thinks I'm being difficult. I just like that paper doesn't have an opinion about what I should say next.

That's what I want to talk about. What the internet was. What it became. What it cost us — in ways we didn't notice until the bill arrived.


In 2026, I was 32. I ran a small SaaS company called Supergrow — a LinkedIn content platform. We helped people find their voice online.

I believed in what we were building. I still do, mostly.

LinkedIn in those days was strange. It had started as a résumé site and mutated — slowly and then all at once — into something nobody had planned. A performance stage for professional identity. You did not simply exist on LinkedIn. You posted. You crafted. You announced your failures with the careful confidence of someone who had already survived them.

Everyone was a thought leader. Everyone had a framework. Everyone had a hot take about AI agents.

And somehow — miraculously — it worked. I watched founders raise rounds because of a thread that went viral. I watched a B2B sales leader activate his 200-person sales team on LinkedIn — each of them posting, sharing, showing up — and watched enterprise deals close because of it. I watched my own company grow from zero to tens of thousands of customers, almost entirely through content.

“The feed was not yet sentient. It was just hungry. And we fed it willingly — our opinions, our stories, our grief, our wins.”

But something was already wrong in 2026. Most of us could feel it. The posts that spread were the ones engineered to spread. Not the ones worth reading. The algorithm had learned what made you stop scrolling, and it was not wisdom.


What the feed became

~2026–2028 — the flood

There was a month — I think late 2027 — where my entire LinkedIn feed flipped.

Not gradually. One week it felt human. The next, it felt like standing in a factory producing sincerity at industrial scale. Perfectly timed vulnerability. Grammatically flawless regret. The “I almost quit but didn't” stories arriving every morning like shifts changing at a plant.

Everyone could feel it. Nobody could prove it.

The content wasn't wrong exactly. It just wasn't alive. The cost of a post had dropped to zero, and so the feed filled — the way a room fills with noise when everyone stops listening — with everything that had been waiting. Engagement went up. Meaning went down. The platforms celebrated the former because the former paid the bills.

~2029–2032 — the retreat

People left. Not loudly. No exodus, no moment you could point to.

More like watching a party slowly empty. First the thoughtful ones. Then the tired ones. Then almost everyone.

They didn't stop talking. They moved somewhere smaller. WhatsApp groups. Private servers. Newsletters with 300 subscribers who actually read every word.

The discovery of that era: people didn't want an audience. They wanted a room. A specific room, with people they'd chosen, where nobody was performing for anybody.

The public feed became what it probably always should have been. A billboard. Something you advertised on. Not something you lived in.

~2033–2036 — work & identity

My neighbour Priya had been a radiologist for nineteen years.

Good at it. The kind of doctor who caught things others missed — who could look at a scan and feel something was wrong before she could say why.

In 2034, her hospital deployed a diagnostics system. It read scans faster than she could open them. It flagged anomalies she'd caught maybe sixty percent of the time. The system caught them ninety-four percent of the time.

She didn't lose her job. She lost something harder to name.

She still came in every day. Still wore her coat. But her mornings — which had once been spent reading scans — were now spent reviewing the system's conclusions. Confirming what it had already decided. Occasionally pushing back. Almost never overturning it.

“I still understand it,” she told me once. “I just don't do it anymore.”

Priya was not unusual. She was just early.

~2036–2040 — fame & creativity

Around 2037, the music industry essentially stopped making sense.

People listened more than ever. AI released ten thousand albums a day. Some were extraordinary. A few moved people to tears. And yet nobody could agree on what a song was anymore, or who had made it, or whether any of it mattered.

Then a pianist in Seoul started streaming herself practicing. Not performing. Practicing. Wrong notes, crossed arms, the same eight bars seventeen times.

Three million people watched live.

She didn't say anything extraordinary. She just sat there, struggling in real time. And the world found it could not look away. Tickets to her concerts sold out in four minutes. People paid what they would have paid for a flight.

Turns out people didn't want perfection. They'd had perfection, endlessly, for free.

What they wanted was proof. That a human being had spent their one life caring about something enough to get it wrong, repeatedly, in public. Scarcity had inverted. The rarest thing on earth was a person sitting down, making something slowly, for no reason except that it mattered to them.

~2040–2044 — the identity collapse

Around 2041, I had a conversation with a founder I'd known since 2026.

Sharp. Warm. Someone whose posts I'd genuinely looked forward to reading in the early days — there was always something real in them. Some corner of actual thought.

I mentioned a comment thread on her most recent post. Something unexpectedly human had happened there. A moment of real exchange. Her face went briefly blank.

“Which post?” she asked.

She wasn't being dismissive. She genuinely didn't know. Her agent had been managing her presence for two years. She reviewed a weekly summary. That was it.

“The engagement is great,” she said. Almost to herself.

She said it the way you might describe food at a restaurant you hadn't chosen to go to.

I think about that conversation more than almost any other from that period. Not because it was extreme. Because it wasn't.

~2044–2046 — where we are now

My daughter has never posted anything publicly in her life. She is fourteen.

She has a circle of about forty people — friends, family, two teachers she stayed close to. They talk the way people used to talk before the feed existed. Slowly. Without an audience. Nobody performing for anybody.

When I try to explain what LinkedIn was — what it felt like to watch your follower count go up after a post — she listens politely. The way children listen to stories about things that are hard to believe.

Like rationing during a war. Like a world before antibiotics.

Something that technically happened. But feels like it must have been lived by different kinds of people.


What happened to software engineers — and then everyone else

I should talk about this separately. Because I was one of them.

A software engineer at Amazon and Gojek, before I left to build my own thing. I had a front-row seat. And I watched it happen faster than almost anyone was willing to admit out loud.

In 2026, “AI will take software jobs” was still a debate. Smart people argued both sides. Meanwhile, the answer was already arriving.

One engineer could do the work of five. Companies didn't fire four engineers — they just stopped hiring. Headcount froze. The engineers who remained felt powerful. Shipping faster than ever. They told themselves this was fine.

By 2028, the entry-level had quietly disappeared.

Not through layoffs. Through the absence of offers. New graduates applied in thousands. Responses didn't come. No announcement, because there was nothing to announce — just a collective, unspoken decision by a thousand hiring managers that the entry pipeline no longer made sense.

I remember a kid who messaged me that year. IIT graduate, top of his class. Had applied to 200 companies. Heard back from three. He wasn't unqualified. He was just arriving at the exact moment the door was closing, and nobody had thought to leave him a note.

By 2030, what remained of the job looked more like taste than technique. You described what you wanted. You reviewed what the AI built. You caught the errors that required judgment, not syntax.

Still work. But it had lost the thing that had made engineers insufferable at parties for fifty years — that particular pride of making something that hadn't existed before, from nothing, with your own hands.

Gone.

And with it, quietly, went a certain kind of person who had built their entire identity around it.

What happened to software engineers is what happened to everyone else — just earlier. Accounting. Design. Marketing. Writing. Teaching. Each field had its own timeline, its own denial phase, its own reckoning. The shape was always the same.

“The cruelest part was not that the machines took the jobs. It was that they took the jobs people had spent years becoming. The identity, not just the income.”

A chartered accountant I knew told me in 2030 that she felt like a fraud.

Still employed. Still paid well. But spending her days reviewing outputs she couldn't have produced herself, approving decisions she couldn't have reached herself.

“I don't know if I'm still an accountant,” she said. “Or just an accountant-shaped human who sits next to an accountant.”

That sentence stayed with me for nearly twenty years.


What we told our children — and what we should have

My daughter asked me once what it was like to have thousands of followers.

I told her it was like speaking into a large room where most people were only half-listening. But occasionally someone really heard you. And that made it feel worthwhile.

She thought about this for a moment.

“That sounds exhausting, Papa.”

She is right. It was.

The parents who navigated this era well were not the ones who predicted the right industries. None of us could see that far ahead — the map was wrong for everyone.

The ones who got it right taught their children that it was okay to not know. Okay to change. Okay to build an identity that wasn't attached to a job title or a follower count. Not as philosophy. As practice. Something they demonstrated in their own lives, daily.

The ones who struggled kept preparing their children for a world that had already ended.

Who pushed for engineering degrees in 2030, certain it was still the safest path — not realising the path had quietly washed away. Who told their kids that hard work in the right field would protect them, because that had been true for their own parents and so felt like a law.

It wasn't a law. It was a specific moment in history. And it had passed.

I understand why they held on. Having no map is more frightening than having a wrong one. We were all doing our best. Some of us just held on longer than we should have.


I don't regret building Supergrow. I don't regret posting. I don't regret the years I spent figuring out how to help people tell their stories online.

Those stories mattered. Some of them changed lives — I know because people told me.

But I wish we had asked harder questions, earlier. About what the feed was doing to our sense of self. About what we were actually optimizing for when we chased engagement. About whether a business built on attention was ever going to end somewhere good.

The internet gave us the greatest publishing infrastructure in human history.

For about twenty years, we used it mostly to perform, argue, and sell things to each other.

We could have done more with it.

Maybe that is what my daughter's generation will figure out. They grew up knowing the machine exists. Knowing it is faster and more tireless than any human. Knowing it does not doubt itself at 3am or need to feel loved.

And they chose, anyway, to do things slowly. To know forty people well instead of forty thousand people barely. To make things that weren't optimized for anything except the making of them.

That is not failure. That is a correction.

I hope they keep it.


With love, and mild nostalgia for the era of the LinkedIn carousel,

Deven Bhooshan Founder, retired at 52. India, 2046.

We sat in the corner of the restaurant so we wouldn't be too visible.

Darjeeling, 2006. An LTC trip – the government-mandated leave travel allowance my father got once every 3-4 years. The only time we went anywhere. The only time we ate at restaurants.

The waiter came over. “How many people?”

I didn't understand the question. My father said “6.”

We got a laminated menu with stains from previous customers. All of us – my parents, my sisters, me – just stared at it. Nobody knew what to order.

My father ordered the safest thing possible: One sabji. One dal. Rice. Roti. Salad.

No starter. No soup. No desserts.

Those things didn't exist in our universe.

We recreated home in a restaurant because we didn't know how to do anything else.


The Pattern

At home, we didn't have the concept of variety.

Every meal was one dal OR one sabji. Not both. One dish.

Breakfast was parantha with tea. Or biscuits. Almost every single day.

Some special days we had non-veg – festivals, birthdays, occasions.

We never went out.

Clothes? We bought them only for occasions. Somebody's wedding. A festival.

We didn't have “day clothes” and “night clothes.” We had summer clothes and winter clothes. That's it.

There was no concept of buying clothes for home. You wore something outside until you couldn't anymore, then it became home clothes.

Travel? That Darjeeling trip. Maybe one or two others. Every 3-4 years if we were lucky.

I didn't have a favorite food. I didn't have a favorite color. I didn't have a favorite place.

Not because I was easy-going or low-maintenance.

Because I never learned to have preferences.

You're just grateful when there's food on the table. You don't develop opinions about what KIND of food.


The Whiplash

2015. My first paycheck from Amazon.

I stared at the number.

I didn't know what to do with it.

What do people even buy? What do people order? Where do people go?

I was that kid from the Darjeeling corner table, now holding a menu with no stains and no idea what I actually wanted.

So I learned. Aggressively.

I tried everything. Went everywhere. Said yes to everything.

Travel. Food. Clothes. Experiences.

If I saw it, I tried it. If someone suggested it, I did it.

By 2021, I had zero savings.

Zero.

Not because I was reckless. Because I was making up for every corner table. Every stained menu. Every LTC trip I never took.


Learning to Choose

My girlfriend has known me for 19 years.

She knew the corner table kid. She saw the first Amazon paycheck. She watched me try everything, go everywhere, say yes to everything.

And when I hit zero in 2021, she didn't judge.

I panicked. Started reading about personal finance. Got serious about saving.

I was earning well, so rebuilding wasn't difficult. But I swung to the other extreme – suddenly afraid to spend on anything.

That's when she helped me understand something I'd never learned:

It's okay to enjoy things. Slowly. Without shame.

It's okay to say “I like this” instead of “I'm grateful for anything.”

It's okay to have a favorite restaurant. A preferred seat. An opinion.

One day in 2025, we were shopping and I kept looking at this watch. $1,500.

I liked it. I really liked it.

But I wasn't going to buy it.

“Just buy it,” she said.

“It's too expensive.”

“You like it. You can afford it. Buy it.”

I bought it. And it felt strange – buying something just because I wanted it. Not because I needed it. Not because someone was getting married. Just because I liked it.

We went to Dubai recently.

We went to this amazing Indian restaurant in Dubai Mall.

We ordered so many things. Tried dishes we'd never had.

And here's the part that would have been impossible before:

We left 2-3 dishes because we didn't like them.

Small portions, but still – we LEFT food.

Growing up, if I put something on my plate, I finished it. Regardless of how it tasted.

Not because of values or environment. Because I was grateful to have anything on my plate at all.

But in Dubai, I had permission to not like something.

Permission to waste a little.

Permission to have an opinion.


The Transformation

My wardrobe now:

I have clothes specifically for airports.

I have clothes for long-distance travel, sorted by weather AND location.

Beach clothes. Multiple swimming costumes.

Socks of different shapes, sizes, and textures.

Undergarments specifically for slightly transparent shorts so they don't look bad.

Three different watches – one for running, one for everyday, one for parties.

And right now? I have 2-3 pairs of clothes sitting in my almirah that I haven't even worn yet. Bought them a month ago. Just sitting there.

The kid who had “summer or winter” now has granular categories for everything.

From one dal, one sabji to eating at so many different restaurants I've lost count.

From occasion-based clothes to unworn outfits in my closet.

From LTC trips every 3-4 years to visiting so many places in India I cannot count. To traveling to multiple countries across the world.


Both Things Can Be True

I feel grateful for everything.

Grateful for my parents who gave us those LTC trips even when money was tight.

Grateful for my sisters who sat with me at that corner table.

Grateful for my girlfriend who showed me I could have preferences without losing gratitude.

Because here's what I figured out:

The corner table taught me gratitude.

But gratitude without preferences isn't humility.

It's just never learning what you actually want.

When I look at those 3 watches, those texture-sorted socks, those unworn clothes – I don't feel guilty.

I feel happy. Proud. Free.

Free to choose. Free to have opinions. Free to leave food I don't like.


If I could talk to that anxious kid in the Darjeeling restaurant, staring at the stained menu, sitting in the corner hoping nobody notices us...

I'd tell him: One day you'll leave food you don't like, and you won't feel bad about it.

Hello

I am Deven, a software engineer turned indiehacker. This is my journey of how I scaled my product from 0 to $230k ARR.

I started Supergrow 2 years ago(April 2023), and it currently has 800+ recurring customers. If I had to start all over again, here's exactly what I would do.

I am dividing this blog post into 8 steps. Let’s go.

Step #0: Finding the Right Idea

People often say ideas are worth zero. I strongly disagree. If you're an indie hacker, choosing the right idea is the most important thing at the initial stage.

How to Find the Right Idea

Here's my approach to finding a winning idea:

  1. Look for validated markets: Pick a market that's already proven and has a positive trend pushing it upward. As an indie hacker, you cannot afford to spend your limited time or money educating users about a problem. The users should already know about the problem.

  2. Find markets with paying customers: The biggest indicator of a real market is that there are companies already making money in it. One important caveat: Don't take VC funding (YC or any sort of funding) as proof that a market exists. Many funded startups are still trying to validate their market.

  3. Avoid creating new categories: Creating an entirely new category in the market is a much harder sell compared to going after a crowded market and iterating on features for an underserved Ideal Customer Profile (ICP).

Let me show you how this works in practice by sharing my own experience.

My Journey to Finding Supergrow

Let me share how I applied these principles and came up with the idea for Supergrow, my current product that's doing $230K ARR:

Before Supergrow, I was working on another product called Honeypot, which helped founders find leads from Twitter. I regularly shared my learnings and journey building Honeypot on Twitter. One day, a SaaS founder purchased the annual plan of Honeypot. Curious about what convinced him, I reached out to ask.

His response was eye-opening: “I saw your content on Twitter and felt the need for the product. I started following you on Twitter. Your transparency made me feel like I kind of knew you, and then I just bought the plan.”

This was my lightbulb moment. I realised the power of personal branding for founders, and thought I should build something that could help other founders build their personal brands on Twitter and LinkedIn.

However, around this time, Elon Musk acquired Twitter and completely changed the Twitter app ecosystem. They effectively killed thousands of apps overnight by introducing a $45K per month API plan that only established companies could afford. This made building on Twitter impossible for indie hackers like me. My product Honeypot.so was at $12K ARR when this API pricing change killed it.

Interestingly, this Twitter change affected many indie hackers who had built their businesses on the platform. My now co-founder was working on another Twitter-based tool that was similarly impacted by the API changes. Having followed my journey and updates on Twitter, he reached out to explore the possibility of working together on something new.

At the same time, I noticed LinkedIn was increasingly focusing on creators and incentivising people who were creating content on their platform. I did some market research and found existing personal branding tools, but they were falling short in helping people with content creation, the most important part of personal branding.

Coincidentally, OpenAI had just launched GPT-3, bringing massive improvements to AI-assisted content creation. I saw the convergence of these market trends: a growing need for personal branding, LinkedIn's creator focus, and the advancement of AI for content creation.

This market analysis led me to create Supergrow—a product in an existing market (LinkedIn personal branding tools), but with a focus on an underserved need (AI-powered content creation), with affordable pricing.

Now that I had identified a promising idea, the next step was to thoroughly understand what was already out there.

Step #1: Study Your Competitors Deeply

Find competitors in your market and use their products day in and day out. The goal isn't to copy them but to understand why they built what they built. Try to identify what you could improve that would improve the core workflow of their users.

My Competitor Research for Supergrow

When I started building Supergrow, I thoroughly studied the three main players in the LinkedIn content creation space:

Taplio: It was the biggest player in the market—very pricey with tons of features. However, I noticed that their content creation capability (the core function users needed most) wasn't great. They had built an impressive set of features, but the most critical component was shit.

AuthoredUp: This was a free Chrome extension. The design was poor, and it didn't work reliably. Yet people were using it simply because it was free. One thing stood out, though they had an excellent post preview feature that users loved.

ContentIn: I struggled to understand why people were using this tool at all. Its UI looked like it was from the 90s, and 90% of the time it didn't work properly. Yet it still had users, which confirmed there was strong demand for this type of solution.

After studying these competitors, I created a small proof of concept focused specifically on generating better LinkedIn posts. The results immediately showed that I could create something significantly better than what was available. This was incredibly motivating.

This experience taught me a crucial lesson: when studying competitors, focus on understanding their core value proposition and where they're falling short in delivering it. Don't get distracted by all their features or fancy marketing. Instead, ask yourself: “What is the one thing users really want from this type of product, and how can I do it significantly better?”

Your improvement should focus on the core user experience, not just cosmetic changes like improving the onboarding flow or the signup page. Those optimizations come later.

I've watched many copycats who duplicated my entire product but failed to add any unique value. Almost all of them shut down within a year.

With a clear understanding of the market gap and competitive landscape, I was ready to build something users would truly love.

Step #2: Build an MLP (Not an MVP)

Build a Minimum Lovable Product, not just a Minimum Viable Product. What's the difference?

An MVP proves your concept works. An MLP proves that people will love using it.

My Approach to Building Supergrow's MLP

My key insight was simple: everybody has stories or learnings that they want to share on LinkedIn, but they don't know how to transform those experiences into an engaging LinkedIn post.

This realisation guided my entire product development. For Supergrow, I focused intensely on simplicity and solving this one core problem exceptionally well. My first version had an extremely simple design with:

  • One-click content generation
  • Two-click content publishing
  • A single feature focused specifically on solving the core problem of personal branding on LinkedIn

The entire product experience was designed around a simple workflow: users would share a short paragraph about their learnings or worries, and Supergrow would generate high-quality content based on that input.

I deliberately avoided feature bloat. No complex dashboards, no analytics, no scheduling tools, no audience insights—just pure content generation that worked better than anything else on the market.

Your first version should focus on doing one thing exceptionally well—so well that users are willing to overlook the features you haven't built yet. It should solve a specific pain point better than existing solutions, even if it has fewer total features.

With a focused product that solved one problem extremely well, it was time to tell the world about it.

Step #3: Share Your Journey Publicly

Document and share your building journey on Twitter, LinkedIn, or other platforms where your potential customers might be. This serves multiple purposes.

How Sharing My Journey Built Supergrow

My cofounder and I consistently shared updates about Supergrow's development on LinkedIn and Twitter. This transparency and public building approach led to several significant outcomes:

  • LTD platforms reached out to us directly – Instead of us having to pursue them, they discovered us through our content
  • We acquired our first customers from my LinkedIn network – People who followed my journey became early adopters
  • Investors started reaching out to us – Without us pitching or seeking funding
  • We built credibility in the space – Sharing our process established us as thoughtful builders

In our content formats, we mixed different types of content:

  • What we were building and our progress
  • Why were we making specific product decisions
  • Memes and relatable content about founder life
  • New feature updates and launch announcements
  • Customer testimonials
  • Specific LinkedIn content strategies that were working for us and our early users

This variety kept our content interesting while consistently reinforcing our expertise and product development. The key wasn't just sharing wins—it was sharing the entire journey, including challenges and decisions.

Don't just share your wins—share your struggles, decisions, and learnings. Authenticity resonates more than perfectly polished updates.

As our visibility grew through consistent sharing, we were ready to monetise our early traction.

Step #4: Launch with Lifetime Deals (LTDs)

Don't give your product away for free. Instead, offer lifetime deals through platforms like AppSumo and RocketHub, or through private Facebook groups dedicated to LTDs.

Our Successful LTD Launch on Rockethub

In our case, the Rockethub team reached out to us after seeing our journey shared online. This is another benefit of Step #3—platform teams are constantly looking for promising products to feature.

The Rockethub team, particularly Charlie Paten and Karan, were incredibly helpful in preparing us both mentally and from the product side for the launch. They understood what would make the campaign successful and guided us through the process.

Our LTD launch on Rockethub generated $65,000. This gave us enough capital to scale both our product development and marketing efforts without needing to raise external funding. Having this cash cushion allowed us to make decisions based on what was best for the product rather than chasing short-term revenue.

Why People Worry About LTDs (And Why You Shouldn't)

I've seen many founders hesitate to offer lifetime deals. Yes, we all know subscription is the holy grail of SaaS, but at the early stage, what you're really looking for is a tight feedback loop and validation, not perfect unit economics.

Here are the common concerns about LTDs and my perspective:

Recurring costs of supporting users for life: From my experience, only about 10% of LTD purchasers will actively use your product, and less than 5% will use it regularly. This drastically reduces the actual support burden compared to what you might expect. The cost of supporting this small group is well worth the capital and feedback you receive.

LTD customers can be demanding: It's true that LTD customers often have high expectations, and this can cause mental strain. However, this pressure forces you to build a better product faster. Their demanding nature becomes an asset if you channel it properly.

Platforms take a significant cut: Most LTD platforms will take 30-50% of your revenue. Despite this, the exposure, credibility, and remaining capital are still worth it at the early stage when your alternative is often $0 in revenue.

Lifetime deals serve three core purposes:

  • They validate that people are willing to pay for your solution
  • They provide much-needed cash flow to continue development
  • They create a pool of invested users who want to see you succeed

Price your LTD high enough that customers take it seriously but low enough that it's an obvious bargain compared to your eventual subscription price.

With capital in the bank and a growing user base, we needed to build a system to capture and implement feedback effectively.

Step #5: Create a Customer Community

Form a Slack, Discord, or WhatsApp community with your LTD customers. The goal is to be as close to these early adopters as possible.

Getting Close to My Early Customers

In the early days after our LTD launch, we dedicated 1-2 hours every day to Intercom, personally responding to customer questions and feedback. This direct communication provided invaluable insights that shaped our product roadmap.

Beyond chat support, I added tools like Microsoft Clarity and Mixpanel to understand exactly what features people were using and where they were getting stuck. The heat maps and user flows revealed patterns that weren't always apparent from direct feedback alone.

Most importantly, we scheduled 3-4 customer calls every week. These conversations went beyond feature requests and revealed the deeper needs and use cases that our customers had. Often, the most valuable insights came from casual conversations rather than formal feedback sessions.

These early adopters will:

  • Provide invaluable feedback on your product
  • Tell you exactly what features to prioritise
  • Help you identify bugs and edge cases
  • Become your product evangelists if you listen to them
  • Share how they're using your product in ways you never imagined

This community connection is the unfair advantage that indie hackers have over larger companies with layers of customer service reps and managers.

Once we had established a direct line to our users, we needed a system to organise and prioritise their input.

Step #6: Iterate Based on Customer Feedback

Talk to your community regularly. Run surveys, conduct interviews, and pay attention to support requests.

Scaling Our Feedback Management

In the beginning, Intercom was sufficient for managing feedback and feature requests. However, as our user base grew, the volume became overwhelming. That's when we integrated with Canny, a dedicated feedback management platform.

This transition accomplished several things:

  • Users could add their feature requests in a structured way
  • Other users could see what we were currently working on and what was planned for the future
  • Customers could upvote existing feature requests, helping us understand demand
  • It created transparency around our roadmap and priorities

We also implemented a proactive approach to gathering targeted feedback. We added prompt messages on Intercom and integrated them with specific pages in our app. When a user visited certain features, Intercom would automatically send a message asking for feedback about that particular feature. This contextual feedback was incredibly valuable—users could respond while actually using the feature, providing much more specific and actionable insights.

To maximize visibility and participation, we prominently placed the Canny link in our product's sidebar. This high visibility generated a significant amount of feedback, almost too much.

Staying Focused Amid User Requests

One critical lesson I learned: not every piece of feedback is worth acting on, no matter how many upvotes it gets. You need to maintain a long-term vision for your product.

For example, many users requested that we build LinkedIn DM automation features. Despite numerous requests, we deliberately chose not to build this. It would have diverted our focus from our core value proposition of content creation and potentially turned us into a completely different product.

The most dangerous feedback isn't the obviously bad ideas—it's the good ideas that aren't right for your specific product vision.

Having a clear picture of what your product should (and shouldn't) become is essential for filtering the feedback you receive.

We prioritised features based on a combination of user votes, our own intuition, and most importantly, alignment with our long-term product vision. This disciplined approach ensured we built a coherent product rather than a collection of disjointed features.

What You'll Have After These Six Steps

If you've followed the process I've outlined so far, you'll have achieved three critical milestones:

  1. A working product that people actually use – Not just a product that works technically, but one that solves a real problem well enough that people incorporate it into their workflows.

  2. Product ambassadors who can't stop talking about you – By listening to your early users and solving their problems, you'll have created vocal advocates who promote your product without being asked.

  3. Most importantly, paying customers – You've validated that people will exchange money for the value you provide, which is the ultimate form of validation.

These three elements create the perfect foundation for transitioning to a subscription model and scaling your business. Now it's time for the final step.

Step #7: Launch Subscription pricing

Once you've validated your product with LTD customers and improved it based on their feedback, it's time to transition to a subscription model and expand your reach.

Our ProductHunt Launch Success

When we were ready to launch Supergrow's subscription model, we decided to make a big splash on ProductHunt. This turned out to be incredibly effective because of all the groundwork we'd laid in previous steps.

We reached #1 Product of the Week on ProductHunt, largely because our happy LTD users were eager to support us. They actively posted about our launch on LinkedIn and Twitter, and many shared in various communities they belonged to. This organic support was far more powerful than any marketing we could have done ourselves.

A Critical Launch Insight

One small but powerful insight from our ProductHunt launch: offer a special deal specifically for people coming from the platform. We gave our product for $1 for the first month to ProductHunt visitors.

The results were remarkable—more than 50% of these trial users converted to full-price subscriptions after the first month. This approach allowed us to:

  • Significantly lower the barrier to entry
  • Give users enough time to experience the full value of the product

Find Your Second Marketing Channel

Beyond your product launch, you need to figure out at least one other scalable marketing channel besides your own personal branding. For Supergrow, it was partnering with LinkedIn influencers.

Finding the right influencers and structuring mutually beneficial offers with them became one of our most important skills. My cofounder took the lead on managing these relationships, developing a systematic approach to identifying and working with the right LinkedIn personalities whose audiences matched our ideal customers.

Whatever channel you choose—influencer partnerships, content marketing, paid ads, SEO, or something else—it needs to be something you can systematically optimise and scale.

With a successful launch and a second marketing channel in place, you can now:

  1. Launch your subscription pricing model

  2. List your product on platforms like ProductHunt, Uneed, and other relevant directories

  3. Leverage the testimonials and case studies from your LTD customers

  4. Start expanding your marketing beyond your initial community

Mistakes I Made Along the Way

Despite our success, two significant mistakes cost us time and growth potential:

Mistake #1: Focusing Too Much on B2C Initially For the first two years of Supergrow, I focused heavily on B2C customers. This was a strategic error. The B2B market offers significantly less churn and more predictable revenue streams. We're now pivoting toward B2B customers, and I wish we had done this from the beginning. For indie hackers building similar tools, consider the lifetime value and acquisition costs between B2C and B2B customers before committing your limited resources.

Mistake #2: Neglecting SEO From Day One We relied heavily on our social media presence and influencer marketing, but completely overlooked SEO. This meant missing out on a steady stream of organic traffic that compounds over time. If I could start over, I would invest in SEO content from the very beginning, even if just publishing one quality article per week. The compounding effect of SEO would have given us a much stronger foundation and reduced our dependence on platform algorithms.

Final Thoughts

To summarise what truly mattered in our journey to $230K ARR:

  • Choose a market with proven demand
  • Build something people love, not just something that works
  • Share your journey transparently
  • Get paying customers early through LTDs
  • Create a direct line to your users
  • Execute relentlessly on feedback
  • Learn from your inevitable mistakes

The path I've outlined worked for me in reaching $230K ARR, and I believe it can work for you too. I am launching another product soon, and will follow the same journey myself.

I'd love to hear what you're working on—connect with me on Twitter here: devenbhooshan

Leaving you with this Twitter post :)

Enter your email to subscribe to updates.