Frequently asked questions

WordPress is the best fit when you need a proven ecosystem with a powerful CMS, when it's important for the client to manage content independently without a developer, and when the project requires WooCommerce. It's a good choice for stores, corporate websites, blogs and portals with regularly updated content. The cost of a custom WordPress theme starts from 6,000 PLN, with a delivery time of 2–6 weeks. Avoid WordPress if the project requires very complex application logic or extreme performance under heavy traffic - Next.js is a better fit there.

Next.js is the better choice when you're building a web application with dynamic client-side logic, when you need very high performance (SSR, SSG, ISR), when you're integrating multiple external APIs, or when you're designing a SaaS product or multi-tenant platform. Next.js gives full control over architecture, but requires a separate CMS (e.g. Strapi, Sanity, Contentful) and backend infrastructure. The cost of a Next.js project starts from 15,000–20,000 PLN, with a delivery time of 6–16 weeks depending on scale. I don't recommend Next.js for simple brochure websites or small stores - WordPress wins there on value for money.

Headless is an approach where the backend (CMS, data) is separated from the frontend. WordPress or Strapi delivers data through an API, while Next.js or another framework renders the interface. This approach gives maximum flexibility, the ability to serve content across multiple channels simultaneously (web, mobile app, kiosk) and very high frontend performance. Headless makes sense with high traffic, multiple content distribution channels, or when frontend and backend teams work independently. The cost of a headless implementation starts from 25,000 PLN, with a delivery time of 8–20 weeks. For most SME companies, headless is overengineering - standard WordPress with a custom theme is enough and cheaper to maintain.

Yes — beyond WordPress and WooCommerce I deliver projects in Next.js, React and React Native. It's a smaller part of my offering, but I have several major deployments under my belt: a multi-tenant e-commerce platform, a mobile app with encrypted storage on iOS and Android, a gamification system for field teams. If a project outgrows what WordPress can offer, I know how to carry it through without you starting over with a different developer.

When at least one of these conditions is met: you need very complex application logic that WordPress doesn't handle natively, you're building a SaaS product or multi-tenant platform, you need extreme performance under heavy traffic, or you have your own backend and just need a modern frontend. In those cases I suggest Next.js — standalone or combined with headless WordPress as the CMS. If you're not sure what fits your project, start with a free call — 30 minutes is enough to figure it out.

Headless WordPress is an approach where WordPress serves as the content management system — your client edits articles and products in the familiar admin panel — but the frontend is built separately, in Next.js. The result: a faster, more flexible and easier-to-scale site, without giving up WordPress as a CMS. It makes sense when you care about performance and a modern stack, but the client needs to manage content independently. The cost of a headless implementation starts from 12,000 PLN, with a delivery time of 4–10 weeks.

Yes, but every such project starts with a paid technical audit (from 800 PLN, 1–2 business days). The audit evaluates the state of the code, architecture, dependencies and realistic possibilities for further development. After the audit you receive a report and a concrete plan — you can decide whether to continue working together. Taking over someone else's code without assessing its technical state is asking for surprises on both sides.

Yes, and this is the most common scenario. A rebuild involves replacing the old theme with custom code written from scratch, while keeping product, order and customer data in WooCommerce. You don't lose your sales history or SEO rankings if the rebuild is done correctly (301 redirects, URL preservation). The cost of a WooCommerce store rebuild starts from 8,900 PLN, with a delivery time of 3–8 weeks. As a result, the store runs faster, looks professional and is easier to develop than before the rebuild.

AI-powered website builders (Wix ADI, Duda, Framer AI) let you launch a simple site in hours at a fraction of the cost of a custom project. This makes sense when testing an idea, setting up a temporary brochure site, or for a hobby project with zero budget. The downsides: generic appearance that's hard to differentiate from competitors, limited control over code and performance, no ownership of the solution (you pay a subscription, you don't own the code), poor SEO optimisation and weak PageSpeed scores. At the first signs of growth - a need for ERP integration, a dedicated store, or an expanded blog - rebuilding from scratch is usually cheaper than trying to extend the generated site. For businesses that treat their website as a sales tool, an AI builder is a starting point, not a final solution.

A CMS (WordPress, Strapi, Contentful) is essential when the client needs to update content independently - a blog, product catalogue, news section, or a multilingual site with regularly changing content. Maintenance costs increase, but you gain independence from a developer for day-to-day changes. A CMS is not needed when site content changes rarely (portfolio, landing page, brochure site) or when data comes from a custom database and application - here an API and framework work better without a CMS layer. No CMS means simpler architecture, faster loading and lower maintenance costs. Rule of thumb: if the client asks "can I change the text on the site myself?" - a CMS is needed. If content changes go through a developer anyway - a CMS may be an unnecessary cost.

A PageSpeed audit and optimisation costs from 2,500 PLN and usually takes 3–7 business days. It covers Core Web Vitals analysis, image and font optimisation, elimination of render-blocking scripts, cache and CDN configuration, removal of unnecessary plugins and database query optimisation. A score of 90+ on mobile is guaranteed - otherwise I refund the consultation fee. For WooCommerce stores with a large number of products, optimisation often reduces load time by 50–70%, which directly translates to conversion rate.

The relationship is well-documented: each second of page loading delay on mobile reduces conversion by approximately 20%. A page loading in 1–2 seconds converts noticeably better than one loading in 4–6 seconds, even with an identical offer and prices. Google uses Core Web Vitals as a ranking signal, so a slow page loses doubly - on conversions and on organic traffic. In one of my projects (Leaf No Trace), reducing First Contentful Paint from 3.8s to 1.2s coincided with a measurable increase in organic sales.

A custom WooCommerce store built without a ready-made template starts from 8,900 PLN. The price depends on the number of products, required integrations and the level of customisation. Typical delivery time is 3–8 weeks.

A custom theme is written specifically for your project - no unnecessary code, full control over performance and appearance. Marketplace templates include features you don't use, which slows your site down and makes maintenance harder. A custom solution loads faster and is easier to develop further.

I start with a free discovery call (30–60 min) to understand the project's goal, scale and expectations. Then I prepare a quote with the scope of work and schedule. After acceptance, I work iteratively - regular contact, phased reviews, no surprises at the end. I use email or Slack for communication, reporting through Notion or a project document. I don't take on more projects than I can handle properly, so I always have a limited number of available slots.

Yes, but every such project starts with a paid technical audit (from 800 PLN, 1–2 days). The audit allows me to assess the state of the code, security, performance and realistic development potential without surprises. After the audit, you receive a report and recommendations - you can decide whether we continue working together. Taking over someone else's code without an audit is asking for problems on both sides.

Yes. I work with clients from Poland and abroad. Communication is available in Polish and English. The website is also available in an English version.

More and more users are searching for products and services through AI assistants (ChatGPT, Gemini, Perplexity). Websites with structured schema.org data, concrete facts and good information architecture are cited more often by AI models than sites without these elements. AI optimisation (GEO) is the natural evolution of classical SEO.

SEO optimises a page for search engine ranking algorithms - it's about position in the results list. GEO (Generative Engine Optimisation) optimises content for language models that generate direct answers instead of a list of links. In GEO it's not about ranking, but about getting AI to choose your page as a source for a quote or recommendation. This requires different techniques: structured schema.org data, content based on specific facts and numbers, clear entity identity (who, what, where, since when) and a Q&A format that directly addresses user intent.