The decision “let’s build a company website” in 2026 usually means choosing between three directions: a cheaper marketplace template, a hosted solution like Webflow, or custom WordPress. Each path has real applications in the B2B SME segment, but the differences are measurable: in three-year cost, in SEO control, in pace of CRM or ERP integration. This text shows specifically when custom WordPress wins, and when it is a waste of budget.
At our studio we have been delivering custom WordPress projects for B2B clients in DACH and Poland since 2018. Over those years we developed a set of criteria that helps a decision-maker (usually CEO or head of marketing, 40-55 years old) consciously pick a stack instead of following trends or sales pressure from agencies. Our reference stack is WordPress core, Astra Pro, custom child theme, and Gutenberg, described in more detail in our comparison of Gutenberg vs Elementor for 2026.
What “custom WordPress” actually means in 2026
Custom WordPress is not “a theme bought on ThemeForest and edited through the Customizer”. Under this term we mean a specific combination: WordPress core, a lightweight base theme (usually Astra Pro), our own child theme with dedicated CSS and Gutenberg blocks, plus optional domain plugins (WooCommerce, Germanized for DACH, Polylang for multilingual). The layout is not built in any page builder: it is coded by hand in PHP and CSS, while content is edited in the WordPress panel through Gutenberg.
The difference from a marketplace theme is fundamental. A theme bought for 60 USD on ThemeForest delivers a ready template that you can change to a certain extent from the admin panel, but every step beyond that range means bending someone else’s code. A parent theme update often breaks such modifications because it overwrites the file you edited. A custom child theme solves this problem structurally: the parent theme provides the framework and receives updates, the child theme contains only your brand-specific changes and is immune to updates.
Our reference stack looks as follows: WordPress 6.7 or newer, Astra Pro 4.x (5 KB perf footprint on the front end), our own child theme (3-8 PHP files, 2-5 CSS files, optionally JS), WooCommerce when the client has e-commerce, Germanized when the client sells in DACH (EU VAT invoices, DSGVO terms, GPSR statements), Polylang Free or Pro for multilingual versions. The whole set occupies about 70 MB on the server, loads in 1-2 seconds, gives full control over SEO, and allows for later extensions without rewriting the project from scratch. We go deeper into the technical side of the child theme in a separate guide: Astra child theme: complete guide to a custom theme.
Four scenarios where custom WordPress wins
Custom WordPress is not a universal answer to every “we need a website” request. It is, however, clearly the best choice in four typical situations we observe with B2B SME clients. Each scenario has a common feature: the client needs control over user experience and SEO, but does not need the marketing team to design layouts themselves.
Scenario 1: content editing yes, layout editing no
A classic client profile: a business owner or product manager wants to add blog posts themselves, update service descriptions, swap gallery images, sometimes add a new product page. They do not want to move sections, change margins, or decide what the hero section looks like. These are brand decisions made once every 2-3 years and require a designer, not a marketing team in ad-hoc mode. Custom WordPress with well-prepared Gutenberg blocks hits this precisely: the content editor has simple, visual tools to edit safe areas, the developer guards everything else.
Scenario 2: multilingual B2B with 3 or more languages
Polylang on custom WordPress supports any number of languages without growing licensing costs and without SEO compromises. We run our own site in five languages (Polish, English, German, French, Czech) with native hreflang support and safe metadata translations. Webflow caps multilingual at 4 languages on the Business plan (29 USD/mo) and requires Enterprise for more. Wix has multilingual built in, but the editing experience becomes tedious at three languages and over 20 pages. WordPress scales smoothly to 8-10 languages without changing the plan.
Scenario 3: e-commerce in headless model or WooCommerce with integrations
WooCommerce in a custom variant (not a “boxed” shop) gives full flexibility for integrations with warehouse systems, ERP, multi-warehouse setup, custom pricing for B2B clients, integrations with Comarch Optima or Subiekt GT. Example from our portfolio: for a DACH e-commerce client (around 50,000 orders annually) we built a custom packing dashboard as a WooCommerce plugin, integrated with Germanized and a thermal printer. Packing pace increased by 30%, error rate dropped to zero. Shopify would not allow such deep integration without moving to the Shopify Plus plan (2000 USD/mo).
Scenario 4: long-tail SEO without platform lock-in risk
Companies that earn from organic traffic (SaaS, B2B services, education, niche e-commerce) must have full control over technical SEO: schema.org, hreflang, sitemap, robots, canonical, OpenGraph, structured data. All these elements are available in WordPress with full access to code and database. On a SaaS platform like Wix or Squarespace something is always “locked” in a black box: no custom JSON-LD, limited robots.txt, rigid hero section markup. When the company grows and starts to compete in specific long-tail keywords, these limits become expensive.
Three situations where WordPress is NOT the choice
WordPress is a great CMS for content sites and e-commerce, but it does not fit every project. Three typical profiles where we propose a different stack to the client look as follows.
First: an application with user auth, dashboard, and real-time data (e.g. B2B client portal with live order status, booking calendar, analytical cockpit). Here we recommend Next.js with Supabase and deploy on Vercel. This stack provides native TypeScript typing, Row Level Security on the database, built-in auth, and real-time components without fighting WordPress REST API. We have been launching Next.js plus Supabase projects since 2025 as a parallel default next to WordPress, described on our stack page.
Second: a simple, heavily marketing landing page for a single ad campaign (Google Ads, Meta Ads, LinkedIn). If the page is to live 3 months, be quickly iterated from the marketing team’s perspective, and does not need to be integrated with the rest of the company ecosystem, tools like Framer or Webflow are fully acceptable. Implementation time drops from 5 weeks to 5 days, and the 3-year cost of ownership does not matter, because the page probably will not survive three years.
Third: e-commerce at extreme scale, over 500,000 SKUs or over 50,000 orders monthly, with multi-million budgets for infrastructure. In this category WooCommerce starts to require aggressive database optimization (sharding, custom indexes, dedicated MariaDB servers), and Shopify Plus or a dedicated stack like commercetools does it cheaper and less painfully. This is, however, the scale that maybe 1% of SME clients hit.
Costs: how much custom WordPress for a B2B company really costs
Custom WordPress pricing is not “from 5,000 PLN”, as you sometimes see in ads. Real ranges for a solid B2B SME project are 8,000 to 25,000 PLN, depending on scope. The breakdown below shows where these numbers come from (data averaged from 20+ projects in our studio since 2018).
- Discovery and brief (8-16 hours, 1,200-2,400 PLN): client conversations, analysis of the current site, identification of business goals, sitemap, technology decisions.
- Design and mockups (16-40 hours, 2,400-6,000 PLN): only if the client does not have own mockups. Work in Figma, wireframes plus hi-fi mockups for 3-5 key templates.
- Child theme build and blocking (40-80 hours, 6,000-12,000 PLN): coding the custom child theme, custom Gutenberg blocks, Astra Pro integration, performance tuning (Lighthouse 90+).
- Content migration and rollout (8-24 hours, 1,200-3,600 PLN): import existing content, set up categories, tags, menu, footer, contacts.
- QA, deploy, documentation (8-16 hours, 1,200-2,400 PLN): cross-browser tests, accessibility, SEO baseline, deploy to production, documentation for the content editor.
The sum for a “minimal” project (client provides content and design) comes to around 8,000 PLN. For full scope with design plus content plus QA we reach 15,000-18,000 PLN. Multilingual adds 25-30%, e-commerce with WooCommerce adds 40-60%, integration with the client’s ERP adds another 5,000-15,000 PLN (depending on REST API complexity). We prepare a specific quote for your project after a short brief, described in more depth in our text on factors influencing the price.
What this quote does NOT include: hosting (200-600 PLN/mo for a solid managed WordPress host like Cyber Folks or Hetzner with CyberPanel), SSL (usually free Let’s Encrypt), plugin licenses (Astra Pro 60 USD/yr, Germanized Pro 79 EUR/yr if DACH, Polylang Pro 99 EUR/yr if more than 3 languages). Total license overhead for a typical B2B project with multilingual is around 250-400 EUR/yr.
Our stack: why Astra plus Gutenberg plus child theme
Every webdev agency has a favorite stack, but the choice should not be a matter of aesthetic preference. It should be justified by numbers and client scenarios. We propose Astra Pro plus Gutenberg plus a custom child theme as standard, because this combination really wins in three criteria: performance, long-term maintenance, multilingual compatibility.
Astra Pro is a lightweight theme framework whose front-end footprint is around 5 KB of gzipped CSS and 0 KB JS on the homepage (if you don’t activate add-ons). For comparison, Divi or Avada generate 150-300 KB CSS plus 200+ KB JS per view. Astra Pro also provides a Header Builder and Footer Builder built in block architecture, which cooperates well with Gutenberg.
Gutenberg as an editor is part of the WordPress core, so there are no additional license costs and no risk that the plugin will disappear from the marketplace. Block patterns and reusable blocks give the content editor ready templates that speed up work 3-5 times compared to an “empty editor”. Custom blocks (the ones we code in the child theme for a specific client) allow us to create dedicated components: “case study tile”, “pricing table”, “team member card”, which the editor picks from a list and fills without risk of breaking the layout.
NO ELEMENTOR philosophy at our studio is a decision from April 2026 and has three justifications: first performance (Elementor adds 200+ KB JS per view, vs 0 KB in Gutenberg), second security (4 critical CVEs in Elementor Pro in 2024-2025), third lock-in (Elementor to Gutenberg migration = 60-80% of the project from scratch). For clients who absolutely need self-edit of the layout, we propose Bricks Builder (10-20 KB JS, 60 EUR/yr, no history of vulnerabilities), not Elementor.
Decision checklist: 8 questions before starting a project
Before you order custom WordPress (from us or from anyone), go through these 8 questions. The answers will help steer your conversation with the agency towards real scope, instead of listening for 30 minutes about “enterprise-class solutions”.
- Who will edit content after launch? One marketing person, an external copy agency, or a team of 5? This affects how much we have to protect the layout from accidental destruction.
- Do you need custom user roles? E.g. a B2B portal for resellers with special prices, a client panel with order history, access to PDF certificates. This grows scope by 30-50%.
- Multilingual day-1 or later? If day-1, we plan the architecture with Polylang from the start. If “maybe in a year”, we build in a way that allows adding it later without rewriting.
- What integrations with existing systems? CRM (Pipedrive, HubSpot, Salesforce), ERP (Comarch, Subiekt), email marketing (Brevo, Mailchimp), payment gateway. Each integration is another 4-20 hours of work.
- Self-host or managed hosting? Self-host (Hetzner VPS, OVH) gives full control and a cost of 50-200 PLN/mo. Managed hosting (Cyber Folks, Kinsta) gives 24/7 support and a cost of 200-800 PLN/mo.
- What timeline? A solid custom WordPress is a minimum of 5 weeks, realistically 8-12 for a project with multilingual and e-commerce. The “by end of month” deadline means a quality compromise.
- What is the realistic budget? We’re talking 8,000-25,000 PLN for a typical B2B SME. If the budget is 3,000 PLN, Webflow with a ready template will be a better choice.
- Do you need a post-launch retainer? Security patches, plugin updates, minor content edits, monitoring. Our standard retainer is 800 PLN/mo, premium 1,500 PLN/mo.
These 8 questions are also a short version of the brief we usually send to the client before the first conversation. The full brief also covers questions about the competitive landscape, business KPIs, and style preferences. If you want to talk about your project, let’s start with a short conversation: contact page.
FAQ
Can I edit the layout myself in custom WordPress?
No, the layout is dev work. You edit content in the wp-admin panel through Gutenberg. This is a conscious design decision, not a limitation. In practice, 95% of B2B SME clients never try to change the layout themselves, because it requires knowledge of typography, visual hierarchy, brand consistency. You do it once every 2-3 years with a designer, not in ad-hoc mode.
How does custom WordPress compare in SEO to Wix or Squarespace?
Custom WordPress wins in three dimensions: full control over technical SEO (schema, hreflang, sitemap, robots), platform independence (when Wix raises prices or changes terms, you’re stuck), flexibility of the content model (custom post types, taxonomies, ACF). Wix and Squarespace in 2025-2026 raised the SEO baseline to “good enough” for small businesses, but for companies competing in specific long-tail keywords their limits become noticeable.
How long does custom WordPress take from brief to live?
A realistic timeline is 5-12 weeks for a typical B2B SME project. Breakdown: 1-2 weeks discovery and design, 3-6 weeks dev, 1-2 weeks content and QA, 1 week buffer for fixes and feedback. Multilingual adds 2-3 weeks, e-commerce with WooCommerce adds 3-4 weeks, integrations with the client’s ERP add another 2-4 weeks depending on REST API documentation. A shorter timeline (e.g. “3 weeks”) usually means “marketplace template, not custom”.
After launch: will I have to pay a retainer?
A retainer is not mandatory, but we recommend it for clients whose site generates revenue (e-commerce, lead gen). Our standard retainer is 800 PLN/mo and covers security patches, plugin updates, uptime monitoring, minor content edits (up to 2h/mo). Without a retainer, the client updates plugins themselves once every 2-3 months and risks that one update will break the site. Premium retainer at 1,500 PLN/mo adds ad-hoc dev (up to 5h/mo) and monthly analytics review.
How does custom WordPress prepare a site for adding an AI layer later?
Custom WordPress is a good fundamental base for later adding AI integrations, because it gives full access to the database, REST API, and hooks. Clients who start from a solid site later add automated customer support, process automation, branded chat assistants. We described this model in our text on AI implementation in a company. A site on a SaaS platform (Wix, Squarespace) limits this future layer because it does not allow deep integrations at the code level.