I get the question more often now, and I understand it. AI generates code, writes tests, and suggests architecture in minutes. Even so, the hourly rate for experienced developers in Norway sits roughly where it has been.
My answer is that the question is the wrong one. You are not buying hours. You are buying a result. But first: the numbers.
What does a senior developer cost in Norway in 2027?
If you are budgeting development work in 2027, 1,300–1,700 kroner per hour excluding VAT is a sensible estimate for experienced developer expertise. The estimate is based on market data from 2026, not documented prices for 2027.
The consulting platform Folq publishes statistics from actual agreements in the Norwegian IT market:
- The average hourly rate for IT consultants was 1,454 kroner in the second quarter of 2026.
- The median rate for software development was 1,450 kroner from October 2025 to September 2026.
- 80 percent of developer agreements fell between 1,250 and 1,600 kroner in the same period.
The figures cover several levels of experience, not only seniors. Experience, specialisation, responsibility, and assignment length push the price up or down.
Source: Folq, Hourly rates for IT consultants, updated September 2026.
With 150 billable hours a month, the calculation looks like this:
| Hourly rate |
Per month |
6 months |
| 1,300 kr |
195,000 kr |
1,170,000 kr |
| 1,500 kr |
225,000 kr |
1,350,000 kr |
| 1,700 kr |
255,000 kr |
1,530,000 kr |
All amounts exclude VAT.
So far, this is familiar. The interesting part starts when the consultant begins using AI.
AI challenges not only how we build, but how we charge
The consulting market is built on a simple model: the consultant brings expertise and capacity, and the client pays for the time spent. The model works as long as effort and hours stay tied together.
That is exactly the link AI weakens. Where the tools actually cut the time spent, the same result can be delivered in fewer hours. Then someone has to answer an uncomfortable question:
Who should get the benefit of AI: the consultant or the client?
A worked example
A company wants to keep developing a web application, estimated at 200 hours at 1,450 kroner.
| Scenario |
Hours |
Hourly rate |
Total |
| Without AI |
200 |
1,450 kr |
290,000 kr |
| With AI, same hourly rate |
140 |
1,450 kr |
203,000 kr |
| With AI, higher hourly rate |
140 |
1,650 kr |
231,000 kr |
The 30 percent time saving is an illustrative assumption, not a documented average.
Look at the last row. The developer charges 200 kroner more per hour, and the client still saves 59,000 kroner. Both come out ahead.
I think that is where we should be heading: the developer is paid for the value created, the client pays for the result, and no one has to pretend that the hour is what is actually being sold.
But does AI actually make developers more productive?
There is reason to be critical here, and I say that as someone who uses AI every day.
In Stack Overflow's 2025 developer survey, 84 percent were using or planning to use AI tools. At the same time, 46 percent did not trust the accuracy of the answers, 66 percent were frustrated by solutions that were almost right, and 45 percent found that debugging AI-generated code could take longer.
Source: Stack Overflow Developer Survey 2025.
A controlled study from METR in 2025 found that experienced developers spent 19 percent more time when using AI tools in codebases they knew well. The study was small (16 developers, 246 tasks). A follow-up in February 2026 suggested that the developers might now be faster, but METR itself warned that the estimate was unreliable because of selection effects.
Sources: METR, Measuring the Impact of Early-2025 AI on Experienced Open-Source Developer Productivity and METR, We are Changing our Developer Productivity Experiment Design.
Google's 2025 DORA report puts it best: AI is an amplifier. Teams with sound processes and a solid technical platform see significant gains. Teams with weak architecture and weak quality assurance see their problems amplified.
Source: Google Cloud, DORA Report 2025.
That matches my experience. AI makes it faster to produce code. A person still has to make sure it is the right code, that it works, and that it solves the actual problem.
The value of a senior developer is not in the code
As more people can produce working code with AI, writing the code itself becomes a less obvious differentiator. Software development has never been only about writing code.
In modernisation work at Posten Bring, B2B solutions at TradeSolution, and e-commerce at Felleskjøpet, I have seen how much is decided by the choices around the code. How should the solution be structured? Which dependencies will cause trouble in two years? When should you build something new, and when should you keep developing what already exists?
Those judgements shape cost, maintenance, and lifespan. AI is a good sparring partner, but the person who delivers still has to assess the suggestions, understand the consequences, and stand behind the result.
I think the divide in 2027 will run between developers who produce code and developers who take responsibility for the whole.
The value of a senior developer lies not in how much code gets written, but in how many poor decisions and unnecessary hours the client is spared.
Three pricing models: choose by what you are actually buying
I do not think the hourly rate will disappear. Companies should choose the model according to what they are actually buying.
1. Hourly rate when the need is ongoing. If the developer is joining an existing team, maintaining systems, or working on continuous product development, you are buying expertise over time. An hourly rate makes sense then. The benefit of AI should show up in what gets delivered, not only be assumed.
2. Fixed price when the delivery is clearly scoped. The client knows what it will cost, and the consultant has an incentive to work efficiently. If the consultant delivers faster with AI without lowering the quality, they keep a larger margin. That is reasonable: the supplier carries the risk that the work grows. The model works poorly when the requirements are unclear or change along the way.
3. Staged delivery with cost limits. The model I recommend most often. Instead of buying six months of capacity, you split the work into deliveries with defined goals and budget limits: first mapping and technical risk, then a concrete improvement or a first version, then an evaluation before the next step. The client stays in control of cost and progress. The developer is free to use the tools that help most. It requires clear acceptance criteria, but that is a low price to pay.
Five questions to ask an IT consultant in 2027
If I were hiring a developer today, I would ask about more than the hourly rate, the CV, and the technology stack:
- How do you use AI in the development work? The way of working affects both cost and pace.
- How do you quality-check AI-generated code? Testing, security, and code review matter just as much no matter who, or what, wrote the code.
- How do you handle confidential data and source code? Which AI services are used, and what do your security requirements allow?
- How do we measure the value of the work? Agree on concrete goals: functionality, performance, technical debt, or delivery pace.
- How does the efficiency gain benefit me? The most important question. The answer does not have to be a lower hourly rate, but the consultant should be able to explain how AI affects the estimates and the result.
Will hourly rates for senior developers fall?
I do not think there will be one simple price effect. AI puts pressure on the price of standardised development work. At the same time, experience, an understanding of the system, and technical responsibility become more valuable when anyone can generate code. And many companies will use the gain to build more, not to cut the budget.
Do not judge a consultant by what the hour costs. Judge what it costs to get the problem solved, and how well the solution holds up over time.
A developer at 1,700 kroner an hour can be a better investment than one at 1,200. And the reverse can be true too.
Do you need a senior developer in 2027?
At Consulted we work with frontend, full-stack, modernisation, and technical advice. You get experience from larger Norwegian development environments in a small, direct model, working with the developer who actually builds the solution. We use AI where it helps, and we say so when it does not.
Are you considering bringing in a developer, modernising a system, or starting a new product? Tell us a little about the project, and we can have a concrete conversation about skills, scope, and delivery model.
Get in touch with Consulted or send an email to hei@consulted.no.
Frequently asked questions
What is a normal hourly rate for a senior developer in 2027?
A budget estimate is 1,300–1,700 kroner per hour excluding VAT, based on Norwegian market data from 2026. The price varies with experience, specialisation, and responsibility.
What does a senior developer cost per month?
At 150 billable hours and 1,500 kroner an hour: 225,000 kroner excluding VAT.
Should IT consultants get cheaper when they use AI?
Not necessarily per hour. If the consultant delivers the same result in fewer hours, the client pays less in total even if the hourly rate stays the same or goes up.
Is a fixed price better than an hourly rate for AI-assisted development?
A fixed price works well when the delivery is clearly defined. For ongoing product development or unclear needs, an hourly rate or staged deliveries is more flexible.
Can AI replace a senior developer?
AI makes parts of the work more efficient. Responsibility for technical decisions, understanding the system, security, and quality still sits with people.
Published November 2026. The 2027 price estimates are based on market data from 2025 and 2026. The worked examples are illustrative and do not represent documented productivity gains.