The month a competitor copied my SaaS (at $30K MRR)

The email came in on a Tuesday. A customer I liked forwarded me a competitor's launch announcement with one line on top: "Isn't this you?" It was. The landing page was my page with the serial numbers filed off. The feature names were mine, lightly reworded. Even the odd little onboarding joke I wrote at midnight a year earlier was there, paraphrased. My SaaS was doing $30,000 in MRR the month a competitor copied it, and for about three weeks after that email I did almost everything wrong.

This is what that quarter actually looked like, with the real numbers, because most of the advice you find when you search for this is not written by anyone living the profit-and-loss statement.

Quick answer (2026): When a competitor copies your SaaS, the copy itself is rarely what hurts you. In this composite of several founders' stories, with rounded, self-reported figures, a clone priced about 35 percent cheaper took six price-sensitive accounts and paused two deals, roughly $780 in monthly recurring revenue. The real damage was the three weeks spent reacting instead of building. What recovered the number was not fighting on features, which a competitor copies in a week, but leaning on the moat they could not copy: customer relationships, proprietary data, and moving upmarket. MRR was back near $31,900 within 90 days.

The morning a customer forwarded me my own product

I want to be honest about the first feeling, because nobody writes it down. It was not fear. It was a hot, embarrassing kind of rage, the feeling of being robbed by someone who then waved at you. I refreshed their site fourteen times before my coffee was cold. I read their pricing page like it was a ransom note. They had priced about 35 percent under me.

By lunch I had drafted three tweets calling them out, written half a cease-and-desist in my head, and answered exactly zero support tickets. My product had 185 paying accounts and an average revenue per account of about $162, and I spent the most important morning of the quarter staring at a stranger's changelog.

The first 72 hours cost me more than the copy did

Here is the thing I could not see at the time. The clone had been live for six days. In those six days it had not taken a single one of my customers yet. What it had taken was my attention, and my attention was the one input the business could not run without.

I was the person who shipped features, wrote the docs, and answered the founder-to-founder emails that closed deals. For three days I was instead a person refreshing a competitor's Twitter. The copy did not stall my roadmap. I stalled my roadmap, and I did it for free.

What the lawyer actually said

I did what the top search results tell you to do. I asked a lawyer about sending a cease-and-desist. In 2026, for a small SaaS, the answer is usually deflating, and this is general reflection rather than legal advice: you cannot copyright an idea, a workflow, or a feature set. Functionality is fair game. What can sometimes be protected is specific expression, your literal marketing copy, a distinctive logo, a registered trademark, or a patented method if you actually filed one, which I had not.

So the entire legal aisle of the internet, the cease-and-desist templates and the "you can sue them" posts, mostly did not apply to me. They copied the what, and the what is legal. That was a hard hour, but a useful one. It forced me to stop looking for a rule that would make them disappear and start looking at my own business.

Did being copied actually hurt the revenue?

This is the part the listicles never show you, so here is my real ledger for the 90 days after the clone launched. The figures are rounded and self-reported, and the founder here is a composite, but the shape is exactly what happened.

The direct damage was about $780 in lost monthly recurring revenue and two paused deals worth roughly $900 a month combined. My churn ticked from around 2.6 percent to about 4.1 percent for a single month, then settled back down. The accounts I lost were, almost to a name, the ones who had only ever emailed me about price. The clone was welcome to them.

So did being copied hurt? A little, and less than I feared. The number that scared me on that Tuesday was never the number that was actually at risk.

The three weeks I want back

Two things I did in that window returned nothing.

The first was calling them out in public. I posted a thread with a side-by-side of their copy and mine. It got sympathy, a few hundred likes, and a wave of "wow, shameless" replies. It closed zero deals and saved zero accounts. It did teach their sales team exactly which of my points to prepare for. Free market research, from me, to them.

The second was surveillance. I built a little routine to check their changelog every morning. Every time they shipped something, I felt the urge to ship the same thing faster, which meant my roadmap was now being written by the company I claimed to be ahead of. I had handed them the pen.

What actually worked: I defended the moat, not the features

The turn came when I stopped asking "how do I stop them copying me" and started asking "what can they not copy." Features were the wrong battlefield. Anything I could ship in a sprint, they could ship in two.

The clearest example in tech is one Jason Cohen uses in his 2022 essay on moats: Snapchat invented Stories, and within months Instagram and Facebook shipped an identical version and swallowed the advantage whole. A feature is not a moat. As Cohen argues, an advantage is only worth something if it is defensible: switching costs, proprietary data, brand, economies of scale, a real relationship. Peter Thiel put it more bluntly back in 2014 when he wrote that competition is for losers, not because competing is shameful but because a market where everyone sells the same thing at the same price is a market where nobody makes money.

So I made a list of what the clone could not lift. Two years of my customers' data lived in my product, and their workflows were built on it. My onboarding emails were answered by the person who built the thing, not a ticket queue. And I knew this narrow niche better than a team chasing ten niches at once ever would.

Then I acted on it. I built two depth features that only made sense if you already held that data, so a fresh clone could not fake them. I wrote personally to every account the clone might tempt, not with a discount but with a roadmap. And I raised prices, moving my thirty heaviest accounts to a new Pro tier at about $50 more a month, the same unglamorous lever I wrote about in my $18K MRR pricing diary. Charging more for depth is the opposite of racing a cheaper clone to the bottom, and it worked. That tier alone added roughly $1,500 in monthly recurring revenue, more than the clone ever took.

The popular advice, "being copied is a compliment," is cold comfort at 2am when a deal is paused. A better framing is this: being copied is information. It tells you which part of your product is obvious enough to clone, which means that part was never your moat to begin with.

The 20-minute moat audit

If a competitor just copied you, here is the one exercise worth doing before you draft a single angry tweet. Set a timer for 20 minutes.

Write down every feature and every reason a customer pays you. Then cross out everything a well-funded competitor could ship within 30 days. Copy your slick UI. Cross it out. Match your feature list. Cross it out. Undercut your price. Cross it out.

Whatever is still standing when you finish is your actual business. For me it was the data, the relationships, and the niche, and none of it was on the landing page the clone copied. Crossing features off that list is clarifying in the same uncomfortable way that deciding whether to kill a product at all is clarifying. It tells you where the real thing lives.

The clone is still around, a year later. Its reviews complain about slow support. Mine grew from $30,000 to a little over $32,000 in the months after, not because I out-shipped a copy but because I finally spent my attention on the thing a copy can never take. The most expensive part of being copied was the three weeks I forgot that.

Founder identity and figures in this diary are a composite drawn from several real founders, anonymized and rounded, shared to protect the people involved.