Web Design Agency
Web Design Agency
A company website isn’t born from counting pages.
It’s born from a more concrete question: how many things does it have to hold together. How many markets, how many audiences, how many brands, how many business systems. The answer determines the architecture, the timeline, the complexity. Everything else comes after.
This is the principle every project we follow starts from: not a generic statement, but what emerges when you look at the projects one by one and ask what really shaped them.
By the numbers
-
Markets
5
Language markets on a single project.
-
Click
88k
Clicks generated at €0.10 each.
-
Portfolio
29
Portfolio projects across three business units.
-
Offices
3
In-house offices: Cerea, Milan, Dubai.
The wrong question
“How many pages will the site have?”
It’s the first thing people ask, and also the least useful. Not because the question is stupid, but because the unit of measure doesn’t match the real complexity of the work.
An eight-page site in five languages, tied to a product catalog and a CRM, is structurally bigger than a forty-page monolingual one disconnected from any system. Pages are counted. Architecture is designed.
The four questions that really size a project
-
How many markets does it have to serve?
Languages, localizations, country-specific catalogs: every market adds layers of architecture.
-
How many different audiences?
Consumer and professional on the same domain require separate paths without splitting the site.
-
How many brands have to coexist?
Multiple brand units under a common hub: distinct identities that must stay recognizable and consistent.
-
How many systems does it have to talk to?
CRM, catalog, pixel, tracking: every integration is an architectural decision, not a last-minute add-on.
Four projects
Four different constraints, four different architectures
Four different constraints, four different architectures
-
Alpego
Five markets, one complex catalog
The constraint was five language markets and a technically dense catalog of agricultural machinery. The architecture that came out of it is a site in Italian, English, French, Spanish and German, with navigation built around the catalog’s logic and touchpoints connected to the CRM. Traffic becomes a traceable lead along the funnel.
See the case -
You&Meat
A dual audience on the same domain
The problem was keeping the end consumer and the professional restaurateur together without splitting the site. The solution: four consumer sections (burgers, BBQ, knife-cut tartare, cooking school) plus a separate Restaurateurs area, with the newsletter collecting contacts from both in a single place.
See the case -
Edil Ferri
Three business units, one shared identity
Three entities that each communicated on their own, with no shared recognizable identity. The work produced a single hub that holds together Edil Ferri, Dinamica Progetti and Ferri Contract, with twenty-nine portfolio projects as shared proof and a brand manual that governs how the three identities are applied.
See the case -
Sani.In.Veneto
Landing pages that change at the pace of the campaigns
The constraint was time: pages that have to be rewritten continuously, not delivered once and left untouched. Development and advertising worked on the same cycle, with pixels and events set up on real contact actions. Pages were updated as the data came in, not after the campaign closed.
See the case
The Sani.In.Veneto case
Why development and advertising need to be in the same place
The landing page is part of the campaign. It’s not a separate asset that advertising uses: it is the campaign.
When the two functions sit in different companies, synchronization doesn’t exist. And the cost of that fragmentation is paid by the client, in pricier clicks and conversions that vanish without anyone knowing where.
88,481 clicks to the site in under two years, at an average cost per click of €0.10.
€9,110 total spend across 17 campaigns, 776k people reached. October 2024 – July 2026. Advertising alone doesn’t produce that number.
The method
How an architecture is born
Development, design and SEO join the project from the first sprint, not in sequence. It’s not an organizational detail: it’s what makes it possible to take certain decisions at the right moment instead of correcting them later.
-
Architecture before design
URLs, catalog structure and content hierarchy defined together with the wireframe, not in sequence.
-
Tracking before launch
Pixels and events set up on real contact actions before the campaigns go live.
-
In-house production
Web, design and development in our own offices. Quick decisions, not tickets.
-
Iteration on real data
Pages rewritten as the data comes in: same numbers for whoever writes the campaign and whoever touches the landing page.
FAQ
Frequently asked questions about web design
Start here