Opinion

Price dumping in IT: market price or a costly saving?

Last week I wrote a LinkedIn post that started an interesting discussion and even brought an interview request from the media. My point was that we IT suppliers are foolish when we sell our expertise too cheaply. Clients, on the other hand, are smart to buy quality expertise cheaply, so they're not the ones to blame. This post looks at the topic and the phenomenon more broadly.

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

What is price dumping and why does it happen?

IT pricing has been much discussed lately. Price dumping in particular tempts buyers with quick savings, but it can turn out expensive in the long run.

Price dumping means selling services below a sustainable cost level just to win a tender. In the short term it looks like an attractive way to win clients (especially ones with potential for further development). The cause is usually fierce competition. Clients also tend to decide almost purely on price.

"How can I get this done as quickly as possible?"

When the hourly rate in a long contract is too low, someone pays for it.

The supplier in my post won the tender at EUR 50 an hour. Of course, it may serve the client humbly, well and quickly for the whole contract. I'd like to believe in goodness. Still, I suspect one or more of the following will happen instead:

  • The client is served when it suits the supplier best. Many other (better paying) tasks and clients come first
  • The work is done by the cheapest possible people, such as interns
  • The work is done significantly more slowly. According to the billing reports, a one-hour task suddenly takes two, for example
  • Nothing gets done.

What is certain is that the supplier will ask itself, time and again, "how can I get this done as quickly and efficiently as possible?" Why? Because every single hour worked at EUR 50 makes a loss for the supplier's shareholders.

Is that a good thing from the client's point of view?

Tivi also wrote about it

Tivi interviewed me and wrote a story on the topic.

Tivi.fi (opens in a new tab)

Price vs. quality. Which one decides?

In public procurement, bids are usually assessed on price and quality. What varies is how much weight each one gets. Quality points cover things like references, the expertise of the people offered, the planned delivery approach and project management. If the client only wants the cheapest option, the weight of price should be sky-high.

In the example tender, price was weighted at 70% and quality at 30%. And here's the trick: the winner got the best score on price but the weakest on quality.

In most public sector tenders the weighting is clearly smarter. Price typically counts for 40% at most and the rest of the points come from quality. So the cheapest bid usually doesn't win automatically. The second or third cheapest does, if it also scores well on quality.

So my tip for clients: you get both 1) competitive bids and 2) high-quality, motivated service when you don't overweight price. Tighter budgets in this economy are understandable. But in purchases of this size, choosing the cheapest option often causes problems in the long run. In the end, it also brings extra costs.

In the end, the client may have to buy the same work again, patch the gaps or invest in fixes. That can cost more than the original "saving".

Short-term and long-term effects

In the short term, a heavy weighting on price can give the client an affordable bid and quick savings. It also raises the risk that quality, support and continuity of service suffer. The supplier simply can't afford to invest enough in them.

In the long term, a model like this can drain the supplier's resources, raise staff turnover and weaken the quality of the work. In the end, the client may have to buy the same work again, patch the gaps or invest in fixes. That can cost more than the original "saving".

We aim for sustainable pricing

Our pricing is based on experienced specialists and on careful definition, design and technical reliability. That's how we keep errors to a minimum and make sure the result matches exactly what the client needs.

We invest in testing and security so that the service lasts. The client always has a named contact person and clear response times. That holds during the project and after it, when the client moves to Care (Huolenpito). They also get a proactive partner who brings ideas for development.

We follow the industry and keep training ourselves, using AI as well, so we can give our clients the best possible value. And one client has even told us they find our meetings relaxing.

Market price is market price

We're not innocent either. We also cut our prices sometimes, for various reasons.

Right now we're working on a couple of public sector website redesigns. In both, the actual hourly rate will be about EUR 70 instead of the normal EUR 110. The difference between EUR 70 and EUR 50 matters, though: at EUR 70 we don't make a loss. At that rate we can cover the production costs of the work, such as salaries, rent and equipment.

If we had bid for those projects at the "right hourly rate", we wouldn't have got either of them. We would have lost. On price.

Looking ahead

We've always spoken openly about industry topics and about our own pricing and project models. So this felt like a topic worth keeping on our blog.

Price competition will remain part of the IT industry. But building a sustainable business, for us and for our clients, takes more than a cheap price tag on a purchase.

So, colleagues: let's not sell our expertise too cheaply.

Read more

All articles
  • 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.

    19 Nov 2026 · 8 min read

  • 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

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