← Back

Capsuleweb.site

An AI website generation product I took from concept to launch, built around a zero-friction flow that turns a single prompt into a live, shareable site in seconds. No sign up, no code, no waiting.

Role

Founder, Product Design, and AI UX (0→1)

Timeline

2025 — Present

Team

Solo design + AI-assisted development

Built with
Claude Codev0AntigravityVercelSupabaseGPT-4oGeminiStripe

At a Glance

  • -Live production app with Stripe payments, real generated sites, and a public gallery
  • -Three-part generation system: intent capture, structured content generation, and deterministic rendering
  • -No-signup model with Site ID recovery for post-publish edits
  • -Public gallery turns every generated site into a discovery path back to CapsuleWeb

The Problem

Website builders are powerful, but for many people they ask for too much work. Most users who need a quick site do not want to design a system. They want a page that is clear, usable, and live.

Too many decisions

Styling choices appear before users see any output. Most people do not want to design a system—they want a page that is clear and live.

Too much setup

Existing builders ask users to configure before they can preview. The effort required upfront does not match the simplicity of what most people actually need.

Editing instead of publishing

Time spent tweaking layouts and fonts is the wrong optimization for lightweight use cases. Most users would trade control for speed.

For freelancers, local businesses, events, and side projects, a website is usually a utility. The goal was to make creation a single action: describe → pay → publish.

Product Thesis

CapsuleWeb is intentionally a vending machine, not a full editor. That framing shaped every product decision.

Fixed price ($1): Keeps the decision simple. No plan comparison, no upgrade prompt.

No signup: Removes account friction from the start. The product earns trust through output, not onboarding.

Fast output over customization: Time-to-live is the metric that matters. Flexibility is the thing CapsuleWeb trades away—intentionally.

How the System Works

The core design decision was to separate AI content generation from layout rendering. This keeps the AI focused on content and structure—not on writing front-end code.

01

01 — Intent Capture

A lightweight input flow captures site type, purpose, tone, and basic content direction. The form is short on purpose—it gathers enough signal without becoming a brief-writing exercise.

02

02 — AI Content Generation

GPT-4o and Gemini generate a structured content plan: headlines, body copy, CTA labels, section order, and content blocks. The model does not write HTML. It writes content and structure. This keeps the AI focused and the output consistent.

03

03 — Deterministic Renderer

The app maps the JSON spec into a prebuilt responsive component system. This gives consistent visual quality, reliable mobile layouts, and predictable output across use cases. It is faster and more stable than letting a model generate front-end code from scratch.

Empty state — the starting line

Filled — describe, choose a vibe, dispense

Dispensed

Hit the button and two things happen immediately: a real site goes live at your custom URL, and a confirmation email lands with your link and site ID for edits later.

Site live at your custom URL

Site ID delivered by email for future edits

Built-in Growth Loop

Every generated site is added to a public gallery on the CapsuleWeb homepage. That does three things:

-

Shows real examples instead of generic templates

-

Builds trust for new users before they pay

-

Turns every shared site into a distribution path back to CapsuleWeb

Every generated site lands in the public gallery

Continuity Without Accounts

Removing signup helped conversion, but it created a follow-up problem: users still need to come back and edit. I solved this with a no-account recovery flow.

01

After publish, the system generates a unique Site ID

02

The user receives the Site ID by email immediately

03

They return later, enter the ID, and describe the change in plain language

04

The site regenerates and updates while keeping the same URL

Key Decisions and Tradeoffs

01

An opinionated product by design

Capsule was intentionally designed not to compete with Webflow, Framer, or full editors. The core decision was to optimize for instant creation and low friction — not deep customization. Everything follows that positioning: $1, no code, no waiting. The tradeoff is control, but it creates a much stronger first-time experience and a clearer product promise.

02

No-signup before value

I kept account creation out of the critical path so users can go from idea to live site without onboarding friction. That choice helps Capsule feel fast and lightweight from the first click. The tradeoff is less persistence and account-based tooling upfront, but it significantly improves momentum and first-time conversion.

03

Template-led prompting to reduce blank-page friction

Most users don't arrive with a perfect prompt — they arrive with a goal. I introduced category templates and example prompts (resume, event, product, local business, etc.) to help users quickly understand what Capsule is good at and get to a solid result faster. This turns the prompt box from a blank canvas into a guided starting point.

04

Sharing as part of the product experience

I treated sharing as part of the core UX, not a post-launch marketing layer. When a site goes live, Capsule creates a share-ready launch moment (receipt-style asset, live link, build speed, branding) so users can immediately post something that feels worth sharing. The result is a built-in viral loop that reinforces Capsule's value proposition every time it gets shared.

My Contribution

This was a systems and product design problem, not just a UI project.

  • -Defined the core product direction and UX strategy for CapsuleWeb as a $1 website vending machine with a clear, constrained user experience
  • -Led the 0→1 product design across the full flow, from prompting and generation through payment, publish, and return editing
  • -Designed the system approach that makes AI output reliable in production by combining AI-generated content with a controlled site rendering layer
  • -Tested and compared models (including GPT-4o and Gemini 3) for generation quality, consistency, and speed, then refined the experience around real output behavior
  • -Built key growth and retention mechanics into the product, including the public gallery loop and no-account recovery/edit flow
  • -Shipped the live product and iterated based on real usage, generated sites, and edge cases

Mobile

Mobile creation

Generate a real site from your phone in one vertical flow.

Mobile edits

Paste your Site ID, describe the change, get an updated site at the same URL.

Desktop Full Marketing Site

The entire product on one page — no nav, no multi-step wizard, no account wall.

Impact

  • -Live product at capsuleweb.site with a growing user base
  • -Average time from landing on the page to a published website: under 30 seconds
  • -Clear $1 pricing with no subscriptions or hidden fees
  • -Built-in viral loop through gallery and social sharing driving organic growth

What I Would Do Next

  • -Expand site types based on gallery data showing what people actually create
  • -Explore custom domain support so users can point their own URL to a CapsuleWebsite
  • -Test higher-tier options for multi-page sites while keeping the single-page experience as the default
Give it a try →