01 — Who this page is for
You need a web designer or developer who works in English fluently AND understands Italian business reality.\nThat combination is harder to find than it should be.
Italian agencies sometimes claim "English-speaking team" but the practice is usually limited to a sales person with survival English and a designer who needs everything translated.\nUK/US agencies handle English natively but miss Italian-market specifics (P.IVA, IVA reverse-charge, GDPR-Italian-style, WhatsApp-first customer behavior).
I work in English daily, write Italian as a native, build in EU regulatory context, and bill in EUR / GBP / USD. One person, both languages, both legal frameworks.
02 — 4 typical client profiles
Expats running businesses in Italy
British, American, German, Dutch expats who've moved to Italy and started a business — boutique B&Bs in Tuscany, wine importers in Piemonte, language schools in Florence, holiday rentals in Puglia. They need someone who speaks their native business language but understands Italian bureaucracy, suppliers, and customer expectations.
Foreign companies entering the Italian market
UK, US, German companies opening Italian operations or selling cross-border to Italian customers. They need an Italian-language site that doesn't read translated, GDPR + Italian privacy compliance handled, and a developer who can brief in English while writing Italian copy that converts.
Italian businesses serving foreign clients
Real estate agencies selling Tuscan villas to international buyers, luxury hotels with English-speaking guests, professional services firms (legal, tax, immigration) helping expats. They need bilingual sites where the English is genuinely good — not Google Translate output.
International remote teams with Italian operations
Distributed companies with European HQ in Italy, cross-border SaaS with Italian compliance needs, EU agencies needing Italian-market localization. English-first communication, Italian execution.
03 — 4 problems with the alternatives
- 01 — Problem
Italian agency that "speaks English" — sort of
You hire an Italian web agency that lists 'English-speaking team' on the site. Reality: the account manager speaks survival English, the actual designer/developer speaks none, briefs get translated badly in both directions, deadlines slip because every email needs a translation pass. By month 3 you're frustrated and the project is 4 weeks late.
- 02 — Problem
UK/US agency with no Italian context
You hire a UK or US agency to avoid the language problem. They build a site that's technically fine but completely wrong for the Italian market: missing P.IVA in footer, no GDPR consent the way Italian regulators expect, contact form without WhatsApp button (which 90% of Italian customers use), language switcher that defaults wrong, address format that doesn't match Italian conventions.
- 03 — Problem
Translated copy that screams "translated"
Italian-language version of an English site that was clearly run through Google Translate or done by a junior translator. Cases (lei vs tu) inconsistent, tone shifts mid-paragraph, idioms calqued from English ('a lungo termine' vs more natural 'nel lungo periodo'). Italian customers spot it within a sentence and the trust drops.
- 04 — Problem
Two separate freelancers, broken hand-off
You hire one English-speaking developer + one Italian translator. Hand-off between them is messy: developer doesn't know the Italian copy is too long for the design until the translation arrives, translator doesn't know which strings are technical vs marketing. You end up project-managing the integration yourself.
04 — How I work bilingually
- Briefs in your preferred language. Most non-Italian clients prefer English; some Italian clients prefer Italian.\nI match.\nMid-meeting language switching works fine if your team is mixed.
- Site copy in both languages, written natively. No translation hand-off.\nThe Italian version reads like an Italian wrote it (because I did), the English version reads like fluent professional English (because I write it daily).
- Design accommodates language differences. Italian text typically runs 15-20% longer than English.\nThe design accounts for this — buttons, headlines, navigation don't break when language switches.
- Bills in your currency. EUR, GBP, USD via wire transfer or Wise/Revolut.\nStandard 50% upfront / 50% on delivery for fixed projects.\nMonthly retainer for ongoing.
- Async tools work in English. Slack, Linear, Notion, Figma, GitHub Issues — all in English by default.\nProject board you can read at a glance.
05 — Italian compliance + foreign business reality
Operating a business that touches the Italian market means handling Italian-specific compliance that UK/US agencies routinely miss.
P.IVA + IVA basics: Italian VAT (IVA) is 22% standard, reduced rates for specific categories.\nP.IVA must appear in site footer for VAT-registered businesses.\nReverse-charge B2B EU.\nOSS for distance selling.\nI configure all this in WooCommerce / Shopify / Stripe correctly.
GDPR Italian-style: Italian Garante della Privacy is one of the more active EU privacy regulators.\nCookie consent must be granular (categories, not single accept), data processing agreements with all third-party processors, privacy policy that meets Italian regulatory expectations (more detailed than typical UK/US version).
Italian customer behavior: WhatsApp is the default contact channel for most Italian businesses (more than email or phone).\nTap-to-WhatsApp button on mobile is non-negotiable.\nItalian customers expect human response, not bot — auto-reply tolerated only as ack, not as actual response.
European Accessibility Act: EAA in vigore from June 28, 2025.\nMandatory for B2C digital services in the EU.\nWCAG 2.1 AA compliance.\nItalian fines up to €40k per violation.\nI bake this into every project as default, not retrofit.
06 — FAQs
Why are you better than an Italian agency that 'has English-speaking team members'?
Because I work in English daily, not just 'when needed'. Briefs in English, written specs in English, async messaging in English, calls in English. Italian gets used only for actual Italian-language deliverables (copy, customer-facing strings). No translation overhead, no 'I'll send your message to our designer who doesn't speak English'. One person, two languages, zero handoff.
What if I need both English and Italian versions of the site?
Standard. The i18n architecture supports both languages natively (Next.js + next-intl), I write the Italian copy as a native and the English copy as fluent professional English, the design accommodates Italian's tendency to be 15-20% longer than English without breaking layouts. You get one consistent voice across both languages because it comes from one person.
I'm an expat running a B&B in Tuscany. Is this overkill for me?
Maybe. For a 4-room B&B with seasonal bookings, a Squarespace or Airbnb-only setup is often the right call (low cost, low maintenance). I'd advise against custom development unless you have specific needs: direct booking channels to avoid OTA commissions, multi-property management, integration with property management software, or you're scaling beyond 4-6 rooms. Discovery call clarifies which side of that line you're on.
How do I know your English is actually good enough for business?
Reading this page is the easiest test. The discovery call is the next test. I work daily in English with UK / US / EU clients on technical and marketing content. References available on request — clients on both sides of the language divide.
Do you handle Italian VAT (P.IVA / IVA) compliance for my e-commerce?
Yes. Italian VAT setup in WooCommerce / Shopify / custom Stripe is part of any e-commerce project: 22% standard rate, reduced rates for specific categories (4% essential goods, 5% feminine hygiene, 10% restaurant + utilities + some services), reverse-charge B2B EU, distance selling thresholds. For non-Italian companies selling to Italy, OSS (One-Stop-Shop) registration is what you actually want — I help configure it.
Can you handle multi-language beyond English/Italian?
Architecture-wise yes, the i18n system supports any language. For German, French, Spanish I work with native translators (have a few in network). I write the Italian and English copy myself, coordinate with translators for other languages, integrate them into the i18n system. You don't pay extra for the framework supporting more languages — only for the translation work itself.
I'm in Italy 6 months a year — do meeting times work?
Yes. When you're in Italy, we're in the same time zone — calls anytime in normal working hours. When you're abroad (US East coast common for expats with family there), I'm 6h ahead, sweet spot for calls is 14:00-17:00 ET = 20:00-23:00 CET. Async on Slack/Linear covers everything else.