Consistency
Internal deck / squarespace-killer

Squarespace killer, built around consistency.

Storybook becomes the visual contract. Tokens, surfaces, type, and motion live in one place, so the marketing site, builder chrome, and published output stop drifting apart.

Open product See the system
  • Sub-second Preview loops and direct manipulation over menu gymnastics.
  • One token layer Shared foundations across marketing, builder chrome, and published sites.
  • Mobile-first Edit, review, and publish without desktop-only compromises.
The problem

The category still feels broken.

Most site builders feel slow, abstract, and inconsistent. The cost is not just ugly UI. It is lost momentum, fragile mobile output, and product decisions that never become reusable rules.

01 Speed

Slow by default

Heavy builders waste the feedback loop before design even starts.

02 Mobile

Desktop decisions break phones

The preview lies, then the live site drifts on smaller screens.

03 Lock-in

Outputs stay trapped

Export paths and domain ownership are still treated like a hostage negotiation.

04 Design

No visible design contract

Teams talk about consistency, but the rules do not live anywhere concrete.

Design system

Consistency means one system, not one more theme.

Storybook should hold the full visual logic of the app: foundations, component surfaces, token roles, and the marketing ideas that explain the product. That turns taste into a reviewable artifact.

Storybook

A visible source of truth

Foundations, marketing concepts, and chrome previews all live in one documented layer.

Tokens

Chrome and site speak the same language

Panel surfaces, page backgrounds, accents, and spacing now draw from shared roles.

Motion

Intentional, restrained movement

Transitions add tactility without turning the product into theatre.

--background --primary --chrome-panel-surface --brand-surface-1 --text-h1 --spacing-6
Product

The product already looks like the deck should.

The marketing site now borrows the same chrome cues, surface logic, and typography Storybook documents for the app.

Direct manipulation

Grab the object, not the settings maze

The editing metaphor stays tactile and immediate instead of menu-heavy.

Live parity

What you shape is what ships

The builder and published output use the same visual grammar, so preview drift drops.

Publishing

Domains, save flow, and launch state stay visible

The chrome cues make infrastructure feel understandable instead of hidden.

Architecture

The stack compounds because the system is explicit.

Fast rendering and clean publishing matter, but the bigger leverage is that design decisions become reusable assets instead of hidden team memory.

What is already working

  • React 19 and Vite keep the loop fast.
  • Convex gives real-time sync and autosave behavior.
  • Cloudflare handles edge delivery and domains.
  • Storybook now documents marketing + product surfaces together.

Next release arc

Now

  • Token coverage for every high-signal surface.
  • Block templates that inherit the same system rules.
  • Builder chrome and marketing pages reviewed from one place.

Next

  • SEO and Open Graph controls.
  • Forms, analytics, and collaboration layers.
  • Sharper AI authoring built on the same visual contract.
Pricing and growth

Simple monetization, clear partner story.

The pricing stays legible. The partner model stays boring on purpose. That makes the business easier to explain and easier to trust.

Starter

Free

$0 forever
  • 1 site
  • Unlimited blocks
  • Live publishing
Core plan

Plus

$12 / month
  • 2 sites
  • Custom domains
  • Remove branding

Also $120/year for teams that want a simpler invoice.

Scale

Business

$29 / month
  • 5 sites
  • Priority support
  • AI-assisted editing and translation
Partner loop

Commission-based growth without weird math

30% recurring for 12 months

Vanity links, Stripe Connect payouts, and a simple explanation: refer the customer, keep a clean recurring cut, stop overcomplicating the story.

  • 1% of a $14.3B category is already a large company.
  • Partners can explain the offer in one sentence.
  • The deck now looks credible enough to support the model.
Launch

Ship the same visual language everywhere.

The point of Consistency is not cosmetic polish. It is reducing the distance between idea, implementation, and review until the whole product starts compounding faster.

Try Consistency Back to top