Montclair Sports & DeuceGC

The temptation as a founder is to design each store as its own product. The diagnosis here was that the products were different but the operations were nearly identical — and operations would kill the project before product would.

• Time logs from week one

  More than half of the working hours in the first two weeks went to operations tasks (fulfillment, returns, inventory), not to product or design work.

• Customer support emails

  Nearly every support email could have been answered by a single canonical product page that did not yet exist on either site.

• Holiday season modelling

  A spreadsheet projection said that the per-order operations cost — measured in time, not dollars — would break the project at expected holiday volume unless the storefronts handled more of the work themselves.

• One person, two stores

  Everything has to be maintainable by one operator. That means no per-store custom code paths, no per-store brand stack, and no per-store editorial calendar.

• Real money, real customers from day one

  There is no soft-launch lane. The first version of the storefront takes real orders from real customers; there is no separate testing environment.

• Hosting and tooling on a fixed monthly budget

  The cost of the stack has to fit inside the gross margin of the products. Anything that scales with traffic is preferable to anything that scales with feature count.

1. 01

   One product model, two skins

   Both storefronts read from the same content model. The visible difference is brand surface; the underlying schema is shared.

2. 02

   Self-serve before support

   Every storefront page is designed assuming the customer will not write in. Support exists, but the default path is a customer who answers their own question.

3. 03

   Operations is a product surface

   Returns, shipping, and fulfillment are designed with the same care as the product detail page. They are part of the brand, not behind it.

Three structural directions were considered for how the two storefronts would relate to each other. The deciding question for each was whether one operator could realistically maintain both stores at holiday volume without burning out.

• Exploration 01 — placeholder

• Exploration 02 — placeholder

• Exploration 03 — placeholder

Both storefronts launched, took real orders, and survived their first holiday season under a single operator. The shared model paid for itself by the second seasonal refresh, when both stores updated in the same week.

Storefronts shipped

2

DeuceGC and Montclair Sports, both running on the same content model.

Time to seasonal refresh

~1 week

Both stores, single operator, second-season baseline.

Solo-operator margin

Positive

Sustained across the first full year of trading.

The most valuable part of this work was not either store individually — it was the underlying realization that the cost of a small commerce business is operations, not product. Designing operations as a first-class surface was the single biggest leverage point either business had.

Founder work taught me something employee work never did: every product decision is also an operations decision. Inside a larger company, ops is somebody else's department; as a founder it is the same person who designed the product. The two storefronts continue to run on the shared model, and the lesson — design the operations as carefully as the product — is one I carry back into every team I work with.