What we’ve actually shipped
Each of these solved a specific operational problem, not a redesign. Where a system is named, we integrated with it directly.
Most started as one defined project and became a standing relationship. Several have been running for years, which is the part a case study is worst at showing.
Manufacturers, distributors and fabricators selling through architects, builders, contractors and reps.
Product data nobody can actually build on
The catalogue of record is a print document, a spreadsheet, and someone’s memory, and the three disagree. Nothing downstream can be better than the data underneath it, so the storefront, the search filters and the ERP all inherit the same mess.
Read the case →Orders nobody can price at checkout
A large share of your volume ships LTL, and nothing can be quoted until someone looks at the pallet. So the order gets taken by phone and typed in again, and the website quietly becomes a brochure.
Read the case →A storefront bolted to the side of a website
The catalogue lives in one system and commerce in another, joined by a sync that drops. Every product change gets made twice, and the two never quite agree about what you sell.
Read the case →The answer exists, in a PDF nobody opens
Everything a buyer needs is already published: datasheets, safety sheets, install guides, videos. None of it reaches the contractor pricing a job at 9pm, so the question becomes an email that waits two days for the one person who knows that product line.
Read the case →The storefront and the ERP have never met
Revenue lives in one system and cost lives in another, and the marketing data lives in a third. Any question that needs two of them at once — which products actually make money, which distributors are drifting away — has no owner and no answer, so it gets estimated in a spreadsheet or quietly stops being asked.
Read the case →A catalogue too big to film
Every product deserves an install video and nobody can afford to shoot three hundred of them. So the two best sellers get one, everything else gets a PDF, and the contractor who needed the other one guesses on site.
Read the case →Pricing locked inside a system nothing can reach
Every product is configured, so nothing carries a fixed price, and the only system that knows the answer has no way to tell anyone outside the building. The catalogue says “call for pricing” because there is no other option.
Read the case →A catalogue only a developer can change
Every product addition, spec correction or price change goes into a queue and waits. The people who know the products are the ones least able to publish anything about them.
Read the case →M&A advisors, trading platforms and capital firms where trust and data accuracy are the product.
Leads that go cold waiting for a callback
An enquiry worth more than a month of marketing spend lands in a shared inbox on a Friday. Somebody sees it Monday. By the time anyone calls, the person has spoken to a competitor or talked themselves out of it entirely.
Read the case →Software that has to run, not just ship
Real-time audio, market data and gated access, live during trading hours. Generating the code is the cheap part; the commitment is that it is still running six years later.
Read the case →Got a process that only works because someone remembers?
That’s the one worth talking about.
Start a project