Pomeranian
Web development — Gdańsk
Websites for Gdańsk port, tourism and startup companies — English-first if you need it, and the code stays yours.
The local market
Gdańsk is three markets at once. The port — the largest in Poland, with the largest container terminal on the Baltic, taking ships straight from Asia — and around it freight forwarders, customs agencies, shipyards, marine services and a growing offshore sector. Tourism: the Motława waterfront, Westerplatte, amber, and heavily international traffic, much of it Scandinavian and German. And the third pillar: one of the country's largest IT clusters, fed by Gdańsk University of Technology and the local startup scene.
In the port trade the counterparty is foreign by default. That inverts the usual arrangement: English is often the primary version and Polish the secondary one. The site has to prove compliance and credibility — ISO and AEO certificates, equipment and warehouse specifications, a contact path that reaches a named operator rather than a shared inbox. And it has to open in a couple of seconds on hotel wifi in Rotterdam, not just on fibre in Oliwa.
The local IT buyer is different again: they will read the source, check your Lighthouse scores and ask about the repository, because sooner or later they will take the project in-house. So I hand over code, not a locked platform — typed content, a CMS your team can extend, and a deployment on your own account. These three markets are split by industry but united by one thing: a shipowner checking certificates, a tourist looking for a room on their phone, and an investor browsing the repository all have exactly the same patience for a slow, generic site — none.
How I work
I work remotely — video calls and a live preview link you can watch as it goes. I travel to Tricity for the kickoff and the handover, at my own cost; on bigger builds we add a mid-project meeting.
See how it works in practice
An event platform connecting service providers — from DJs to wedding venues — with clients organizing events.
EventizerCommon questions
Our clients are mostly foreign. Can you build a site where English is the primary version and Polish the secondary one?
Yes, and it is often the smarter setup. English then takes the x-default URL, Polish gets its own URL branch, and hreflang makes sure the search engine serves the right version to a Danish shipowner and the right one to a buyer in Gdynia. Technically it is the same work as a Polish-first build — the only thing that changes is which language is the default.
We are a startup. Do I get the repository, and can my team take it further?
You get the repository, a deployment on your own account and content in a typed structure — no locked platform and no subscription to access your own website. I write Next.js and TypeScript, the same stack most teams here already run, so your developer picks up the code straight away, with no onboarding. I stay on for support if you want it; if you do not, nothing holds you.
This is a big, demanding market, and you're one person. Can you actually handle a project at our scale, on a real timeline?
Yes — and it's precisely because there's one of me that I can promise a specific date instead of a vague 'it depends.' I don't run five large builds in parallel, so the project you commission gets my full attention, not half of it split across other clients. At the widest scope — a design system, integrations, payments — real delivery is typically 6–10 weeks; you get the exact date after we talk scope, and it goes into the contract, not a promise on a handshake.
Clients keep asking us for certificates and documents. Can we keep those on the site?
Yes, and it is worth doing. A documents section with current PDF versions — ISO, AEO, insurance, equipment specifications — saves your team emailing the same file ten times a month. You swap the files yourselves in the CMS; if part of it should be partner-only, I put it behind a simple form or a login.
We want to take payments or bookings online. Is that a separate project?
No, it is part of the same project. I wire payments through Stripe — that is how Eventizer, the platform I co-founded, works. In practice what gets added is defining exactly what the customer buys, handling failed payments, and invoicing; that is usually 2–3 weeks of work, not a separate engagement.