Skip to content
Start a Project
All Work
Client Engagement

A real engagement, documented by the team that engineered it. The client is not named, and nothing identifying or confidential appears.

Winning the procurement desk before the first call

An authority website for a commodity logistics operator mid-expansion, built to the standard freight procurement teams apply before they request a meeting. Engineered so the growth story rides on verifiable structure, an invented fact has no way to ship, and a serious buyer has one clear path from research to a conversation.

Commodity logistics·May 2026·5 min read

At a glance

  • Where they stood: a Pacific Gateway trucking, transload, and warehousing operator that had outgrown its website while expanding into rail and new commodity types.
  • What that was risking: a procurement team sizes up a freight partner by their website first, and a thin, dated site puts real bids at risk before a phone call ever happens.
  • What got built: a full company website that proves the operator's scale and progress with facts a buyer can check, and turns that check into a meeting request.
  • The standard held: every claim on the site is something a buyer can check, and a missing fact says so plainly instead of hiding the gap.
  • Built to grow with them: new yard capacity, commodity lines, and named customers all have a place to go later without rebuilding the site.

A procurement manager sizing up a new freight partner pulls up the website first. A site that reads thin, or one that reads too polished to be true, can cost the meeting before anyone dials a number. This client was becoming a much bigger company, and the website hadn't caught up to prove it.

Context

This operator runs its own trucking fleet, transload yards, and warehousing on Canada's Pacific Gateway, moving export commodities into ocean containers bound overseas. It's established in one line of business and now mid-expansion, with rail infrastructure in development, more yard capacity coming online, and new commodity types on the way.

The website hadn't kept pace. For a company whose contracts are won on trust and scale, an outdated site is the first impression a procurement desk uses to decide whether it's worth a call. The job was a site built for that next chapter: services, industries served, facilities, and a clear way for a serious buyer to get in touch.

The Constraint

The tricky part of this brief was showing where the company is headed without sounding like it's bluffing. It meant telling the story of a company still becoming what it's going to be, without writing a line a sharp buyer could catch as exaggeration.

The client couldn't name a single customer at launch, and their old site's anonymous "customers love us" quotes had cost trust rather than earned it. Much of the growth story was still happening on the company's own schedule, not the website's. And this buyer punishes hype: language that sells fine on a retail page reads as a warning sign on a freight contract.

The System Engineered

Every sentence had to hold to one test. Plain, direct writing, numbers instead of adjectives, and a standing rule that if a paragraph couldn't survive being read aloud to a skeptical buyer, it got rewritten. The page follows the same bar: it holds still instead of rotating through a carousel, because this buyer researches from a desk instead of being sold to.

With named customers off the table, credibility had to come from standing a buyer can check instead: approved tenant status with the federal port authority, the operating record, physical capacity, capital investment underway, and certifications on file. A procurement team can verify every one of those independently. The one customer voice on the site is real, live Google reviews at the operator's actual rating, and it's built not to appear until that data actually exists.

The rule with the longest reach: nothing on the site ever gets invented. Where a real fact was missing, such as a date, a number, or a contact detail, the page shows an obvious "to be added" marker instead of a guess dressed up to look finished. A visible gap is easy to fill in later. A fact that looks true but turns out not to be is much harder to undo.

The look and feel stays just as restrained. It's a dark, industrial palette with a single bright accent used sparingly, more like a highlighter than a paint color, with one deliberate moment of motion that respects visitors who've told their device to keep still. The meeting-request form runs on infrastructure the client controls, so leads never sit inside a third party's system.

More procurement teams now ask an AI assistant to summarize a company before they ever visit its site, so the pages had to answer clearly when asked that way, with plain summaries and direct answers built into the content itself.

What Changed

The finished site has four service pages, four industry pages, facility pages, the public projects-underway page, six in-depth articles, and one clear way to book a meeting: roughly thirty pages in total, sized to match the company it now represents. The industry pages are honest about which markets it fully serves today versus which ones it's still adding, so the growth reads as tracked progress rather than one big claim nobody can check.

Every fact on the site traces back to something real, or to an honest "not yet" marker. The site earns trust through standing a buyer can check, like being an approved tenant of the federal port authority, without a single named customer anywhere on it.

And it keeps working as the company keeps growing. A finished project updates the tracker instead of rewriting the story. A commodity line going live flips its page from "in progress" to "in service." Whenever the client is ready to name real customers, there's already a place built for them: a site engineered to be grown into, which was the actual ask.

If you're buying a build like this

  • Demand a no-guessing rule: a fact that isn't known yet should say so plainly, never get papered over with a sentence that sounds true.
  • Buy proof you can check: growth claims should show up as things a buyer can verify, like a project underway or a certification on file.
  • Ask where your facts actually live: every claim on your site should be easy to find, easy to check, and impossible to quietly get wrong without someone noticing.

Details that would identify the client have been withheld; everything described above is observable in the finished site.

BUILD YOURS

You've seen how we build.Now point it at your business.

Submit a project request. We'll bring the same engineering discipline to your highest-leverage system, and document it the same way.

Start a Project