Who will build my company website on WordPress?
gdamian.pl is a one-person web development studio run by Damian Gębala, building company websites on WordPress from structure and copy through to deployment on your own domain. You work with a single person accountable for scope, deadline and outcome — no agency handoff chain and no freelance marketplace. Scope, deadline and a price range arrive in writing before work starts, and after launch you edit the content yourself without an invoice for every correction.
A company website should sell or serve, not merely exist. Below: the scope, the timeline and what stays with you afterwards — so you know what you are paying for before you ask about price.
- →Site structure and copy agreed before the first pixel — we do not start from a template
- →A theme built around your processes, not assembled from a plugin catalogue
- →An ACF editing panel: you change content in fields, not in code and not in a page builder
- →WooCommerce where the site has to sell — payment and shipping configured
- →Performance and SEO verified before launch, not after someone reports a problem
- →Correct structured data, a sitemap, and access for AI crawlers
- →Handover with a recorded editing walkthrough and every credential on your side
A working site is usually live 1–4 weeks after the scope is approved. Larger builds are split into stages so the first part works before the rest exists. You see a working version every week, not only at the end.
Billed per project or per day. The range arrives in writing after a free call, and no work starts before you approve it.
WordPress or Astro for a company site?
It comes down to who edits the site. If a non-technical person changes content often, WordPress with ACF fields wins. If the site changes rarely and speed and running cost matter most, Astro with server-side rendering is the better choice. I advise on the first call, once I know who sits down at the admin panel.
Will I be able to edit the content myself?
Yes, and that is the starting point of the project rather than an add-on. Editing happens in labelled ACF fields, so you cannot accidentally break the layout. At handover you get a recorded walkthrough showing how to change every element.
Who owns the code and the credentials afterwards?
You do. The code goes to your repository, hosting and domain sit on your account, and handover includes a short maintenance guide. There is no situation where you have to come back to me for a password.
Will you take over a site someone else built?
Yes. Short fixes are billed per day and I tell you the number of days up front. If reading the code convinces me that rebuilding is cheaper than patching, I say so directly, with the numbers.
Will the site be fast and visible in search?
Performance and SEO are verified before launch, not after someone reports a problem. Every site ships with structured data, a sitemap, correct canonical URLs and open access for both search engine and language model crawlers.