Websites
From constraint to handover
-
Challenge
A regional distributor was forwarding a PDF catalogue. The public site did not explain who the product was for, or how to ask for a price.
-
Approach · 01
The public site existed and still failed the only test that mattered: a salesperson would not forward it. The product lines lived in a PDF. The homepage talked about the company. A buyer who arrived could not see who a line was for, or how to ask for a price without starting an email from scratch.
-
Approach · 02
The block was a business website, not a rebrand. The page map put a line, the buyer, and the enquiry on a short path. Price lists were allowed to change, so website care was named as a separate month rather than buried in the build. The team could stop after the site.
-
Approach · 03
What stayed manual was the price itself. The site explains the line and collects the request. It does not invent a trade price in public. That refusal is part of the result, not a missing feature.
-
Result
A business website with a short path from product line to enquiry, plus website care so price lists do not live in someone's inbox.
If your job rhymes with this one
-
Start with the lines
List what a salesperson is actually asked, and make those the pages.
-
Keep the PDF as an attachment
The page should not depend on someone downloading a file to understand the offer.
-
Separate care
If prices move every month, say so. Care is a month at the hourly rate times 30, not a silent retainer.
A composite is useful when it shows the boundary. It is not a logo and it is not a promise that your version will match.