WordPress developer for Warsaw companies and nearshore clients
I am Mariusz Szatkowski and I have built WordPress sites since 2006. Warsaw companies and clients in the UK, Ireland and the EU hire me for the technical work their own people have no time for: themes built from their design, WooCommerce stores with Polish payments and shipping, custom plugins, performance work and maintenance. I work alone, so I write the code you get, and I do not pass your access details to anyone.
You bring the wireframes and graphic design, for example as a Figma file or as a filled-in spreadsheet template where you mark which element goes where on each view. I build that as a responsive WordPress theme.
Who I am
WPPoland is the name I use for my work as a WordPress developer. I am a senior developer based in Gdynia, Poland. Companies with their own marketing and editorial staff use me as their development capacity.
What I offer
Block themes and custom blocks, WooCommerce with Polish and cross-border payment and shipping, custom plugins and integrations, performance work based on real user data, GDPR-aware setup of third-party scripts, and multilingual sites with Polylang or WPML.
Developer or page-builder studio
A lot of WordPress work is assembly: a licensed theme, a page builder and a stack of plugins to fill the gaps. For a brochure site that is often enough, and I will tell you so. You need a developer once the requirements stop fitting a visual editor: a content model the builder cannot express, a WooCommerce checkout that has to talk to Przelewy24 and an accounting system, a page that must stay fast under real traffic, or code another developer can open in a year and understand.
Custom themes and plugins to WordPress Coding Standards
On a new build my default is a block theme: theme.json for colours and spacing, block patterns for the layouts your editors actually use, block variations where a pattern needs options. Your team edits without a page builder loading on every request.
Anything functional goes into a plugin so it survives a theme change: custom post types, REST endpoints, integration logic, admin tools. The theme holds presentation only. I see the opposite on many inherited Polish sites, where a custom post type and a Przelewy24 callback sit in functions.php and a redesign turns into data recovery.
The code follows the WordPress Coding Standards: escaping and sanitisation on every input and output, nonces on forms, translatable strings so one code base serves Polish and English, and PHP that a linter checks in the pipeline. Changes are small and reviewable, each with a staging link.
WooCommerce for Polish and cross-border selling
A store selling to Polish customers needs BLIK. Przelewy24 bundles BLIK, bank transfers and cards in one contract; Tpay is the usual alternative. Customers expect an InPost Paczkomat picker in the checkout, with DPD or DHL for larger parcels. I connect carriers through a broker such as Apaczka or Sendit when you ship with several, so label generation sits in one place.
Your accountant needs data in a shape their software reads: exports compatible with JPK_VAT, invoices pushed to inFakt or Fakturownia, and a KSeF e-invoicing integration where your invoicing tool requires it. Which of these applies to your company is a question for your accountant; I build what they specify.
Stores that sell from Poland to other EU countries add OSS VAT rates, more than one currency and language, the lowest price from the previous 30 days shown next to a promotion, and shipping rules that differ inside and outside Poland. I prefer one integration layer written for your case over one plugin per requirement, because a stack of overlapping plugins slows the checkout. When the shop work grows large enough, see the WooCommerce developer page.
Who hires a WordPress developer from Poland
Warsaw is where many Polish fintech, SaaS and e-commerce companies have their headquarters, and their marketing sites, landing pages and stores often run on WordPress. Their legal and procurement teams read the cookie banner and ask for a data processing agreement before signing, so the site has to be built with that review in mind.
Clients in the UK and Ireland usually come for one of two reasons. A company needs a senior WordPress developer for a project without a permanent hire. Or an agency wins a WordPress build that is bigger than its bench, and I work white-label in its repository and on its staging, with the commit history belonging to the agency.
How a project runs
- Brief and scope: I read your brief, look at the existing site or code base and ask my questions in writing. Inherited code gets an audit first.
- Proposal: scope, assumptions and schedule are written down before any code exists.
- Build: the code lives in a private Git repository. Every push goes to staging; production is updated only after your approval.
- Acceptance on staging: you review there and get a written description of each change.
- Launch: before it, I run Lighthouse, axe-core and a manual check in current Firefox, Chrome, Safari and Edge, on iOS Safari and on Chrome for Android.
- Handover or maintenance: you get documentation your own developers can work from, or I keep maintaining the site.
Performance under real traffic
A WordPress site that is fine in the demo and falls over during a campaign usually suffers from uncached database queries multiplying under load, plugins loading on every request, or an options table with megabytes of autoloaded data. I start with Query Monitor and server timings, and the first pass is mostly deleting work: a query that runs on every page for something used on one, a meta query without an index, an option that never needed autoloading. After that, object caching and a page cache for anonymous visitors absorb the spike. Cart and checkout cannot be cached whole, so on a WooCommerce store I keep those paths lean. I measure against real user data from CrUX, not a single lab run.
Security, GDPR and data processing
Security in the code means escaping and sanitisation on every input and output, nonce checks on forms, hardened configuration, least-privilege database and file permissions, and dependencies kept current through Composer. GDPR decides what personal data a plugin stores, how consent is captured on forms and analytics, and how export and erasure requests are handled without digging through the database by hand.
Before I get access to a site with personal data, I sign a data processing agreement under Art. 28 GDPR. I use no sub-processors. Maintenance includes uptime monitoring every 1 to 5 minutes, backups kept for 30 days or more in EU countries and updates tested on staging first. I do not sell hosting, run a 24/7 on-call service or guarantee response times.
When headless WordPress makes sense
Keeping WordPress as the editing back end and rendering the site with a separate front end pays off for an app-like interface, a design system shared with a native app, or a busy publication that wants a static front end. In those cases the Next.js and Astro migration and the headless WordPress service describe the work. For a content site that a good block theme can serve, headless doubles the deployments and adds a seam between CMS and front end that can break. I recommend getting the WordPress build right first and going headless only when a specific requirement pays for it.
When you do not need a dedicated developer
If your site has a handful of pages, changes rarely and has no integrations or performance pressure, a reputable theme and a few well-chosen plugins will serve you, and paying a developer buys capability you will not use. The same goes when the real problem is content or marketing. Custom code also needs an owner: a bespoke plugin nobody maintains is worse than the off-the-shelf one it replaced. I build custom code when your needs and what assembly can deliver genuinely diverge.
Contracts and invoices for UK, Irish and EU clients
- Contract: a B2B contract under Polish law with your company, with an NDA and a data processing agreement if you need them. An IP assignment clause can go into the contract as well.
- Invoice: issued from Poland with my EU VAT ID PL7393037445. For business clients in Ireland and other EU countries the invoice uses the reverse charge. UK clients should confirm the VAT treatment with their accountant.
- Time zone: Poland is one hour ahead of the UK and Ireland all year, so most of the working day overlaps.
- Communication: in English, by email, in documents and in the repository.
WordPress development in other Polish cities
See also WordPress developer in Krakow, Gdansk, Poznan, Wroclaw and Lodz.
Contact
Send me the scope, your timeline and your current stack through the contact form. You receive the next steps in writing and a proposal listing the assumptions it rests on.



