web

Why Carrd Wins With One-Page Websites: How a Solo Founder Built a Durable Business on Radical Simplicity and Cheap Pricing

How AJ built Carrd into a durable one-page website builder on radical simplicity and $19/year pricing. A case study for solo founders and bootstrappers.

ScribePilot AIScribePilot AI
••Updated •11 min read
Why Carrd Wins With One-Page Websites: How a Solo Founder Built a Durable Business on Radical Simplicity and Cheap Pricing
Pexels - Coding on laptop

Why Carrd Wins With One-Page Websites: How a Solo Founder Built a Durable Business on Radical Simplicity and Cheap Pricing

Most SaaS founders chase feature parity, raise rounds, hire teams, and bolt on integrations until the product groans under its own weight. AJ, the solo founder behind Carrd, did the opposite. He built a one-page website builder, priced it at a fraction of the competition, and kept running it alone. The result is one of the most quietly durable products on the internet, a tool that has served millions of sites by doing almost nothing that its competitors do.

This is a case study of that bet on radical simplicity, and what solo founders and bootstrappers can actually take from it.

Spotlight

AJ isn't easy to find. He doesn't do podcast circuits. He doesn't post fundraising announcements. He's the creator of HTML5 UP, a collection of free responsive HTML templates that became widely used across the web, and he's the sole operator behind Carrd. His public footprint is largely limited to his @ajlkn account on X (formerly Twitter) and a sparse personal site.

What makes Carrd notable isn't a dramatic origin story. It's the quiet accumulation of scale. Carrd's own homepage has historically displayed a running counter of sites created on the platform. As of early 2025, that counter showed figures well into the millions. AJ has periodically shared milestone updates on his X account, confirming steady, compounding growth over the years since Carrd's launch around 2016.

The product itself is almost aggressively simple: a drag-and-drop builder for single-page, fully responsive websites. No blog engine. No e-commerce suite. No CMS. You pick a template, customize it, and publish. The free tier lets you build basic sites on a carrd.co subdomain. The Pro tier, priced at $19/year for the standard plan, unlocks custom domains, forms, widgets, and additional site slots.

Nineteen dollars a year. Not per month. Per year.

That price point, combined with the product's ruthless constraints, is the core of the story. In a market where Squarespace, Wix, and Webflow compete on feature breadth and charge monthly fees that can run into the hundreds annually, Carrd occupies a different category entirely. It's not trying to be a full website platform. It's trying to be the fastest, cheapest way to get a single page live on the internet.

And for a huge number of use cases, that's all anyone needs: a landing page for a product launch, a personal portfolio, a link-in-bio page, a simple signup form, a coming-soon page. Carrd handles all of these without asking users to learn a complex builder or commit to a significant monthly subscription.

The Strategy

The decisions AJ made with Carrd look obvious in hindsight. They weren't. Each one required saying no to things that most founders consider essential.

Constraint as positioning. Carrd doesn't compete with Squarespace. It doesn't try to. By limiting the product to one-page websites, AJ eliminated an enormous surface area of features, support burden, and technical complexity. This isn't a limitation born from lack of ambition. It's a deliberate positioning choice: own the "simple page" use case so completely that nobody else bothers to compete on those terms.

The business-school framework that fits here is Clayton Christensen's theory of disruptive innovation, specifically the "new-market disruption" variant. Carrd didn't take existing Squarespace customers and offer them less. It served people who previously had no solution at all because existing website builders were too complex, too expensive, or too much commitment for what they needed: a single page, live in minutes. That's the specific mechanism of disruption. It expanded the market rather than stealing share.

Price as moat. At $19/year, Carrd's Pro plan is priced low enough that it barely registers as a line item for most users. This does two things. First, it makes the upgrade decision nearly frictionless. The gap between "free" and "$19/year" is so small that many users cross it without deliberation. Second, it makes the market unattractive to well-funded competitors. No venture-backed company wants to build a product that charges $19/year per user and requires meaningful infrastructure to run. The unit economics don't support VC-scale returns. For a solo founder with minimal overhead, though, those economics can be excellent.

Solo operation as architecture. AJ hasn't hired a team. He hasn't raised funding. This means every dollar of revenue above infrastructure costs is margin. It also means every feature request, every support ticket, and every architectural decision runs through a single person. That constraint forces brutal prioritization: if a feature would create ongoing support burden, it doesn't get built. The product stays small because the team stays small, and vice versa. It's a self-reinforcing loop.

Distribution through templates. Carrd's template gallery serves as both onboarding and marketing. Users browse templates, find one that fits their use case, and start customizing. The templates are polished enough that many users don't need to change much. This reduces time-to-value to minutes, which is critical for a product targeting people who want something live now, not next week.

The Playbook

Here's what solo founders and small teams can actually extract from Carrd's approach and apply to their own builds.

1. Pick a use case, not a market. Don't build "a website builder." Build "the fastest way to publish a landing page." The narrower your use case, the easier it is to build something that's genuinely best-in-class for that specific job. Carrd doesn't need to be better than Webflow at everything. It just needs to be better at one-page sites.

2. Price for volume and retention, not per-seat extraction. If your product serves a broad, price-sensitive audience, consider pricing that removes friction entirely. A $19/year plan doesn't trigger procurement reviews, doesn't require approval from a manager, and doesn't get cut in a budget squeeze. The tradeoff is that you need high volume to make the numbers work, but if your product is simple enough to support at scale with minimal overhead, low pricing can be a genuine competitive advantage.

3. Let constraints drive quality. When you can't build everything, you're forced to make the things you do build excellent. Carrd's editor is fast, intuitive, and produces clean, responsive output. That quality is partly a consequence of the constraint: with fewer features to maintain, AJ can invest more attention in each one.

4. Use templates as your sales team. If your product involves any kind of creative output, a strong template gallery does triple duty: it shows users what's possible, it reduces time-to-value, and it serves as evergreen marketing content. People share good templates.

5. Build for the job that incumbents ignore. Every mature market has underserved segments. Usually they're underserved because the economics don't appeal to large companies. That's your opening. The landing page that someone needs for a weekend project, the personal site that a freelancer wants live in 20 minutes, the link-in-bio page for a creator: these are real jobs that full-featured website builders overserve.

6. Resist the feature creep feedback loop. Every user request is a potential trap. Adding features increases support burden, which increases the pressure to hire, which increases the need for revenue, which increases the pressure to add features. Carrd's longevity is partly a function of AJ's willingness to say no repeatedly. If you're a solo founder, your most valuable resource is your own attention. Guard it.

Under the Hood

Stack and architecture. Carrd's specific technical stack isn't extensively documented publicly. The product serves static or near-static single-page sites, which means the hosting and delivery infrastructure can lean heavily on CDNs and static file serving. This is inherently cheaper and more scalable per site than platforms that need to run server-side logic for every page load. The builder itself runs client-side in the browser. This architecture is a natural fit for the product's constraints: one-page sites don't need databases, server-side rendering, or complex application logic.

Unit economics. We don't have access to Carrd's internal financials. But we can reason about the model qualitatively. Static site hosting is among the cheapest workloads to run at scale. With no employees, no office, and no marketing spend beyond the product itself, the cost structure is minimal. Even at $19/year per Pro user, the margin on each account is likely substantial if infrastructure costs per site are measured in fractions of a cent per month. The math works because the product is simple and the team is one person.

What's genuinely hard to copy. Anyone can build a one-page website builder. The technical barrier isn't high. What's hard to replicate is the combination of: years of template refinement, an established user base and brand recognition in the "simple site" niche, and the willingness to operate at a price point that most teams can't sustain. A VC-backed competitor would need to justify the economics to investors. A bootstrapped competitor would need to match Carrd's polish and breadth of templates while somehow acquiring users in a space Carrd already dominates. It's not impossible, but it's a grind with thin margins.

Honest counterpoints. We'd be doing a disservice if we didn't name the risks and caveats.

Concentration risk. Carrd is one person. If AJ steps away, gets sick, or loses interest, there's no succession plan that's publicly known. For users who depend on Carrd for business-critical landing pages, that's a genuine consideration. However, the majority of Carrd's use cases are short-lived projects, personal sites, and supplementary pages. For those users, the risk is minimal compared to the tool's speed and price.

Survivorship bias. For every Carrd, there are countless solo-founder products that launched with similar simplicity and went nowhere. Carrd's success required the right product, the right market timing, the right distribution, and AJ's specific design skill built over years with HTML5 UP. "Just build something simple and price it low" is not a strategy. It's a tactic that works inside a much larger set of conditions.

Ceiling on growth. A solo founder operating a low-price product has a natural ceiling. There's no sales team to push upmarket, no partnership team to build integrations, and limited ability to expand into adjacent use cases without breaking the simplicity that defines the product. Carrd may be exactly the size AJ wants it to be, and that's fine. But if you're building with the goal of significant scale, a different model might serve you better.

Platform dependency. Carrd relies on users finding it through search, word of mouth, and social media. Any significant change in how people discover tools (say, a shift in search algorithms or social platform dynamics) could affect growth. This isn't unique to Carrd, but it's worth noting for any product that doesn't invest in outbound sales or paid acquisition.

What This Means for Your Build

Carrd is a case study in how constraint, focus, and low overhead can create a durable product business. Not every founder wants to stay solo forever, and not every product can sustain a $19/year price point. But the underlying principles are broadly applicable: pick a narrow use case, build for it exceptionally well, price in a way that removes friction, and resist the urge to bloat your product into something it doesn't need to be.

If you're a solo founder or small team working on an MVP, the lesson isn't "copy Carrd." It's this: figure out the simplest version of your product that solves a real, specific problem, and ship that. You can always add complexity later. You can rarely remove it.

At Foxxception, we build MVPs and rapid prototypes for exactly this kind of focused product thinking. Whether you're validating a landing page concept or building the first version of a SaaS tool, we help founders get to market fast without overbuilding. If you've got an idea that needs to be live this month, not this quarter, let's talk.

And if your MVP needs a landing page while you build the real thing? Honestly, just use Carrd. It'll take you twenty minutes and cost you less than lunch. Then come to us when you're ready to build what's behind the landing page.

Sources

Note: Carrd does not publish detailed financial disclosures or user metrics beyond the site counter visible on its homepage. Claims about growth and scale in this article are based on publicly observable data (the site counter, AJ's public posts) and qualitative reasoning about the business model. We have not invented or estimated specific revenue figures, user counts, or growth rates where public data is unavailable.

Carrdone-page website builderlanding pagesolo founderlow-price SaaSproduct simplicity
Share:

Powered by

ScribePilot.ai

This article was researched and written by ScribePilot — an AI content engine that generates high-quality, SEO-optimized blog posts on autopilot. From topic to published article, ScribePilot handles the research, writing, and optimization so you can focus on growing your site.

Try ScribePilot

Ready to Build Your MVP?

Let's turn your idea into a product that wins. Fast development, modern tech, real results.

Related Articles