Shopify
— updated
Zapier changed how it bills. Most advice hasn’t caught up.
Zapier bills successful actions; Make moved to credits; n8n Cloud bills executions. What counts, what doesn’t, and how the entry plans compare.
Legwork is a small publishing imprint. We write operational books for people who run a business without a team — the ones doing the accounting, the support inbox and the photography in the same afternoon.
Every figure we print carries a label saying where it came from: measured, vendor-published, self-reported or estimated. Where we do not know something, the book says so rather than rounding the gap into confidence.
Vertical one — Shopify
Building an AI operations team for a one-person Shopify store
Ten operational roles handed to a language model one at a time, with the cost of each, the ways each fails, and an honest account of the three that are not worth doing yet. 15 chapters, 11 figures, written against one real store over twelve months.
Read about the book PDF, $29 — founding price
The method is the same each time: pick a job people do alone, follow one real operator for a year, and print what we find. The subject changes; the sourcing standard does not.
Published
One person, one store, and the operational work of a team of ten. The first title covers what to hand to a model, what to keep, and what each handover actually costs.
In research
Scheduling, ordering, and the reservation stack. Research in progress; no publication date yet.
Planned
The unpaid operations job. Planned, not started — listed here so you know where this goes.
Shopify
— updated
Zapier bills successful actions; Make moved to credits; n8n Cloud bills executions. What counts, what doesn’t, and how the entry plans compare.
Shopify
— updated
Klaviyo bills every contact who could be emailed. Tier prices, the February 2025 definition change, the 90-day suppression lock, and the 20% high-spend surcharge.
Shopify
Gorgias helpdesk plans start cheap; AI Agent is a separate meter. Two overage lines, marketed automation rates, and how both can hit the same conversation.
We publish slowly. Roughly two emails a month: what we are researching, what a tool actually charged us this month, and a note when a new title is out.
This form is not connected yet. Set
PUBLIC_EMAIL_ENDPOINT
in the build environment and redeploy.
Until then the field is disabled rather than quietly dropping addresses.