Services · 02 · Done properly
WordPress, done the engineering way.
Custom theme, a curated handful of plugins, zero page-builders - a WordPress site your content team can run and you never have to rebuild every three years.
A custom theme, a short and version-locked plugin list (the handful that don't make a mess in year three) and no page-builder. Your content team keeps the CMS they know, and the site doesn't need a full rebuild every three years. Jølstad's funeral planner has run on WordPress and a custom plugin since 2016.
Pick this when
- Content is the product - marketing site, editorial, documentation, an actual shop.
- Non-developers need to edit pages without breaking them.
- You've been burned by page-builder themes and want out.
WordPress gets a bad name because most of it is built badly - a bought theme, a page-builder on top, and a plugin for every feature until the whole thing is too fragile to touch. We build it the way we build software: a custom theme, a short list of plugins we trust, and content models that fit what you actually publish.
The plugin pile is a choice, not a requirement
Every plugin is code someone else maintains on their schedule, not yours. We keep the count low on purpose - a curated, version-locked set - and write the rest as a few lines of theme code. Fewer moving parts, fewer surprises when WordPress updates, and no mystery slowdowns to debug in year two.
Your content team keeps control
The CMS your editors know stays the CMS they use. Custom fields where structure matters, plain editing where it doesn’t, and no way to accidentally break the layout. You get a site that is easy to run and does not need a rebuild every time the marketing plan changes.
- Scope / budget
- €12-55k
- WooCommerce included.
- Timeline
- 5-10 wk
- Theme to production.
- Built with
- WP · ACF · Woo
- Custom theme. No builder.
- Plugins
- ~8 core
- Curated, version-locked.
Agrosec
Complete WordPress site, built from scratch, for a grain-drying and grain-storage supplier. Composable product pages across an extensive catalogue, launched in Polish and English. Built to keep running, and it has - no rebuild.
Read the caseWhat we won't do
- Elementor, Divi, WPBakery, any page-builder. Not negotiable.
- Install twenty-four plugins to fake what a custom theme would do in fifty lines of PHP.
- Start a "WordPress SaaS." That's not WordPress. See Laravel + Vue.
Common questions
Can you take over and fix an existing WordPress site?
Yes. A large part of our work is inheriting sites, often after an agency handoff, auditing the plugin pile, and taking it back down to a short list we can maintain for years.
What about WooCommerce - can you do a real shop?
Yes, for catalogues up to a few thousand SKUs with custom rules - multi-currency, B2B pricing, configurators, integrations with ERP, payment and shipping. Above that, WooCommerce stops being the right tool and we steer you to either headless Woo (Laravel frontend, WP admin) or a different platform entirely. We’ll tell you in the first reply.
How do you handle a multi-language site?
With WordPress Multisite: one site per language, each with its own content, URLs and settings, under one install and one codebase. It is how this very site runs (infigo.pl and infigo.dev). Every string in the theme is translatable the standard WordPress way, and the content lives in the CMS, so your editors own the translations. We don’t layer WPML or Polylang on top - a translation plugin bolted onto a single site is a second content model to maintain and the usual source of broken URLs.
Do you use a page builder like Elementor or Divi?
No. On every site we have shipped, we build a custom theme and structure content with ACF Flexible Content, so editors compose pages from modules we designed. No Elementor, Divi or WPBakery.
Bring us the plan. We'll price it.
If this isn't the right pattern for you, we'll say so in the first reply.