N°00The PracticeQUEUE OPEN · 2026 Q2

On working small · a manual for our practice

A small practice,deliberately

Built around the work — not the agency.
Six chapters. One workbench. The constraints are the practice.

Read the practice Or skip — open a brief

workbench · wezby/practice — liveN°02

06–08engagements / year

100%bespoke · no templates

08–15wbuild duration

VIIchapters in this practice

N°01Origin

Why the practice exists.

ezby started because material brands kept hiring engineers for problems that were not solvable in theme code. The brief would arrive at a freelancer; the freelancer would openShopify admin, look at the available apps, and quote a workaround. Six months later the brand was paying three monthly subscriptions and still doing the work in a spreadsheet.

The problems were specific. A $4.99 sample that needed to credit forward six weeks later. A cart whose freight bracket morphed at item fourteen. A slab of marble that should not be sold without its photograph. Theme code was never going to hold those answers — not because the theme was bad, but because the answers were operations questions wearing storefront clothing.

So we built a workbench. Headless storefronts, automation graphs, custom apps, integrations — done at system scale, not at plug-in scale. We named it Wezby and capped the year at six to eight engagements. The cap is the practice; the cap is also the answer.

◆

N°02The journey

Six stages. Paid start, fully owned finish.

Four rules of practice woven into six stages of work. Scroll to advance — the system does the same.

NOWN°01 · Discovery01/06

N°01— stage 1 of 6

DURATION1–2 weeks

Paid. Always.

Discovery.

We are paid to understand the problem before we propose a solution. By the end of discovery you own a system design — not a sales deck. If the fit is wrong, the engagement ends here with a deliverable in your hand.

RULE · 01

Paid discovery filters for serious work — and protects time we owe to brands already on the bench.

N°02— stage 2 of 6

DURATION2–3 weeks

Custom, top to bottom.

Architecture.

Data model, flow graphs, integration map, and every decision recorded in a living document. We do not adapt a template; we draw the system from your operations. By the end of this stage you can read the architecture before any code is written.

RULE · 02

Bespoke only — no packages, no tiers. Every build starts from your actual operations.

N°03— stage 3 of 6

DURATION4–10 weeks

Two engineers. One file open.

Build.

Headless storefront, automation workflows, custom apps, integrations — built in parallel by a tight team that does not split attention across other engagements. You see weekly demos and have direct access to staging from week one.

RULE · 03

Six to eight engagements a year. The cap is not aspiration — it is the only way the work gets the attention it needs.

N°04— stage 4 of 6

DURATION1–2 weeks

With your operations, not against them.

Test.

Your team runs real orders through staging — sample orders, trade flows, freight edge cases, the slab on hold for 36 hours. We watch the data, you watch the operations, and we close the gap together before launch is even on the calendar.

N°05— stage 5 of 6

DURATION1 week

Cutover · monitoring window.

Launch.

DNS flips at a time you choose. We watch every metric for the first 96 hours — order rate, automation runs, freight calculations, CDN cache hits. Issues are resolved while they are still small; the launch register is signed when the curve flattens.

N°06— stage 6 of 6

DURATIONimmediate

Ownership transfer — not access.

Handover.

Source code, admin permissions, n8n instance, custom app keys, workflow exports, architecture diagrams, decision log, Figma files, brand tokens. Everything you'd need to run, extend, or replace the systems without us in the loop. Signed and dated.

RULE · 04

Full handover. We are not building a dependency — we are building a system the brand owns.

N°02The journey

Six stages. Paid start, fully owned finish.

Four rules of practice woven into six stages of work.

N°01

Paid. Always.

Discovery.

1–2 weeks

RULE · 01

Paid discovery filters for serious work — and protects time we owe to brands already on the bench.

N°02

Custom, top to bottom.

Architecture.

2–3 weeks

RULE · 02

Bespoke only — no packages, no tiers. Every build starts from your actual operations.

N°03

Two engineers. One file open.

Build.

4–10 weeks

RULE · 03

Six to eight engagements a year. The cap is not aspiration — it is the only way the work gets the attention it needs.

N°04

With your operations, not against them.

Test.

1–2 weeks

N°05

Cutover · monitoring window.

Launch.

1 week

N°06

Ownership transfer — not access.

Handover.

immediate

RULE · 04

Full handover. We are not building a dependency — we are building a system the brand owns.

N°03Discipline

The bench,
and what's on it.

Six capabilities. Each chosen against the lazy default. Each replaceable by you if we ever stop being useful. This is the stack a small practice can actually master.

N°01STOREFRONT

Hydrogen

React + Remix, on the edge.

Headless storefront on Shopify Hydrogen. Server components, edge runtime, full control over the data graph. Composable from cart to PDP to checkout-adjacent flows.

N°02AUTOMATION

Shopify Flow

Operations as graphs.

Native automation for the events that matter — sample orders, tag transitions, draft-order completion, refund branches. Connected to your existing apps without scripts in admin.

N°03INTEGRATIONS

n8n bridge

Where Shopify meets the back office.

Self-hosted n8n workflows connect Shopify to ERPs, sheets, freight APIs, accounting systems. Triggered by webhooks, observable, versioned — and yours to extend without us.

N°04CUSTOM APPS

Remix apps

When the platform stops.

Embedded Shopify apps in Remix + TypeScript when no app on the market fits — trade portals, project rooms, slab inventories. Built once, owned forever.

N°05INTELLIGENCE

Reports · dashboards

The numbers you actually run on.

Custom Shopify reports, Looker / Metabase dashboards, GA4 funnels, CAPI deduping — shaped around how your business actually thinks, not the platform's default charts.

N°06INFRASTRUCTURE

Markets · Ads · CAPI

The plumbing, done once.

Shopify Markets, Google Merchant Center, Ads, GA4, Conversion API, server-side tagging. Configured once, documented, never touched in panic.

What turns the stack into a practice

N°01Every decision is documented.
N°02Every workflow is portable.
N°03Every system is yours to extend.

— REFUSED ENTRIES —the discipline is also what we don't do

N°04Compound

Wezby is a grow system.

What you saw on the bench is the means — this is the end. Each capability translates to a specific business outcome. Compound them and you get the practice we are actually selling: a foundation that grows the business while you focus on the brand.

01Sample data becomes ad data becomes revenue.

02Automation absorbs the work that would have hired three more people.

03Reports answer themselves; you focus on growth.

N°01SAMPLE LOOP

From $4.99 to retargeted revenue.

Every sample becomes a tracked touchpoint. The same data feeds your ad sets — you retarget the people who literally held the material. Sample cost stops being a marketing line item and starts being the cheapest customer acquisition channel you run.

N°02OPERATIONAL LEVER

One operator, full warehouse.

Category management, order routing, tag transitions, refund branches — all automated, all error-free. You do not hire data clerks. The team stays small while the catalogue scales. Cost per order falls; attention turns toward growth.

N°03AUTOMATION BRAIN

A brain in the pipes.

n8n wires Claude, GPT, Gemini, Deepseek into the workflow — blog drafts, product descriptions, SEO meta, customer replies. Not generic AI output; your voice, your brief, your guardrails. Content stops being a sprint and starts being a system.

N°04NATIVE COMMERCE

Past the theme's limits.

Hydrogen is a real React surface. The flows the theme cannot hold — slab gallery, pattern visualiser, project rooms, trade portal — get built natively. Third-party services plug in cleanly. You stop apologising for what Liquid will not do.

N°05SYSTEMS OF RECORD

Stock, customer, order — one place.

Inventory syncs from your ERP. Local pickup respects per-warehouse stock. CRM updates back from order events. The spreadsheet middleman goes away. Customer service stops checking three places to answer one question.

N°06CONVERSATIONAL DATA

Ask the store anything.

Shopify MCP wires the store to Claude. "What was the trade margin in March?" is one sentence away from an answer with the source query attached. Tax, profit, attribution — still scheduled. Everything else: a conversation.

This is what we mean by grow system.

Build the foundation right.
The growth follows.

Six chapters of work. One promise — that when the engagement closes, the business is grown onto a system, not into a dependency.

N°05Handover

Not the code.
A practice, in a box.

When the engagement ends, this is what ships. Not just source — the know-how, documented and indexed, so the team you have today can run the system and the team you have in two years can extend it.

WEZBYEngagement Handover · Manifest

N° 08 / 08FINAL · SEALED

FROMWezby · workbencha small practice

TOYour operations teamadmin + builders

DATEDLaunch + 0non-negotiable

CARGO8 ITEMS

01SOURCE
The monorepoHydrogen storefront, custom apps, scripts. README that runs.
git · primary branch · tagged
02FLOWS
Automation graphsShopify Flow exports, n8n workflows, all triggers documented.
json · yaml · runbook
03DOCS
Architecture & decisionsSystem diagrams, ADR log, the why behind every choice.
markdown · indexed
04INTEGRATIONS
Keys & endpointsAPI credentials in your vault, endpoint map, failure-mode notes.
encrypted · rotated
05APPS
Embedded Shopify appsRemix + TS source, build instructions, deployment recipe.
shopify · cli ready
06DESIGN
Figma & tokensComponent library, brand tokens, generated CSS variables.
figma · published
07TRAINING
Two-week handoverAsync docs + four live sessions with whoever runs the system.
loom · zoom · written
08ESCROW
30-day on-callDirect line to the build team for 30 days after launch.
shared channel · sla 24h

From day one after launch, you can run, extend, replace, or hire someone else to extend the system without us in the loop. The practice is not a dependency. The manifest proves it.

N°06Next step

If the practice fits the work,
the brief is the next step.

wezby/brief — interactive sessionLIVE

QUEUE02 slots · 2026 Q2

DISCOVERY1–2 wk · paid

REPLYat the earliest

PRACTICEEST · 2024

Six chapters, one workbench. If the engagement is right for both sides, we will know by the end of discovery.