› ECOMMERCE & RETAIL
Commerce that actually ships. Storefront, catalog, fulfillment — one engineering team.
We embed senior engineers inside DTC brands, scaleups and marketplace operators. Spree, Shopify and BigCommerce extensions. Custom catalog and ops platforms. The boring integrations (Stripe, ERP, OMS, tax, shipping) that mean you don't end up with three vendors fighting over a missed sync. Built to ship in weeks, scaled when growth requires it.
Two shapes of commerce team we tend to be a good fit for.
Commerce isn't one audience. The way we engage with a DTC founder shipping subscription depth on top of Shopify looks different to a marketplace operator running thousands of SKUs through Prime Day — but the operating model is the same: senior engineers, embedded, owning outcomes.
Founders shipping a brand, or scaling one past 0→1.
You have a catalog, customers, a tight roadmap. What you need isn't a Shopify partner adding plugins — it's an engineering team that can take the bits Shopify can't do (custom checkout, configurator, headless storefront, ERP / OMS sync, subscription depth) and ship them so you can focus on the brand.
TYPICAL: 2–8 MONTH ENGAGEMENTS · WEEKS TO LAUNCH · OWNED HANDOFFMarketplaces and brand operators with thousands of SKUs.
You're past PMF — supplier sprawl, dropship sync, multi-tenant catalog, peak-traffic events that punish anything weak in the stack. We've built the catalog ops, real-time data pipelines and integrations that survived Prime Day at $1B operating volume.
TYPICAL: 6–24 MONTH ENGAGEMENTS · EMBEDDED · ROADMAP-DRIVENThree product shapes we keep coming back to.
Most of our commerce engagements land in one of three categories — but the interesting work usually crosses two or three of them at once. A storefront that pipes into a custom catalog ops platform that pipes into the boring integrations behind it.
Storefronts that don't need replatforming every two years.
Spree custom builds, Shopify and BigCommerce extensions, headless setups, multi-currency commerce, virtual try-on and configurators where the brand needs them. Built to be owned by your team after — not rented.
EXAMPLES: Spree · Shopify · Headless · ConfiguratorsCatalog, data and ops platforms.
PIM at scale, supplier and dropship sync, real-time pricing, inventory forecasting, anomaly detection. The work that goes when the storefront is the easy part — and where most marketplace operators quietly lose their margin.
EXAMPLES: PIM · Dropship sync · Inventory forecastingThe boring integrations.
Stripe, ERP, OMS, tax (Avalara, TaxJar), 3PL, shipping (ShipStation, EasyPost), subscription billing. Not glamorous, but where most commerce platforms quietly fall apart on month three.
EXAMPLES: Stripe · ERP · OMS · 3PL · TaxThe day-2 problems we tend to land on.
Every commerce platform looks fine until growth, peaks, or an audit show up. These are the problem shapes we've ended up owning — across DTC subscription brands, retail platforms and a $1B marketplace operator.
Black Friday, Prime Day, drops.
Built to absorb the spike — caching, queueing, graceful degradation. Shipped through five Prime Days at $1B operating volume on a marketplace ops platform that didn't blink.
New stack, same site live.
Wordpress → Rails, Magento → Shopify, Salesforce → headless. We migrate piece-by-piece without a big-bang launch. The newsletter goes out on Tuesday, regardless.
When 500 SKUs become 50,000.
PIM discipline, supplier sync, deduplication, data quality pipelines. The work that scales linearly with growth — built so your data team isn't cleaning spreadsheets at 11pm.
Tokenised, scope-tiny, boring.
Stripe-first. Card data stays out of your infra. PCI scope as small as it can be — your auditor's checklist runs short. GDPR, CCPA and CPRA flows where they apply.
We're not a procurement layer. We don't sit between you and Stripe, between you and Shopify, between you and your data warehouse. We integrate, we extend, we hand back when you want it back.
The stack we ship every week. Boring tech, picked on purpose.
Commerce stacks that compound. Rails for the depth Shopify can't reach. Next.js for the customer-facing portal. Stripe for the payments. Snowflake or Postgres for the data side. Whatever your team already runs — we extend it, we don't replace it.
Ruby on RailsBackend · subscriptions
ShopifyCommerce · extended
Next.jsCustomer portal
StripePayments · scope-tiny
PythonData · ETL
SnowflakeWarehouse
ElasticsearchSearch · PIM
AWSInfraHow a commerce engagement runs — from first call to shipped.
The exact shape varies with the catalog, the channel and the constraint. The four steps are consistent in every commerce engagement we run.
Read the operation.
We sit with your ops, your support inbox, your Shopify admin. The friction usually shows up there before it shows up on the engineering roadmap. Two weeks of looking, mapping the workflow, the integrations, the peak-traffic shape. No build until this is on paper.
WEEK 1–2Design with your operation, not at it.
UX work runs alongside discovery — wireframes and clickable prototypes validated with the people who actually run the catalog and answer the support tickets. We design for the SKUs you have, not the ones a template assumes.
WEEK 2–6Build inside your stack.
We don't replatform you. We integrate, extend, replace pieces in flight. Shopify-extended Rails services, headless storefronts, custom catalog ops — whatever fits the constraint. Code your next hires can own.
WEEK 6–[X]Ship to real customers. Hand over when ready.
Phased rollout, regression suite your team can run, runbooks. We stay on a defined cadence after launch — or hand over to your engineers, with everything they need. Long engagement is by mutual choice, not lock-in.
ONGOINGBuilding or scaling a commerce platform?
Tell us where the catalog or the checkout is fighting back, where the back-office is breaking, where Shopify can't quite reach. Thirty minutes is usually enough for both sides to know whether this is a good fit — and if it isn't, we'll point you at someone who is.