Systems over hacks
I like fixes that solve the problem more than once. A quick hack is fine when it’s actually temporary. The trouble starts when temporary becomes architecture.
Websites for small businesses · Switzerland
I’m Patryk. I create websites that help small teams explain what they do and make it easy for customers to get in touch. My field and software experience keeps the work grounded in practice.
Introduction
For a team of 1–10 people, a website should show the work clearly, earn trust and make it easy for customers to get in touch. I start with those needs, then choose the design and technology that serve them.
I also work with software and telecom infrastructure. I’m exploring how AI and automation can help small teams in the future; they are topics I write about, not services I’m offering here today.
Explore website servicesSelected websites
A selection of sites I’ve created for companies, organisations and individuals. Each brief has a different answer, but the goal stays the same: clear content and a useful experience.
Projects
A modern website for a Swiss company delivering and maintaining infrastructure for 5G and next-generation networks.

A calm, trust-building website for a certified psychodynamic psychotherapist, guiding visitors from understanding her approach to booking a session.

A clear online presence for an orthoptist in Lublin, designed to explain services and make first contact easier.
Website enquiry
Tell me what your business needs
A few answers help me understand your business and suggest the next step. You can leave the details you don't know yet open.
Blog
Practical notes on websites and the technical questions small businesses face. I also explore AI and automation as future directions.
A personal account of limiting music, films, and news: less borrowed drama, more calm, and a selective return to art worth contemplating.
A free-form journal of the journey through life: how AI helps organise records, tasks and context without inventing the author’s experiences.
Activity is not a result. Experiences with Paperclip and telecommunications show why metrics need context and independent evidence of completion.
How I think
I like fixes that solve the problem more than once. A quick hack is fine when it’s actually temporary. The trouble starts when temporary becomes architecture.
If it only works on the diagram, it doesn’t work. I care much more about what happens after deployment than how clean the plan looked before it.
I try to keep facts, assumptions and opinions separate. They can all be useful, but mixing them together is a good way to make bad decisions.
I don’t want to stay busy just to keep things moving. I prefer building systems that need less of my attention over time. If something needs me forever, I probably haven’t finished building it yet.
Other matters
A question beyond a website?
For course access, editorial notes or another matter, use this general contact form.
I share new Blog posts on Facebook and X. You can also find my professional profile on LinkedIn.