Amir Salmaniplatform and reliability engineer

cases / A one-person shop

An online shop for a one-person business, built from her own list

Amir Salmani,

  • 289 messages became 1 list of 20
  • shop, checkout, owner's desk
  • built, in preview, not yet selling

The business

One woman sells cosmetics. She had a site that didn’t work for her and a long conversation full of what she wanted: 289 messages over 3 months, 24 of them voice notes. She’d sent her list 3 times, the last time only so we could tick things off.

So the first job wasn’t code. It was her list: 20 requests on one page, each in her own words, each marked built, half built or not built, with the reason.

Some of what she asked for wasn’t a feature. “The site is dry and lifeless” is a request too.

It’s built and running behind a preview gate. It hasn’t taken an order yet.

The product

  • The shop window is the front page, because that’s what she said mattered most.
  • Search, cart, checkout and order tracking.
  • A wishlist with no account to create.
  • “Tell me when it’s back”: the buyer leaves a number and she sees who’s waiting.
  • An owner’s desk made for her phone: orders, a return, stock, a price, a new product.
  • An invoice for each order. A gift prints without prices.
  • Her colours exactly, and a small mascot, because of that “dry and lifeless”.

The tech

TypeScript and Next.js, in containers, started with one command.

The checks are the part I’d point at. A browser buys something through the payment provider’s sandbox and then cancels once. Another works the owner’s desk the way she would. Another tests it with large text, on a narrow screen, by touch.

the questions this answers

Tell me what you need