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.
Selected Work / Case Studies
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
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.
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.
Read the constraint and implementation sections. They explain why the obvious fix was not enough and what tradeoffs shaped the final solution.
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.
Jump to the reusable lesson. It condenses the case into a principle that can help with future websites, stores, applications, or integrations.
Showing 10 to 18 of 54 · Page 2 of 6
E-commerce
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.
Read case studyWordPress systems
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.
Read case studyAPI integrations & automation
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.
Read case studyE-commerce
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.
Read case studyE-commerce
A free-product promotion became an inventory problem, a pricing problem, and a cart-state problem at the same time.
Read case studyE-commerce
Clickable Buy 3, 6, 10, and 20 choices needed to feel like a bundle selector without becoming a second inventory system.
Read case studyE-commerce
Legacy post-purchase scripts had to move to Shopify's extension model without silently dropping analytics, reviews, or affiliate attribution.
Read case studyE-commerce
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.
Read case studyE-commerce
Automated accessibility testing exposed small markup problems that did not look broken visually but made the interface less reliable for assistive technology.
Read case study