What we actually do.
Three service lines, run by the same small team, on the same fixed-fee basis. Most projects use more than one — that's the point.
ERP migrations & implementations.
Odoo deeply, plus the integration depth to bring data over from A2000, Cin7, Finale, and the spreadsheets-pretending-to-be-an-ERP setups. Discovery, data migration, configuration, integrations, UAT, training, cutover, hypercare. The seven phases that decide whether the system actually works on Monday.
How we run an Odoo project →02 · B2B & channel integrationB2B and channel rollouts that connect to your reality.
Elastic, Shopify B2B, marketplaces. Catalog, pricing, orders, customers, ATS — synced from whatever system of record you have, however many you have. We move data on the right cadence, in the right shape, so storefronts actually reflect what you can sell.
How we run B2B integrations →03 · Custom integrations & dataThe plumbing nobody else wants to touch.
EDI (SPS Commerce 850 / 810 / 856), Shopify pipelines, channel sync, shipping and payment integrations, Azure Data Factory and AWS Lambda glue, and the reporting layer that ties it all together. The custom work that turns a stack of systems into a single operation.
Talk to us about a project →The lines blur, on purpose.
Real projects don't separate ERP from integrations from the people running them. Don't worry about which bucket your project goes in — that's our job. A few examples of how engagements typically combine:
A typical apparel migration touches all three: ERP migration as the spine, EDI and Shopify integrations to keep channels live, and an Elastic rollout for the wholesale side.
A B2B-only engagement might mean Elastic plus light Custom Integrations work — connecting the storefront to an ERP that's staying put. No migration involved.
Sometimes it's just one Lambda, one EDI mapping, or one Shopify pipeline. No ERP, no B2B platform — just the integration that's been on the “someday” list for a year.
Five commitments, regardless of which line you're buying.
Fixed-fee SOWs
Every engagement is fixed scope, fixed price, defined deliverables — no hourly billing, no open-ended retainers.
Weekly demos
Every week of every project includes a working demo. No surprises at go-live, no theater on status calls.
One owner
Will is the named single point of contact on every engagement. The person you talk to is the person doing the work.
Defined go-live
Every SOW has a target go-live date and the phasing required to hit it. Sliding dates is a decision, not a default.
Four-week hypercare
Every project includes four weeks of hands-on support after cutover. We stay until the system is genuinely running on its own.