Skip to content

Selected Work / Case Studies

Real development case studies you can learn from.

These are production scenarios and product work, not a gallery of screenshots. Named live work is shown where it can be public, while other client details stay private. Alongside client case studies, in-house products such as ConduitTools show how focused ideas are designed, built, and maintained over time.

54case studies

How to use this portfolio

Read the part that helps you make a better decision.

You do not need to understand every technology mentioned in a case study. Start with the problem and result, then go deeper into the implementation only if it is relevant to your own site or product.

01

If you have a similar business problem

Read the plain-English summary, real situation, and result first. Those sections explain what the work changed without requiring you to know the code or platform details.

02

If you are evaluating a technical approach

Read the constraint and implementation sections. They explain why the obvious fix was not enough and what tradeoffs shaped the final solution.

03

If you are planning a release

Use the release-check section as a practical QA reference. It shows what needed verification before a change was safe to ship to real users.

04

If you only want the takeaway

Jump to the reusable lesson. It condenses the case into a principle that can help with future websites, stores, applications, or integrations.

54 case studies

Showing 10 to 18 of 54 · Page 2 of 6

10E-commerce
  1. 01Cart changes
  2. 02Check eligibility
  3. 03Read Shopify pricing
  4. 04Refresh offer UI
Real scenario · client identity private

E-commerce

Free gifts and BOGO messaging that follow Shopify's actual discounts

A storefront needed automatic gifts and clear BOGO messages while Shopify remained responsible for the final price. The theme reconciled gift eligibility with cart results and used promotion-specific discount allocations to explain savings accurately.

ShopifyLiquidJavaScriptNative discounts
Read case study
11WordPress systems
  1. 01Regional configuration
  2. 02Shared PHP template
  3. 03CMS content
  4. 04Content + layout checks
Real scenario · client identity private

WordPress systems

Regional WordPress landing pages with shared templates and approved-copy tests

A regional landing-page system separated location content from its shared layout. New pages could use a configuration file and a CMS record, while Playwright checked approved wording and responsive behavior.

WordPressPHPConfiguration-driven templatesPlaywright
Read case study
12API integrations & automation
  1. 01Product page
  2. 02Participating branch
  3. 03Serverless relay
  4. 04Team workflow
Real scenario · client identity private

API integrations & automation

Product-page viewing requests connected to an in-store workflow

A Shopify product page needed to let shoppers request an in-store viewing without losing product or branch context. A request form, brand-aware location choices, and a serverless relay connected the storefront to the team's Zapier workflow.

ShopifyAPI integrationNode.jsVercel
Read case study
13E-commerce
  1. 01Sold-out product
  2. 02Relevant variant
  3. 03Klaviyo subscription
  4. 04Contact fallback
Real scenario · client identity private

E-commerce

Variant-specific back-in-stock alerts with a working contact-form fallback

A sold-out product needed a useful Notify Me flow even when the notification integration was unavailable. The theme started with a working contact form and enhanced it with variant-specific Klaviyo subscriptions when the service was configured.

ShopifyKlaviyoJavaScriptProgressive enhancement
Read case study
16E-commerce
  1. 01Audit legacy scripts
  2. 02Map responsibility
  3. 03Install replacement
  4. 04Place test order
Real scenario · client identity private

E-commerce

Migrating Thank You and Order Status customizations without losing tracking

Legacy post-purchase scripts had to move to Shopify's extension model without silently dropping analytics, reviews, or affiliate attribution.

ShopifyCheckoutApp BlocksApp Pixels
Read case study
17E-commerce
  1. 01Ad landing URL
  2. 02Variant-safe URL
  3. 0324h last-touch store
  4. 04Cart attributes
Real scenario · client identity private

E-commerce

Preserving Meta and UTM attribution from ad click through the Shopify order

Variant navigation was stripping campaign parameters even while browser tracking still fired correctly. The solution preserved Meta and UTM values during product interaction, kept a 24-hour last-touch attribution snapshot, carried the valid data into checkout, and used Shopify Flow to persist the final six campaign fields on the order.

ShopifyMeta PixelUTMShopify Flow
Read case study