Discovery & PDP.
3 systemsWhere intent is formed. Samples, patterns, and provenance — the moments before the cart exists.
[SYS] Standing library
Eleven working systems we keep on the rack — built once, named, kept ready. Each came out of a real engagement; each can be lifted off the shelf and shaped to your case. We do not write case studies. We file the systems.
Where intent is formed. Samples, patterns, and provenance — the moments before the cart exists.
Where the math gets real. Square feet, waste factor, pallet count, carrier bracket — all reactive as the cart grows.
Where the buyer changes shape. Contractors, designers, architects — different pricing, different rules, different rooms.
Where the stock actually lives. Slab-level identity, ERP and sheet bridges, no double-listing.
Where the lead time bites. Eight-to-fourteen weeks of visibility, from quarry block to door delivery.
[N°03] Common questions · systems library
What counts as a system, why they are not for sale as standalone apps, and how the same problem becomes a slightly different build for each brand.
A surface or workflow purpose-built against a specific operational reality of material commerce — sample-with-postage, slab-as-product, freight-as-conversion-driver, custom production tracking. Each system was built once for a real engagement, named, refined, and kept on the shelf. Eleven sit here now.
No. Every system is built against the specific data shape of the brand it runs for — the metafields, the catalogue architecture, the integrations it touches. Lifting one out as a standalone app would erase the part that makes it work. The library exists as a record of what has been built; we rebuild each system into the shape of the next engagement.
No. They are custom builds — some as Hydrogen islands on the storefront layer, some as embedded Shopify apps in Remix + TypeScript, some as n8n workflows, some as Shopify Flow exports. They live inside the brand's own Shopify account and storefront, not as third-party rentals.
We build the system that fits your data shape and operations — and that often resembles one of these. The Sample System looks similar across builds because the underlying problem looks similar; the FTL Simulator differs sharply because freight logic is highly brand-specific. The library is a starting bench, not a copy-paste menu.
Most can attach to a Shopify theme via the Storefront API or App Bridge — but the surfaces that depend on real-time data (FTL Simulator, Slab Gallery, Pattern Visualizer) ship cleaner on Hydrogen. We will tell you which is which in the discovery brief, not retroactively.
What this isn't
Every engagement begins with a paid discovery. We map your case against the rack, decide what fits, build what is missing.
Open the brief