How I built a SaaS, hit my first $68 MRR in 3 days, and why I immediately slashed my prices - The Full Story

If you had told me a few months ago that I would launch a SaaS, get paying customers within 72 hours, and then immediately drop my pricing by almost 50%, I would have called you crazy.

But building in public has a funny way of teaching you hard lessons very quickly.

I’m the solo founder of Snyho (a Content Command Center for digital agencies and creators), and this is the raw, unfiltered story of how I went from burnout to building a SaaS, facing silent server crashes, securing my first $68 in Monthly Recurring Revenue (MRR), and why I decided to pivot my pricing on day 4.

If you are a solo dev or an indie hacker currently grinding in the dark, grab a coffee. I wrote this for you.

Chapter 1: The Problem (My Personal Hell)
Before writing a single line of code for Snyho, I was managing multiple WordPress sites and social media accounts. My daily workflow was an absolute operational nightmare:

Write a draft in Google Docs.

Copy it to WordPress.

Fix the formatting that inevitably broke.

Guess the On-Page SEO score.

Download images, compress them, and re-upload them to the WP Media Library.

Open ChatGPT to generate promotional tweets and LinkedIn posts.

Open a scheduling tool to distribute the social posts.

I was experiencing chronic "tab overload." I spent roughly 5 hours a week just on distribution. I realized that teams don't fail from a lack of ideas; they stall because of operational friction.

I looked for tools that combined WordPress content management, On-Page SEO analysis, AI generation, and Social Media scheduling into one dashboard. They were either disjointed, required 10 different plugins, or cost hundreds of dollars a month.

So, I decided to build it myself.

Chapter 2: The Vision & The Architecture
I wanted to build a "Command Center." A unified workspace where you write once, optimize, and publish everywhere.

The Tech Stack:

Framework: Next.js (App Router) & TypeScript.

Styling: Tailwind CSS (Strict minimalist monochrome UI – white backgrounds, slate text).

Database: PostgreSQL with Prisma ORM.

Authentication: NextAuth (Google OAuth + Credentials).

Emails: Resend API.

Payments: Paymento (and Stripe).

The core engine relies heavily on external APIs. I had to build a system that securely connected to WordPress via Application Passwords (bypassing the need for custom plugins) and integrated with the official APIs of X, Meta, and LinkedIn.

But building a SaaS is never just about the "happy path."

Chapter 3: The Nightmares & Obstacles
To get to V1.0, I had to wrestle with some incredibly frustrating bugs. Here are the top three that almost made me quit:

Obstacle 1: The WordPress Multisite Upload Cap
One of Snyho's killer features is that any image you drop into our editor gets automatically uploaded to your connected WordPress Media Library to save server space. During beta testing, image uploads kept failing randomly. After two days of debugging, I discovered that a WordPress multisite installation I was testing on had a hardcoded 64MB max upload limit hidden deep in the network configurations. I had to build custom error handling to gracefully inform users when their WP limits were rejecting the API payload.

Obstacle 2: The "Silent" Resend Failure
I set up Resend for my welcome and verification emails. Everything worked perfectly on localhost. I pushed to production, and users started signing up via Google OAuth.

Days went by, and I realized no one was getting welcome emails.
Because the NextAuth Google provider bypasses the manual registration route, the createUser event wasn't triggering my email utility properly. Worse, because the RESEND_API_KEY was missing a specific environment configuration on my VPS, the app was failing silently. I had to rewrite the entire authentication flow, wrapping every email trigger in strict try/catch blocks and hooking directly into the Prisma DB creation events to ensure no user was left behind.

Obstacle 3: The Financial Brain (Webhooks & Redundancy)
Building the Paywall (I call it PaywallGuard) was relatively easy. But tracking the money was hard.
I built a payment webhook (/api/webhooks/paymento/route.ts). Then, I decided to build a Hybrid Referral System where referrers get +10 free days AND 20% cash commission.

I almost created a catastrophic redundancy by making a second webhook for referrals, which would have caused the payment gateway to fail. I had to step back, architect a single, monolithic prisma.$transaction inside the existing webhook. Now, when a payment succeeds, the system simultaneously unlocks the paywall, finds the pending referral, adds funds to the referrer's wallet, and extends their trial by 10 days—all in under 800 milliseconds.

Chapter 4: The Go-To-Market & The First $68
With the legal pages (Privacy, Terms, DPA) written and the Stripe/Paymento gateways live, it was time to launch.

I didn't have a massive email list. I didn't have a huge marketing budget. I used guerrilla marketing. I went into niche Facebook groups and LinkedIn communities filled with agency owners and SEO experts.

I didn't spam links. Instead, I used the "Founder's Story" approach. I wrote exactly what I was feeling: "I was wasting 5 hours a week copy-pasting between WP and X, so I built a command center to do it in one click."

Within the first 72 hours, the traffic spiked. Users started creating accounts. I watched my Microsoft Clarity dashboard like a hawk, observing how users navigated the minimalist UI.

Then, the Stripe notification hit.
Payment Successful.

Someone had hit the PaywallGuard after their trial and decided the tool was valuable enough to pay for. They bought the "Pro" plan, which I had initially priced at $34/month. A few hours later, a second user upgraded.

$68 MRR. Day 1 of monetization.
Seeing strangers pay for code you wrote in your bedroom is a feeling I will never, ever forget.

Chapter 5: Why I Immediately Cut My Prices
You might be thinking: "If people are paying $34, why lower it?"

Watching the session recordings and talking to my initial users, I noticed a trend. The $34 price point was a no-brainer for established digital agencies, but it created too much friction for the solo creators, indie hackers, and freelance writers who desperately needed the tool.

I looked at my infrastructure costs. My margins were excellent because of the direct-to-WP image routing and efficient API usage.

I made a gut decision. I slashed the Pro plan down to $19/month.

Why? Because I want Snyho to be an indispensable utility, not a luxury expense. Lowering the barrier to entry combined with my 20% Lifetime Referral Commission meant that my early users could easily become evangelists. If a user invites just 5 people, their account is basically free.

The $19 price point is an investment in volume and community growth over immediate, short-term cash flow.

What’s Next?
We are just getting started. The roadmap includes native desktop apps for Q4, deeper AI integrations, and expanding the Social Command Center to include Pinterest and TikTok scheduling.

If you struggle with content distribution, or if you just want to support a fellow indie hacker, I’d be honored if you checked it out.

🔗 Snyho.com
(There’s a 14-day free trial, no credit card required).

If you’ve built a SaaS, what was your biggest obstacle in getting your first paying customer? Let’s talk in the comments!