Hitting $125k MRR as a solo founder by doubling down on the right
segment
Jason Zigelbaum saw a gap and filled it, funding the build with his savings and revenue from another app. It took two years to get traction, but then, he doubled down on a specific segment. Now, he's at $125k MRR — and he's solo.
Here's Jason on how he did it. 👇
The tool he wished he'd built
Before building Zigpoll, I built a couple of SaaS products. Shopify absorbed one of them (an app called Metafields Manager), and I sold the other, so I needed a reliable income.
I grew up in e-commerce, mostly on the agency side, and for years, I watched brands pour money into ads and analytics to understand what was happening on their stores, then guess at the crucial part — why people did what they did. Analytics could tell them a cart was abandoned, but never why. This gap between measurable data and essential insights bothered me enough that I eventually built the tool I wished we'd had internally.
That tool is Zigpoll. It's a survey and customer feedback platform, built initially for e-commerce, but now also used by many SaaS teams. It offers post-purchase, exit-intent, and CRO surveys — questions that capture a customer at the exact moment they will answer honestly. One question on a thank-you page ("What almost stopped you from buying?") can teach more than a $15K CRO audit, and it does so for free, forever.
I run the company solo: no cofounder, no funding, no sales team. It took about two years to get traction, but it has doubled in revenue every year since. I started 2026 with about $1.03M ARR and am closing June around $125K MRR, roughly a $1.5M run rate. This represents about a 44% increase in the first half of the year. That's nearly half a million dollars of new annual revenue added in six months, achieved solo.
My current goal is $2M ARR, which means adding about $43K more per month.
Funding himself
Building Zigpoll cost far more time than money. I'm technical, so I built the first version of Zigpoll myself with a code editor, not a budget. Nights and weekends were the real currency. I've never taken outside money. I took no VC, no angel, and had no cofounder to split equity or decisions with. That was a deliberate choice as much as a circumstance. I'd spent enough time around other people's businesses to know I wanted one that was fully mine, one I could change on a Tuesday afternoon without asking permission.
Meanwhile, my other app supported me, requiring only a couple of hours per week. When you're a solo developer, your main cost is the income you're not earning while you build, and I funded that gap myself rather than diluting to cover it. Just a product I thought should exist, and enough runway in my own savings to find out if anyone agreed.
Validating and pivoting
The most helpful factor wasn't a tool; it was the vantage point. My agency background meant I'd already watched dozens of e-commerce brands hit the exact same wall, so I wasn't guessing at the problem.
I built the tool, then used the tool to validate and iterate. My customers' answers, rather than my own opinion, informed almost every good roadmap decision I've made. That's a cheap way to build when you're one person, because you're not spending months guessing. You ship the small thing forty people asked for, they stick around, and it compounds.
In fact, the original idea did not focus on post-purchase surveys, but as demand emerged, I leaned into that use case. The same pattern repeated for exit-intent, conversion rate optimization, and order delivery surveys.
A reliable stack
Here's the stack:
JavaScript from front to back
Express + Mongo on the backend
React on the frontend
As the scale increased, I leaned into using Redis as a caching layer, but the stack is very stable.
Being a solo developer, it's important to lean into reliable third-party tools whenever you can. These tools save a ton of time, and if you choose your spots well, they can save a ton of money too.
Pricing and expansion
Zigpoll is a straightforward SaaS subscription. Customers pay monthly, and plans are tiered by the number of survey responses they collect. Because I run the entire operation solo, without a team, office, or sales floor, margins are what you'd expect from a software business with one employee. Real costs include infrastructure, business tools, and some paid acquisition. That's the quiet advantage of staying solo: the model expands faster than the cost base.
Pricing is a product surface, not a one-time launch decision. I redesigned mine several times, and each version taught me something a spreadsheet never would have.
But I'd say the biggest unlock wasn't a price increase; instead, I noticed which customers naturally expanded and then deliberately built for them. Find the segment that grows when you serve them well, and pour your energy there.
As far as chrun, it exists, as it does for anyone selling to small ecommerce brands, some of whom close or pause seasonally. I treat it as a number to keep boring rather than a story to obsess over. I keep it boring by using my own product to find out why people leave and fixing issues they report.
Marketplaces, word of mouth, and GEO
No single launch made the business. No viral post. No Product Hunt day. Zigpoll grew, and still grows, through a handful of channels quietly compounding. When I break down where new customers come from, no single channel tells the whole story.
The Shopify App Store is the biggest single source, accounting for around a third of new signups. Building Zigpoll as a Shopify app first proved to be my most important distribution decision. As a solo founder with no marketing budget, the App Store placed me directly in front of brands with the problem I solve, precisely when they sought a solution. I couldn't have bought that reach. I earned it by optimizing the listing, taking reviews seriously, and shortening the install-to-value path so people quickly understood its benefit.
Word of mouth accounts for the next quarter of signups, and it's my favorite because I can't fake it. Almost all of it traces back to agency operators. A freelancer installs Zigpoll on one client's store. It works, so they go to the next client's store, and the next. When I analyzed "How did you hear about us?" answers, the most common phrase was a version of "A freelancer I work with uses you on everything." So I stopped treating that as a happy accident and started building for it intentionally. The more I remove friction for those who install me everywhere, the harder that flywheel spins.
AI tools represent a channel that barely existed a couple of years ago. Roughly 14% of new signups now come through ChatGPT, Claude, and Gemini, as people ask an assistant what to use and get pointed to Zigpoll. That's my third-biggest channel, and I treat it as an SEO problem for a new kind of search. I ensure the content, docs, and positioning are clear and specific enough that a model recommending a survey tool easily explains what mine does and who it's for.
The remaining channels collectively add up: Google search, some YouTube, and paid social. I write on LinkedIn nearly every day, appear on podcasts, and co-market with my integration partners. None of those are huge acquisition channels individually, but they accomplish something the App Store cannot. They build trust and familiarity, so when someone encounters my listing or asks an AI about surveys, the name isn't unfamiliar. I share the tactics and real numbers behind the business, and the product sells itself as a byproduct of its usefulness.
If I could start over, I'd start building in public from day one. I only got serious about writing openly and sharing the real numbers this year, and it has compounded faster than almost anything else I've done for distribution. It builds trust before someone reaches the product, and it forces me to think clearly about the business because I explain it out loud. If you're building something now, don't wait until you have a milestone worth announcing. The audience compounds like revenue does, and both reward the years you can't get back if you start late.
But here's my main growth advice: Find the channel where the platform handles distribution for you and commit to being the best option there. For me, that was the Shopify App Store. Then, observe which customers refer you without prompting, and build for that segment relentlessly, because word of mouth is the only channel that becomes cheaper as you grow instead of more expensive.
The most expensive mistake
My most expensive mistake was misunderstanding the customer for too long. For a long time, I pictured my user as a single in-house ecommerce team, and I priced and built accordingly. At one point, I even gated integrations and AI features to the higher plans, a standard SaaS packaging approach on paper.
In practice, it quietly punished my best-growing segment — agency operators running Zigpoll across a dozen client stores — by charging them extra just to connect tools every client already used. I throttled exactly the people I most wanted, and I didn't see it until I read the onboarding data closely.
Fixing it meant rebuilding the pricing so integrations live on the standard plan, and then building for that segment on purpose. That correction largely explains why my revenue per account climbed 24% this year without a single price increase.
I wish I had committed to the agency operator segment far earlier. My data showed the signal for months before I acted on it, and every good roadmap decision I've made since came from listening to how those operators use the product differently than I imagined. The lesson generalizes: Watch who refers you and expands without being asked, and relentlessly build for them sooner than feels justified.
Listen to your customers
My advice: Listen to your customers.
The first mistake is thinking you listen when you only hear the loudest few. Founders who tweet ask Twitter, founders in a Slack group ask the group, and everyone mistakes the vocal minority for the market. Real listening is quieter and more structured than that. It means asking people who are using or leaving, right at the moment when they can tell you something true, then reading the answers closely enough to act. Most of my best decisions this year came from data sitting in front of me for months.
The most valuable feedback is almost never a feature request. It's the reason someone didn't buy, or the place they quietly wasted ten minutes and never mentioned it. Ask a customer, "How did we do?" and you get a rating you can't use. Ask "What almost stopped you from buying?" and you get a list of every objection your product page didn't close, written by the people who bought anyway. Timing matters as much as the question. A survey on the thank-you page right after checkout will out-teach any email you send three days later, because you caught them while the reason was still fresh.
And you need far less of this than you think. People tell themselves they'll act once the data is statistically significant, so the survey sits and the decision waits. Qualitative feedback doesn't work like a conversion test. You're looking for patterns in why people do things, and patterns show up fast. When forty of your first fifty responses say the same thing, you don't need response number eight hundred. You need the nerve to go fix it. Collecting is never the hard part. Acting on what you hear, especially when it contradicts the thing you were excited to build, is the whole game.
Here's what surprised me most. If you listen well enough, your customers won't just tell you what to build. They'll tell you who you are for. I spent a long time picturing my user as one kind of person, but my own onboarding answers revealed that real growth was coming from a completely different segment I hadn't been building for. The customer knew before I did.
That's what I'd tattoo on a new founder if I could: You are not the smartest person in your own business. Your customers are, collectively. The sooner you build the habit of asking them and believing them, the faster everything else gets easier. It's the reason I built a feedback company in the first place, and it's still the only strategy I fully trust.
What's next?
My near-term goal is a number I think about most mornings: $2M ARR. I like having a number that's close enough to feel real but far enough that I can't coast to it. The number itself was never the prize, though. I am chasing the proof that a single person, listening carefully and shipping consistently, can build something that compounds without a team, a board, or a funding round pushing it.
My bigger goal is to stop being just an e-commerce tool. Zigpoll started on Shopify because that's the world I came from, but I built a feedback engine, and every business needs to understand its customers, not only those selling physical products. SaaS and app companies face the exact same problem in a different costume. They guess why people don't convert, why they churn, and what to build next. That's the same gap I set out to close for e-commerce brands.
So, I want to widen the aperture: making Zigpoll the obvious way for any business to ask its customers the right question at the right moment and turn the answers into decisions. The more value I can add across the whole ecosystem — through integrations, through AI tools easily recommending it, through serving the agency operators who run it across dozens of stores — the more useful the product becomes to people I wasn't even thinking about when I started.
And I want to do all of it the same way I've done it so far: solo, bootstrapped, changeable on an afternoon, built on what customers tell me rather than what I assume. The freedom to do that is the entire point, and hitting $2M without giving any of it up would mean more to me than a much bigger number achieved someone else's way.
You can follow along on LinkedIn and X. And check out Zigpoll!
Leave a Comment
The insight about 14% of signups coming from LLMs like ChatGPT, Claude, and Gemini is fascinating. We talk a lot about standard programmatic SEO and app store discovery, but treating AI recommendation engines as a dedicated acquisition channel is a brilliant look at where search is going.
Also, huge respect for admitting the mistake with gating integrations. So many SaaS founders default to the standard copy-paste pricing model where integrations live on the top tier, not realizing they are actively bottlenecking their best word-of-mouth multipliers (agencies). Unlocking that constraint and letting the agency flywheel spin is clearly paying off.
Awesome execution, Jason. Massive congrats on the $125k MRR milestone solo!
I honestly didn't connect with the survey part in the first line of description, asking myself what consumers would willingly answer questions during the buying process - it feels intrusive.
Then, I opened up when I read "at the exact moment they will answer honestly".
Then the example: One question on a thank-you page ("What almost stopped you from buying?"). Wow
Genius, absolutely genius
The line that stuck with me was "you need far less of this than you think... when forty of your first fifty responses say the same thing, you don't need response number eight hundred." Most founders (including me, admittedly) use "let's get more data" as a socially acceptable way to avoid acting on something inconvenient.
The timing point underneath that is what's really interesting though, catching someone on the thank-you page while the reason is still fresh, versus an email three days later that gets a much shallower answer. I'm building something built entirely around that same idea, just for personal memory instead of customer feedback. Capturing a thought the moment it happens because by the time you sit down to "properly" write it later, the actual reason or detail is already gone.
Question for you: when forty-ish early responses agreed on something, was there ever a case where you almost talked yourself out of acting on it anyway, some version of "yeah but my segment is different" and what actually got you to act instead?
Stealing the "what almost stopped you from buying" survey question for my own funnel. Congrats on the solo run to $125k MRR.Stealing the "what almost stopped you from buying" survey question for my own funnel. Congrats on the solo run to $125k MRR.
To be honest i am a young founder and don't have too much experience yet, but one thing I have realised and learnt is that so many founders obsess over building more features. This was a great reminder that understanding who your best customers are is often a much bigger lever than building more for everyone.
This is such a powerful reminder that success often comes from going deep in one niche rather than trying to serve everyone. Two years of struggle and then massive growth once you focused - that's the classic founder journey. Did doubling down on the niche also help with word-of-mouth and customer quality? I'm curious if you saw better retention or lower churn with more targeted customers vs the broader market approach.
This is impresseive!
Congratulations Jason and a really great article James. This really really resonates with me. A niche is everything. For example, we are building a dot com called AnimationDr and another one called FreePayCalc and each of these have a particular niche. For example, the animation studio w/ a built-in ad agency was designed from the get-go to place animated videos in the FMCG market niche in India. This is strictly B2B. For FreePayCalc (you can Google that; we're the only one that comes up and therefore excellent for GEO positioning w/ AI) our niche are freelancers (B2B also), all 1.47 Billion of us! That's a big niche for a big group who need our specialized help saving and making more money. So to bootstrap one's way there is very possible these days like never before. The obstacles are fewer if you are humble enough to ask AI to help you. I'm 67 years old and couldn't code my way out of a paper cup! The really cool thing is, I don't need to since AI is such a big help! Look, can an old noob like me see himself as an Indie Hacker? Yup, even if all the real hackers laugh at me, I'm already laughing all the way to the bank! And again Jason, good for you for sticking it out to realize your dream!
Incredible milestone, Jason! Doubling down on a specific segment is always a game-changer, but often hard to execute when you want to please everyone. It's fascinating how a simple thank-you page survey can uncover insights worth more than a $15k CRO audit. Congrats on the $125k MRR, truly inspiring for solo founders!
Very very impressive. It's great to see hard work and strategic thinking paying off! Hope to hear updates in 6 months to see where you've landed, and how you got there.
I feel this should be a textbook article on how to demonstrate your app and convince people how good it is. Although it contains a lot of specific, valuable points about running a business, what impressed me most is that he made decisions based on data collected by his own app. As he said, the app isn't just a tool but an engine that helps him make decisions that create a positive feedback loop
Really good read. The part that stood out to me is that the best segment wasn’t something he guessed at the start — it showed up through behavior.
People were referring it, using it across multiple clients, and naturally expanding. That feels like a much stronger signal than just saying “this is our target customer.”
I’m learning this with my own SaaS too. It’s tempting to describe the market too broadly, but the real question is: who gets value fastest, who comes back, and who would actually miss the product if it disappeared?
Also liked the point about pricing. It’s easy to treat pricing like a one-time decision, but it’s really part of the product. The right pricing should remove friction for the users who are already getting the most value.
The 'doubling down on the right segment' lesson is one most content and directory sites learn too late, including me at dailyaitools.io. We try to be useful to everyone and end up being essential to nobody. Jason's move of going deep on e-commerce rather than staying broad is the kind of decision that feels risky but is actually the safer bet long term. The most expensive mistake section is what I'd read twice, premature scaling before segment clarity, where most bootstrapped products bleed out quietly.
This is a great reminder that the biggest opportunities often come from solving a problem you've experienced firsthand. The part that stood out most was using customer feedback to discover the ideal customer segment instead of relying on assumptions. That's a lesson many founders learn too late. Congrats on building such an impressive business.
I see that achieving real success takes years, and I think a key trait of successful people is persistence—not giving up, just like you. I build websites for SaaS businesses, and it’s impressive that you’ve achieved this level of success on your own. Do you avoid taking money from investors so you could work with greater freedom?
Gating integrations on higher plans while your fastest-growing segment were agency operators installing on dozens of client stores is such a painful mistake to read because it makes complete sense in hindsight and zero sense while you're doing it. Standard SaaS packaging logic actively punishing the exact people driving your word of mouth.
The 14% of signups from ChatGPT and Claude is the number I want to understand better. Are those converting differently from App Store installs or behaving similarly once they're in?
This is the most relevant thing I have read since launching my first Shopify app three days ago.
I built AltGuard — a Shopify app that helps EU merchants comply with the European Accessibility Act using AI-generated alt text. Solo founder, no team, no funding, approved July 1st. Reading about Zigpoll's growth through the Shopify App Store is exactly the signal I needed that the platform itself can be a real distribution channel if you earn it.
The agency operator insight stopped me cold. I had not thought about who installs my app across multiple client stores. Web accessibility agencies and Shopify consultants who manage EU merchant portfolios could do exactly that — install AltGuard on every client store that needs EAA compliance. I was not building for them at all. That changes starting today.
The GEO channel also surprised me. 14% of signups from ChatGPT and Claude recommendations is a number I did not expect to see. I am going to look at my documentation and public-facing content specifically through that lens now.
One question — when you say you "shortened the install-to-value path," what specifically did you change? Was it onboarding flow, the first screen they see, or something else entirely?
$125k MRR solo is genuinely one of the most motivating numbers I have seen on this platform. Congratulations.
That is an incredible breakdown of an impressive solo founder journey. The way you leveraged your existing background to pinpoint a real problem—and then iteratively used the product itself to guide the roadmap—is the textbook way to build a sustainable SaaS.
It is especially fascinating how you recognized agency operators as your true growth engine and adjusted your pricing to fuel that flywheel rather than choke it. Removing friction for the people who manage multiple stores is a brilliant distribution hack.
Congratulations on hitting a $1.5M run rate solo, and good luck on the push to $2M!
hitting 125k mrr solo proves that doubling down on the right segment beats chasing every lead. you didn't win by building more features but by focusing entirely on one high-value group to skyrocket LTV and crush CAC. that discipline to ignore the noise and just serve the right people is what turns a side project into a machine.
the 14% from GEO is the number that stopped me. that's not a rounding error, that's a real channel now. and the insight you give about why it works, "post-purchase surveys for Shopify stores" fits in one sentence, is exactly right. LLMs surface things they can explain cleanly. if your product positioning requires two paragraphs of context, a model won't recommend you even if you're technically the best option.
the pricing mistake about gating integrations is a really common trap and probably one of the most expensive classes of SaaS pricing errors. it feels right on paper because integrations look like "power user features," but in practice integrations are often the things that make the product actually work for how someone uses it. gating them creates friction precisely at the moment where a user is trying to embed your product into their workflow, which is the moment you most want to reduce friction.
the JS full stack (Express + Mongo + Redis) is a sensible choice for exactly the reasons you don't mention, which is that at this scale it just stays out of your way. Redis as a caching layer on top of Mongo is a solid pattern for survey response reads, especially when you're aggregating across high-volume post-purchase events where the same store's data gets read way more often than it's written. curious if the survey delivery itself is server-rendered or fully client side, given that it's triggering on checkout thank you pages which are often pretty restricted environments.
The segment discovery is the most transferable lesson here. I'm in early customer discovery for a coding tool, and the same thing happened I kept pitching developers with sophisticated workflows and getting polite nods. When I started talking to people who didn't have their own workaround yet a tax lawyer doing no-code projects, a school admin they described the pain in more detail and with more urgency than anyone I'd deliberately targeted. The people who haven't built their own fix are the ones who'll actually pay.
Also, the GEO stat caught my eye 14% of signups from ChatGPT/Claude/Gemini recommendations. Building in the AI space myself, the products that get surfaced by LLMs are the ones whose use case fits in one sentence. "Post-purchase surveys for Shopify stores" is exactly that. Same forcing function as positioning for humans, just a faster feedback loop.
Great story. Listening to customers and shipping consistently are timeless lessons. Congrats on building such an impressive solo business!
Nice
This is a solid reminder that growth doesn’t always come from adding more features or chasing every possible user. Sometimes the real unlock is noticing which customer segment is already getting the most value, then building around them properly. The agency angle makes a lot of sense because one happy agency can quietly become multiple active accounts through client work. Really liked the point about using customer feedback as the roadmap instead of guessing from the outside.
With this story I've understood several things I can change:
Build what you need: we get obsessed with finding the "winning product" and forget that our own problems or needs are the best product to build. Solving problems we actually have should come first.
One well-exploited channel is better than 10: we don't need 10 channels to reach our customers, we just need one where the platform does the distribution for you.
Build in public from day 1: the person regrets not sharing his experience earlier, because it could've been useful to document the process, guide, or help others.
GEO (Generative Engine Optimization) is already a real channel: it's worth optimizing your site/landing page so an LLM recommends it.
This resonates so much - the power of choosing a niche and going deep seems like the pattern across every successful solo founder I know. Most people try to be everything to everyone and end up serving nobody well. Curious if you found that your customer acquisition got easier once you had the right segment validated, or was it challenging to pivot?
Thats a great read
The GEO section is what stuck with me. We're building a no-code E2E testing tool for mobile apps, and we made a related bet early: we shipped MCP support so an AI assistant can generate and drive test cases directly, instead of treating "AI recommends us" as a channel to optimize after the fact.
Your point that LLMs surface products whose use case fits in one sentence is exactly right, and it cuts two ways now. It's not only about writing docs so a model can recommend you - increasingly the model is the user, calling your tool through MCP. That changed small things for us, like how we name test steps and structure output: it has to read cleanly for a human in a visual editor and parse cleanly for a model running the same flow.
The segment lesson landed too. We currently point at QA engineers, startups, and indie devs all at once, and "watch who expands and refers you without being asked" is the nudge to actually read our onboarding data instead of guessing which one to build for. Filing that under things I should do sooner than feels justified.
Congrats on $125k solo — genuinely motivating.
The Qampanion team
Really impressed by how you clearly identify the core problem and build a solution to solve it. The doubling down on a specific segment story resonates - so many founders try to be everything to everyone. Your approach to staying solo and keeping 100% control is also inspiring. The focus on getting the customer feedback loop right through your survey tool is exactly what founders need to understand. Thanks for sharing the details.
The Shopify app store angle is underrated. Distribution built into the platform beats chasing traffic from day one. Picking the right ecosystem matters as much as the product.
Your journey is incredibly inspiring, man. I have a few questions about building in public, since you mentioned starting it from day one:
What exactly do you share? Do you post about how you came up with the idea, or is it more about the day-to-day coding and development updates?
Where do you usually post your updates? My Reddit account just got banned, so I’m currently looking for other platforms that work well.
How do you balance development and marketing? Right now, I’m spending almost all my time coding and fixing bugs, leaving barely any time for marketing. Are there any high-leverage marketing strategies or tools you'd recommend for a solo founder?
This is the big milestone and I know it was not achieved overnight. Very congratulations. I would be glad to get tips about your strategy on growing products and building platforms that scale.
This resonates a lot.
I'm building an AI platform for retail traders, and I've been forcing myself to treat distribution and product as two separate experiments.
One thing I've learned is that "building more" often feels like progress because it's measurable, while talking to users is uncomfortable and unpredictable. But almost every meaningful product decision I've made came from real conversations, not from my roadmap.
Right now I'm deliberately keeping my product in early access and collecting feedback before assuming which features people actually value. It's slower than shipping feature after feature, but I think it leads to a much stronger product in the long run.
For me, the hardest part isn't writing code anymore—it's earning enough trust that someone is willing to try the product and tell me what's wrong with it.
Reaching $125K MRR as a solo founder often comes from focusing on a well-defined customer segment instead of trying to serve everyone. By doubling down on the right niche, you can improve product-market fit, increase conversions, and grow revenue more efficiently.
This is one of the most honest breakdowns I have read in a while. The part about misidentifying your customer for too long hit me personally because I am going through the exact same realization right now with Wealtii, a fintech platform I have been building solo for 10 months.
Jason's point about the agency operator segment is so underrated. The instinct is always to build for the loudest, most obvious user. But your real growth segment is almost always the quiet one who keeps coming back, expanding, and referring without being asked.
The AI discovery channel at 14% is also fascinating. That is a massive signal that most founders are still sleeping on. Content and positioning that answers the "what do I use for X" question is the new SEO, and it compounds silently in the background exactly the way Jason describes.
The biggest takeaway for me personally: Do not wait until you have a milestone worth announcing to build in public. The audience compounds exactly like revenue does. Wish I had started sharing the journey openly from month one instead of month nine.
Congratulations on $125K MRR solo. It is a genuinely rare thing to build with this level of intentionality and patience. 🙌
I am also building a product for bootstrapped founders. Thank you for your post. it guides through me a specific path
The line that stuck with me was "I keep churn boring rather than a story to obsess over." That's basically the thesis I'm building around right now. Most churn tools treat it like a mystery to solve with predictions, but the boring version, just surfacing the failed payment or the downgrade before the cancellation, is usually enough.
Also appreciated the honesty about wishing you'd built in public from day one. I just shipped my first thing after months of working alone, and that regret is exactly what I'm trying to avoid repeating.
Super impressive Jason. Your post motivates me to work harder and start thinking much more strategically.
Wow, impressive!
I'm currently at the early idea validation stage, but your post really inspires.
I also love the idea of working solo on a product, but I always thought that at some point I'll have no choice but starting building a team. Your story proves that it doesn't have to be that way. Good luck with your next milestone!
man, super jealous tbh. i'm on the indie dev grind right now too, exhausting myself every single day and still sitting at $0 revenue. really makes me wonder when i'll actually be able to support myself doing this. congrats though, seeing this gives me hope.
This resonates a lot. I'm running a couple of solo projects right now — one's an Arabic-language World Cup 2026 fan hub, the other's a workflow automation SaaS — and the "doubling down on a niche" part is exactly where I'm at with the first one. There's a huge, noisy market for football content in Arabic (mostly low-quality streaming/piracy sites), and I've been debating whether to compete broadly or go narrow on something like real-time match data + recaps that the bigger players don't do well. How did you know you'd found the right segment vs. just a segment that felt easier to defend?
this is the one nobody wants to hear early on. going narrow feels like you're leaving money on the table but it's the opposite - a tight segment means your message actually lands and word spreads because everyone in that niche knows each other. i spent way too long trying to be relevant to "all b2b" before realizing a vague message to everyone converts worse than a sharp one to a small group. what finally made you commit to the segment instead of hedging?
It is true that SEO is the only thing that last that much in 2026. No Tiktok, no Ads, just SEO.
The agency-operator insight is the whole story here, and it generalizes: those freelancers aren't customers, they're a channel. I built a Microsoft reseller business for 20 years on that exact model, and the moment you treat multi-account installers like partners (consolidated dashboards, volume pricing, maybe margin) instead of end users, acquisition cost drops while account count compounds. The 24% revenue-per-account jump from un-gating integrations is what happens when you stop taxing your best channel.
I really enjoyed reading this. One of the most interesting parts of your story for me was treating AI recommendations as "SEO for a new kind of search." I think that's a mindset more founders should start adopting. I also loved your point about customers eventually telling you who your real audience is if you're willing to listen. Thanks for sharing such an insightful journey, and congrats on everything you've built!
Hitting $1.5M ARR solo with a basic stack (Express, Mongo, React, Redis) just proves that distribution beats over-engineering every damn time. No need for an over-engineered mess to scale. Just focus.
good
Nice work.
The "no single launch made the business" part is refreshing. Most IH content revolves around the perfect Product Hunt launch or the viral tweet that 10x'd signups. Jason's story is the quieter reality: a handful of channels compounding over 2 years, funded by another app's revenue, not a VC check.
The portfolio approach is interesting too—he didn't go all-in on Zigpoll from day one. He kept his other app running (supporting him with "a couple hours per week") while building Zigpoll on nights and weekends. That's a different risk profile than the "quit your job and bet everything" narrative we usually hear.
Question: when you noticed e-commerce was the segment to double down on, was there a specific metric that told you "this is it"? Or was it more of a gut feeling after talking to 40-50 customers?
That 14% stat on signups from AI assistants is wild, love how you're framing it as SEO for a new kind of search.
Quietly building Attractable, it turns visitors who'd otherwise bounce into leads with instant interactive tools, and flags the exact UX issues costing you conversions.
Did you notice that same pattern, plenty of traffic but flat conversions, across the brands you worked with before Zigpoll?
Would love your honest take, and if it resonates, the waitlist's open at attractable . co
This is the playbook. The Brief Network bet on 8 hyper-specific niches instead of 1 generalist newsletter — same principle: double down on what works, segment ruthlessly, ignore the rest. Niche beats scale every time because switching costs are massive once you own the credibility. What was the moment you realized your segment was the unlock?
"The absolute 'unlock' moment was looking at our onboarding data and realizing our standard pricing was quietly punishing our fastest-growing segment—agency operators.
We were gating integrations and treating them like a standard single-store e-commerce team, which added massive friction for the exact people driving our word-of-mouth flywheel. The moment we dropped those restrictions and started building features specifically for multi-store management, our revenue per account jumped 24% in a single year without a price increase.
You're spot on—owning the credibility within a hyper-specific niche makes switching costs massive and builds a moat that scale alone can't touch."
Love this.!Analytics tell you what happened, surveys reveal why it happened. We're exploring a similar problem from a different angle with Flow Era—using an AI conversation instead of a survey. When visitors hesitate, a contextual popup starts a real-time conversation, understands what's blocking them, answers based on the creator's product knowledge, and helps prevent lead leakage before they leave. I think both approaches highlight the same truth: understanding the "why" is where growth begins.
The what/why split is exactly the gap most content businesses ignore too. You can see traffic going up in analytics and still have no idea why people didn't buy — or why the ones who did chose you over a free alternative. The conversational angle makes sense: a survey is passive, a real-time conversation catches the hesitation while it's still live.
This comment was deleted 4 days ago