Founder narrative
Anya Petrova10 min read9 views

The month I sent a DMCA takedown notice at $48K MRR: a founder diary (2026)

A composite founder diary (2026): at $48K MRR a competitor cloned eleven of the fourteen sentences on my landing page, comma splice included. A DMCA takedown notice got the page down in six days, and a counter notification put it back on the table on day nineteen. Why the CDN was the wrong recipient, why copying expression is actionable when copying features is not, and the arithmetic nobody publishes: ten to fourteen business days to file a lawsuit against a copyright registration that was averaging about four months.

Minimalist editorial illustration: a short solid terracotta bar above a pale grey bar about seven times its length, both squared off on warm off-white, with a fine charcoal hairline dropping from the terracotta bar's right end across the grey bar, and a small charcoal square at upper right.
Minimalist editorial illustration: a short solid terracotta bar above a pale grey bar about seven times its length, both squared off on warm off-white, with a fine charcoal hairline dropping from the terracotta bar's right end across the grey bar, and a small charcoal square at upper right.
In this story
Our client's material was removed in error. We are submitting the enclosed counter notification and expect the page restored.

Nineteen days after I filed a DMCA takedown notice that worked, a paralegal I had never heard of undid it in four paragraphs. I was at $48,000 MRR in 2026. I had spent six days getting a competitor's landing page taken down and I was about to learn that the removal was the easy half, and that the clock which mattered had started running the moment their letter arrived.

Quick answer (2026): This is a composite founder diary about sending a DMCA takedown notice as a small SaaS company, and about what happens when the other side pushes back. Three things surprised me. The thing that made this copyright at all was not that they copied my product, it was that they copied my sentences, and functionality is not protectable while specific expression sometimes is. I sent the notice to the wrong company first, because the name on the nameservers is almost never the host. And the counter notification put me on a statutory clock of ten to fourteen business days to file a lawsuit, while the registration I needed before I was allowed to file one was averaging about four months. That gap, not the notice itself, is the whole game. This is a founder's account and general reflection, not legal advice.

A prospect forwarded me a competitor's landing page with one line above it: "is this you?"

It was not me. It was my writing. Not the idea, not the feature list, not the pricing shape. The actual sentences. Eleven of the fourteen lines in their hero and features section were mine, in my order, with my rhythm. One of them still had a comma splice I had put there myself and never fixed.

I want to be precise about why that matters, because it is the fork in the road and almost nobody who tells you to "send a DMCA" explains it. Two years earlier a different competitor had cloned what my product did, and a lawyer told me, correctly, that there was nothing to be done: you cannot copyright an idea, a workflow, or a feature set. I wrote about that month at $30K MRR, and the conclusion then was to defend the moat rather than the features.

This was a different thing. They had copied the expression, and expression is the part copyright actually covers. A comma splice is not a feature. Nobody arrives at my exact comma splice independently.

That single distinction is what converted a bad feeling into a filing.

I sent it to the wrong company first

I did what anyone does. I looked up the domain, saw Cloudflare Cloudflare on the nameservers, found the abuse form, and filed.

Cloudflare's own published position on this is unambiguous, and reading it saved me from repeating the mistake: "Cloudflare does not host content through those services, and we cannot remove content from the Internet that we do not host." What they do instead is "forward your complaint to the website operator and the hosting provider to allow them to take action on it." (See Cloudflare's stated approach to abuse reports.)

So my notice did move. It moved sideways, to the copycat, who now knew I had noticed, four days before it reached anybody with the ability to take a page down.

A pass-through CDN in front of a site is not the host. It is a curtain. The name you can see is almost never the name you need.

What I should have done first, and what took nine minutes once I knew it existed, was search the Copyright Office's DMCA Designated Agent Directory. Service providers register an agent there specifically to receive these notifications. If the provider is in that directory, you have the correct recipient and you stop guessing.

What the notice actually has to contain

Every "how to send a DMCA" article I read gave me a template. None of them gave me the statute, which is shorter and clearer than any of the templates and is the thing the recipient's legal team is actually checking against.

Under 17 U.S.C. 512(c)(3), a notification has to be a written communication to the provider's designated agent including substantially the following six things:

  1. A physical or electronic signature of a person authorized to act for the owner of the infringed right.
  2. Identification of the copyrighted work claimed to have been infringed, or a representative list where there are several at one site.
  3. Identification of the infringing material, with "information reasonably sufficient to permit the service provider to locate the material."
  4. Information reasonably sufficient to let the provider contact you.
  5. A statement that you have "a good faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent, or the law."
  6. A statement that the information is accurate, and, under penalty of perjury, that you are authorized to act for the owner.

Two practical notes from getting this wrong once. The perjury statement in item six attaches to your authority to act, not to your legal conclusion that the material infringes. And item three is where amateur notices die: I sent a first draft that identified the offending site. The correct object is the specific URL and the specific passages, listed so that somebody with no context can find them in under a minute.

I rewrote it as a two column table. My sentence, their sentence, the URL of each. Eleven rows. That table did more work than the letter around it.

Six days later the page was gone

The host acknowledged in under a day and the page came down on day six. No argument, no negotiation. This is by design: the safe harbor that protects the host depends on acting expeditiously, so a well formed notice is far easier for them to honour than to litigate.

I want to be honest about how good this felt, because it is exactly the feeling that made the next part expensive. I closed the tab. I told my one contractor it was handled. I did not do the one thing that would have mattered, which I will get to.

Then the counter notification arrived

Day nineteen. Four paragraphs, a signature, a statement under penalty of perjury that the material was removed by mistake or misidentification, and consent to federal jurisdiction. That is the mirror image of my own notice, and it is set out in 512(g)(3) in almost the same shape.

Here is the part I did not know, and it is the reason this diary exists.

Once a valid counter notification lands, the statute tells the provider to inform me that it "will replace the removed material or cease disabling access to it in 10 business days." And then, under 512(g)(2)(C), the provider "replaces the removed material and ceases disabling access to it not less than 10, nor more than 14, business days following receipt of the counter notice."

There is exactly one thing that stops the page going back up. The provider must first receive "notice from the person who submitted the notification ... that such person has filed an action seeking a court order to restrain the subscriber from engaging in infringing activity."

Not a threat. Not a lawyer's letter. A filed lawsuit.

So the takedown I had won on day six was, from day nineteen, a fourteen business day loan.

The arithmetic nobody shows you: ten business days against four months

I called the lawyer. The first question was not about the copying. It was: "when did you register the copyright?"

I had not. I had assumed, the way I think most founders assume, that copyright exists automatically on creation and that this was enough. The first half is true. The second half is where the trap is.

17 U.S.C. 411(a) says that "no civil action for infringement of the copyright in any United States work shall be instituted until preregistration or registration of the copyright claim has been made in accordance with this title."

Read those two facts next to each other, because I had to read them three times:

  • I had ten to fourteen business days to file a lawsuit, or the page went back up.
  • I was not permitted to file a lawsuit until my registration had been made.

And registration is not fast. The Copyright Office publishes its own registration processing times, and for cases closed between 1 October 2025 and 31 March 2026, an online eService claim that required no correspondence averaged 3.6 months, ranging from 2 to 5.3 months. Across every claim type the average was 4.1 months, and the Office had to correspond with the applicant on 27% of all claims, which pushes those cases to a 5.0 month average.

Ten business days is about two calendar weeks. The path to being allowed to use them was averaging four months.

That is the entire structural asymmetry of the DMCA for a small company, and I could not find it stated plainly in a single one of the pages that rank for how to send one of these. They all end at "the content comes down."

What $800 bought

There is an escape hatch, and it is worth knowing before you need it rather than during a fourteen day window.

The Copyright Office offers special handling, where, in its own words, "once a request for special handling is received and approved, every attempt is made to process the claim or recordation within five working days." It is granted only on stated grounds, and one of them is "pending or prospective litigation." Per the Copyright Office's published fee schedule it carries a special handling fee of $800 on top of the ordinary registration fee, and the Office's own FAQ sets out the qualifying grounds.

So the honest answer to "what did the takedown cost" is not the notice, which was free. It was $800 to buy back the four months I had not spent earlier, plus a bit over $2,000 of lawyer time, of which the most valuable forty minutes were the ones that told me the counter notification was normal and not a catastrophe.

Roughly $3,200, to enforce a right I had held for free the entire time and had never made usable.

The clause that cuts both ways

One more thing, and this is the reason I stopped drafting my notices angry.

512(f) says that anyone "who knowingly materially misrepresents" either that material is infringing, or that it was removed by mistake, "shall be liable for any damages, including costs and attorneys' fees, incurred by the alleged infringer."

That is aimed at me as much as at them. If I had done what I wanted to do in hour one, which was fire off a notice covering their whole site because the product looked like mine, I would have been asserting infringement over functionality that is not protectable. The eleven sentences were defensible. "They built the same thing" would not have been, and the exposure runs the other way.

It also explains the counter notification, which I had taken personally. It is a cheap, structurally encouraged move: their statement is about mistake or misidentification, sworn to the same standard as mine, and it costs them a stamp to reset a clock they know most small claimants cannot beat.

What actually happened

The registration certificate issued inside the special handling window. My lawyer sent the copycat's counsel a short letter enclosing it, along with the eleven row table and a draft complaint.

They did not restore the page. They rewrote it. Badly, and in their own words, which was all I had ever actually wanted.

Here is the ledger, rounded and self-reported, for the three months around it. It picks up where the previous month's SLA claim left off.

Scroll to see more

MonthMRRWhat moved
Filing month$48,000Page removed on day 6; counter notification on day 19
Month 1~$47,600Two deals paused while the clone was still live and cheaper
Month 2~$48,900Rewritten page reads generically; one paused deal closes
Month 3~$50,400Registered the marketing copy, the docs and the changelog as a batch

The revenue effect of the copying itself was small and hard to separate from noise, which matches what happened at $30K MRR. The measurable cost was twenty two days of my attention during a quarter when I had planned to ship onboarding.

The one thing I would tell you

Register the words before anything happens to them.

Not the product, not the code, not the idea. The marketing copy, the documentation, the onboarding emails. The finished expression, as a batch, once a quarter, at the ordinary fee and the ordinary speed, when nobody is waiting.

The takedown notice is free and anyone can send one in an afternoon. The registration is the only thing that makes the notice survive being argued with, and it is the one part you cannot acquire at the moment you discover you need it. On day nineteen, holding a counter notification, you are not choosing between good options. You are choosing between $800 and losing.

I found that out with fourteen business days on the clock. It is a much cheaper afternoon when the answer to "when did you register" is "in March, with everything else."

A

Written by

Anya Petrova

Anya Petrova writes first-person founder diaries for OperatorBook, reconstructed as composites from interviews with bootstrapped SaaS founders. She focuses on the months that do not make the highlight reel: the pricing changes, the churn scares, and the quiet operational decisions that move MRR.

Frequently asked questions

Is this a real founder's diary?

It is a composite. The founder is a blend of several bootstrapped SaaS operators who sent DMCA takedown notices over copied marketing copy in 2026. The MRR figures (about $48K moving to roughly $50K), the eleven copied sentences, the six day removal, the counter notification on day nineteen and the roughly $3,200 total cost are self-reported and lightly rounded. No single named company, competitor, host or law firm is described. Every legal provision and every figure attributed to a source is real and was read in full: the statutory text is quoted from 17 U.S.C. 512 and 411, and the registration timings come from the Copyright Office's own published processing times. This is a founder's account and general reflection, not legal advice.

What does a DMCA takedown notice have to contain?

Under 17 U.S.C. 512(c)(3), a notification must be a written communication to the service provider's designated agent including substantially six things: a physical or electronic signature of someone authorized to act for the owner of the infringed right; identification of the copyrighted work; identification of the infringing material with information reasonably sufficient to permit the service provider to locate the material; contact information for you; a statement that you have a good faith belief that the use is not authorized by the copyright owner, its agent, or the law; and a statement that the information is accurate, and under penalty of perjury that you are authorized to act for the owner. In practice the third item is where amateur notices fail, because naming the site is not enough. List the specific URLs and the specific passages.

What happens if the other side files a DMCA counter notification?

The clock reverses and it moves fast. Under 17 U.S.C. 512(g)(2), once a valid counter notification arrives the provider promptly sends you a copy and informs you that it will replace the removed material or cease disabling access to it in 10 business days. It then restores the material not less than 10, nor more than 14, business days after receiving the counter notice. There is exactly one thing that stops restoration: the provider's designated agent must first receive notice that you have filed an action seeking a court order to restrain the infringing activity. A lawyer's letter does not count and a threat does not count. It has to be a filed lawsuit.

Do I need to register my copyright before sending a DMCA takedown notice?

No, and that is the trap. You can send a notice without registration, because copyright exists on creation. But 17 U.S.C. 411(a) says no civil action for infringement of the copyright in any United States work shall be instituted until preregistration or registration of the copyright claim has been made. Since a counter notification gives you only 10 to 14 business days to file suit, and since the Copyright Office reported an average of 3.6 months for online claims needing no correspondence and 4.1 months across all claims for cases closed between October 2025 and March 2026, an unregistered work usually cannot beat the restoration clock. Register the finished marketing copy, documentation and onboarding emails as a batch, in advance, at the ordinary fee and the ordinary speed.

Can I get in trouble for sending a DMCA takedown notice?

Yes. 17 U.S.C. 512(f) says any person who knowingly materially misrepresents that material or activity is infringing shall be liable for any damages, including costs and attorneys' fees, incurred by the alleged infringer. The same provision applies to a counter notification claiming removal by mistake. Practically, this is why the scope of the notice matters: copying of your specific expression, such as your literal marketing sentences, is defensible ground, whereas asserting infringement because a competitor built a product with the same functionality is not, since functionality and ideas are not protected by copyright.

Where do I send a DMCA takedown notice if the site sits behind a CDN?

Not to the CDN, in most cases. Cloudflare's published position is that it does not host content through its pass-through services and cannot remove content from the Internet that it does not host, and that it will instead forward your complaint to the website operator and the hosting provider. That means filing with the CDN can tip off the copycat days before the notice reaches anyone able to remove the page. The reliable route is the Copyright Office's DMCA Designated Agent Directory, where service providers register an agent specifically to receive these notifications, so you can identify the correct recipient rather than guessing from the nameservers.

Founder narrative

The month an SLA breach cost me $240 at $47K MRR: a founder diary (2026)

A composite founder diary (2026): at $47K MRR an enterprise customer's procurement team invoked section 8.2 and claimed a service credit for 47 minutes of downtime. Why their number and my number were different lengths and theirs was the one that counted, why the same 42 minute outage breaches in February and clears in July, why the $240 credit was a seventeenth of what the month cost, and the three clauses the large published SLAs carry that mine did not.

9 min read37
Founder narrative

The month a website accessibility lawsuit threat landed at $45K MRR: a founder diary (2026)

A composite founder diary (2026): at $45K MRR a twelve page ADA demand letter arrived by certified mail alleging eleven barriers and giving fourteen days to respond. Why a demand letter is not a website accessibility lawsuit and what that changes, why the published filing counts of 3,117 and 4,928 describe a category I was not in, the overlay widget I nearly bought at 11pm, the nine defects behind the eleven allegations, and what the whole month actually cost.

12 min read48