Building a SaaS product as a solo founder while running an agency is not for the faint of heart. I’m doing it right now with FollowPerClick — a CTA overlay tool I built to solve a conversion problem I kept running into on client sites. This post is about what I’ve learned from that process. Not the idealized version you read in startup blogs — the actual experience.
Why I Built FollowPerClick
I didn’t start with a grand vision. I started with a problem I kept running into: clients had solid landing pages with good traffic, but visitors were scrolling past CTAs and not converting. Heatmaps showed engagement throughout the page. Session recordings showed reading. But the CTA button in the hero was long gone by the time most visitors were ready to act.
The existing solutions were all the same: intrusive popups, exit-intent modals, or sticky headers that were about navigation rather than conversion. I wanted something different — a persistent but non-disruptive CTA element that followed the user and tracked separately from in-page conversions. When I couldn’t find exactly what I wanted, I built it.
That’s the cleanest origin story for any SaaS product: a real problem you have, that you’ve already validated exists for others, that existing solutions don’t adequately solve.
The Advantage of Being the First Customer
Building a product you use yourself is the single biggest advantage a solo SaaS founder can have. I’m not guessing at the user’s pain points — I have them. Every feature I’ve added started as something I needed on a client’s site. The product decisions have been grounded in real use cases from day one.
This also means my feedback loop is short. I push a feature, deploy it on a client site, check the data, and iterate. No waiting for users to report issues — I find them myself in production. The downside is that my perspective is narrow: I’m building for people who think like me, with my same workflow and context. Getting outside perspectives from different types of users is important to correct for that.
Lesson 1: Solve One Problem Completely
The most common early mistake in SaaS is feature sprawl — adding features because they seem related or because a user asked for them, before the core problem is solved exceptionally well. I’ve resisted this deliberately with FollowPerClick. The tool does one thing: keeps your CTA visible and converts more visitors from long-form content. That’s it. It does that well.
The temptation to add analytics dashboards, A/B testing frameworks, multi-site management, and six other things is real. But each of those features adds complexity, development time, support burden, and cognitive load for users. A product that does one thing brilliantly is harder to compete with than a product that does ten things adequately.
Lesson 2: Pricing Is a Product Decision
I’ve repriced FollowPerClick three times. Each iteration taught me something about who the real customer is and what they value. Too low, and you attract customers who want to pay nothing, cancel when they feel like it, and expect enterprise support. Too high without clear ROI proof, and qualified buyers hesitate.
The right pricing tells a story: it signals value, it filters for serious customers, and it reflects the real cost of delivery. For a conversion tool, ROI-based pricing makes the most sense — the customer’s math is simple: if the overlay lifts my conversion rate by even a few percentage points on a page with meaningful traffic, the tool pays for itself in the first week.
Lesson 3: Don’t Build Before You Validate
I made this mistake on an earlier project and I was careful not to repeat it. Before building more than a functional prototype of FollowPerClick, I tested the concept manually — building custom solutions for specific client sites and tracking results. I needed to know that the concept worked before investing in proper infrastructure.
It worked. Consistently. The manual version was ugly and required developer time for each installation, but the conversion lifts were real and repeatable. That validation made the product investment a business decision rather than a bet.
Lesson 4: Distribution Is the Hard Part
Building the product was the easy part. I’m a technical person running a marketing agency — I know how to solve product and go-to-market problems. Getting distribution for a new SaaS product in a crowded landscape is genuinely hard, and it’s the thing most solo founders underestimate.
My distribution advantage is that I already serve 25+ clients and I’m in active conversations with other agencies and freelancers. My personal brand — this site, my content on LinkedIn, and my 20-year track record — gives me credibility that a cold launch wouldn’t have. But that’s still a limited audience, and growing beyond it requires deliberate effort.
Content marketing, SEO, and partnership distribution are the channels I’m investing in. Not paid ads for a bootstrapped SaaS early in its life — the economics don’t work until you know your LTV and conversion rates cold.
Lesson 5: Running an Agency and a Product Simultaneously Requires Systems
The biggest personal challenge of building FollowPerClick while running an active agency is time and context switching. Agency work is reactive — clients have needs, campaigns have issues, opportunities come up. Product work requires sustained, focused attention to make real progress.
I’ve handled this by treating FollowPerClick development as a protected time block, not as something that gets the leftover hours. Three focused hours on product work beats a scattered seven. The agency work happens in defined hours. Product work happens in defined hours. They don’t bleed into each other if you’re disciplined, and they absolutely will if you’re not.
Where FollowPerClick Is Now
FollowPerClick is live, actively being used on client sites, and producing measurable lift on conversion rates. The core product does what it promises. I’m actively expanding installation options, improving the analytics interface, and building out the use cases for different site types and industries.
It’s not a unicorn startup story. It’s a product built by someone who identified a real problem, validated it, built the solution, and is growing it one user at a time while keeping the agency running. That’s the actual solo founder experience for most of us, and it’s a legitimate path.
If you’re building your own services stack and want to explore working with me on digital marketing or are curious about FollowPerClick, reach out. You can also see more of what I’ve built and worked on in the portfolio.
Frequently Asked Questions
Do I need a technical background to build a SaaS product?
It helps significantly, but it’s not a hard requirement. Many non-technical founders have successfully built SaaS products by partnering with technical co-founders or by using no-code and low-code platforms for early versions. What you do need is the ability to translate user problems into clear product requirements and the business sense to prioritize ruthlessly. Technical skills accelerate everything, but they’re not the only path.
How much capital do you need to start a SaaS product?
Far less than most people think if you’re building deliberately. A focused MVP built by a solo technical founder can often be brought to market for under $20,000 in direct costs. The trap is building too much too soon — over-engineered infrastructure for a product without proven demand is the most common way to burn capital before finding product-market fit. Build the minimum that lets you validate demand, then invest in scaling.
What’s the difference between a SaaS product and a digital agency service?
Agency services trade time for money — you can’t deliver more service without adding more hours or people. SaaS products have revenue that scales independently of your time once built — the same code serves one customer or ten thousand without proportional cost increases. The combination of agency revenue (immediate, predictable) with SaaS revenue (delayed, scalable) is a powerful business model if you can manage both effectively.
How do you get your first SaaS customers?
Your first customers almost always come from your existing network. Solve the problem for people you already know, gather real feedback, and use early results as case studies. Direct outreach to people who have the problem you solve is more reliable than content marketing or paid ads in the early days. Get 10 paying customers before you worry about scaling marketing.
When should a solo founder consider hiring help?
When the cost of not having help (in lost revenue, slower growth, or quality degradation) exceeds the cost of the hire. For a SaaS product, the first hire is often customer support — once users are regularly reaching out with questions, that work either consumes your development time or gets done poorly. The second common first hire is a specialist in a critical skill the founder lacks, whether that’s marketing, design, or additional engineering.
How do you balance feature requests with core product focus?
Track every request, but implement few. A spreadsheet of requested features grouped by theme will quickly show you which problems are common to many users vs. one user’s specific workflow. Build what solves the most common high-value problems, and be transparent with users about what’s on the roadmap vs. what isn’t. Users generally respect honesty about priorities more than they resent declined requests.
