When you need this

You have more than one thing to say and more than one kind of visitor. Services, a team, finished work, news, offices in several cities. The site has to explain a business, not sell a single item — and your own people have to keep it current for years without writing to a developer every time.

What I actually build

The map of the site before the look of it: which pages exist, what each one is for, and what a customer types into Google to find it. Most weak company sites are weak here, not in the design.
Editing built for whoever will actually do it. Fields named the way your office talks — service, branch, opening hours — not a wall of blocks. If your office manager cannot add a service without calling me, I built it wrong.
Findable without a plugin holding it up. Every service and every location is a page Google can read, with the titles and descriptions in the site itself.
Several languages when your customers genuinely speak several. The hard part is never the translation; it is keeping one catalogue instead of three that drift apart.

Where this shows up in my work

A course catalogue that has to work in three languages — 113 courses and 41 instructors, one catalogue in Polish, Ukrainian and Russian, kept up by the academy itself. And Nineteen years of renovation work, made findable, a demonstration build showing what the structure looks like when the archive is deep and the prices are on the page.

What you get

A site your team runs without me, a written description of how it is put together, and a structure that takes a new service, branch or language as an edit rather than a rebuild. Domain, hosting and code in your name from the first day.