WordPress Block Theme for a Newly Founded Planning Office

This post is written for founders, decision-makers, and agencies facing the platform question. Not a technical deep-dive, but a decision framework based on a real project.

The Starting Point

Planungsbüro Holzwarth is a newly founded planning office. Small team, fresh company, first projects running. Now they needed a website.

The real question wasn't "what should it look like". It was: What foundation do you use to build the online presence of a young company that's supposed to grow?

What the Client Needed

Four things, in order of importance:

1. Online quickly. A new company needs visibility. Waiting months for the perfect launch isn't an option.
2. Self-manageable. The team should be able to edit text, projects, and team photos without paying a developer every time.
3. Ability to scale. Today an online business card is enough. In two years a client portal might make sense, or a job board, or a protected document area. No one knows exactly today.
4. Affordable. Three-digit budget. A newly founded company has different priorities than five-figure website investments.

Point 3 is the strategically decisive one. The platform decision today determines how expensive scaling becomes tomorrow.

What Options Were on the Table

For a young company, several paths make sense. All have their merit, but not all fit this scenario:

• No-code platforms like Wix or Squarespace. Fast to launch, low effort, cheap to start. Great for simple sites without growth plans.
• Webflow. Strong design freedom, clean markup, popular with designers. Excellent for marketing sites and campaigns.
• WordPress with a ready-made theme. Quick start, large ecosystem, but often overloaded with features the client doesn't need.
• WordPress with a custom Block Theme. More effort upfront, but lean, scalable, and without platform lock-in.

For Holzwarth, three criteria tipped the balance: true ownership of the website (own server, own code), open growth paths (plugin ecosystem, custom development possible), and predictable costs without a tiered subscription.

That narrows the choice down to WordPress. No-code platforms and even Webflow have their strengths, but their growth paths are tied to the platform. Whoever later wants a client portal or shop often ends up rebuilding instead of extending.

Why a Custom Block Theme

Next step: ready-made theme or custom Block Theme?

Ready-made themes install quickly. But they come with many options that aren't needed at the start and clutter the admin area. Updates sometimes change design decisions, and the code is often not optimized for the specific brand.

Page builders like Elementor, Divi, or Bricks are a solid choice for many projects, especially when clients need strong visual control or when agencies without deep dev resources want to ship fast. For the Holzwarth use case they would have been overkill: the site should stay lean, have a few clearly named elements, and avoid additional plugin dependencies.

My approach: A lean, custom Block Theme with exactly the features that fit the current stage. Easily extendable when new requirements come up.

Purpose-made, Not Generic

Instead of giving the client a toolbox with many generic blocks, I built exactly the blocks that are needed right now. The site currently serves as an online business card. When more is needed later, the theme is simply extended.

The principle: A few clearly named blocks the client understands right away. No clutter, no technical jargon in the admin area.

Simplicity as a Scaling Advantage

The hardest part of this project wasn't the code. It was the reduction.

The blocks had to be simple enough that no training is needed. That means:

• No unnecessary options. Colors and fonts are fixed. The corporate design stays consistent, no matter who edits content.
• Clear labels. No technical jargon in the block interface. "Add project image" instead of "Media Library Asset Upload".
• Sensible defaults. When a new block is inserted, it immediately looks good.

The effect: When the team grows and new people manage content, anyone can get up to speed quickly. No know-how bottleneck at the web developer.

Technical Foundation

The usual standards for a clean WordPress setup:

• Fluid typography for clean display on every screen
• Locally embedded fonts, no external requests
• Optimized images, automatically converted and scaled
• Lean CSS, no JavaScript where it isn't needed

The Result

A young company has a professional website that looks like it belongs to a company that's been around longer. The team manages content itself. And the technical foundation is ready when more is needed later.

All of this for a three-digit budget.

In practice:

• No monthly platform fees
• No waiting on the developer for text changes
• Extendable through the WordPress plugin ecosystem or custom development
• When a client portal, shop, or job board is added later: the platform stays, it just gets extended

My Takeaway

The platform choice for a young company is a strategic decision, not purely a technical one. No-code tools and page builders have their merit and are the right choice for many projects. For the Holzwarth case (young company, three-digit budget, clear growth path), WordPress with a custom Block Theme was the best fit.

The underlying question for any project like this: Which growth paths do I want to keep open, and which platform gets out of my way the most?