Anti-Over-Engineering, The Lean Web Agency Approach

The industry has a complexity problem

The web development industry makes more money when projects are complex. A database that is not needed adds development hours. A CMS that the client will never log into justifies a monthly retainer. A JavaScript framework that requires a team of developers to maintain ensures the client is locked in for years.

This is not always intentional. Many agencies genuinely believe that more technology equals a better product. But for most businesses, the opposite is true. More technology means more things that can break, more things that need updating, more things that cost money every month, and a slower website that frustrates visitors.

We call this over-engineering, and we have built our practice around eliminating it.

What over-engineering looks like in practice

Over-engineering is not always obvious. It often arrives disguised as “best practice” or “future-proofing”. Here are some patterns we see constantly in projects we inherit from other agencies:

The CMS nobody uses, A business with 5 pages that change once a year was sold a headless CMS with a monthly fee, a complex editing interface, and a deployment pipeline. They have logged in twice since launch. The content could have been hardcoded for maximum speed at zero ongoing cost.

The database that stores nothing, A professional services firm has a PostgreSQL database running 24/7 on a VPS. It contains a contact form table with 47 entries and a blog with 3 posts. The database costs €20/month in hosting alone and adds 200ms of latency to every page load. A static site with a form API would be faster, cheaper, and more secure.

The framework that demands a team, A small business was built a React SPA with server-side rendering, a state management library, a GraphQL API, and a component library. The site has 4 pages. It could have been built in Astro with zero JavaScript in half the time at half the cost, and it would load in a quarter of the time.

The plugin ecosystem that becomes a liability, A WordPress site with 27 plugins, 14 of which are “required” for functionality. Each plugin is a security risk. Each update is a potential breaking change. The business pays €150/month in maintenance just to keep the plugins from causing problems. The functionality they actually use could be replicated with 200 lines of modern code.

The lean alternative

Anti-over-engineering is not about cutting corners. It is about making intentional choices. For every feature in a project, we ask one question: does this directly serve the business goal?

If the answer is yes, we build it. If the answer is “maybe later” or “it would be nice”, we do not. We document it as a future option, we design the architecture so it can be added later, and we move on.

This approach produces websites that are:

• Faster, Less code means less to load. Our sites score 95-100 on PageSpeed Insights because there is nothing unnecessary slowing them down.
• More secure, Every component is a potential attack vector. Fewer components mean fewer vulnerabilities. A static site with no database and no admin panel has an attack surface of effectively zero.
• Cheaper to maintain (No plugins to update, no database to optimise, no server to patch. The ongoing cost is hosting only) typically €20/month for a managed plan.
• Easier to evolve, When the business does need more capability, adding it to a lean codebase is straightforward. Adding it to an over-engineered codebase means navigating layers of abstraction that should not have been there in the first place.

Who benefits most from this approach

The lean approach works for any business, but it delivers the most value for:

Businesses that were burned by a previous agency, You paid €15,000 for a site that takes 5 seconds to load, breaks every month, and requires a retainer to keep running. You want something that simply works. We hear this story multiple times a month.

Service businesses with stable offerings (Law firms, consultancies, clinics, accounting firms, architectural studios. Your services do not change every week. Your website should reflect that stability) not demand constant attention.

Small businesses watching their budget, Every euro spent on unnecessary technology is a euro not spent on marketing, hiring, or serving clients. A lean website is an investment; an over-engineered one is a tax.

Founders launching something new, A Launch page that does one thing well is worth more than a platform that does twenty things poorly. Start lean, prove the concept, then invest in complexity when the business justifies it.

Businesses migrating from WordPress, If you are paying monthly for a CMS you rarely use, plugins you are afraid to update, and hosting for a database that serves 10 pages, you are the textbook case for this approach.

How we decide what to build

Every project starts with a conversation about the business goal, not the technology. We ask:

1. What does this website need to achieve? (Lead generation? Credibility? Direct sales? Information?)
2. How often does the content change?
3. Who needs to be able to edit it?
4. What integrations are actually required today?
5. What might be needed in 12 months?

From these answers, we scope the simplest architecture that achieves the goal. If that means a 3-page static site with a contact form, that is what we build, and it will look premium, load instantly, and cost almost nothing to run. If it means a multi-page Platform with a headless CMS and API integrations, we build that, but only the parts that are needed, not the parts that look impressive in a proposal.

The technology choices that keep things lean

• Astro, Compiles to static HTML with zero JavaScript by default. Only adds JavaScript where interactivity is explicitly needed.
• Vanilla CSS or Tailwind, No heavy CSS frameworks. The styling is fast, maintainable, and lightweight.
• Decap CMS or Keystatic, Git-based content management with no database. Only added when the client actually needs to edit content.
• Cloudflare Pages, Free hosting for static sites with global CDN, SSL, and DDoS protection built in.
• API-first integrations, Forms, payments, and booking via lightweight APIs instead of heavy plugins.

Pricing

Lean websites start from €4,500 for a Launch page and from €8,000 for a Presence site. The price reflects the quality of the design and engineering, not the volume of unnecessary code.

For businesses that want a technical audit of their current site, to understand what is over-engineered and what can be simplified, we offer strategic sessions from €650.

Build only what matters

If you have been sold complexity that your business does not need, or if you want to start with a website that does its job without demanding your constant attention, get in touch. We will build you something lean, fast, and built to last.