Freight & Logistics · Case study
Kattz LogisticsMaking an unfamiliar shipping problem easy to explain — before anyone has to know the vocabulary.
- Client
- Kattz Logistics
- Industry
- Freight & Logistics
- Market
- Nanaimo, British Columbia
- Launched
- 2026
- Published
- Live site
- kattzlogistics.com
Overview
Kattz Logistics is a freight and logistics company based in Nanaimo on Vancouver Island, coordinating port and container drayage, rail-ramp pickups, commercial-barge freight to the Island, and deliveries across Canada and into the United States. Local Cochrane Web Design built kattzlogistics.com so that a shipper who does not speak logistics can still describe what they need to move and get a useful reply.
Freight websites usually assume the customer already knows the equipment, the terminal and the paperwork. Most do not — and the Island adds a layer almost nobody outside the trade understands: a commercial barge sailing, a terminal with a dwell clock, and a tractor that has to be waiting on the other side. The build answers that in two ways. It explains the whole journey in plain language, page by page, with sources. And it replaces the usual quote form with a four-step rate request that asks questions in the order a dispatcher would, offers a tile for every common need including 'not sure', and lets the visitor add a photo instead of a description. Where a fact was not yet confirmed by the owner — hours, a street address, fleet size, a response-time promise — the site leaves the space empty rather than guessing.
The live site
Built to be judged in the only place that counts.
Captured from the live site — different pages, real pixels, no mockups.
The client
Kattz works the part of Canadian freight that is hardest to explain: the mainland-to-Island crossing. The site states its position plainly — forty-five years in logistics, customers of seventeen years and more, and a company that is 'built for flexibility' where the big networks are built for standardisation.
Its customers are a mix of freight forwarders and carriers who know the trade, and businesses and individuals who do not — a retailer waiting on a container, a buyer with a sailboat arriving from overseas, a contractor with a job-site delivery. The same site has to serve both without talking down to either.
The challenge
The first problem was comprehension. A rate request is only useful if the customer can describe the shipment, and most first-time shippers cannot: they do not know whether their load needs a container chassis or a flatbed, which terminal it will land at, or that a trailer can cross to the Island without its tractor. A standard form with the trade's own field labels simply stalls.
The second was credibility without the usual props. The company publishes no fleet count, no on-time percentage, no street address and no office hours, because those facts were still being confirmed at build time. The site had to feel established and specific without inventing any of them.
Strategic objectives
What the build had to accomplish.
Let a visitor with no logistics vocabulary start a rate request by choosing what their situation looks like, not by naming equipment.
Explain how freight actually reaches Vancouver Island — barge lanes, terminals, what Kattz does and does not use — clearly enough to be cited, with sources.
Make 'Get a Rate' reachable from every page, with the request carrying the context of the page it was opened from.
Publish only what the owner has confirmed, and leave the unconfirmed facts visibly blank rather than filling them with plausible copy.
Serve every page as complete HTML so the explanations are readable by search engines and AI assistants without running the application.
The insights that shaped the work
The customer's job is to describe a problem, not to classify it. The form should carry the classification; the person should only have to say what is sitting where.
On the Island, the honest explanation is the differentiator. Competitors do not explain the crossing because it exposes the coordination — Kattz explains it because that coordination is the product.
A withheld fact reads as discipline. An invented one, once noticed, undoes every other claim on the site.
Chapter
A rate request in the order a dispatcher would ask
Insight
A quote form that opens with 'equipment type' or 'container size' asks the customer to answer a question they came to the site to ask. The drop-off is immediate and invisible.
Decision
The site's primary action, Get a Rate, is a four-step flow that the page itself describes as 'Four short steps, in the order a dispatcher would ask them.' Step one asks only 'What do you need moved?' and answers with seven photographed tiles in the customer's language — 'A container at the port', 'Freight to, from or around the Island', 'Have the trailer? Need the tractor?', 'A few skids or boxes from a destuff facility', 'Oversized, unusual or complicated' — plus a seventh that reads 'Not sure? Just tell us what you're moving. We'll work out the rest.' The next questions follow the same rule: 'Where is it now?' accepts a port, a rail ramp or an address and offers a 'Not sure yet' button; 'When does it need to move?' is five plain choices from 'As soon as possible' to 'Not sure yet'; and the customer can attach photos or a video, or take a photo on the spot, instead of describing a load they do not have the words for. The last step asks how Kattz should reach them — email or a call — and the page states what happens next without promising a turnaround: 'We'll review what you've sent and follow up. No commitment.'
Effect
A first-time shipper can finish the request with nothing but a description and a photo, and the company receives a lead that is already sorted by need, origin, timing and urgency. The form carries the trade's vocabulary so the customer never has to.
Chapter
Explaining the crossing instead of hiding it
Insight
Most mainland carriers treat the Island as a line item. The customer only learns how complicated it is when something is late, which is also when they learn the carrier never understood it either.
Decision
The Vancouver Island page is written as an explainer, not a sales page: 'How does freight get to Vancouver Island?' is answered in full. Freight crosses on a freight-only commercial barge from Tilbury in Delta or the Fraser at Surrey to Duke Point in Nanaimo or Swartz Bay in North Saanich; the trailer crosses on its own and a Kattz tractor meets it on the Island side. The page is explicit about what the company does not do — 'Kattz does not use BC Ferries' drop-trailer service' — and about the facts a customer might assume: there is no freight rail on the Island, and the DP World container terminal at Duke Point is not operating at present. Sailing frequencies are cited to a provincial freight study and the barge operator's own terminal pages, listed under a Sources heading, with the data date printed on the page. Eight questions a shipper would actually ask follow, each answered directly.
Effect
The company's expertise becomes checkable rather than asserted. A buyer comparing carriers can read exactly how the move will happen before the first phone call, and a search engine or AI assistant asked how freight reaches Vancouver Island has a sourced, dated answer to quote.
Chapter
One request, reachable from every page
Insight
The moment a visitor understands what Kattz does is rarely on the Get a Rate page. It is halfway down a service page, or at the end of the Island explainer.
Decision
The same four-step request opens as a slide-in panel from any Get a Rate button on the site, so the visitor never leaves the page that convinced them. The panel remembers its state if they close it to check something, and links can open it pre-filled — a service page's button starts on that service, and the navigation's 'Not sure what you need?' link opens it on the 'unsure' tile. A phone number sits beside the Continue button on every step for the customer who would rather talk.
Effect
The distance between understanding and asking is one tap, wherever the understanding happened. The request arrives already knowing which page the customer came from, which is the first thing a dispatcher would have asked.
Chapter
The facts that were left blank on purpose
Insight
Fleet size, on-time rate, office hours, a street address and a response commitment are the stock reassurances of a logistics website. Kattz had not confirmed any of them when the site was built.
Decision
The site omits them. Its content layer carries each as a claim with a status of withheld and no value, and the pages simply show nothing in that place rather than a rounded guess — the studio's working rule being that until the owner fills a fact in, the site shows nothing there. The About page leads instead with what is true: forty-five years in logistics, its own tractors and drivers on the Island, an active commercial-barge account, and a view of cost the page states as 'We care about the money in your pocket.' Proof comes from customers rather than numbers — testimonials the owner cleared for publication with names and company logos, and a single case study about a sailboat that arrived inches too tall for the route and was moved by lowering it on its own tires.
Effect
Nothing on the site can be caught out later. The reassurance comes from specifics a competitor could not fake — named customers, a real problem solved, an explained process — and the empty slots are ready to be filled the day the owner confirms them.
Recognize your own business in this problem? The same system builds yours.
The mobile experience
Freight questions get asked from a yard, a loading dock or the cab of a truck, usually on a phone, often with the load in view. The rate request is composed for exactly that: the seven need tiles stack as a single thumb-scrollable column with their photographs intact, 'Take a photo' uses the phone's camera directly, and the Continue button and the phone number stay fixed at the bottom of the screen through every step. The long Island explainer reads as a single column with its sources at the end, and the desktop's animated freight-journey experience is never sent to a phone — the mobile build is the plain, fast version by design.
Colour & type
The palette below is sampled from the live Kattz Logistics site — the exact tones the brand is built on.
#0A0D12
#141D28
#313C4E
#536270
#5FA8E0
#ADB5BC
Search & discoverability
The discovery layer is built so the explanations can be found and quoted. Every route is prerendered to complete HTML at build time, with the critical styles inlined and a check that the served page matches what the application renders, so the Island explainer, the service pages, the fifteen frequently asked questions and the rate form's first step are all present in the raw response. Each page carries its own title, description, canonical and Open Graph image, and a connected JSON-LD graph: a LocalBusiness with the Nanaimo address region and seven listed services, FAQPage markup wherever questions appear, Article markup on the explainer, and breadcrumbs throughout. A sitemap, robots file and llms.txt are generated from the same route registry the pages are built from. No ranking or traffic is claimed anywhere; the structure that earns a citation is simply in place.
Technology & ownership
The site is the company's own asset: a fast static build on its own domain, with a rate request and a contact form that deliver to the business through a private backend, and photo and video attachments stored privately rather than emailed. Forty of the owner's own photographs were re-encoded into 376 responsive renditions so the pages open quickly on a phone over mobile data, each caption stamped with the date and time it was taken. On desktop-class devices, and only after the page is interactive, a scroll-driven 3D freight journey loads as an optional layer; everything a customer needs works without it.
Immediate outcomes at launch
A visitor who cannot name their equipment can still complete a rate request, choosing from seven photographed situations — or 'not sure' — and attaching a photo in place of a description.
The mainland-to-Island crossing is explained end to end, with sources and a data date, including what Kattz does not use and which terminal is not operating.
Get a Rate opens as the same four-step panel from every page, pre-filled with the context of the page it was opened from.
Hours, address, fleet size, on-time rate and response time are withheld rather than invented; the site shows nothing in those places until the owner confirms them.
Every page is served as complete HTML with per-page structured data, so the explanations are readable by crawlers and AI assistants without running the application.
The site credits its builder in the footer — 'Website by LocalCochraneWebDesign.com, a VeePo company' — the attribution this study rests on.
Common questions
What owners ask before commissioning a build like this one.
How does a freight website help visitors explain an unfamiliar shipping requirement?
By asking in their words, not the trade's. Kattz Logistics' rate request opens with 'What do you need moved?' and seven photographed situations — a container at the port, freight to the Island, a trailer that needs a tractor — plus a 'not sure' option, then lets the customer attach a photo instead of describing the load.
Should a logistics company publish its fleet size, on-time rate and response time on its website?
Only if they are confirmed. Kattz Logistics' site carries each of those as a withheld claim with no value, so the pages show nothing in that place rather than a rounded guess. Credibility comes instead from named customer testimonials, company logos, and a case study about a specific problem solved.
How should a website explain freight to Vancouver Island?
Literally and with sources. The Kattz site states that commercial freight crosses on a freight-only barge from Tilbury or Surrey to Duke Point or Swartz Bay, that the trailer crosses without its tractor and a Kattz tractor meets it, that the company does not use BC Ferries' drop-trailer service, and that there is no freight rail on the Island — with the provincial study and terminal pages it relied on listed below.
What should a rate-request form ask, and in what order?
What a dispatcher would ask, in the order they would ask it: what is moving, where it is now, where it needs to go, when, anything unusual, then how to reach you. Kattz's form takes four short steps, accepts 'not sure yet' at the points a first-time shipper gets stuck, and states what happens next without promising a turnaround it has not confirmed.
What results does this case study claim?
None that were not observed. No enquiry counts, rankings or revenue figures appear here, because none have been measured and confirmed for this project. What is documented is the build itself — the rate request, the Island explainer, the withheld facts and the discovery layer — verified against the live site and the studio's repository on 21 October 2026.
Where it stands
Kattz Logistics sells the ability to work around a problem the customer does not fully understand. Its website does the same thing in miniature: it lets a stranger explain a shipment in their own words, shows them how the move will actually happen, and refuses to promise anything the company has not yet confirmed. The next customer arrives already knowing what they need — which is the only kind of lead a dispatcher wants.
- Web Design
- Rate-Request Flow
- Content Architecture
- AI Search Optimization
More case studies
The same system, a different market.
Your project
Your business may have outgrown its website.
Kattz Logistics needed more than a redesign — it needed its real-world strengths made visible online. If that sounds familiar, tell us about your business. A written, itemised proposal comes back within one business day.
Free · No obligation · Written quote within 24 hours
Building Websites That Work as Hard as You Do