What stops a copy of Substack working?

Deliverability. Getting the mail sent is trivial; getting it into an inbox rather than a promotions tab or a spam folder is a specialist discipline involving domain reputation, warm-up schedules, SPF, DKIM, DMARC, feedback loops and list hygiene. One bad send from a shared IP pool and your writers' open rates fall off a cliff, which they will notice and blame you for. Unsubscribe handling and consent compliance are legally load-bearing, not features. Sending to 100,000 addresses is a queue and a rate limit, not a for loop.

Can AI copy

Substack

Q: Can AI copy Substack?

Skin deep. You will clone the interface and then meet the wall. Realistically a long weekend.

A newsletter, a subscribe button, and a payments split.

Skin deep

Verdict: Skin deep
Time to copy: a long weekend
Category: ¶ Publishing
Source: Proprietary

The prompt

Written to be pasted straight into an agent with no editing. It describes the whole job, including the parts that will go wrong.

Build a newsletter platform. Rich-text composer with scheduled publishing, a public archive with per-post pages and RSS, subscriber lists with free and paid tiers, and double opt-in signup. Sending goes through a transactional email provider with a dedicated domain: configure SPF, DKIM and DMARC, implement one-click unsubscribe headers, process bounce and complaint webhooks, and suppress hard bounces permanently. Send through a queue with per-minute rate limiting and resumable batches. Track opens and clicks with a privacy-respecting default of off.

Open inClaude ↗Terminal agents take it from the clipboard.

What copies cleanly

The writing surface, the archive, the post page. This is a blog with an email field.
Subscriber management, paid tiers, and a checkout, if you sit on a real payment processor.
Sending the email itself, which is one API call to a transactional provider.

Where it stops

Deliverability. Getting the mail sent is trivial; getting it into an inbox rather than a promotions tab or a spam folder is a specialist discipline involving domain reputation, warm-up schedules, SPF, DKIM, DMARC, feedback loops and list hygiene.
One bad send from a shared IP pool and your writers' open rates fall off a cliff, which they will notice and blame you for.
Unsubscribe handling and consent compliance are legally load-bearing, not features.
Sending to 100,000 addresses is a queue and a rate limit, not a for loop.

What actually protects them

Recommendations between publications, which is a genuine network effect and their strongest asset.
Readers already have accounts and payment details on file.
The writers who would leave are exactly the ones whose audience arrived through the network.

Editor's note

The gap between it works on my machine and it arrived in their inbox is the entire business.

Somebody already did it

Go and look at the original

We would rather you formed your own opinion than took ours. They built the thing; we only measured it.

substack.com ↗