Skip to content
michael@dishmon-ops$zsh
00:00:00
STATUS
shipping
SLOTS
2/3
REPLY
<50h
SHIPS
70/wk
CLOCK
--:--:--
BUILDS
ytd

Five departments. One person. You talk to me the whole time.

> scan
Or tell me what’s brokenSee the work
// tail -f /var/log/opsLIVE
// editor / lead-magnet.tsutf-8 · ts
> deliver_checklist({
email: "",
type: "12-point DTC",
send: true
})
// click to type your email

NOTE 02 / WHAT I DO

If you’re running a $2-10M DTC brand, you probably know the feeling: Shopify, Meta, and GA4 never agree on what you made last month. I help by being one person who can plug the server-side tracking, write the copy, ship the theme, build the Klaviyo flows, and rank the SEO. Less telephone, more getting stuff done.

What you should expect from one hire, in the same week.

If you’re splitting this work across a brand shop, a Shopify dev, a martech consultant, a compliance advisor, and a content agency, you already know how much time gets lost in translation. Here’s what a single engagement can cover:

  • 01Concept a brand campaign
  • 02Write ads, emails, and landing pages
  • 03Build the Shopify theme
  • 04Ship CAPI + Stape so ROAS stops lying
  • 05Write the SEO content and rank it
  • 06Build the Klaviyo flows
  • 07Set up the analytics dashboard
  • 08Define who the customer actually is

That’s what one engagement actually looks like. All eight capabilities, one brain, shipped in the same week. I’ve been doing this for 20+ years across brand, code, tracking, and ops. It’s a weird combination of skills, but it turns out to be really useful.

$ cat /var/log/scope.md | tail -1

01a designera design director
02a developeran engineering manager
03a marketerrunning a marketing ops team
04a copywriteran editorial director
05a homelab hackera cloud ops lead

I've worn all five hats. Turns out they fit pretty well together.

$ diff applied. exiting.

Three paths.
Pick yours.

A quick route to the part of the site that matches you.

The work speaks for itself.

Tracking fixed. Pages shipped. Pipelines unclogged. Below are three receipts with dated numbers you can expect a similar engagement to return.

ALL CASE STUDIES

$ git log --oneline --since="2024" | wc -l

Running experiments. Everything here is live.

Interactive code experiments I build between client ships. Shaders, particle fields, type specimens, canvas toys. Play with any of them right here. There are 19 in the full lab.

ALL EXPERIMENTS

$ ls /lab/ | head

SEC.05 / WRITING / 199 POSTS / 15 CLUSTERS

Field notes from inside the stack.

Browse all writing →

Build logs, case studies, post-mortems, and decision logs from inside a DTC and martech stack I actually ship. Organized by cluster, not date - each section below is a working map of a domain.

SEC.00 / CLUSTERS / 15 TOPICS

Browse by cluster

Scroll to browse all 15 topics

SEC.01 / LATEST / UPDATED 2026-04-24

Latest

Attribution & CAPI

12 articles

Everything about getting Meta, Google, and Klaviyo to agree on what a conversion is. Pixel to CAPI migrations, event_id dedup patterns, consent-mode gotchas, and the forensic work of finding the 30% of conversions your reports are missing. Each piece is grounded in a real DTC rebuild.

The field guide to Meta CAPI for DTC operators
Hub·10 min read

The field guide to Meta CAPI for DTC operators

A pattern-library field guide to Meta CAPI for DTC operators. Six failure shapes, six working fixes, grounded in a 48-hour Shopify rebuild.

Read article
Attribution windows after iOS and Android privacy updates
APR 22 · 8 min

Attribution windows after iOS and Android privacy updates

Field notes on how attribution windows ios android shifts changed what Meta and GA4 actually measure, and what DTC operators should do in 2026.

Debugging CAPI payload mismatches in production
APR 22 · 9 min

Debugging CAPI payload mismatches in production

A postmortem on capi payload mismatch debugging. Three root causes, the verification sequence, and the fix that held in production at a Shopify DTC.

CAPI for subscription commerce without double counting
APR 22 · 10 min

CAPI for subscription commerce without double counting

A tutorial on capi subscription commerce. How to fire new-acquisition and rebill events so Meta optimizes against the right DTC cohort, not rebills.

Pushing Meta CAPI match quality score from 6 to 9
APR 22 · 13 min

Pushing Meta CAPI match quality score from 6 to 9

A tutorial on meta capi match quality score improvement. The field-by-field moves that took a DTC Shopify store from a 6 to a 9 in a production rebuild.

Hashing PII for CAPI purchase events without leaks
APR 22 · 12 min

Hashing PII for CAPI purchase events without leaks

A tutorial on capi purchase event pii hashing. The six-step pipeline that normalizes, hashes, and keeps raw values out of every log sink in production.

Wiring CAPI events around Klaviyo flow triggers
APR 22 · 11 min

Wiring CAPI events around Klaviyo flow triggers

A pattern-library look at capi klaviyo flow integration. Three DTC failure modes where server events and triggers fire out of order, and the fix.

Consent Mode v2 and CAPI - what actually fires on your server
APR 22 · 14 min

Consent Mode v2 and CAPI - what actually fires on your server

A pattern-library breakdown of consent mode v2 capi behavior across four consent states, with the DTC failure modes each one produces on Meta attribution.

Event_id strategy across Shopify Pixel, CAPI, and GTM
APR 22 · 11 min

Event_id strategy across Shopify Pixel, CAPI, and GTM

A shopify event_id strategy that holds across Pixel, CAPI, and GTM. Five steps with Liquid, GTM web, and server snippets from a Q2 2024 rebuild.

Reconciling GA4, Meta, and Shopify purchase counts
APR 22 · 9 min

Reconciling GA4, Meta, and Shopify purchase counts

The short, full, and nuanced answer on ga4 meta shopify reconciliation. Five sources of variance and the one number to trust per question asked.

Why DTC brands should run lift tests over last-click
APR 22 · 10 min

Why DTC brands should run lift tests over last-click

A contrarian case on lift test vs last click dtc attribution. Why last-click misreads incrementality and how a cheap geo lift gives the real answer.

Stape vs self-hosted GCP for a server container
APR 22 · 9 min

Stape vs self-hosted GCP for a server container

A decision log on stape vs gcp server container hosting for a Shopify CAPI rebuild. Costs, control, and the tradeoffs that changed my mind on the pick.

Pick the tier that matches your problem.

If you need the workflow, start at the entry tier. If you need templates you can drop into your stack this week, take the mid tier. If you’re rebuilding your whole operating system, the flagship is for you. No hourly consulting. No generic “AI strategy” decks.

FULL CATALOG

Entry / Diagnostic report

$149

CAPI Leak Report

A 14-point diagnostic of your Meta Conversions API setup, delivered inside your dashboard within 72 hours.

// available nowbuy

Entry / Self-serve diagnostic

$129

DTC Stack Audit

A self-serve diagnostic that scores your Shopify store across tracking, analytics, theme performance, and attribution.

// preorder opendetails
Most popular

Mid / Course + Templates

$497

The Operator's Stack

Video course, production templates, Claude Code skills pack, and 6 months of async Slack.

// preorder opendetails

Flagship / Full system

$1,997

One-Person Studio OS

The complete operating model for running a solo practice that outships agencies.

// coming soondetails

Productized / Shopify

$349

DTC Theme Starter

A production Shopify theme for DTC brands, with Meta CAPI already wired and Core Web Vitals tuned.

// preorder opendetails

Productized / AI Workflows

$149

DTC Audit Skills Pack

12 production Claude Code skills that run a DTC operator's full diagnostic stack. 4 more skills shipping free.

// available nowbuy

$ cat /etc/pricing.conf

A few things you’re already wondering.

Q.01

Can I trust one person with everything?
>I'd rather show you than talk about it. Every case study on the site has the dates, the tools, and the result. The work speaks for itself.

Q.02

I need a real team.
>Totally get that. I've done all five of these roles hands-on, so you're getting team-level coverage from one person. I also work alongside your existing people when you have them.

Q.03

What if you get hit by a bus?
>You get documented systems, knowledge transfer artifacts, and agent recipes from day one. If anything happens, your team keeps shipping.

Q.04

You're probably too expensive. Or too cheap.
>All pricing is published on the site. Products are fixed price. Retainers are time boxed. What you see is what you get.

$ exit 0

Notes from people who signed off on the work.

Quotes pulled directly from past clients and collaborators. Real people who hired the work, signed off on it, and were willing to put their name on the experience.

MD–001 · FILED01 / 10
Mike's been a great source of encouragement and wisdom in a time where I needed direction in my business. He's been a partner, a friend, and an awesome mentor in this process and I'm looking forward to continuing our professional and personal relationship.
Eric Sin
Founder & CEO / 2717 Design
5 / 5 · VERIFIED
auto-advance · 8s

$ ls /testimonials/ | shuf

Let’s fix
some problems.

Instead of briefing four vendors, you work with one person across brand, code, infrastructure, compliance, and growth. You get dated receipts, published pricing, and an agent library you own after the engagement ends. You work with me directly. That’s kind of the whole point.

or email direct hello@michaeldishmon.com