Kuyavian-Pomeranian
Web development — Bydgoszcz
Fast, multilingual websites for Bydgoszcz companies. Fixed price, fixed scope, a date in the contract.
The local market
Bydgoszcz does not live off tourism or corporate headquarters — it lives off logistics, manufacturing and shared-service centres. The S5 and S10 crossing, the A1 within an hour's drive, an airport, the Bydgoszcz Industrial and Technology Park, and a dense network of freight forwarders, metalworking plants, packaging makers and component suppliers. Alongside that sits the second pillar: shared-service and BPO centres that came here for the skills and for costs lower than in Tricity or Warsaw.
That changes what a website is for. In B2B nobody buys from an advert — a purchasing manager opens your site after getting your name at a trade fair or from a referral, and checks whether you are a real company: certificates, licences, machinery, actual technical data. The site is the document they use to check you out, not a flyer. The catalogue has to be searchable by part number, datasheets have to be downloadable as PDFs, and the form has to collect the parameters of the job — tonnage, route, material — instead of asking how it can help.
Exporting companies need an English version and often a German one, because the counterparty reads the site before picking up the phone. Service centres have an entirely different goal: their site is a recruitment tool — job listings, employer branding, and a careers section that loads on a phone in a couple of seconds. I build both on the same foundation: statically generated Next.js, a multilingual structure from day one, and a CMS you edit yourself.
How I work
I live and work in Bydgoszcz, so a meeting happens the same week. I run the project remotely — video calls and a live preview link you can watch as it goes — and I am there in person for the kickoff and the handover.
See how it works in practice
Industrial B2B website for Pol-Med — UCO oils trade & collection, education stations, industrial tools. Next.js 16 with a polished silver-accent aesthetic.
Pol-MedCommon questions
I sell B2B and get clients from trade fairs and referrals. Why do I need a website?
Precisely because they come from referrals. A purchasing manager gets your name, opens your site and decides within a minute whether you are worth a conversation. The site is not there to replace trade fairs — it is there to not kill the leads the fairs already produced. It is the document they check you against: your scale, your certificates, what you can actually manufacture.
I have several hundred products and datasheets in spreadsheets and PDFs. Can that go on the site?
Yes, and it is usually the highest-return part of the project. I import the spreadsheet into the CMS as a catalogue filterable by part number, spec and application, and attach the datasheets as downloads on each entry. The result: a buyer lands on the exact part number straight from Google instead of phoning to ask whether you stock it at all.
I need an English version and possibly a German one. Does that mean two separate sites?
No. I build the structure multilingual from day one — each language gets its own URLs and correct hreflang, so each version ranks separately in Google. It is still one site and one CMS: the layout, components and integrations are built once. What gets added is translation and one proofing pass per language, not a second website from scratch.
I want someone to see the plant and talk to our engineers. Will you come out?
Yes — I travel for the kickoff and the handover. Photos of the shop floor, a conversation with your process engineer and half an hour by the machines produce content you cannot write from an emailed brief. The rest runs remotely: video calls and a preview link that updates continuously, so you see progress without asking for a status.