Anyone can build you a WordPress site. The question is what you get back.
WordPress is a commodity. Anyone can build you a site. The harder question is whether what gets delivered is something your team can run, your visitors can use, and the next person who touches it can understand.
I build WordPress sites for small and mid-sized businesses – presentation sites, company sites, landing pages, content-heavy sites, eCommerce stores. From design coordination through build, launch, and handover. One point of contact, one quote, one person responsible for the whole thing.
Sounds familiar?
You've been quoted by agencies and the numbers don't add up
Agency quotes that come in at €15,000 for a site that’s mostly off-the-shelf templates and stock photos. You’re not sure where the money goes. You’d rather pay for the actual work than the agency overhead.
You've been burned by a cheap build
Hired a freelancer or platform that promised the world for €500. The site went live, looked acceptable for a few months, then started breaking, slowing down, or being impossible to update. You want something that won’t end up in the same place.
You need to launch by a specific date
A product launch, a rebrand, a conference, an end-of-financial-year deadline. You need someone who can scope the project honestly against the date and tell you upfront if it’s not realistic, rather than discovering that in week ten.
The current site has been patched for years. Every change takes longer than it should. You’re not sure if you should rebuild or maintain – and you want someone who’ll tell you straight which one makes sense.
Your current site doesn't reflect what your business is now
The business has grown, the offer has changed, the brand has evolved. The site is two product lines and one rebrand behind. You don’t want to relaunch every two years – you want to build the next one to last.
What's in a build
Discovery and scope
Before any design happens, we figure out what the site needs to do. What’s the business goal, who’s the audience, what’s the team going to maintain, what’s realistic for the timeline and budget. The estimate comes out of this conversation, not before it – I won’t quote a number until I understand what I’m quoting on.
Design coordination
I’m a developer who handles the build, but I stay your point of contact for design too. For simpler sites where the design is largely template-based, I’ll execute the design work directly. For projects that warrant a real designer, I coordinate with designers I trust. Either way, you don’t manage the design handoff – I do.
Development
The actual build. Page builder of choice (more on that below), the templates and layouts, the content management setup, the forms and integrations. Built so your team can update content without breaking layout, without needing a developer for every change, and without the editor sadness that comes from over-engineered builders.
Performance from day one
Performance isn’t a thing you bolt on at the end. Image optimisation, asset discipline, caching configured properly, hosting recommended for the actual load, Perfmatters to disable scripts and styles where they don’t belong – all of it built in from the start. By launch, the site should be fast. Three years later, after content and plugins accumulate, it should still be fast. That’s what monthly maintenance handles.
SEO foundations
On-page SEO baked in as standard – title tags, meta descriptions, heading structure, schema markup, internal linking, XML sitemap, Search Console setup. The technical foundation that gives your content a fair chance to rank. Content marketing and link building are out of scope and I can recommend specialists.
Forms and integrations
Contact forms, newsletter signups, lead capture, conditional forms with logic, file uploads, payment forms for non-eCommerce contexts. Formidable Forms for most of this – it’s stable, well-supported, and the conditional logic covers almost everything clients ask for. CRM, email platform, and analytics integrations connected as needed.
Launch
Migration from staging to production, DNS, SSL, redirects, sitemap submission, analytics verification, broken-link sweep, performance check. The boring checklist that makes a launch a non-event. Done right, the site goes live and nobody notices.
Handover
A walkthrough of the site for your team – what to update, what to leave alone, what to email me about if it comes up. Plus written documentation. If you hire someone else two years from now, they should be able to pick up the site from the documentation.
Approach
Bricks for most builds
Bricks is my default page builder. It’s developer-friendly, lean, and doesn’t add the bloat that comes with most WordPress builders. The output stays fast even with significant customisation, and the editor experience is good enough that non-technical team members can update content without breaking things.
Elementor when it's the right call
If your existing site is on Elementor, your team already knows it, or there’s a specific reason Elementor is the right tool, I’ll build there. I don’t do religious wars between builders – the right tool is the one that fits the project and the people maintaining it.
Astro and headless WordPress, where it fits
For content-heavy sites where front-end performance and developer flexibility matter more than editorial UX flexibility, Astro with WordPress as a headless CMS is worth considering. I’m currently exploring this stack and taking on the right kind of project to learn it properly.
If you’re considering headless and want to talk through whether it makes sense for what you’re building, I can have that conversation honestly – including telling you when a traditional WordPress build would serve you better.
Custom plugins where the alternatives are worse
Sometimes the available plugins do almost what you need, but not quite, and stitching them together creates more fragility than building something purpose-made. In those cases I’ll build a small custom plugin rather than glue together three off-the-shelf ones. Custom code stays in the right places (proper plugin structure, no hardcoded edits to other people’s files) so the next developer can read it.
Multilingual sites
Sites in multiple languages are a real category of work, not an afterthought. WPML, Polylang, or TranslatePress depending on the project – they’re not interchangeable and the wrong choice creates maintenance pain for years. I’ll recommend the right one for your situation and set it up properly.
Scope
eCommerce builds
Yes – eCommerce is part of WordPress build work. WooCommerce or SureCart, product setup, payments, shipping, the performance work that keeps stores fast. The eCommerce page has more detail on the specific considerations for stores, but if you’re here with an existing WooCommerce site or planning a new one, this is the right place to start.
Basic copywriting input, not full copy
I’ll tell you when your homepage doesn’t actually say what you do, when a section is buried, or when a CTA isn’t doing its job. That’s free advice during a build. Writing the actual copy isn’t my work – for substantial copy, I’ll recommend copywriters I trust.
Not design from scratch
I’m a developer who coordinates design, not a designer running brand work. For simple sites I can execute design directly from existing brand assets and references. For projects that need original brand or visual design, I’ll work with a designer – either yours or one I recommend.
Not photography
Stock photography choices and basic image selection are part of the build conversation. Original photography (product shots, headshots, branded photography) is its own work and I’ll point you to people who do it well.
Not paid marketing, not link building, not SEO content strategy
I do the technical SEO foundation. The content side, link building, and paid acquisition are different specialties and I’ll refer you to people who do that work properly.
Small presentation sites and landing pages start under €1,000 and usually take 2-4 weeks. Full company sites from €2,500, usually €5,000-€12,000 depending on scope, 6-10 weeks from kickoff. Larger or more complex projects scoped individually. Monthly maintenance retainers from €100 are available after the build completes – I keep on retainer the sites I’ve built, so I know what I’m maintaining.
Process
Step 1
You email me with what you're trying to build. A rough description of the business, the goal for the site, any deadlines, any rough budget range is enough.
Step 2
We have a discovery conversation - usually a call, sometimes an email exchange. I'll ask the questions that matter for an accurate scope, and you'll get a sense of whether we're a fit.
Step 3
I send you a written scope and quote. Fixed price for the project, timeline, what's included, what's out of scope. If anything changes during the project, the change is scoped and quoted before it starts.
Step 4
If we agree, we start. Design coordination, build phases, review milestones, launch. No surprises.
For projects, it’s a fixed scope and price. For ongoing work after launch, I move to a monthly retainer – the build comes first because I need to know the site before I can keep it running. Either way, you know what you’re paying for.
Once we start, I send regular progress updates and you review at key milestones. Two or three rounds of revisions come with the project; past that, I’ll scope extra rounds separately. When the build is complete, you get the walkthrough, the documentation, and a site your team can run.
Let's talk
Tell me what you're trying to build. I'll tell you if I can help.
A few paragraphs is enough. What the business does, what the site needs to do, when you need it live, what kind of budget you’re working with. The more specific, the easier it is for me to give you a useful response. I’ll reply within a day or two with either a clear “yes, here’s what that would look like” or a clear “this isn’t quite for me, here’s who might be better placed.”