Servizio · Web Design
Web Design
An old website isn't a relic: it's commercial friction. If it doesn't bring contacts, if it looks like the competitor's, or if it depends on plugins thrown in to plug holes, the problem isn't "redo the graphics". The problem is putting things back in order.
I design showcase, institutional and portfolio websites with clear structure, recognizable web design and clean development — in WordPress when it makes sense, or custom with Astro and Next.js when control is needed. Inside: base technical SEO, GDPR, Google Business, Analytics and Search Console.
On a recent local rebuild, time-to-form dropped from 6 taps to 2: not magic, just information architecture done well. After launch I don't disappear: a year of support is included. Period.
01 — Awareness
The problem isn't just the ugly website
It's the fragile technical chain that makes it slow, anonymous and impossible to manage.
- 01
Zero real contacts
The site exists, but doesn't produce inquiries. Vague pages, hidden forms, interchangeable copy and no serious tracking. You don't even know where the path breaks.
- 02
Already-seen template
Same structure, same icons, same tone as the competitor. Change the logo, the copy effect remains. A serious business can't show up with a mask taken off the shelf.
- 03
Agency disappeared
Everyone present at launch. After, nobody replies. The site hangs between hosting, plugins, updates, credentials and vague responsibilities. When something breaks, the bouncing-around starts.
02 — What you get
6 features- 01
Design without templates
No bought theme with color tweaks delivered as a project. The layout starts from content, from the type of customer who has to understand what you do, and from the actions the website needs to make easy.
- 02
Mobile-first development
The website is built first for real screens, not desktop screenshots. Navigation, copy, forms, images and buttons get tested on mobile, tablet and desktop before going live.
- 03
WordPress or custom
WordPress when you need content autonomy and a familiar way to manage the site. Astro or Next.js when you need performance, technical control and fewer dependencies. The choice isn't decided by current fashion.
- 04
Base technical SEO
I configure sitemap, robots, metadata, essential schema, necessary redirects and a readable structure. I don't promise Google magic: I remove the technical errors that prevent the site from being read properly.
- 05
GDPR and tracking
Cookies, privacy, Analytics and Search Console get configured with judgment. No banners copied poorly, scripts pasted everywhere, or tracking active before consent when it shouldn't be.
- 06
One-year support
After launch you stay covered for technical interventions, small adjustments, checks and ordinary problems. You don't end up in the classic void between designer, hosting, developer and someone who stopped replying.
03 — How I work
5 phases- 01
Discovery call
30 free minutes to understand the real need. I listen, ask questions, take notes. No cold quotes: I need to know what you're actually building first.
- 02
Quote
Flat fee with clear scope, timeline and costs. No surprises: if something falls out of scope I tell you upfront, not when the invoice lands.
- 03
Design / Strategy
Wireframes, moodboard or audit with action plan — depends on the service. You see the direction before any code or content gets touched.
- 04
Build
Development, technical work or operational execution. Agreed check-ins along the way, none of that "let's sync end of month".
- 05
Launch & follow-up
Go-live + 30 days of assistance included. Documentation, training if needed, and an open door for the small things later.
04 — AFTER LAUNCH
The site doesn't end when it goes online
The most ignored part of web design is what comes after publication. That's where you see if the project was built well or if it was just a packaged delivery. Forms that don't send, cookies configured badly, Search Console never opened, Analytics half-installed, plugins demanding updates every week, shared hosting that slows everything down as soon as visitors arrive. The chain of providers multiplies the problem: whoever did the design doesn't touch the server, whoever manages the server doesn't know about the form, whoever installed the plugins doesn't reply. Here the perimeter is clear: site, technical setup, GDPR, Google tools and one year of support. One contact, fewer hand-offs, fewer excuses. You decide.
05 - What you get
Deliverables
| No. | Deliverable | Format | Timing |
|---|---|---|---|
| 01 | Main pages sitemap | Miro + .md | week 1 |
| 02 | Lo-fi navigable wireframes | Figma | week 1 |
| 03 | Base design tokens | Figma + .json | week 1 |
| 04 | Hi-fi homepage design | Figma | week 2 |
| 05 | Inner page templates | Figma | week 2-3 |
| 06 | Documented UI components | Figma | week 3 |
| 07 | Form and CTA microcopy | .md | week 3 |
| 08 | Responsive checklist 4 breakpoints | PDF report | pre-launch |
| 09 | Development handoff and assets | Figma + .zip | pre-launch |
| 10 | Post-launch check | Checklist | post-launch |
07 - Related services
08 - Free audit · 15 minutes
Want to know where you lose customers before starting?
I look at structure, mobile, CTAs, forms and tracking. 15 minutes on Meet, no quote disguised as consulting.
No obligation - reply within 24h
09 — Frequently asked questions
6 answersThe questions I hear all the time.
My site is old: should I rebuild it or fix it?
Depends on what's underneath. If the site has clear structure, recoverable content and a decent technical base, you can intervene without throwing everything out. If instead it's a theme full of plugins, slow, fragile and untracked, rebuilding is often cleaner. We assess the real state first, not the calendar age.
Better WordPress or custom development?
WordPress fits when you want to update pages, articles and content autonomously with a familiar interface. Custom development makes sense when you want more speed, fewer useless components and greater technical control. There's no universal choice: there's the right context. The rest is meeting-room religion.
Will the site be editable after delivery?
Yes, but with different criteria depending on the chosen technology. In WordPress you can manage content and predefined sections. In a custom site, changes pass through a more controlled structure, often more stable. The goal is to avoid chaos: total freedom without rules becomes technical debt.
Do you also handle domain, hosting and email?
I can coordinate domain, hosting, DNS and technical aspects connected to the site. If the current situation is a mosaic of providers, lost access and panels never seen, we put things in order before launch. Slow shared hosting and opaque configurations aren't details: they're problems that always come back.
Is SEO included in the work on the site?
The base technical part is included: correct structure, metadata, sitemap, robots, essential schema, performance and Search Console connection. It's not an ongoing SEO campaign and doesn't promise guaranteed positions. It puts the site in the right conditions to be read, indexed and monitored.
What happens after the site goes online?
After launch I check forms, tracking, indexing, technical errors and details that often only emerge online. A year of technical support is included to avoid the classic post-publication abandonment. The site doesn't get launched and left there like a forgotten zip file. End of story.
10 - Start here?
Ready to start?
A 30-minute call to figure out what's actually needed. No PowerPoint.