Skip to content

Selected work

Shopify systems built around real commerce constraints

A selection of production storefront work across subscriptions, complex catalogs, merchant tooling, performance, analytics, and theme delivery.

Each case focuses on a different engineering decision: what to build, what to preserve, how to measure it, and how to keep the store operable.

ShopifySoftware

Flagship Shopify case

Engineering a Conversion-Focused Shopify Storefront

One connected commerce system: the subscription offer designed on native Selling Plans, buy-box and cart state, real-user performance, funnel tracking through the closed checkout, and production-safe delivery.

Wellness DTC mobile product page
  • +45% total sales in the eight weeks after release, period over period
  • Native Shopify Selling Plans with custom subscription presentation
  • Three silent cart failures traced to one shared root cause
  • Mobile CLS issue discovered through real-user monitoring
  • Shopify
  • Subscriptions
  • Commerce systems

Absolute Support: Extending Dawn for a Complex Compression Catalog

A custom product-selection and educational layer for a medically complex catalog, while Shopify's native variant, cart, search, and filtering systems remained the source of truth.

  • Compression modeled separately from purchasable variants
  • Custom controls feeding Dawn's native state
  • Merchant-editable OS 2.0 content layer
  • Dawn
  • Product modeling
  • Search & Discovery

Boxwood Coffee: Knowing What Not to Rebuild

A disciplined Prestige adaptation for a specialty roaster spanning retail, subscriptions, two cafés, catering, and wholesale, with custom code reserved for coffee-specific product data and navigation.

  • Configure, extend, or build
  • Coffee product data modeled with metafields
  • Prestige commerce behavior preserved
  • Prestige
  • Metafields
  • Theme adaptation

Co-founded product · Software

A five-language quiz funnel, from the first click to the subscription

A consumer product launched with partners, not on Shopify. Paid traffic enters a nineteen-screen quiz and leaves as a paid subscription: the quiz engine, the paywall, billing, report generation, three analytics layers and five languages are my code. The brand and the revenue stay with the partners.

  1. 01Pre-lander or landing
  2. 02Session from the first click
  3. 03Quiz, 19 screens
  4. 04Partial reveal
  5. 05Paywall, three tiers
  6. 06Trial week in portions
  • Session from the first click: every answer and its attribution on the server
  • Paid content never leaves the server; competitors keep it in the DOM
  • Browser and server-side events deduplicated by event_id
  • Five languages with their own addresses, ads routed straight to the language
  • Quiz funnel
  • Subscription
  • Server-side events

Hand over the storefront. Consider it handled.

Send the task and the goal. From there I read the code, take the work through release and verify it myself.