Skip to content
Back

How to tell if your IT contractor is ripping you off

Mak Kordić •
How to tell if your IT contractor is ripping you off

You get three quotes for building a web app. The first is €12,000, the second €28,000, the third €55,000. All three promise “the same thing”. How is that even possible?

If you are a director or business owner without an in-house IT team, this is a frustrating position to be in. An IT contractor's price is often a black box: you don't know what you are paying for, why it costs that much or whether it should cost less. According to McKinsey, 66% of IT projects go over their original budget. That is no coincidence. It is the result of mistakes made before a single line of code is written.

This article shows you how to check an IT contractor's price, how to tell a realistic price from an inflated one, and when a cheap IT quote ends up costing more than an expensive one.

Where the problem really starts

Before we talk about prices, we have to be honest about why comparing quotes is so hard in the first place. In most cases the contractor is not the problem. The problem sits on the client's side.

Three causes come up again and again:

There is no detailed brief. Most clients come to a contractor with a general idea, not with specific requirements. “We need an app for managing orders” is not a brief. It is a topic. Without clear requirements every contractor estimates the scope differently, and you end up with three quotes you cannot compare. The difference between them is not who is better. It is who put the lowest price on what they think you wanted.

There is no IT expertise on the client's side. When someone without technical knowledge makes the decisions on an IT project, things happen: decisions are made without understanding the consequences, requirements change mid-project, and warning signs in the quote go unnoticed. Contractors know this. Some count on it. A vague requirement allows a vague quote, which then grows unchecked during the project.

There is no product discovery phase, or it was skipped. Discovery is the systematic work of finding out what to build, for whom and why, before development starts. Without it, the contractor prepares a quote based on assumptions. The client approves it based on the same assumptions. The result: a project that costs €30,000 on paper ends up costing €70,000 and does not do what it should. That is not bad luck. It is a predictable outcome.

When someone without technical knowledge and without a clear brief decides on an IT project, the difference between quotes says nothing about the quality of the contractors. It shows how much each of them allowed themselves to imagine.

Why quotes for the same project differ so much

Because they are not offering the same thing. It was never clear what the same thing actually is.

The €12,000 quote probably covers only a stripped-down version of what the brief describes. No user analysis, no interface design, no testing, no documentation. The €55,000 quote may include product discovery, UX research, iterative development, testing and post-launch support. These are not the same product, even if both say “web app” on paper.

What actually drives the price: the scope of functionality (how many screens, integrations with other systems, how complex the logic is), the quality of the process (whether the contractor does discovery, testing and code reviews), the experience of the team (senior developers in Western Europe cost €80 to €100 an hour, while juniors in Eastern Europe cost €25 to €45), and the long-term costs the quote does not mention (maintenance, technical debt, vendor lock-in).

A cheap quote that leaves out product discovery with user experience work, and testing, is like a cheap building project without structural calculations: you pay more in the end.

5 signs your IT contractor may be ripping you off

One: a quote with no breakdown. If all you get is a total with no split by phase, hours or roles, you cannot know what you are paying for. Any serious contractor can explain how many hours go into design, how many into development and how many into testing. If that is missing, ask why.

Two: a timeline with no reasoning behind it. “We'll do it in three months” with no explanation of what happens in each month is a warning sign. The timeline has to be broken down into steps, and it has to include your own tasks and the dates by which you will need to respond (making decisions, preparing content and so on). If a contractor cannot explain the timeline, they probably cannot estimate the scope either.

Three: no questions. A good contractor asks more questions than you do. If they send a quote straight after the first meeting, without detailed questions about your users, processes and goals, they are not offering a solution. They are offering hours.

Four: everything is included, but the price is too low. If a €12,000 quote includes strategy, design, development, testing and 12 months of support, someone is lying. Either they will charge for extras as they go, or they will deliver half a product. According to BCG, most budget overruns come from decisions made in the early phases of a project, not the late ones.

Five: unclear code ownership. If the contract does not state explicitly that the code is yours, you will pay for every change. That is vendor lock-in, and it is one of the most common ways cheap projects turn into expensive ones.

If a contractor asks no questions after the first meeting, they are not selling a solution. They are selling hours.

How to check whether an IT contractor's price is realistic

Write a brief first. Before you approach contractors, write down the specifics: what the system has to do, who will use it, which systems it has to integrate with, and which measures will tell you the project has succeeded. Without this you cannot compare quotes and you cannot judge whether an IT contractor's price is realistic. The easiest way is to get one of the AI tools (ChatGPT, Claude and so on) to help you with it.

Ask for a breakdown. Every quote should include a split by phase (user experience, design, development, testing, launch) with the estimated effort for each. If a contractor claims to work “fixed price” without a breakdown, that is not fixed price. It is guesswork.

Compare like with like. When you collect quotes, prepare a single description of your requirements (an RFP) and send it to everyone. Without it you are comparing different interpretations of the same problem. Price differences between providers are not necessarily wrong, but they reveal different approaches that you need to understand.

Check benchmark hourly rates. In Slovenia, hourly rates for senior developers range from €60 to €100, and for mid-level developers from €40 to €70. If a quote is well below that, either juniors are doing the work or the scope has been underestimated. If it is well above, ask for the reasoning.

Consider a discovery phase. Before you sign a development contract, invest in product discovery with an independent team. Treat it as insurance, not as a cost. Discovery sets out specific requirements, which give you comparable quotes and protect you from scope creep during the project. We explain why this phase matters so much in our article on product discovery.

66% of IT projects go over budget. Most of those overruns trace back to decisions made in the first weeks of the project.

The real price of an IT project: what you can't control but can anticipate

No quote can be 100% accurate. Software development is not a building project with square metres you can measure. But the difference between a good and a bad contractor is not whether the final price matches the quote. The difference is whether the contractor tells you in advance where the risks are, what will cost more if you change the requirements, and how they will communicate changes.

And the difference between a good and a bad client is whether they come prepared: with a brief, with a grasp of the basics and with someone on their side who understands what is being negotiated.

If you are looking for practical guidance on choosing a contractor, read our article on 9 pitfalls when hiring an IT contractor as well. It covers the bigger picture, from unclear requirements to hidden costs after launch.

Frequently asked questions

How much does it cost to build a website in Slovenia?

It depends on the scope. A simple brochure site costs between €3,500 and €10,000. A more complex web app with user accounts, integrations and custom logic starts at €15,000 to €20,000 and goes up quickly. The key is to understand what the price includes and what it does not.

Why do IT quotes for the same project differ so much?

Because providers interpret the scope differently, and the scope is often not defined clearly enough. Without a detailed brief and a discovery phase, each contractor estimates what they think you wanted. Before you compare prices, make sure every provider is answering the same question.

How do I know if my IT contractor is ripping me off?

The simplest way to check an IT contractor's price: ask for a breakdown by hours and phases. Check the hourly rates against the Slovenian market (€60 to €100 for a senior developer). If the contractor cannot explain why something costs what it does, or asks no questions about your needs, that is a warning sign. If you are working on a larger project, we strongly recommend hiring an independent external consultant who can comment on the quote, or join you in a meeting with the contractor and ask the right questions.

Is the cheapest quote always the worst choice?

Not necessarily, but often. A price that is too low usually means the scope has been underestimated or the costs will rise during the project. According to McKinsey, 66% of IT projects go over budget, and most overruns originate in the early phases, when the estimates were too optimistic.

We write about it. We also build it.

Let's talk about your project

A 30-minute call to understand what you're building and how cvan we help. No brief required.

Prefer email?

info@cnj.si