Agro-industrial · catalogue and engineering
One site for two buyers who have nothing in common
Technical catalogue and service pages for AGROPROIECT, a firm doing consulting, process engineering and equipment distribution for grain storage and processing. Next.js, 31 product pages, downloadable datasheets.
AGROPROIECT does consulting, process engineering and equipment distribution for grain silos, mills, feed mills and breweries. It distributes STIF from France, BORGHI and General Dies from Italy, and designs the plants the machines end up working in.
The structural problem is that two completely different people land on this site. One has a mill standing still and needs, today, an elevator bucket that fits a machine installed eight years ago. The other is planning a feed mill and is at the start of an investment that will take a year and a half. The first wants to reach the part in two clicks. The second wants to see whether the firm knows what it is doing.
A site that tries to please both at once, without choosing, loses both.
What I built
Piece by piece
Catalogue first, engineering right beneath it
At the top of the home page, a search field asking “Which part are you looking for today?” and the 31 products grouped into three categories. Below it, the consulting and engineering section with the three stages of an investment. The person in a hurry doesn't have to wade through a company introduction to reach a part, and the investor finds, immediately underneath, the proof that this firm designs plants rather than just reselling kit.
Every product on its own URL, with a datasheet
31 product pages, each in the sitemap, each with a technical description and a PDF to download. In industrial purchasing the decision is never one person's: whoever is searching has to be able to forward a document inside the company, to someone who has never opened the site.
Entry through the part, not through the company
A dedicated section for the real case: “Got the make and model of the machine? Send them over with a photo of the old part.” The person with the stalled machine doesn't know what the part is called in a catalogue — he knows what it looks like. The form starts from what he has, not from what the site would prefer.
No prices, but the reason is written down
Equipment is sized by capacity, product and site, so a price on the page would be a convenient lie. Instead of silence, the question is asked outright in the FAQ, with the answer and the turnaround: one working day. The difference between hiding a price and explaining why there isn't one.
Two sitemaps, one of them for images
Alongside the ordinary sitemap with its 50 URLs, a separate one listing 54 images across 34 pages, declared in robots.txt. On a machinery catalogue plenty of people look for the picture of the part first and read afterwards. Images declared explicitly are images that can be found.
Measured
The numbers, not the adjectives
Measured directly on the live site, on 28 October 2026. Anyone who opens the developer tools in their browser can check them.
- 37 ms
- TTFB
- 38 KB
- Product page
- 31
- Product pages
- 0
- Images with no alt text
time to first byte
total transferred
each with a datasheet
on the home page and the product pages
Let's start
Got a project in mind?
Tell me what you want to build. I answer personally, usually within 24 hours, with a clear proposal and a plan.