I'm a solo founder. It took me 9 months and at least 3 stack rewrites to ship my SaaS.

First of all, I genuinely have to say this: indie hacking is really not easy.

Seeing you receive your first Stripe payment instantly reminded me of the first sponsorship payment I ever got myself. Only people who’ve actually built something on their own understand how much that first dollar is truly worth.

Your post honestly made my brain buzz because it felt way too relatable. I come from an architecture background, and now I’m basically a passion-driven “vibe coder.” For the past two months, I’ve been grinding away on an AI translation SaaS focused on long-form documents.

A lot of people have told me: “LLMs are already so powerful — who would even use your tool? There’s no future in this product.”

I don’t see it that way.

My idea came from a very simple frustration: AI has made translation easier, but serious external-facing content still can’t be handled as effortlessly as one-click machine translation promises.

For SaaS teams, founders, technical writers, and global businesses, translation is not just about converting words. It affects trust, product understanding, documentation quality, terminology consistency, and ultimately a company’s professional image in foreign markets.

During testing, several professional translators gave my product surprisingly high praise. Some of them even joked that tools like this might eventually replace their jobs. Honestly, I think their concern is valid — because I truly believe in what I’m building.

Along the way, AI has also been my only full-stack mentor.

Back then, constantly seeing people on X bragging about “launching a micro SaaS in 48 hours” genuinely made me anxious. But reading that it took you 9 months to figure out Auth, databases, and webhooks from scratch honestly gave me relief. That’s the raw, unfiltered reality for founders like us who didn’t come from traditional technical backgrounds.

What’s even crazier is that our products somehow collided in the funniest possible way.

Right at this moment, I’m sitting in front of my computer doing a huge amount of GEO work (Generative Engine Optimization) — wrestling with Codex prompts, modifying robots.txt to allow GPTBot and ClaudeBot crawling, and tweaking JSON-LD structured data so AI engines can better reference my site in the future.

Then I refreshed X and saw your post about building IvaBot — a tool that audits a website’s “AI citation readiness.” That honestly felt like some kind of weird quantum entanglement inside the coding universe. I’m definitely going to try your product later today.

As for balancing coding and marketing: honestly, I’m struggling with it too.

Hiding behind code and chatting with LLMs feels comfortable because there’s instant feedback. Marketing feels like shouting into an empty wilderness most of the time. When I improve my code, I can immediately see my product moving closer to the vision in my head. With promotion, it often feels like punching into cotton.

Right now, I’m forcing myself to treat marketing like manual labor. I spend 90% of my energy learning distribution and promotion. On days when I’m focused on SEO and Twitter growth, I strictly ban myself from opening the code editor at all. I physically separate the two worlds.
good luck with your Product Hunt launch on May 27th. Your family might already be tired of hearing Stripe webhook errors all day, but somewhere across the planet, there’s another slow-moving indie builder cheering for you.

Keep going.

Honestly, I think a lot more founders are going through this than people admit.

AI and modern tooling have dramatically lowered the barrier to building, but they also make it easier to start moving before the product structure, architecture, or long-term workflow is fully thought through.

The hard part is that early momentum feels productive… until rewrites start compounding.

One thing I keep noticing is that the real cost usually isn’t the rewrite itself — it’s all the lost time from changing assumptions:

• product direction
• workflow design
• architecture
• data structure
• user expectations

That’s a big part of why we’ve been thinking so much about upfront product clarity and structured planning while building Agiloop. Not heavyweight requirements — just enough alignment that the system can evolve without constantly restarting.

Three rewrites in nine months sounds slow until you count what the first two taught you about your own data model. Mine took two rewrites before the schema stopped fighting me, and the third took a weekend because by then I knew the shape of the thing. The 9 months bought the last 2 days.

Nine months solo with three stack rewrites and you shipped and got a real Stripe payment. That is the path. Most people reading this have not done what you did.

One thing I would add to your 'what I would do differently' list: validate payment intent before building, not after. Not 'people said they would pay' -- actual money in an account, before the product exists. I am testing this right now with BillWatch, a federal bill tracker for small business owners. Landing page only, no product yet, pre-orders at /month. Every person who pre-orders tells me something the waitlist-only people never would -- the ones who paid are compliance folks and accountants, not the politically engaged founders I assumed were my audience. That reshaped the whole product.

The 9 months makes sense when you were also learning full-stack from scratch. The right question now is: what is the cheapest test to find out if someone will pay for module 4 before you build it? The first Stripe payment you got is not the ceiling -- it is the starting point for figuring out who actually has the problem badly enough to solve it.

billwatch-landing.vercel.app -- not to pitch, just to show what I mean by 'landing page only.'

Slow solo here too. Three months on a Telegram quiz platform in production with paying users — and the build path was basically "rewrite everything once I knew what I actually needed." Your 9 months isn't slow. It's the realistic number when you're learning the tools while you're building with them. On dev vs marketing: I underestimated marketing by an order of magnitude. I had a working product for months before anyone outside my network heard of it. The thing I'm betting on now is that writing publicly about the technical decisions reaches more people than writing about the product itself. The blog post you mentioned (ChatGPT/Perplexity/Claude/Google citing different sources for the same query) is actually your real positioning. Every other SEO tool optimizes for Google rank. Yours measures readiness for AI citation — that comparative data IS the differentiator. A monthly version of that report, broken down by industry, would probably do more for top-of-funnel than any paid ad.
Congrats on the first Stripe payment. That one hits different after 9 months alone with the doubts.

Nine months is not slow — it is honest. The founders I have consulted with who shipped in 6 weeks usually spent the next 6 months untangling tech debt that blocked every feature they wanted to build next. You built something real and got a paying customer. That is the actual benchmark.

On dev vs marketing balance: strict time-boxing works better than splitting every day. A week of focused build followed by a week of focused outreach tends to produce better output than 4 hours of each daily. Context switching at this stage is genuinely expensive.

The stack cost reduction is underrated as a signal. Going from $200 to $40/month before revenue is the kind of infrastructure discipline that keeps you in the game long enough to find product-market fit. Most no-code-heavy stacks quietly become anchors around month 8-12 when you need to add something the tools do not support.

The AI citation readiness angle is real and differentiated. Curious: are you tracking which content attributes (structure, source links, entity density) correlate most with getting cited across different AI engines? That data would be genuinely valuable product signal.

Nine months solo, non-dev, three rewrites, learning the backend from scratch with AI as your teacher — and a live Stripe payment at the end of it. That's not slow, that's stubborn in the best way. Respect.
On the dev-vs-marketing balance, I went the other way and it's its own kind of hard. I'm a non-dev solo founder too, and I got so scared of the "build for 9 months then hope someone wants it" trap that I flipped the order: landing page + waitlist first, see if strangers will actually give me an email, then build. The downside is it feels backwards — you're "marketing" something that doesn't exist yet, and some days that feels fake. But it's already saved me from one build into silence.
No clean answer on the balance, honestly. But the $200 → $40 cut after moving to Claude + a real stack hit home — went through almost the exact same "my no-code bill is eating me alive before a single sale" moment.

My first batch image processing tool was launched in just one weekend, and it has been iterated for five months. It is still being iterated and its features are being added. At first, I didn't pay much attention to the promotion and operation of this tool. As a result, almost no one knew about it or used it. Later, I started to add effective and useful backlinks, and the site ranking improved slightly. The number of clicks increased, and I occasionally received feedback from users. I am not currently running this business full-time; I am just doing it part-time. However, I do my side hustle whenever I have free time. I persist in doing things that may fail, because if I don't do them, I will not have the opportunity to change the status quo.
I usually work on my product tools after my family goes to sleep at night and get up an hour or two earlier in the morning. I also use my commute to communicate with AI and learn more about SEO. As a front-end application development engineer with 10+ years of experience, I have a lot of knowledge to learn.

I have been a software developer for decades and fluent in servers, networking and cloud services as well. I just built a new type of relationship app in 4 months. 16-22 hours per day for 4 months, so probably close to the same man-hours that you put in.

I was completely focused on building everything from the schema to the CSS. Marketing is now what I need and I find that harder than building awesome software.

I also started using Claude about half way through to speed up the front end development, as that is my weakest coding ability. He definitely sped things up, but he also has some very bad habits I had to talk him out of.

1. tendency to replace an entire module rather than fix the one line that was wrong. This is bad if you have already tested that module, you now need to retest everything in that module and anything that relies upon it.
2. inconsistency code style. Doesn't matter if you don't care to understand the code itself, but if you intend to do manual maintenance in the future, having similar things work in a similar way will certainly help you understand what is going on.
3. guessing when debugging. A certain amount of guess-work is normal when debugging, but it is better to check what the cause could be and investigate that. Also randomly changing your code while guessing can break things that were working previously. After 3 guesses, I ask him if he is guessing and he admits it and we then investigate rather than guessing. It is faster that way.
4. he can overly complicate things. Knowing how to code gives me an advantage when he brings back code that is inefficient. I can ask him why, or explain a better way of doing things and he responds well to that critique. Be especially careful with database retrievals, as he sometimes pulls back more rows, or unnecessary columns which will slow down your database at scale. You may not notice it today with 1,000 users, but when you have 1 million users and everything crawls, this is why.
5. generic variable naming conventions. It took a while to get him to stop naming functions and variables as generic versions, when I knew we would need a similar function or variable in a different module. This would lead to confusion later on and very likely the introduction of bugs. Suggest better names if you don't like what he came up with.

That was more than I intended. It got away from me, yeah. Claude is an excellent tool for development, the best I have found, just be aware he is at the same level as a 6 month in Junior Developer, not even an intermediate developer and he needs supervision and direction to excel.

So well done on getting something working. Getting something working as a non-developer in 9 months is amazing!

I wish you the best in getting the marketing done and people using your product.

I am just starting with the marketing and as capable as I am, marketing is not my strong suit, and not where I should be focusing my efforts. I think I need to find someone to help me with that.

Nine months is almost exactly our timeline too. We rebuilt the data layer three times - started monitoring everything (news, social, legal databases) and ended up doing one thing: Congressional bill tracking by keyword and sponsor, delivered to Gmail or SMS.

The convergence that unlocked the first Stripe payment was the same pattern you're describing. Narrowing scope until the value became undeniable rather than impressive. The rewrites weren't wasted - they taught us what the product actually was.

First payment is a real signal. Most founders hit it and then immediately try to expand scope again. The rare move is to go narrower still until the retention proves out. Congrats on getting there.

Honestly, this was refreshing to read because it sounds much closer to real solo-founder building than the “built in 14 days, hit $20k MRR” stories we constantly see online.

The part that stood out most:

“AI was my teacher.”

I think we’re entering a phase where non-traditional builders can finally execute ideas that previously required full engineering teams — not because AI replaces expertise, but because it reduces the fear barrier to learning and building.

Also relatable:
rewriting stacks, rebuilding systems, realizing the first architecture wasn’t scalable, spending months learning things nobody sees from the outside.

People usually celebrate launches.
Very few talk honestly about the messy middle.

And honestly? Getting the first Stripe payment after building something alone for months is a huge milestone.

Wishing you a great Product Hunt launch 🚀

The stack rewrites are so relatable — I think every dev secretly believes the next framework will be the one that finally ships. Glad you pushed through anyway.

The blog post about how ChatGPT, Perplexity, Claude, and Google AI cite different sources for the same query is your strongest asset going into the May 27 PH launch — it demonstrates the exact problem IvaBot solves instead of just describing it, and SEO founders are already searching for that data. Leading with the comparative engine-citation finding as the hook will give PH visitors a specific reason to care before they’ve heard the pitch in a way that “AI citation readiness tool” on its own won’t.

One thing worth solving before the launch: PAYG at $5 creates low first-purchase friction, but audits aren’t naturally recurring events. The retention trigger probably isn’t a reminder to run another audit — it’s a change in how a specific AI engine weights citations. Even a lightweight email alert for that (score drop, competitor gains a citation you lost) would shift IvaBot from a one-time diagnostic to a monitoring habit, which is a completely different retention story.

The 9 months isn't really the build, it's the apprenticeship. You shipped two things at once: the product, and yourself as someone who can build the product. The first one converts to MRR. The second compounds into every project that comes next at maybe 10x the speed. Most founders only count the first. The second is where the real return on the 9 months lives.

The 'everyone ships in 2-3 months' line is mostly survivorship bias. Most don't ship at all. 9 months solo, no dev background, three pivots, and a Stripe charge at the end is a fast outcome by any honest measure. The real asset you built isn't the stack, it's 15 years of SEO judgment baked into the audit logic. Competitors with twice your engineering speed can't replicate that. Next move I'd focus on: find 10 SEO consultants who already audit client sites manually, give them free credits, and let them sell IvaBot for you. Distribution is now your bottleneck, not code.

Adding to this - three things worth setting up before that next signup, and they're not feature work, so they don't conflict with the "distribution first" focus this thread keeps landing on:

One: authorization on every endpoint, not just authentication. Being logged in isn't a check. Every request that reads or writes a record needs to verify this user owns that record.

Two: signature validation on every webhook you accept. Stripe especially. Without it, anyone who knows the URL can post fake payment events at your endpoint. Stripe's library has a one-liner for it.

Three: secrets in environment variables, never in the repo. Rotate anything that's ever been committed, including to a private repo, because private repos are one careless invitation away from public.

These aren't AI-code bugs. They're move-fast bugs that AI made easier to ship, because the model will happily generate the auth-check-free endpoint and won't flag what's missing. Worth an evening of your time.

This hit close to home. I'm a solo founder too — built LifePilot (iOS app that turns goals into 4 daily actions) and today is literally my first real public launch on Uneed. No team, no launch squad, I'm even traveling alone while watching the upvote counter.

The 9 months and 3 rewrites part is real for everyone who builds without a team. You just don't see it from outside. Congrats on the first Stripe payment — that one always feels different.

If you're curious how a solo launch looks in real time: https://www.uneed.best/product/lifepilot-ai-planner

The $200 to $40/month optimization is incredible. The key insight here that often gets missed: you didn't need a no-code tool to validate, you needed to learn how to build. Using Claude to learn the fundamentals while building (webhooks, HTTP, JSON parsing, etc.) is exactly the right approach for a non-technical founder. Most people get stuck trying to outsource all the learning. Your timeline (9 months from zero to paying customers) is legit solid, especially launching with live Stripe payments and already with viral traction (that ChatGPT/Perplexity blog post). One question: are you planning to keep the $5 entry point, or does the May 27 PH launch change pricing strategy?

Congrats on shipping. 9 months feels long when you read it back, but the lessons compound. My first product took 8 months and my 8th took 4 weeks because the same boring problems repeat (auth, billing, error tracking, legal pages, basic analytics, a working landing).

Two things that helped me cut time the most after product number 3:

1. A ship-ready checklist locked in stone. Auth + Stripe + Sentry + privacy/terms + plausible. If any of those is missing I'm not done. If I'm tempted to add anything beyond, it goes to v2.

2. No stack rewrites after week 1. The cost of switching from Typebot to Claude was probably worth it for you because the unit economics changed, but if I had done that 3 times in product number 1 I would have quit. After week 1 I force myself to ship on whatever ugly thing I picked first.

On IvaBot: the PAYG at $5 against $50-300/mo competitors is a real wedge, the audience just needs to see that comparison front and center. Most SEO founders I know will pay $5 to test a tool but never sign up for $50/mo from a name they have not heard of.

Good luck with the next two weeks of traffic. The second paying customer is usually the hardest one because it confirms the first was not a fluke.

The $200 to $40 stack switch is an underrated milestone — it's not just about cost savings, it shows you understood your product well enough to cut the dependencies you no longer needed. And the 9-month timeline is something to own, not apologize for: you weren't slow, you were teaching yourself a completely new discipline while shipping something real. That Typebot phase where ChatGPT was your teacher for 6 months clearly laid the foundation that made the Claude rewrite possible — most people skip that kind of deep hands-on learning and pay for it later in technical debt. Congrats on the first paying customer, that's the real milestone.

9 months doesn't sound slow to me — it sounds honest.

I'm also building solo right now. Just launched an AI citation tracking tool
(which is funny because your IvaBot literally checks AI citation readiness —
we're solving adjacent problems from different angles).

The stack rewrite cycle hit close to home. I went through similar phases
before finding a setup that actually worked. And the moment you said
"my partner is tired of hearing about Stripe webhooks" — I felt that deeply.

One thing that helped me: I stopped thinking of rewrites as failures and
started calling them "paid education." You clearly learned something real
at each stage — the Typebot phase alone sounds like it taught you more
than any course would have.

Congrats on the first Stripe payment. That one hits different.

this post is very refreshing, alot of people can learn secondhand through you

3 stack rewrites — I felt that. I come from industrial automation (PLCs, SCADA systems) and building a SaaS was a completely different world. The hardest part wasn't learning React or setting up Stripe — it was the constant second-guessing about whether the architecture would hold up once real users showed up.

What finally got me to stop rewriting and start shipping was accepting that version 1 doesn't need to be perfect. It needs to exist. Congrats on getting it out the door. That takes more courage than most people realize.

This felt very real to read. I think a lot of solo founders quietly go through the rewrite phase but never talk about it publicly. The $200 → $40/month cost drop also stood out, that kind of discipline matters way more than people realize early on.

Congrats on the first Stripe payment. That’s a huge milestone.

On the PAYG pricing, smart for first-purchase friction but the trap for audit tools is that audits aren't naturally recurring. Someone runs the audit, applies whatever the report flags, and that's it. No reason to come back until something changes on the site. The retention play for IvaBot probably isn't pricing tiers but a change detection layer that pings users when their score drops or when their competitors get cited and they don't. That turns a one-time tool into a monitoring habit. PH launch traffic will tell you who buys once. The next 30 days will tell you who buys twice.

Great post! I really resonate with the struggle of stack rewrites. I’m currently building my first SaaS for local businesses, and I also went through some challenges while containerizing it for Azure deployment. It’s definitely not easy to ship, but the learning process is worth it. Congrats on finally launching!

Nine months solo is not slow. It is honest. The
people who "ship in 2-3 months" are usually
shipping a landing page, not a working product with
three modules, Stripe integration, and a real
backend.

I am months into building protocol infrastructure
as a solo founder. Claude changed my velocity too.
The shift from "AI as a curiosity" to "AI as a
daily implementation tool" is the single biggest
productivity unlock I have found. Your cost drop
from $200/month to $40/month by cutting the no-code
stack and building properly with Claude is a
pattern I think more solo founders will follow.

To your question about balancing dev time against
marketing time: I spent the first 5 months on pure
dev with zero public presence. Started posting a few
weeks ago. The mistake was not starting
conversations earlier, because the feedback changes
how you explain and position the product. You do
not need to stop building to do marketing. You just
need to talk about what you are building while you
build it. Even one post a week changes the
trajectory.

Congrats on the first Stripe payment. That is the
hardest one to get.

i feel you on the github usage and the rewrite. My first rewrite was thanks to GPT Codex after i gave it full control and it messed up my code.( actual deletion of code files)

9 months as a non-developer with 3 rewrites is not slow, it's the actual pace. The 2-3 month ship stories are selection bias, we only hear the fast launches because slow ones get abandoned before they post about them. The Typebot phase wasn't wasted either, every prompt and webhook you wrote is muscle that compounds on the next thing you build. The trap now is going back to product, more modules, more polish, when the bottleneck is distribution. Your first Stripe payment is the signal to spend the next 90 days finding ten more of that exact buyer, not adding features.

9 months and 3 rewrites without quitting is the actual skill. I've been building PM tools on the side for 2 years - rewrites are where you figure out what the thing actually is. congrats on the first Stripe.

Really resonated with this, especially the 9 months and 3 rewrites part. I'm in a similar spot, solo founder, built an e-signature tool, just launched it a couple of weeks ago. The stack decisions alone can eat months. I started with the right stack luckily (Next.js + Neon + Vercel) so I avoided the rewrite pain, but the distribution side is where I'm struggling now. Every platform has restrictions for new accounts - Reddit flags you for spam, HN won't let you comment on your own post, directories need 7-day-old accounts. Building was maybe 30% of the work. The "what I would do differently" section hit hard, especially "think about security from day one." Good luck with the PH launch on the 27th!

9 months is real, and not that slow if the product came out right. Dev vs. marketing balance is the right question, but here's what took me too long to learn: marketing doesn't start after you ship. The best product decisions I ever made came from customer conversations I had while still building, even one call a week. Not for validation theater, just to stay honest about who you're actually building for. Did you talk to potential users during the build, or mostly after launch?

the blog post about how ChatGPT, Perplexity, Claude, and Google AI cite different sources for the same query going slightly viral makes sense because nobody has good data on that yet and it's the question every SEO person is quietly panicking about. how did you find it, did you write it before or after the product launched and how much traffic did slightly viral actually mean in absolute terms? asking because that content strategy is probably your best distribution channel right now and it would be worth understanding what made that specific post work

9 months from scratch plus learning and coming up with a saas product is just awesome. Will definitely try as I am a seo lead. Will give my feedback on this

This feels real because stack rewrites are often part of learning, especially for solo founders building while figuring things out. Reducing costs, shipping, and getting the first payment matters more than matching someone else’s timeline.
Foundersbar helps startups focus on validation and sustainable product building so founders do not confuse speed with progress.

The B2C-to-B2B logic is clean, but there's one number missing from your post that's going to shape the pivot more than reply rate or demo close rate: your effective price per user is ~$14 ($650 / 45 paying). That's the anchor your B2B per-seat pricing will get back-solved from, whether you want it to or not — the first agency that asks "what do your individual users pay?" will benchmark you against that.
Two things worth pressure-testing before outreach hardens:

Per-seat vs. per-cohort pricing. Agencies running peak season (March–Aug) don't want seat math — they want capacity. A "100 mocks/month, pooled across students" SKU usually closes faster than $X/seat because it matches how counselors actually think about their bottleneck.
The waiver elimination is a pricing event, not just a demand event. Every B2C visa-prep tool in the Indian market is about to reprice or launch institutional tiers in the next 2 quarters. If you anchor low on the first 3 B2B deals, that becomes your ceiling for 12 months. Worth checking where the closest substitutes in Indian study-abroad counseling sit before you quote your first agency.

One concrete thing to watch: the gap between what a counselor's hour costs the agency and what your tool replaces per hour. That delta is your real pricing room, not your B2C price.
Also — 5% free-to-paid on a one-time product with no retention loop is genuinely strong. Don't let the pivot narrative bury that signal.

Nine months is not slow, it's just honest. I went through a similar arc building a browser-based tool, where the first version worked but the architecture was wrong, and I had to tear it down and rebuild before anything felt shippable. The $200/mo to $40/mo cost reduction by ditching no-code for a custom backend is a move more solo founders should hear about. Curious how you're balancing dev time vs marketing now that you're post-launch.

Eight months in, two rewrites done, and one I'm still kicking myself over — your timeline isn't an outlier. I'm a non-traditional solo dev too (a small iOS memo app, a Captio replacement). My biggest detour was a server-side sync layer I deleted before users ever saw it: three weeks of confidence drained right before launch. The pay-as-you-go from $5 is a smart call — subscriptions add a second friction layer most early SEO tools haven't earned yet. The first Stripe payment is a quiet shift; mine made me stop negotiating with the roadmap and start honoring usage data instead.

Love how this actually makes docs ‘doable’ for Ai instead of just readable brings testing and feedback full circle

The rewrite cycle is real. I think most solo founders go through at least 2-3 before finding the right abstraction. What finally made you stop rewriting and ship?

The $200→$40 cost reduction before revenue is the kind of discipline most founders skip and then wonder why their runway evaporated. The other thing that stood out: you treated three stack rewrites as learning, not failure. That's the right read — each rewrite compressed your understanding of the problem until the third one only took a weekend. One framing I'd offer for after the Product Hunt launch: instead of adding more modules to this product, consider what adjacent tiny products share the same backend. A portfolio of small tools on the same infra distributes risk across buyers without multiplying your engineering burden.

The $200/mo to $40/mo cost reduction by killing Typebot + Memberstack is a smart move that many solo founders delay too long. I went through a similar realization — no-code tools are great for prototyping but the monthly costs stack up fast before you have revenue. Curious about your pay-as-you-go pricing at $5 — how did you decide on that vs a subscription model? For a solo SEO tool, PAYG feels like the right call since usage can be irregular.

"This really resonates with me. I'm also a solo founder building TraderTracking — a trading journal for forex, crypto and stock traders. I went through a similar journey: months of development, multiple rewrites, and learning to make better architectural decisions along the way. I also moved my dev workflow to Claude and it was a game changer for productivity. The part about balancing development time with marketing is something I'm struggling with right now — just launched and trying to figure out the right split. Thanks for sharing so honestly, it helps knowing others go through the same grind."

For the non-tech person it's really impressive result!

First of all, you DID finish the product — it's already pretty nice :)

You are free to ignore it, but: as a tech person, I would like to recommend you some product design actions to take before the implementation. From my point of view, the toughest part is not to build (it's already pretty hard) but to maintain what you have created. So you will definitely benefit from the planning stage.

Besides that — wish you luck and a ton of subscribers!

9 months is not slow, it's honest. Most people claiming 2-3 months either had prior experience, a cofounder, or didn't really ship. You came in with zero dev background and got a paying customer. That's the actual benchmark.\n\nThe stack cost drop from $200 to $40 before a single sale is also a real lesson a lot of people need to read. Congratulations on shipping it.

The best advice I got was to launch as early as possible and actually talk to users. It's so tempting to keep polishing before showing anyone, but every time I've done that I ended up building things nobody wanted. Getting that first batch of feedback is brutal but so worth it. How did you find your first users?

Nine months and three stack rewrites with a first Stripe payment is not a failure timeline, it is a real product timeline. The SEO + AI citation readiness angle is sharp and timely. One observation from someone who does this daily: the pay-as-you-go model at $5 is a strong entry point for solo founders but the challenge will be LTV. Make sure the first audit delivers enough actionable insight that users immediately see the ROI that is what drives the second purchase. On distribution: Reddit and Indie Hackers are great for early feedback, but for SEO tools the real distribution channel is SEO itself. The fact that you're already seeing impressions in Search Console is the early signal that matters most.

Nine months and three rewrites with a first Stripe payment is not a failure timeline, it is a real product timeline. The mistake most non-technical founders make is treating shipping as the finish line. You just hit the start line. From here the next 9 months should be about distribution, not more rewrites. Pick two channels you can run yourself given your SEO background (you have an unfair advantage on organic), and stop adding modules until customer 50. The product is built. Now sell it.

Last winter I hit the same wall on my own solo build — a lightweight memo app for iPhone, a Captio replacement that emails notes in one tap. I tried to box it: Tuesdays and Thursdays no code, only outreach. It collapsed by week three because I'd open Xcode "for ten minutes" and lose the morning.

What ended up working was tying marketing to a shipping rhythm — every TestFlight build forced one IH or Reddit post about the smallest visible change. Felt cheesy at first; it's the only reason I have 20-something testers now instead of zero. The "ship in 2-3 months" myth on this forum quietly stings — most honest solo builds I see inhabit your 6-9 range. How are you planning to protect marketing hours during Product Hunt week itself, when the temptation to fix one more bug is highest?

I think a lot of people underestimate how messy the journey can get before something actually ships.
Curious — looking back, is there anything you would simplify or do differently from the start?

This is extremely relatable as a solo builder. The “I rewrote everything 3 times before first Stripe payment” part hits hard.

Also interesting to see how AI changed your development speed — feels like that’s becoming a real shift in how solo devs build now.

9 months is not slow — it's honest. Most "shipped in 6 weeks" posts skip the 3 versions they threw away first.

The no-code -> proper backend path makes sense. You outgrow the tools when you finally understand the problem well enough to build it right.

I started piecing together ideas around last October, then went heads-down on solo development from January, and finished a few days ago. Reading your post, I felt a lot of overlap with my own experience.

I also started knowing almost nothing about coding. Used Cursor at first, then switched to Claude midway through the build. I sank around $200/month on Cursor for a while and still kick myself for not switching to Claude from the start.
I spent months heads-down on just the build, and I'm now in the stage where I've completed it and switched fully to marketing. Doing all of it alone really makes simultaneous multitasking impossible.

Wanting feedback or validation from other founders is completely natural, and IH or Reddit definitely help. But for the dozens of decisions a founder makes every day, researching threads one by one and reading comments isn't realistic or efficient. Honestly, that's the gap I built around. Feels like a fit for what you described. Let me know if you want a look.

This is way more honest than most “I built a SaaS in 2 months” stories.

The part people always skip: the rebuilding phase.

3 stack rewrites in 9 months isn’t a failure — it’s literally what happens when you’re:

learning backend + auth + infra from scratch
validating product direction at the same time
and trying to keep costs alive long enough to survive

What actually matters here is this:
👉 you didn’t stop
👉 you simplified the stack
👉 you reduced costs from $200 → $40/month
👉 and you got your first Stripe payment

That’s the real milestone, not the timeline.

Also, the shift from no-code tools → Claude-assisted custom backend is a big inflection point. That’s usually where a project stops being “a prototype” and becomes “a real system.”

Most people never get past that middle stage where everything is messy and expensive.

Respect for shipping this solo — especially in a space that’s evolving as fast as SEO → AI search.

Curious: what ended up being the biggest time sink for you — auth, backend logic, or integrations like Stripe/webhooks?

good luck!

This felt very real to read.

The part about rebuilding the stack multiple times and learning backend/webhooks/database concepts while actively building resonated a lot with me. I’m also building solo right now, and I think people massively underestimate how mentally difficult the “unfinished middle” phase is — where you’ve spent months building but still don’t have clear validation yet.

Getting the first Stripe payment after all that probably felt incredible.

Also agree on the AI point. Tools like Claude and ChatGPT have genuinely lowered the barrier for technical execution, but they still don’t replace persistence, product judgment, or actually sticking with the problem long enough to ship.

Really respect the transparency in this post.

Congrats on shipping, Galyna! 9 months as a solo founder is incredibly honest work, especially doing stack rewrites along the way. Shifting from Memberstack to Supabase Auth to save on monthly runway is a massive win that most founders overlook early on.

I’m currently building Velaris, which is a curated marketplace specifically for Micro Tools, Dev Tools, and Datasets. We launched it because we noticed so many independent builders waste months trying to figure out distribution and marketing after spending a year building their tools.

On balancing dev vs marketing: Time-boxing works wonders. We spend one sprint purely focused on code/design, and the next sprint strictly doing SEO optimization and community outreach.

Your AI citation readiness module sounds highly differentiated—would love to see how you structure your data filters!

This is a strong founder story, but the real product angle is sharper than “SEO tool.” IvaBot is really sitting in the new AI visibility layer: helping small businesses understand whether ChatGPT, Perplexity, Claude, and Google AI can actually cite them.

That matters because traditional SEO tools still talk in rankings, keywords, and audits, while the buyer pain is shifting toward “will AI engines understand and reference my site?” That is a cleaner category than broad technical audit plus content generation.

The naming layer is where I’d be careful. IvaBot.xyz makes the product feel like a small chatbot experiment, even though the actual product is more serious: AI citation readiness, content coverage, and technical visibility. If this grows into a broader AI search intelligence platform, Beryxa .com would carry more trust and SaaS weight than a bot-style .xyz name.