No enforced window
Orders trickled in past cutoff, so makers couldn't plan production against a number they could trust.
Back to work
Case study · Drop commerce
Zero to a livemarketplacein two weeks.
DropQ is an operating system for independent sellers running timed product drops — scheduled preorder windows, live on-site QR sales, pickup scheduling, inventory, orders and customer messaging. Built for food makers, collectors, artists and vintage sellers.
Vendor to buyer, end to end: create the drop, take the order, hand it over. Customer details blurred.
Drops were running on DMs, forms and Venmo.
No inventory truth
Overselling, or hand-tallying Instagram DMs at midnight. Neither is a system.
Pickup chaos
Customers arrived, couldn't find the vendor, and had no way to reach them. The drop succeeded and the handoff failed.
The turning point
Shipping fast got us to a real drop.Auditing it told us what to build next.
The first commit landed on 11 June. Fourteen calendar days and 131 commits later there was a live MVP: storefronts, drops, inventory, Stripe Connect payments. Two weeks, zero to working marketplace — which sounds like the headline, but isn't.
The headline is what happened on 4 July. The first real drop went live and took real money, and instead of celebrating we ran a full UX audit across the entire experience — drop creation, through purchase, through pickup. The biggest finding wasn't in the checkout everyone worries about. It was the breakdown in communication between customer and vendor at pickup: people standing in a parking lot, holding a paid order, unable to find the person they'd bought it from.
That became the next build cycle. Pickup windows. "How to find us" descriptions. Open-in-Maps. Opt-in vendor contact. Vendor check-in broadcasts. Customer "I'm here" arrival. Shipped within a week of the audit.
That's the whole argument for shipping fast, and the honest admission of what shipping fast costs. Speed got us to a real transaction. Only a real transaction could tell us what was actually broken. And when you compress design and build that hard, QA becomes the thing that saves you — because the gaps don't hide inside any one role, they hide in the seams between admin, vendor and customer.
What it delivered.
- 01
Overselling is structurally impossible
An atomic conditional SQL claim; lost races auto-cancel and refund. Not a validation rule — a guarantee.
- 02
The buyer never sees DropQ
Vendor-branded link previews, emails and storefronts. The platform stays out of the vendor's relationship with their customer.
- 03
No customer accounts
Order links work as capability URLs with localStorage saves. Nobody signs up to buy a cookie.
- 04
Timezone-correct scheduling
UTC instants authored in each vendor's IANA zone — because a drop that opens an hour late is a drop that failed.
- 05
Built end to end, front and back
Data model, Stripe Connect payments, messaging, scheduling, auth and every screen — one team, whole stack, no handoff.