A ceramics studio sold out its first online drop on a Webflow storefront

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Kiln loads set the rhythm of the studio: every few weeks a batch of 30–60 pieces emerges, gets photographed, and sells through Instagram direct messages, first message first served. The owner throws, glazes, films, packs, and ships everything herself, with occasional help from a friend on packing days. The audience is loyal and arrives quickly when a drop is announced — the bottleneck was never demand. Each drop meant a night of manual invoicing, and enthusiasm occasionally outran inventory.

What it was costing

Drops sold through Instagram DMs — first-come-first-served by message, with manual invoicing, double-selling, and hours of admin per drop. The studio needed a storefront that could take a drop live in minutes.

What they could see

• Drop nights ran past midnight: hundreds of DMs to read in order, winners to invoice by hand, and payments to chase.
• Two pieces per drop sold twice on average — messages crossing mid-checkout meant apologizing and refunding one disappointed collector.
• The hours after each announcement went to admin instead of the studio, which made drops feel like a tax on making.
• Collectors in other time zones missed drops entirely, because first-come-by-DM rewarded whoever was awake at announcement time.

The constraints we worked inside

• The brand's identity is handmade and spare; the storefront had to feel like the studio, not a commerce template.
• Drops are small (30-60 pieces); heavyweight commerce machinery was the wrong tool.
• The studio owner runs everything; the post-drop workflow had to be one screen.

What had been tried before

A waitlist form was added to the studio's site, meant to serialize demand into a queue she could work through calmly.

The queue serialized interest but not sales — she still invoiced manually in list order, so the bottleneck moved from reading DMs to sending payment links one at a time.

Payment links were batched in advance for the most anticipated pieces, ready to paste on announcement.

Links outlived their stock — a paid link after a piece sold created refunds and the same double-sell apology the batching was meant to prevent.

What we proposed

We proposed a Webflow storefront built around the drop as an event: every piece modeled as a structured product with glaze, dimensions, and firing-batch fields, and a drop page assembled from components — countdown, set view, piece cards — so a new drop is content entry, not a design project. Stripe's hosted checkout takes the selling, so a piece sold is a piece gone. The spare, handmade identity would carry the design, and the post-drop workflow had to fit one screen, because the owner runs everything alone.

Just as important is what we ruled out, and why:

• A full Shopify build with a custom theme — Commerce machinery sized for hundreds of daily orders is overhead for 30–60 pieces a month, and the checkout customization needed to feel handmade would eat the budget.
• A drop-commerce tool built for sneaker-style releases — Raffle and queue mechanics fight the studio's fairness instinct, the branding would sit inside someone else's template, and monthly fees for six drops a year never penciled out.

How the work ran

Delivered by the experience pod — designer + frontend engineer over 4 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

Webflow Ecommerce

The drop page is fundamentally a designed object; Webflow lets the countdown, set view, and piece cards live in one visual system the owner can update.

Stripe checkout

Hosted, battle-tested under concurrent buyers, and free of maintenance — inventory decrements at payment, which is what makes double-selling structurally hard.

Webflow CMS

Glaze, dimensions, and firing batch become fields, so each drop is a content-entry session and past drops become a browsable archive for collectors.

Instagram

It is where the audience already is; announcement posts link straight to the drop page rather than rerouting a loyal crowd through a new channel.

What went wrong

How we worked together

Cadence

A 30-minute call twice a week around studio hours, plus a shared checklist doc that doubled as the drop-day script.

Client side

The owner did everything client-side — design approval, piece data entry, photography — with her packing-day friend drafted for the first rehearsal.

Decisions

Design calls were settled by a simple test: did it feel like her feed? If she hesitated, we revised rather than argued.

They provided

Piece photography, glaze and batch details for three past drops, her announcement captions as tone reference, and rehearsal time on two afternoons.

What changed

The headline: time for the first online drop to sell out — previously a multi-day dm process — 48 min, read from Order timestamps. A second check: double-sold pieces since moving online at 0.

A drop is now an hour of attention instead of a lost night: the announcement goes up, the pieces sell in under an hour, and packing lists print themselves. Double-selling stopped being a background anxiety, which changed how she talks about limited pieces — she no longer hedges in her captions. Collectors abroad buy on equal terms for the first time, and several have used the drop archive to request commissions. The studio calendar gained breathing room she has, so far, spent on larger kiln loads.

The result was read from Order timestamps against the pre-engagement baseline over the stated window, with a guardrail check on double-sold pieces since moving online. Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The Webflow project under her own login, with the drop template and component library.
• A one-page drop-day script covering entry, publish, announcement, and the post-drop checklist.
• The load-rehearsal script so future drops can be stress-tested the same way.
• Stripe account with payout schedule and refund procedure documented on one screen.