Digital calipers and a micrometer resting on a machined aluminium part on a steel bench.
Specification-driven products need specification-driven systems.

What we do, specifically

Not a service list. These are the problems we get called about.

01

Ecommerce for configured products

Products priced by configuration rather than SKU, tiered for distributors, contractors and reps. And freight that cannot be quoted at checkout until somebody builds the thing that quotes it.

  • Craft Commerce builds, headless or conventional
  • Rep and distributor pricing tiers, per customer
  • Quote-to-order workflows for configured products
  • Payment-hold and deferred freight billing
  • Freight quoted at checkout rather than over the phone
See it in the work →
02

ERP and system integration

The website should write into the system your team already uses, not sit beside it. Most of the difficulty is in the systems that were never built to be talked to.

  • 10X ERP, Order Time and QuickBooks
  • Custom pricing APIs for systems that expose none
  • Custom REST and webhook integrations
  • Orders written into fulfilment without manual re-entry
  • Sync that fails loudly rather than drifting quietly
See it in the work →
03

Product data and catalogue architecture

Usually the real project, and almost always underestimated. We have turned a catalogue that existed only as a 1990s print layout into a working data model.

  • Attribute and variant modelling
  • Normalising specs and units across decades of entries
  • Migrating print and spreadsheet catalogues into structured data
  • PIM integration, or the data model that means you do not need one yet
  • Submittal and spec sheet delivery
See it in the work →
04

Agentic video and product media

Explainer and installation video built from your specifications, so what the video shows is what the drawing says. Conventional production cannot cover a catalogue. A pipeline can.

  • Explainer and installation reels built from product data
  • Narration synthesised, captions aligned to the audio word by word
  • Brand treatment and music applied per client
  • A new video reuses the pipeline instead of restarting production
  • 3D product renders where submittal drawings are the only reference
See it in the work →
05

Assistants that answer from your catalogue

A model that invents a specification for a regulated product is a liability. Ours answer from your product data, cite the document, and escalate rather than guess.

  • Answers drawn from your product data, not the open internet
  • Specification and compatibility questions handled without a rep
  • Traceable back to the document the answer came from
  • Says it does not know instead of inventing a number
  • Deployed on the site, or wherever your customers already are
See it in the work →
06

Reporting across systems that do not talk

Most manufacturers can report on the storefront or the ERP, never both side by side. That gap is access and system knowledge, not tooling.

  • A reporting database you own, fed from the storefront and the ERP
  • Cost brought across from the ERP, so margin is reportable
  • Read-only against production, so reporting cannot slow the system taking orders
  • Reports organised by the business question, not the chart type
  • Scheduled and self-serve reporting for non-technical teams
See it in the work →
07

Finance that reports while the numbers still mean something

Most of bookkeeping is rule-shaped: classify, match, reconcile, chase. None of it needs judgment, and all of it is why the books close six weeks late.

  • Transaction capture, classification and reconciliation without manual entry
  • Books that close continuously instead of in a month-end scramble
  • Cash position, margin and runway on a dashboard that gets opened
  • Alerts when a number moves, rather than a monthly report nobody reads
  • Proved against our own books before it goes anywhere near yours
08

Whole-operation automation, not one system at a time

Departments buy software one problem at a time and the seams become somebody’s full-time job. Vendors in a spreadsheet, partners in a portal, samples in an inbox.

  • EDI where partners require it, and a sane path where they do not
  • Purchase orders tracked from raise to reconciliation
  • Sample requests and lab submissions as records, not email threads
  • Formulation and specification history tied to the product
  • One spine across departments, not one system each
09

Compliance and tax

The obligations that arrive with regulated products and multi-state selling — the ones a normal checkout ignores entirely, until somebody asks to see the record.

  • Hazmat acknowledgement captured in-cart, only where required
  • Arbitration acknowledgement recorded at the point of order
  • Sales tax nexus mapped state by state
  • TaxJar and Avalara integration
  • PCI scope and payment gateway configuration
See it in the work →

Not sure which of these you need?

Describe the process that’s costing you time. We’ll tell you what it actually is.

Start a project