head-to-head· buildability comparison
buttondown.emailvssurething.io
which is easier to build?
→ build buttondown.email first.a full tier easier, cheaper at the floor, matched moat depth.
clone time
6 weeks
month6 weeks
buttondown.email
newsletter sending & subscriber management
55/ 100
buildability scorefull report ↗
→vs←
clone time
∞
don't∞
surething.io
multi-agent AI automation platform
18/ 100
buildability scorefull report ↗
moat
how deep is each moat.
tie · ±0.0
buttondown.email · aggregate
5.8/10real moat
moat delta±0
surething.io · aggregate
5.8/10real moat
6.0
capital+1.0 →
7.0
4.7
technical+4.0 →
8.7
0.0
network±0
0.0
10.0
switching±0
10.0
8.0
data-8.0 →
0.0
0.0
regulatory±0
0.0
overlap
where they fight, where they don't.
features only one ships, plus the small middle they share.
only buttondown.email · 66
behavioral datamarketing emailrate limitingrich text editoruser-data flywheeluser data storage
shared · 55
automationsbackground jobsintegrationssocial loginwebhooks
only surething.io · 33
ai agent platformvisual workflow automation platformllm inference
stack
what they're built on.
shared infra and the differentiating bits.
only buttondown.email · 77
PostgresPostmarkRedisResendTiptapTrigger.devUpstash
shared infra · 44
CloudflareNext.jsSupabaseVercel
only surething.io · 77
AnthropicLangGraphNangoOpenAICloudflare R2ShopifyTemporal
floor
cost + time, side by side.
monthly floorbuttondown.email wins
buttondown.email
$62
surething.io
$72 + usage
delta −$10buttondown.email costs less per month to keep the lights on.
time to clonebuttondown.email wins
buttondown.email
6 weeks
surething.io
∞
delta · finite vs. ∞buttondown.email is buildable; surething.io effectively isn't.
the verdict
same comparison surface, two different fights. give the buttondown.email clone a month. circle back to surething only if you genuinely need what it does that the other doesn't.
full reportmonth · 55
→ read the buttondown.email report
full reportdon't · 18
→ read the surething.io report
← saaspocalypse · directoryhead-to-head