This page is for three kinds of companies: an agency that needs a senior WordPress and WooCommerce engineer under its own brand, a company building a product that is looking for a technical partner, and a company with a working system that wants to connect AI to it. On the other side is one engineer, Mariusz Szatkowski, with 19 years of running WPPoland and work for clients in Germany, the UK, the USA, Norway and the Netherlands.
Three partnership models
| Model | Who it is for | What you get | What you do not get |
|---|---|---|---|
| White-label development | an agency with clients on WordPress and WooCommerce | a senior engineer under your brand, from estimate to deployment | contact with your client, unless you want it |
| Technical partner | a company building a product on WordPress, WooCommerce or a headless architecture | architecture, the first version of the product, documentation for handover to a team | a team of five developers from day one |
| AI integrations | a company with a working system | a connection between the system and AI agents, read-only by default, logged and reversible | a model trained from scratch |
White-label development for agencies
The agency keeps ownership of the client relationship, and the work reaches it as a finished deployment, fix or audit. Package prices, response times and handover rules are set out on the agency development desk page.
Technical partner for a product company
This makes the most sense for a product being built on WordPress, WooCommerce or a headless architecture with an Astro or Next.js frontend. The first version is built against a success criterion written down before the start, with documentation that lets a future team take over the code without depending on one person.
AI integrations in an existing system
The starting point is the data and processes that already work. The AI agent gets access through a controlled MCP server: read-only by default, with call logging and the option to roll back. Where client data cannot leave the client’s infrastructure, the model runs locally. Details are on the MCP and AI integration page.
What I bring to a partnership
- Open code you can check before we talk: an MCP server for WooCommerce under the MIT licence (wppoland/woocommerce-mcp) and a tool that detects hidden text in PDF and DOCX files (wppoland/hidden-text-detector).
- My own products: Plogins, a suite of 45 WooCommerce extensions, 21 of which are in the official wordpress.org directory (motylanogha profile).
- The WordPress community: WordCamp Europe organising team since 2024, organiser of WordCamp Gdynia since 2015, co-organiser of CMSConf in Gdynia.
- Contract work at scale: since October 2025, full-stack engineer on contract for WP-Stars in Vienna, on a subscription-based media and sales platform.
My full professional background is on the about page.
What I do not do
- Graphic design, mockups and UX. The client supplies the layout of each view, and I implement it as a working, responsive interface.
- Native mobile apps and 24/7 support.
- Pretending to be a team. One person means one calendar. Large, parallel workloads are a job for an agency or a software house.
How we start
- A description of the product, the current state of the system and what needs to be built, sent through the contact form or by email.
- A written reply: scope, questions, terms and timelines.
- Work begins once the deposit has cleared. Every stage has a written criterion that tells us when it is done.
Photo: WordCamp Gdynia 2025, by Julia Marszewska.
