Skip to content
DS Program

Website and web experience development

I start from the question people have in mind when they arrive, and build the pages around it. Speed, copy and structure come next. But they do come.

Tell me about your projectSee the projects

What it looks like

It usually starts like this

  • The website exists, but it brings in no inquiries
  • The information people need is buried in a price list PDF
  • On a phone, it’s slow or hard to read
  • The website talks about the company instead of answering searchers

A website that lists what a company does and a website that answers someone who’s searching only look alike from a distance. The second starts from a real question and carries it all the way to an inquiry; the first just waits.

What I build

  1. Company websites

    The structure follows the questions of the people who arrive, not the org chart of the people publishing. Every page has a stated job and an obvious next step.

  2. Landing pages

    One page, one goal, one action. Built to be measured: you see what works and fix it, instead of debating it.

  3. Web experiences and configurators

    When the product needs to be understood before it’s requested: guided paths, configurations, quotes built together with the reader.

  4. Performance and accessibility

    Fast loading on mobile networks, readable text, keyboard navigation, proper contrast. It’s not an extra: it’s the difference between a website people use and one they abandon.

  5. Technical foundations for search

    Semantic structure, headings, structured data, sitemaps, canonical URLs, social previews. The part you don’t see, but that decides whether a page can be found.

How it works

The system, not just the screen

How a website comes to life

  1. Problem
  2. Design
  3. Development
  4. Launch
  5. Site in use

Real example:Valsusa Serramenti

From the home film to the quote request.

HomeCatalogProjectsPromotionsRequest

  1. The question first, then the pages

    It starts from what visitors are looking for and what they need to be able to do. The structure grows from there: it’s the only way for one more page to mean one more answer, and not just one more item in the menu.

  2. Content is part of the project

    Copy, images and the order of information are decided together with the design, not at the end. A beautiful website filled in later with whatever was on hand is a different website from the one that was approved.

  3. Built for the phone

    Most visits come from there, often on the move and on a slow network. If it works well in those conditions, it works everywhere else.

  4. Inquiries reach the right place

    A form that sends an email to an inbox nobody checks isn’t a contact. The website connects to the place where inquiries actually get handled.

Use cases

  • Rebuilding a website that brings in no inquiries, starting from the questions visitors have
  • Building a landing page for a service or a campaign, measurable from day one
  • Giving a complex product a path that explains it and collects the inquiry
  • Adding the missing piece to an existing website, without rebuilding it from scratch
  • Connecting the website to CRM, automation and notifications, so a contact doesn’t get stuck in an inbox

Technologies

Next.js, React, TypeScript, Tailwind CSS, Vercel, GitHub

The tools I use most often on this kind of project. They aren’t affiliations: they’re choices I revisit when a project calls for something else.

The proof

Projects where I’ve done it

Questions

Do you also handle the content and images?
I work on structure and copy together: I know what a page needs to say and in what order, but the real information about the business is yours. Where materials are needed that don’t exist yet (photos, data sheets, documents), I decide with you how to get them before starting.
Can I update the website myself?
It depends on what needs to change and how often. If content changes constantly, I build an area to manage it; if it changes twice a year, a management area is a cost that never pays for itself, and work on request makes more sense. I decide with you, based on how often it really changes.
Do you also take care of Google rankings?
I build the technical foundations and the structure so pages can be found: content organized by search intent, structured data, speed, canonical URLs, sitemaps. I don’t promise rankings: nobody can guarantee them, and anyone who does is selling something else.

If yours isn’t here, see all the others.

Tell me about your case.

I’ll reply with what I’d build and how.

Tell me about your project