Case study · Savannah French
A two-sided marketplace where independent makers sell handmade goods and buyers pay each maker directly. I did the product design, architecture, implementation, testing and deployment myself. It runs as a live demo with fictional shops and Stripe test-mode payments.
Big handmade marketplaces are crowded with mass-produced goods relabeled as handmade, so real makers get buried and buyers can’t tell what they’re getting. Wildloom only lists shops that a person has reviewed, and it gets out of the way of the money: makers keep their full price.
The first version charged buyers on the platform account and transferred each maker’s share afterwards. That made the platform the merchant of record and meant it paid the card fees on every sale. I moved it to Stripe Connect Standard accounts with direct charges. Each maker’s own Stripe account is the merchant, the platform takes no fee, and there’s no money sitting with the platform to manage. The trade-off: a payment can only land in one account, so a multi-maker cart checks out once per maker, and the cart is designed around that.
Auth, data access, file storage and payments each sit behind a thin interface, and nothing else does. That paid off: storage moved from Supabase Storage to Cloudflare R2 by flipping an environment variable, and the whole app runs against in-memory implementations for fast, deterministic end-to-end tests.
Onboarding is a single checklist with one obvious next step at a time. Forms ask plain questions (“How many do you have?”), accept prices typed the way people type them (“$85”), and default to the common case. Makers invited directly skip the application entirely with a one-time link that creates a pre-approved shop.
Guest checkout through Stripe’s hosted page collects email and shipping, and the webhook stores the ship-to address on the maker’s Orders page. Webhooks are verified per account, so an event from one maker’s Stripe can’t mark another maker’s order as paid.
Every shop is reviewed before it goes live. Makers explicitly agree to the terms, and the time and terms version are stored as a record. Error and 404 pages give visitors a one-click way to report problems.
The suite walks a first-time buyer through a two-maker purchase, and walks an invited maker from invite link to first listing, on desktop and phone sizes. It also covers webhook security, empty and error states, and access rules. A separate smoke test runs the real payment path against Stripe’s test environment and the staging database, checking that the charge lands on the maker’s account with no platform fee. Writing these tests caught real bugs before users did, including a crash on the page makers return to after Stripe setup.
I help teams design and ship product, payments, and AI features end to end.
savannahfrench.com