Work

Built for industrial companies

Each record below gives the sector, the scope and the technical problem — the same way we would describe your project to somebody else. Much of this work sits under a confidentiality agreement, so owners are not named unless they have told us we can.

Start your project How we work

Why there are no logos on this page

Some of our work is under NDA. We describe the scope, the market, and the technical challenge without naming the owner or showing an identifiable site. The alternative — publishing a name, a screenshot or a number because it makes the page look fuller — is the one thing that would make everything else here worth less.

If you want to see a specific build, ask on a call. Permission to show it is the owner's to give, and we ask them rather than assume.

Coatings & industrial maintenance

The specialty. Product data, safety data and repair records have to be right on the page, because the people reading them are specifying a system that has to hold.

How we build for coatings & protective services→

A protective-coatings supplier's product and data-sheet library

Every product carries the two documents its buyers actually need: the technical data sheet the specifier reads, and the safety data sheet the customer's EHS team files before anything goes through the gate. The catalogue was built so the sheet on the page is the sheet in the product record — when a revision publishes, the superseded version stops being the one a visitor downloads, and both documents come off the product page instead of out of a support request.

Product catalogue
Technical and safety data sheets, versioned
Distributor and applicator routing
Search by product line and substrate

Design, build, content structure and launch

An industrial maintenance contractor's capability and service-area pages

The work gets bought by plant engineers and reliability managers, usually while a pump, a tank floor or a containment area is already out of service. So the site is organised the way that search actually happens: a page per capability and a page per area worked, each written in the nouns the caller would use. Repair records follow the format the sector already trusts — the asset, the failure mode, the surface preparation, the system applied, and the finished condition.

Capability pages
Service-area pages
Repair records in the sector's own format
Quote requests routed by area

Design, build, content structure and launch

A coatings manufacturer's catalogue, with a dealer tier behind a sign-in

The public catalogue reads as a spec. Behind a sign-in, a dealer sees the pricing tier their account is on, the collateral for their territory, and the order history that answers most of the calls they would otherwise have to make. Product data lives in one record feeding both views, so a price change or a superseded part number is a single edit rather than a spreadsheet sent round.

Public product catalogue
Signed-in dealer portal
Territory collateral
One product record behind both views

Design, build, product data model and launch

Manufacturing & industrial

Sites that get used as a reference document — by an engineer picking a part, long before anyone in sales hears about it.

How we build for manufacturing & industrial→

A manufacturer's catalogue an engineer can spec from

Parts published with the dimensions, materials, finishes and downloadable drawings a specifier needs before they can design you into an assembly. Part numbers resolve as their own addresses, so searching the number lands on the part rather than on a category page, and a superseded number sends the reader to its replacement instead of to a dead end.

Part-level pages
Drawings and spec downloads
Part numbers as their own URLs
Superseded numbers redirected, not dropped

Design, build, catalogue structure and launch

Distribution & wholesale

Storefronts that behave differently depending on which account is signed in, and that hand the order back to the system already running the business.

How we build for distribution & wholesale→

A distributor's storefront that knows which account is signed in

Contract pricing, tier multipliers and the exceptions that override both, applied to the account that is looking rather than to a public price list. A pasted part list becomes a quote in one step, purchase orders check out on terms instead of on a card, and the order writes back to the ERP — the system that already runs inventory, pricing and orders — so the website is not a second set of books.

Account-level contract pricing
Paste-a-part-list quick order
Purchase orders on terms
Write-back to the ERP

Design, build, commerce and integration work

Construction & contracting

Two audiences, one site: the owner drawing up a shortlist, and the tradesperson deciding where to apply next.

How we build for construction & contracting→

A specialty contractor's project record and prequalification packet

Completed jobs published with scope, market, role and finished-condition photography, filterable by trade and project type. Licenses by state, bonding capacity, insurance certificates and safety record kept together on one page, so a prequalification request gets answered with a link and a file rather than a rebuilt packet. Applications from the field are short enough to finish one-handed in a parking lot.

Filterable project record
Prequalification page and packet
Bid requests routed to estimating
Field-length job applications

Design, build, forms and routing, launch

Also built for

Fewer builds, and not what we lead with — but the same method, and the pages describe it honestly.

Tell us the goal. We'll map the route.

Start your project

A few quick questions — about two minutes.