What I’ve Learned Building My SaaS Since September
Jul 30, 2025
When I started building this SaaS in September, I didn’t even want to launch a SaaS. I was working with a local client who had a tight budget and was using a mess of disconnected services that refused to talk to each other. None of them offered a usable API. I realized the only way to get them what they needed was to build something myself. That was the spark.
Writing Code Was Less Than 40% of the Work
I thought this journey would be all about coding. Maybe some bugs here and there, but mostly code, deploy, done. In reality, writing the software is maybe 30-40% of the work. The rest? Dealing with FCC emissions concerns with the hardware, back-and-forth with payment processors to facilitate payment token transfers, setting up relationships to get better processing fees for my clients and myself, endless testing, support, and explaining what the product does to non-technical people in a way that makes sense.
Cold Email Trials and Mistakes
One client wasn’t going to keep the lights on, so I had to learn cold email fast. It’s not glamorous. It’s a numbers game and a constant grind to refine messaging, avoid spam filters, and get a conversation started. Once I bring a customer on, the relationship side is the rewarding part. Helping them clean up their processes and seeing them get real value keeps me going.
Recently, I’ve started using tools to help automate some of this outreach. The results aren’t in yet, but anything that helps keep the pipeline warm while I handle everything else is worth testing.
SEO Lessons and Content Experiments
Organic traffic takes time, but it compounds. I’m seeing a lot of search impressions but weak click-through rates. I’ve started using Ahrefs and Search Console to refine my pages to appear more attractive in search results and to target keywords customers are actually searching for, not just the terms I think they should care about.
PPC Tests and Burn Rate Reality
I tried paid ads, thinking they would be a quick way to get new users. Reality check: they drain your cash fast if your landing pages aren’t dialed in. So far, I have seen zero ROI on paid ads, but I know it’s a lever I can pull once I have a healthier budget to test properly and optimize targeting.
Legal Details: Terms, Privacy, and Email Compliance
This part of the business is not fun. Drafting clear terms, privacy policies, and making sure all emails have proper opt-outs is not why I got into SaaS, but skipping it is asking for trouble. Doing it once, correctly, was worth the time.
Documentation
One of my SaaS’s selling points is simplicity, but the reality of managing memberships has complexity baked in. Features that I build today need to be documented for tomorrow, so I remember why they exist and how they work. As I scale, I don’t want every user to require a personal onboarding call or a long email chain just to get started. Good documentation is a force multiplier for support and growth.
The Mental Rollercoaster
There are days it feels like no one cares, and days it feels like everything is finally working. One day you get a cancellation, the next you get a glowing customer message. Sticking to consistent outreach, incremental product improvements, and remembering why I started helps keep the swings manageable.
Building vs Marketing: You Need Both
I can build features all day, but if no one knows they exist, it doesn’t matter. Blocking time for marketing, outreach, and ad testing is just as important as writing clean code. It’s easy to hide in the comfort of coding, but it doesn’t get customers.
The Next Phase
The foundation is built. Now it’s time to grow. My goals are clear: increase user signups, gather customer stories, and improve retention. It’s been fun, but the mantra of “if you build it, they will come” is a lie. Building was just the start. Getting people to care, pay, and stick around is the real game.