The no‑code world
moves in fifty
directions.
"We point you toward the three that matter."
Glide's new data grid turns any Google Sheet into a full ops dashboard — without a single line of code
Read in Issue #147 ↗Why this newsletter
exists at all
Every editorial decision has a story behind it. Here are the five moments that shaped how Curate is made.
Drowning in 47 browser tabs
In 2022, I was running a two-person SaaS and spending nine hours a week just deciding which tools to evaluate. Product Hunt sent fourteen launches a day. Twitter threads promised every one was the future. The signal-to-noise ratio was zero.
The tool I found three months too late
A community member in a Bubble forum mentioned Outseta — an all-in-one membership tool — in passing. I'd already hand-stitched that exact stack with four separate services. Three months of integration debt, solved by one link I didn't see in time. That hurt.
Every link is tested before it's typed
Nothing goes into Curate without a 20-minute hands-on session. I spin up a free account, build the smallest meaningful workflow, and ask: does this change how I'd build? If the answer is yes — and only then — it gets a paragraph. No affiliate incentives. No press releases. Just the builder's perspective.
Three links. One automation. One tool. One read.
After 40+ issues of experimenting, readers told me clearly: they wanted depth over breadth. Now every Thursday edition carries exactly three items — one tool, one automation workflow, one long-read. Each gets 200 words of honest context. You can read it in eight minutes. You'll think about it for a week.
Built by 14,200 builders, not one curator
Forty percent of issues now start with a reader submission. Agency owners send me their Framer experiments. Ops managers share the Zapier chain that finally worked. Solo founders DM me the Bubble plugin that shaved two weeks off their MVP. I surface it, test it, and send it back to you — credited, contextualized, useful.
What's inside
each edition
Bubble's new native mobile export: what 3 months of testing actually revealed
The export is real. The performance gap is also real. Here's the honest middle ground for solo founders building mobile-first.
The Make scenario that replaced a $400/month VA for one ops team
Invoice parsing → Airtable → Slack digest. Forty-two hours saved in month one.
Retool vs. Internal.io: which one wins for ops dashboards under $200/month
Tested both on the same data set. The winner surprised me.
Framer client handoff in 2026: the workflow that cut revision rounds by half
One shared Framer link, one Loom walkthrough, zero "can you move that 2px" emails.
Fillout just killed my Typeform subscription
Logic branching that actually works, at a third of the price.
The real cost of your no-code stack: a forensic breakdown of what 12 founders actually pay
Subscriptions add up in ways that sneak past monthly reviews. The median surprise: $340 more than expected.
147 issues · 441 tools reviewed · 290 automations documented
Find issues for your stack →Find your
reading path
Five questions. Two minutes. A filtered view of the archive built for the stack you actually use.
Not just a newsletter.
Your newsletter.
Five questions reveal which 40+ back issues are most relevant to your stack. We'll also tag your subscription so future issues are weighted toward the tools you actually use.
Takes 2 minutes · No email required to see results
Every Thursday, you get:
Already know you're in?
Just subscribe, no quiz required.
14,200 subscribers · Unsubscribe anytime
14,200 builders
can't all be wrong
Real outcomes from real readers. No testimonials written by our team.
"I found Softr through Issue #122 and migrated our client portal off Webflow in three days. Saved $180/month and two days of dev time."
"The Make scenario in Issue #141 became the backbone of our onboarding workflow. We retired a $400/month contractor doing the same job manually."
"I've tried every no-code newsletter. Curate is the only one that tells me why something matters for MY stack instead of everyone's."
"The Framer vs Webflow comparison in #147 saved my agency from a bad platform decision. We went Framer. Client launch was 11 days, not the usual 20."
Ready to find your stack?
Join 14,200 builders · Next issue: Thursday, March 5