Skip to content
Back

9 pitfalls when hiring an IT contractor that will cost you time and money

Mak Kordić •
9 pitfalls when hiring an IT contractor that will cost you time and money

70% of digital projects fail: they run late, go over budget or simply do not deliver what was ordered. In the public sector the figure is even higher: 81% of IT projects in public institutions overrun their original schedule, and costs are on average three times higher than for private clients.

The figures are not new, and the reason behind them is often surprisingly similar: on one side is an IT contractor who knows exactly what they are doing. On the other is a client who does not.

And that is where the trouble starts.

Most organisations that take on digital transformation and commission websites, mobile apps or digital platforms, private companies and public-sector institutions alike, have no in-house staff who understand IT development from the inside. There is nothing wrong with that. Nobody expects you to know the difference between backend and frontend.

It is a problem, though, if you hire an IT contractor without knowing where the typical pitfalls lie. In this article we reveal nine of them, along with the questions you should ask yourself before you sign the contract.

Pitfall 1: The project brief is too general to be useful

When an organisation, be it a company, a municipality or a public institute, decides on a digital project, the first job is to prepare a requirements document: the project brief. And this is where things usually go wrong straight away.

A typical project brief for hiring an IT contractor says something like this: “We need a web app that lets users log in, view information and submit applications.” That is a description of almost any web app in the world.

A vague project brief does not protect the client. It protects the contractor. When the requirements are loose, the contractor is free to interpret them. When a disagreement comes up, they will point to what they understood. And they will be right.

A good project brief answers specific questions: Who exactly will use this? How many users at the same time? What data does the system process and where is it stored? Which scenarios are critical and which are optional? What happens when the system fails?

You should have a clear picture of these answers before hiring an IT contractor is even on the table. Without a well-prepared project brief, the quotes you receive cannot be compared with each other: each contractor will be pricing a different digital project, based on different assumptions.

In the public sector, a poor project brief has an added, legal dimension. Incomplete or imprecise tender documentation is the most common reason for an appeal to DKOM, the National Review Commission.

One bad paragraph in the technical requirements is enough for a bidder to file a request for review, and the project stops for three to six months. In the worst case, the whole procedure has to be repeated.

That is not just a delay. It is budget spent on preparing the tender, lost time for the team and political pressure that lands on the person responsible.

Pitfall 2: You went to a contractor before mapping and fixing your own processes

When an organisation comes to an IT contractor saying “we want to digitalise this process”, that is often the moment to take a step back.

Digitalisation is not a synonym for improvement. A bad process that has been digitalised is just a faster bad process. If your procedure for handling applications needs seven approvals, three printed forms and two manual email steps, and you simply move it into a web system, you have digitalised chaos, not a solution.

Before you go to a contractor, you should do process discovery: who does what, why it is done that way, where the bottlenecks are, where time is lost, where errors creep in. This is often where you find that the problem is not technical at all, but organisational. And that the right solution would take half the development and half the money.

The contractor will not do this for you, at least not unless someone asks them to. They will build exactly what you described in the project brief for the digital project, even if it is the wrong thing. Process analysis before development is one of the most important investments in digital transformation, and it can be done relatively quickly and cheaply, before you really commit to development.

The question you should ask yourselves: Before going to a contractor, did we take the time to understand our own process and check whether it even makes sense to digitalise it in this form?

Pitfall 3: Nobody set UX as a measure of success, and it will cost you dearly

This is probably the most important pitfall, and the one that gets talked about least.

When organisations in the private sector or public administration commission digital products, such as citizen portals, internal systems or mobile apps, the KPIs are typically the delivery deadline, the budget and a list of features. Nobody writes down: “The product must be easy to use for someone who is not comfortable with technology.”

And when the client does not define UX (user experience) as a measurable requirement, the contractor will not optimise for it. Why would they? It takes extra time for research, testing with real users and iterations. None of that is in the contract.

The result: systems that technically work but that nobody wants to use. An e-government service that takes seven steps to submit an application when two would do. An employee portal that works on a computer but not on a phone, even though 80% of employees work in the field. An app where you first have to work out how to use it at all.

The cost of poor user experience is not just frustration. It is measurable: lower process completion rates, higher support costs, more calls to the help desk, lower productivity, resistance to the system. In the public sector, it means citizens would rather come to the counter in person because the digital system is too much of a pain. That is not successful digitalisation. It is an expensive imitation.

Real UX is not aesthetics. It is the answer to the question: “Will this person, in this context, at this hour, with one finger on a phone, manage to complete this task?”

How do you protect yourself? Require user testing in the contract as part of the process. Require at least 5 actual end users to be involved in testing before acceptance. And require UX metrics (time to complete a task, error rate, Net Promoter Score) to be measured at acceptance.

Pitfall 4: Nobody checked for buy-in from the team

Few things are as destructive as an app your own employees do not want to use.

Internal IT solutions, from document management systems and CRMs to internal platforms and management systems, are often designed without really consulting the people who will use them every day. Nobody asked the team: how do you work at the moment? What information do you need? What takes up your time? What annoys you about the current system?

The result is predictable: employees find workarounds. Spreadsheets the system was “not supposed to need”. Emails that bypass the system. Manual procedures that run alongside the digital ones. In the end the system is paid for and maintained, yet half the team does not use it, because nobody sold it to them.

The truth is that an IT project without internal buy-in will not succeed, however good it is technically. You do not get that buy-in from a one-day training session after implementation. You get it by involving the team in discovery, design and testing before and during development.

The same goes for instructions and explanations. A system that does not come with clear, accessible instructions for every type of user will always underperform, not because it is bad, but because nobody knows how to get the most out of it.

Pitfall 5: Management does not understand technology as a tool

This may be the least noticed pitfall, because it shows up quietly: in projects that are too ambitious for real conditions; in projects that are not ambitious enough and miss the opportunity; in decisions made on the basis of marketing brochures rather than analysis.

When management does not understand what technology can and cannot do, the mistakes follow a pattern. They buy an expensive system for a problem a standard tool would have solved. They do not buy a system where the return on investment would be clear and measurable. They approve a project without understanding what is realistically achievable within the given budget.

The consequence is twofold: either over-investment in the wrong thing, or under-investment in the right one, because the director did not understand how the solution would make a key business process faster, cheaper or more efficient. Or how it could be used to deliver better, faster and cheaper services to customers and citizens.

Nobody expects every director to understand architectural decisions. What is expected, and critical to the success of the project, is that they understand what the technology solves, what the ROI is and how it can be used strategically as a business tool. Organisations that invest in this, even if only through an independent adviser who translates technical language into business arguments, make considerably better IT decisions.

Pitfall 6: When the project “ends”, the real costs are only beginning

You sign the acceptance. The contractor leaves. And a month later you find that:

  • the system does not work on a newer version of the browser

  • there is no documentation for the people maintaining it

  • for every fix or addition you have to go back to the same contractor, who now charges by the hour and at much higher rates

This is a classic case of technological dependence, or vendor lock-in, where you are forced to stay with the same contractor because only they understand your system.

Protection: At acceptance, require technical documentation, ownership of the source code, maintenance instructions and at least one handover meeting with your IT team or the new contractor. Without these, you have bought a car without the keys.

Pitfall 7: Nobody thought about technical debt and integration

Every organisation has an existing IT stack: the set of systems, tools and platforms it already uses. And every new IT solution has to fit into that stack.

This is where a common mistake happens: the contractor proposes a technology they know and can build with. The client accepts it without question. But nobody asked: is this technology compatible with the existing systems? Will the two solutions even talk to each other? What will integration cost? Would a solution built on a different technology, perhaps one already in place, be cheaper, less risky and easier to maintain?

Just as relevant is the question of technical debt: will this system be obsolete in three years? Is it modular, and can it be extended without a complete rebuild? What new technologies are coming that would solve this problem far better and more cheaply, and would it pay to wait, or to adapt?

There is no easy answer here, but it is a question every client should put to the contractor, and expect a clear, expert justification in return. A contractor who only cares about getting the digital project delivered, and not about the long-term success of your digital infrastructure, will not raise the question themselves. Technical debt does not appear overnight. It grows quietly until one day it costs more than building from scratch.

Pitfall 8: Why you cannot simply switch contractors

Dependence on a contractor often comes not from ignorance but from a contract that protects the contractor more than the client. This applies to the private sector and to public procurement alike, and in public administration, according to the OECD's findings, dependence on external IT contractors is one of the systemic challenges of the whole region.

What to watch out for: Who owns the source code? Where is the data stored and who has access to it? Is the system built on the contractor's proprietary platform or on standard technologies? What happens when the contract is terminated?

This is especially sensitive in the public sector. In its review of Slovenia's digital government, the OECD explicitly warned that dependence on IT contractors affects the transparency and functionality of systems, while contractors often invoke the protection of intellectual property.

A good contractor will have no trouble answering these questions. One who replies “that is our proprietary technology” or “we don't do that” has told you everything you need to know.

Pitfall 9: You have accepted the system. But has anyone tested it with real users?

The last pitfall is, paradoxically, the easiest one to prevent.

Before you formally close a digital project and move it into production, whether it is a solution for the public sector or for a private company, it should go through structured testing with real or representative end users. Not developers. Not the project manager. Not the director. Real users who are seeing the system for the first time.

In practice this rarely happens, because it is not in the contract, because it takes time, because the budget has run out. The result: the bugs are found by citizens trying to submit a building permit application at 10 pm from a mobile phone. Or by an employee on their first day with the new internal system. Neither of them will forget it, and your IT reputation suffers along with them.

Fixing errors after acceptance costs on average 6 times more than finding them during development. An hour of UX testing before launch saves days of firefighting after it.

Why the public sector cannot solve this problem by hiring

The logical solution would be to hire an in-house IT expert to oversee projects. Unfortunately, in the public sector that is structurally hard to do.

The public sector grades jobs by pay bands defined in legislation and collective agreements. An experienced IT architect, UX strategist or senior developer on the Slovenian market earns €2,500 to €5,000 net or more. The public sector often cannot offer them even half that within the existing bands without upsetting the pay grades of all its other employees.

The result: IT specialists in public administration are often inexperienced, overloaded with operational tasks, or long gone to the private sector.

This is not a criticism of public servants. It is a systemic reality that leaders need to recognise and make up for with outside capacity. Not with contractors who build, but with an independent partner who represents the client, oversees the work and protects the client's interests throughout the life cycle of the project.

What does it cost you to go about a project the wrong way?

Let's look at concrete numbers. They are indicative, because every project is different, but they illustrate the point.

Developing a digital portal for managing applications or services in the public sector often costs between €80,000 and €300,000. Now add the typical consequences of the mistakes described in this article:

  • A budget overrun of 50–100%, entirely typical according to public-sector data: that is €40,000 to €300,000 in extra cost

  • Fixing UX after launch, because the system was not tested with users: 20–80% of the initial budget

  • Legal consequences of ignoring WCAG, which is a legal obligation, not a recommendation: the Accessibility of Websites and Mobile Applications Act (ZDSMA) requires compliance for all public digital services, and the Information Society Inspectorate supervises it. Fines and mandatory remediation within short deadlines

  • Support and a call centre for a system users do not understand: thousands of hours a year

  • A rebuild in 3–5 years, because the system is not adaptable and cannot be upgraded (vendor lock-in)

Altogether we are talking about a difference of between €50,000 and €500,000, depending on how many mistakes were made in preparing and running the project. Nobody writes this into the cost-benefit analysis before the tender. But someone should.

According to PMI, 12% of every investment in an IT project is lost purely to poor management. On a project worth €200,000 that is €24,000 of lost money, and that is just the start, before counting delays, fixes and rebuilds.

For the public sector, add the risk of an audit by the Court of Audit. The court does not only check whether the project was completed. It checks whether public funds were spent prudently and efficiently. A project that finished within budget but that nobody uses, or a system that needs immediate fixes after acceptance, is a problem for the auditors. In that case responsibility does not fall on the organisation in the abstract. It falls on the specific person who led the project and signed the acceptance.

What good looks like

The opposite of all the scenarios described above is not a utopia. It is an approach that good digital partners practise systematically.

It starts with understanding the problem before any code is written: mapping processes, validating assumptions, talking to actual users. Then comes a clearly defined project brief that protects the client and sets measurable success criteria, including UX. Clear milestones with realistic estimates. Transparent communication about risks. A handover with documentation and no hidden dependencies. And testing with real users before the product goes into production.

This approach is not more expensive. It is cheaper, because it prevents costly fixes and delays. And that is exactly what digital transformation that really works looks like: not a project with every box ticked, but a change felt by the people who use it every day.

It does require a partner who can say no, who challenges you before agreeing, and who understands that the goal is a working product for real people, not a completed project.

Does this sound familiar?

Hiring an IT contractor is an investment of public money that can, and must, be protected. Most of the problems described in this article arise not because the contractor is incompetent or dishonest, but because the conditions, expectations and criteria were not clearly defined at the start. And because there is nobody on the client's side who knows how to ask the right questions, spot the risks and protect the public interest, rather than just check whether the project was formally completed.

If you are facing a digital project and have no in-house experts to guide you through it, consider an independent partner who represents you on the client side: in preparing the project brief, evaluating quotes, overseeing development and accepting the result.

Do you recognise yourself in what you have read?

If you have a project that seems to be heading the wrong way, or you are about to go to tender and want to make sure that what you have read here is not repeated, call us.

We offer a free 45-minute consultation, with no obligation and no sales pitch. Just an honest conversation about your project and where the real risks lie.

Book a free consultation

Frequently asked questions (FAQ)

Why do IT projects run late? The most common reasons are a vague project brief at the start, a lack of clear milestones with penalties, poor communication between client and contractor, and changes to requirements during development. Global statistics show that 70% of IT projects fail to meet their original goals.

What is UX and why does it matter for digital projects? UX (user experience) describes how simple and intuitive a system is for the actual end user. Poor UX means the system technically works but nobody wants to use it or knows how to, which leads to lower productivity, higher support costs and resistance to the system.

Why do processes need to be put in order before digitalisation? Because digitalisation does not improve bad processes, it only speeds them up. Every step that is redundant or illogical in the analogue world will cause the same problems in digital form, only faster. Process discovery before development often reveals that the right solution is much simpler and cheaper than the one originally planned.

How do I check whether an IT quote is realistic? Ask for a cost breakdown by feature, not just a total price. Compare at least three quotes and ask each bidder about their development methodology, how they communicate and who is liable for delays. An unexplained price difference between quotes is always a reason for a more detailed conversation.

What does technical debt mean in IT development? Technical debt builds up when quick or short-sighted decisions made during development later make maintenance, upgrades or integration with new systems harder. A good contractor will warn you about technical debt and propose architectural decisions that hold up in the long term, not just ones that work today.

How do I make sure employees will actually use the new system? Involve the team from the discovery and design phase, not only at rollout. Provide clear instructions and explanations for every type of user. And choose a contractor who understands that success is not “the system is built” but “people are happy to use the system”.

What does vendor lock-in mean in IT development? Vendor lock-in is a situation where you are forced to stay with the same IT contractor because only they understand and maintain your system, either because you have no contractual ownership of the code or because the system is built on proprietary technology. Protection: ownership of the source code and documentation are a contractual requirement, not an option.

How much does it cost to develop a web app in Slovenia? Prices vary with complexity. A simple website with integrations starts at around €10,000, a mobile app at around €20,000, and complex portals and platforms range from €50,000 upwards. Extremely low prices are often a warning sign, not a bargain.

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