I build websites, systems and everything around them

A simple business site is usually PLN 999–3,000 net, a larger site with SEO-focused content PLN 3,000–6,000, an online store from around PLN 2,500, and a custom web app from around PLN 4,000. The exact quote comes after a free diagnosis — you pay for an agreed scope, not for surprises.

WordPress wins when a non-technical person changes content often and you need a familiar panel. Next.js wins on speed, security and freedom with unusual features. I work in both — you get a recommendation with reasoning at the architecture stage, before the quote.

Business site: usually 3–6 weeks. Online store: 6–10 weeks. Web app: from 8 weeks upwards, depending on the scope of version 1. The most common holdup isn't the code, it's the content — which is why I help prepare it rather than wait on "materials from the client."

Yes — technical SEO is part of every build, not a paid extra. As standard: semantic HTML, metadata, schema.org structured data, sitemap, fast loading (Core Web Vitals) and a content structure that generative search engines can read too. Ranking itself (content, links) is separate, long-term work — honestly, the site gives you the foundation, not a guarantee of position.

Yes. With WordPress you edit everything in a familiar panel. With Next.js I connect a CMS (e.g. WordPress as a content backend) where you change text and photos without touching code. You also get a short guide — and if something goes wrong, I'm on the other end of an email.

Yes. I start with a backup and a technical audit, then you get a short report: what's broken, what it's costing the business and what to fix first. I also help recover access to your domain and hosting.

Yes. After launch you can stick to ad-hoc jobs or arrange ongoing care: updates, backups, monitoring and a package of hours for fixes or development. The scope and rate are agreed up front — no "on standby" subscription with nothing behind it.

Yes. I run an audit, show you what's genuinely doing harm and what the repair costs, and next to it I give a quote for a new site. If the repair makes no economic sense, I'll say so plainly.

We start with a workshop where we set the scope of version 1 and what deliberately waits. After it you know the cost of the first version before you spend a złoty on code. I quote larger systems in stages, so the budget isn't one big unknown.

Yes. Before any code exists, we lay out what the system should do and what it deliberately won't. Sometimes it turns out that part of the problem is solved by order and a single tool, not a separate app — and I'll say that too.

A few sentences about what isn't working now, or what the new site or app should do. Useful: the address of your current site, examples you like, and a rough budget. I'll ask about the rest.

Yes. Version 1 covers what delivers value the fastest; we add the rest when there's a real need. You validate the idea on the market sooner and save on features nobody uses.

Changes are normal. Small ones fit within the agreed scope; larger ones I quote separately and you decide whether they go in now or after launch. I don't quietly add them to the invoice.