3
5 Comments

$2k MRR after 228 days - This is what building a SaaS REALLY looks like

Today we hit $2K MRR for our startup, Ferndesk πŸŽ‰

β†’ It took 2 months to build it to the point were we were comfortable launching
β†’ It took 3 months get to $1K MRR
β†’ It took 2.5 months get to $2K MRR

Lots of people genuinely think that all it takes to build and grow a SaaS is an audience, and a good product.

Well I have an audience (~40K followers across X & Linkedin), and I have a great product, but building it has been an absolutely grind.

We still spend 8-12 hours a day building, marketing, talking to customers etc, and it's only after putting in so much effort that we're getting any semblance of consistent growth.

And we're still not fully profitable yet πŸ˜…

Building a SaaS means putting in the reps and showing up daily. Talking to customers to refine your positioning and messaging, shipping constantly until you're a viable alternative etc.

The people going from $0 to $10K in days are the exception, not the rule.

Here's the #1 thing helping us grow: making sure last week's work snowballs into this week. We're trying SUPER hard to conserve momentum.

Every single week, we:

build a core feature our ICP needs

record videos, create content around it, use it in customer conversations

launch on our newsletter, socials, forums, communities

Then repeat.

We're putting in the reps daily to grow the business, no matter how small they may be. That work is starting to compound... big time.

The product is becoming magical and people are upgrading long before their trials expire.

And Ferndesk is quickly becoming the best documentation platform for busy founders who don't have time for docs.

We're just getting started πŸ’ͺ

on January 28, 2026
  1. 1

    228 days to $2k MRR even with a large audience β€” at that stage failed renewals often hide inside β€œchurn.”

    If you export last 30d failed invoices (email, amount, date, decline code), I’ll map recoverable $ by code in 48h free. No OAuth, no emails to your customers. Would you pay $29/mo for that to run automatically?

  2. 1

    The "conserve momentum" line is the most useful sentence I've read on
    this site all week β€” and the numbers around it are the proof. You had
    40K followers and it still took 228 days of daily reps. Most people
    will read that as discouraging. I read it as clarifying: the audience
    was never the engine. The compounding was.

    I'm a non-coder running an AI agent workforce, days from my own launch,
    and momentum-conservation is the one thing I built into the structure
    itself rather than trusting my discipline to provide: every working
    session ends by writing down what's now true, what's proven, and what's
    still open β€” and the next session starts by reading it. Nothing
    important is allowed to live only in anyone's head, mine or the
    machines'. It's your weekly snowball, run at the hour scale, because I
    learned fast that the gaps between sessions are where builds quietly
    die.

    If you could keep only one rep from your weekly loop β€” the core
    feature, the content around it, or the launches β€” which one is actually
    moving the needle? My money's on the customer conversations hiding
    inside all three, but you have 228 days of data and I have a hypothesis.

  3. 1

    Hard work, but if you enjoy it and believing in it then it will pay off. Good luck!

  4. 1

    The "snowball into next week" framing is useful β€” it reframes consistency as compounding rather than just repetition.

    A few questions:

    1. 40K followers but 8-12 hours/day grind β€” how much of that time is spent on distribution vs actual product work? Curious if the audience has changed the ratio or if it's still mostly building + customer conversations.

    2. "Upgrading before trial expires" β€” that's a strong signal. What do you think is driving it? Is it a specific feature, or the onboarding experience, or something else?

    3. Documentation for busy founders β€” how do you handle the "I'll do docs later" objection? That's a common reason people put off tools like this.

    Congrats on the milestone. The realistic timeline is refreshing.

  5. 1

    The "conserving momentum" point resonates hard. I'm about 7 months into building and the weeks where I maintain that cadence - ship something, talk about it, push it out - those compound noticeably faster than the weeks where I get pulled into internal cleanup or refactoring.

    The $0 to $10k overnight stories get all the attention but 228 days of daily reps is the actual pattern. Congrats on the milestone.