Trust before the ask
- Show how the report is made before asking for anything
- Four steps, in order: identification, classification, desk analysis, on-field analysis
One page. Three ways in.
The Italian Tech Landscape is the yearly scientific map of technology made in Italy. Its site had to earn trust in the report first, then move each visitor to one of three things: download the report, book a seat at the 2027 presentation, or become a partner.
3ways in: the report, a ticket, a partnership
2languages, every line in English and Italian
0frameworks or page builders: hand-written HTML, CSS and JS
The brief
Three jobs. One page.
01
Get the 2026 report downloaded, with company details the client can use.
02
Sell the 400 seats for the presentation on 24 February 2027 in Milan.
03
Find partners and sponsors for the 2027 edition.
The readers are investors, managers who buy technology, public administration and universities, in Italy and across Europe. Many arrive from the press or LinkedIn, still deciding whether the report is worth their time.
My approach
The method is the proof.
It should read like a scientific publication, not a campaign.
Every number has a source
- Each figure carries its edition and its page in the report
- Figures that conflicted inside the report stayed off the page until the client confirmed them
Quiet motion
- A slow network of points in the background: the event is about connections
- It stops for anyone who has Reduce Motion turned on
No buried actions
- Each action has its own button and its own place on the page
- Nothing is hidden behind something else
Three ways in
Never bury one action behind another.
Pick an action to see every place it shows up on the page, and why it’s there.
The page, top to bottom. Numbers match the list.
3rd edition · April 2026
The official report on Italian tech.
Every edition maps the companies, solutions and categories of technology developed in Italy, checked against official records and validated with the companies themselves.
Italian is the language of the event and the press, English of the report and European readers. Both pages are complete, and linked so search engines show the right one.
Built with AI
AI wrote the code. I set the rules.
The whole site was designed and built in conversation with Claude. The speed came from the AI. The judgement about what to say, what to leave out and what counts as done stayed with me.
Rules first
- A product brief before any design: who visits, the three goals, the evidence on hand
- A written list of what must not be invented: agenda, partner prices, conflicting figures
Design and build
- Hand-written HTML, CSS and JavaScript. No framework, no page builder
- Four full versions before the one that went live
Checked like any build
- Phones, keyboard, contrast, Reduce Motion, both languages
- Each fix went in as a small, named change on GitHub
Shipped
- Versioned on GitHub, live on the client’s hosting
- Security headers, and a small endpoint that emails every lead to the team
Up close
Laptop and phone, side by side.
Screens from the live site. Drag through them, or open one full size.
What it does now
Ready for 24 February.
Report downloads, behind a short form with consent
Ticket sales through the external checkout
Partner enquiries and the partner kit
Complete English and Italian pages
The site went live in October 2026. Downloads, ticket sales and partner enquiries are what it will be judged on, and it’s too early for those numbers. They’ll go here when they’re in.
A report.
A reason to be in the room.
The work
What went into it.
Work included
Strategy and UXProduct briefUI designFront-end buildEnglish and ItalianLead forms with consentMotion design
Tools
ClaudeGitHubHTML, CSS and JavaScriptPHP for lead emails
One page. Every visitor placed.
Tell me what your site needs people to do. A free call, about 30 minutes, no pitch.