Do you actually need a full landing page builder?
Here's the question I kept coming back to while building this thing. When someone searches for an Unbounce landing page builder, what are they really after? Most of the time, near as I can tell, it's one page. A profile. A launch page. A "here's the thing I made and here's the button" page. Not a whole conversion suite with a hundred knobs.
So I made a deliberate bet. Instead of trying to do everything, do one thing, a single page, and make it dead simple to build. That's the whole idea. One page, built from a simple "stack" of elements you drag into place. Narrow on purpose.
And I'll be honest, that made me nervous at first. Narrowing scope feels like tying an arm behind your back. But it turned out to be the point.
Why keep the focus so narrow?
When I set out to design the builder, I wrote down the goals plainly, because I wanted something to hold myself to. It had to be minimal in style and interface. Self-explanatory for someone who'd never seen it before. Light enough to run mostly on its own, without leaning on the backend for every little thing. And mobile-friendly, not just the sites it makes, but the act of making them.
That mobile-friendly-builder part matters more than it sounds. A lot of tools give you sites that look fine on a phone but expect you to build them on a big desktop screen. I wanted you to be able to actually put a page together from your phone if that's all you've got.
The reason the focus stays narrow is the same reason it stays easy. A single page made of a simple stack of elements has a natural limit to its complexity. There's only so far it can sprawl. Compare that to a general landing page builder, where the surface area of what you could configure just keeps growing. Split tests, dynamic text, pop-ups, integrations, the works. All powerful. All also things you have to learn.
But they could stay simple, and I decided they should.
What can you actually do with something this simple?
The fear with "simple" is that it means "can't." So let me be specific about what's in there, because the narrow focus isn't the same as thin.
Custom domains. You can publish to any custom domain you own, with full SSL support handled through Let's Encrypt. So it's your address, and it's HTTPS, not some subdomain you're stuck renting forever.
No forced branding. Sites publish without the "Made with Carrd" tag on them. It's your page. It should look like your page.
Your own code, if you want it. This one surprised people. You can download the actual HTML, CSS, and JS for any site you build. If you outgrow the tool or just want to host it somewhere else, the code comes with you. (That one's a Pro Plus feature.)
All of that sits on top of the same simple stack. The depth is in the details, the customization that matters, not in the number of screens you have to click through.
Simply built, customizable, responsive
Those three words are basically the whole pitch, so let me hold each one up.
Simply built. You add elements to a stack. That's the mental model, start to finish. New users get it without a tutorial, which was the whole "self-explanatory" goal.
Customizable. Narrow focus doesn't mean take-it-or-leave-it. The room to fiddle is aimed at the parts that actually change how your page feels, rather than scattered across a thousand settings you'll never touch.
Responsive. The page works on a phone because that's where most people will see it. This isn't 2006. Mobile isn't the afterthought, it's the default.
All looked great on paper, but how would it play out in practice? I did a dry run building a real page, start to publish, and much to my surprise, the results were good. Really good. Fast enough that the "gorgeous site in under 5 minutes" line stopped feeling like a stretch and started feeling like a normal Tuesday.
Where the messy part actually was
I don't want to make this sound cleaner than it was. The building isn't where I got humbled, the plumbing is.
When I added the Pro Plus plans, I assumed the hard work was the pricing and the feature gating. Nope. The thing that bit me was the upgrade flow. Turns out you can support multiple plans in your data model and still have single-plan assumptions baked into the processes that use it, like upgrades. The structure allowed for more. The flow quietly didn't. So I ended up rewriting the upgrade flow to match reality.
Boring story, maybe. But it's the honest kind of thing that never makes the feature list, and it's most of what building software actually is.
How much does it cost?
One page can be free, and the paid tiers are cheap enough that pricing isn't the reason people hesitate. Here's the shape of it, in plain numbers.
Pro Plus, $49/year. 25 sites, the full feature set, custom domains, no branding, code download.
Pro Plus 50, $89/year. Same features, 50 sites.
Pro Plus 100, $159/year. 100 sites, plus room for bigger, higher-quality images and backgrounds.
Pro Plus 250, $349/year. 250 sites.
Pro Plus 500, $599/year. 500 sites, for the folks building at real volume.
The jump between tiers is basically "how many sites do you need," not "which features do you get to have." That was intentional. I didn't want the good stuff locked away at the top.
So — Unbounce landing page builder, or this?
Here's my genuinely un-salesy answer. If you need heavy conversion tooling, run a whole marketing operation off your pages, and want every dial, a dedicated landing page builder is built for exactly that. Use it.
But if what you actually need is one fast, clean, mobile-friendly page, a profile, a launch, a link-in-bio, a small landing page, then the narrow focus here is a feature, not a compromise. Fewer things to learn, a natural limit to how complicated it can get, and, short of me royally screwing up, a page you can ship today.
That's the honest version. Simple on purpose, and better for it. At least in theory, and, near as my dry runs can tell, in practice too.