Blog

I built a website for five grand, but it would cost you 30 grand

We are one of Finland's leading WordPress agencies. Yet our new website does not contain a single line of WordPress. Most of the site was built by me, the CEO, and I can't code. In this article I explain what that proves and what it doesn't.

Author: Aapo Mäki, CEO / Senior Service Designer, partnerPublished 8 min read

We are one of Finland's leading WordPress agencies. Yet our new website does not contain a single line of WordPress.

It gets better. Most of the site was built by me, the CEO, and I can't write a line of code. No Figma and no traditional development project. Just me, Claude and an open fire.

The finished website scores a full 100 in every category of Google's Lighthouse test: performance, accessibility, best practices and SEO. Frankly, it is the best site we have ever had, technically speaking.

Priced on time spent, building the site would have cost about EUR 5,000. On the same basis, the same site would have cost EUR 30,000–40,000 only a year or two ago. That gap tells you the IT industry has to change.

“That gap tells you the IT industry has to change.”

So anyone can now vibe-code anything?

It is tempting to draw that conclusion. If a CEO who can't code can produce a top-class website, who needs web agencies any more?

I understand the thought. Partly it's even true. AI has made it much easier to get things done.

But the story does not end there. In fact, this is where it starts. I am a CEO, an owner and a passionate advocate for this industry. And I am more excited than ever.

What was really behind the prompts?

I didn't code the site, because I can't code. But I can do plenty of other things. I have run a web agency for years. I know practically everything about planning and building web services. Except the code itself.

Behind every prompt was an understanding of content, strategy, findability, marketing and sales, among other things. I knew what to ask for, why and in what order. I also knew what a good folder structure, security, reliability and search engine optimisation look like. I knew to demand them.

Even so, that didn't take it all the way to the finish:

  • Technology. Our CTO Antti Lassila spent a few hours finishing the site. Not days, hours. He did the checks and improvements. He also built the deployment pipelines that make it safe to develop the site.
  • Design. On my own I got the user interface and user experience a long way, even to excellent. Our designer Ella Killinen made it truly great.
  • SEO, GEO and analytics. We did the redirects, the measurement plan and the tracking set-up together with Otso and Mari, the super experts at our subsidiary Parvi.

Our site is also relatively simple. It has hardly any functionality. There is only one integration: a HubSpot form. The more complex the service, the more real technical expertise it still needs.

“AI multiplied our expertise, but it didn't replace it.”

The last few per cent that separate good from excellent were still done by people.

Why no WordPress and no Figma?

WordPress is an excellent content management tool. We will keep using it for most of our projects. But it didn't fit our own needs. We want to manage both content and development entirely through Claude, and that doesn't need a traditional content management system.

The same principle applies to our clients. We don't recommend WordPress to those who don't need it. Even though we are Finland's leading WordPress agency.

We also wanted to test whether design could be done entirely without Figma or other design software. It could. The site was designed entirely with Claude, following our existing brand guidelines.

The site's technical set-up in brief

  • Technology. Next.js and React, with styling in Tailwind CSS. Every page is a ready-made HTML file at build time, so a visitor's request doesn't start a server or a database. The site runs on servers of a Finnish hosting provider.
  • Content management. Texts are first written in a shared Claude document, which is their single source. From there they move into version control in Finnish and English. Every change is traceable. If I make a content change directly by prompting, the update also goes into that document. I am writing this article there too.
  • Deployment pipeline. Every change goes through type, quality and vulnerability checks, unit tests and a test build. After that it goes to a protected preview. Browser tests and Lighthouse tests run against the production version. Deployment stops if, for example, accessibility or SEO falls below 100 points. The previous version can be restored with one command.
  • Metrics and analytics. Tracking runs through Google Tag Manager, consent is managed with Cookie Information and visitor analytics is in PostHog. Enquiries come from HubSpot forms straight into the CRM. From the price estimator we follow which services people ask about, where they drop off and how many get in touch, without personal data.

Technology is a tool, not the starting point

Our own site is a small example of a bigger shift. In the age of AI, we have to serve our clients in a technology-agnostic way. Technology has no value in itself.

In practice this means that sometimes a service is built heavily with AI. Sometimes a project uses no AI at all. And sometimes the aim is to move fast and cheaply: first a lighter pilot to test the idea, then proper development later.

Three things guide our choices:

  1. Fitness for purpose and client satisfaction. Sometimes the right call is a top-quality build, sometimes a quick experiment on a small budget. We have to serve each client in exactly the way the situation calls for.
  2. Business. When choosing technology, what decides is what benefits this particular client's business in this particular situation. We also weigh the client's own team's ability to maintain and develop it.
  3. Security and privacy. We never compromise on this, however fast we work. Say we build a client a micro-app with AI assistance, with a calculator and a contact form. We always go through carefully how the data collected through the form is handled.

We price the value we produce, not the time spent

Our own website project shows in concrete terms why time-based billing has reached the end of the road. The price difference between EUR 5,000 and EUR 30,000–40,000 does not mean a worse result.

Quite the opposite. The value produced is the same or greater, even though the work took a fraction of the time. Had this been a client project, the price would have landed somewhere between those figures. In other words, we want to share the benefit of the productivity leap with the client.

The price is based on the value produced and our decades of expertise, not on time spent at the keyboard. The client gets the same or a better result for clearly less than before. We get fair pay for our expertise. Or the client gets a significantly better or broader build for the same budget as before. Both we and the client get more value for the money.

“Time-based billing rewards slowness. It makes no sense.”

When web services can be built ever more efficiently, time-based billing loses its meaning. That is why we don't talk about time spent but about value produced.

We also believe the industry needs to talk about prices more openly and move to fixed prices. That is why our website now has a price estimator. Tell it a few things about your project and you get a fairly accurate estimate of its price. Without hour estimates.

What would your web service cost?

The estimate takes a few minutes and does not ask for your contact details.

Get a price

So what does this really prove?

Not that anyone can vibe-code anything good. But that expertise and AI together produce more, faster and at lower cost than either does alone.

For us and our clients this is a huge opportunity. Until now, coding alone could take up as much as 70% of a project's budget. Now more and more of the work goes into what really adds value to the business. Strategy, content, findability and sales, for example.

“A WordPress house without WordPress is not a contradiction. It is our strategy in a nutshell.”

We always choose what serves the client and the situation best. That might be WordPress or something else. We price it by the value it produces. Not by how long someone sat at the keyboard.

Frequently asked questions

Can you build a website with AI without knowing how to code?

A simple one, yes. We built ours mostly with Claude, without coding. But the result did not come from prompts alone. Behind it were years of know-how in content, findability and security, among other things. Our CTO, our designer and experts from Parvi then finished the technology, design and measurement. The more complex the service, the more real technical expertise it needs.

Why doesn't a WordPress agency use WordPress on its own website?

Because we don't need it. We manage both content and development entirely through Claude, so a traditional content management system would be an extra layer. The same principle applies to our clients: we don't recommend WordPress to those who don't need it. We always choose what serves the client and the situation best.

How much does a website built with AI cost?

Priced on time spent, our own site would have cost about EUR 5,000. Only a few years ago a similar build would have cost at least EUR 30,000–40,000. We price the value we produce, though, not the time spent. You can get a price estimate for your own project with our price estimator in a few minutes.

Aapo Mäki

CEO / Senior Service Designer, partner

Want to know what your own project would cost, or how AI could fit into it? Tell me what you need and I'll get back to you.

Read more

All articles
  • Blog

    WordPress security vulnerabilities: what is actually going on?

    July and August 2026 were a historically heavy stretch for the WordPress ecosystem. Within a couple of months we saw a critical vulnerability in WordPress core itself, more than a hundred plugin security fixes, an unpatched login bypass in a popular SSO plugin and a case where malicious code reached thousands of sites straight through the official plugin directory. The National Cyber Security Centre Finland at Traficom also issued its own warning. In this article we explain in plain language what happened, why and when.

    17 Aug 2026 · 13 min read

  • Blog

    The EU AI Act gets real: what does Article 50 mean in practice?

    The EU AI Act has been talked about for a long time. Now it finally means something. And it means something for all of us who build or use AI-based digital services. On 2 August 2026, the Act's transparency obligations in Article 50 started to apply. In practice, they affect every organisation that uses AI in its website, online service or content.

    9 Jun 2026 · 3 min read

  • Blog

    How does a website move business forward?

    We say we build websites that move our clients' business forward. What does that actually mean? In practice, we first agree on the goals together with the client, such as growing the number of leads. Only then do we design and build what serves those goals. Finally, we follow the numbers and keep improving the site based on the results.

    13 Feb 2026 · 2 min read

Get a price estimate or tell us what you need

The estimate takes a few minutes and does not ask for your contact details. You can also describe your need. We will get back to you by the next working day at the latest.

Get a priceTell us what you need