What a Web Developer Course Really Costs, and What You Are Actually Buying

The call lasts forty minutes.

The advisor is well prepared, friendly, asks the right questions about your background and makes you feel understood, at ease.

They talk about placement rates, partner companies, a method. The price of the web developer course arrives at minute thirty-eight, by which time you have already decided.

That sequence is not an accident: it is designed.

And it works, because by then you are weighing a sum of money against the wish to change your life, not against what that money actually buys.

The people who write to me after spending it almost never complain about the quality of the lessons.

They complain about something else: having paid for something they believed was included and was not.

A web developer course is one of the few large purchases people make without knowing what they are buying.

Nobody would sign a mortgage without looking at the interest rate, yet almost everyone signs up to a training programme costing thousands without once asking who will review their code, and how often.

This article is about money.

What a web developer course really costs, what sits inside the price, which costs never appear on the quote, how job guarantees, official accreditation and funding schemes work, and which questions take an offer apart before you sign.

It is not about which course to choose in the abstract, nor about how much you earn afterwards: there are other pages on this blog for that, linked where they are useful.

It is about the part nobody explains to you, namely how to assess a training investment with the same cool head you would bring to any other purchase of that size.

Fair warning: you will not find the phrase "training is always an investment" in here. It is the kind of statement that suits whoever is selling, myself included.

Training is an investment when it is done well, and a straight loss when it is done badly, exactly like everything else.

What a web developer course costs, and why the price tells you almost nothing

Intensive bootcamps in Italy cost between 5,000 and 15,000 euros.

It is the only reference figure the industry offers, and on its own it lets you decide nothing, because that range contains products with nothing in common.

The reason is a piece of basic economics nobody ever mentions: recording a lesson costs money once, looking at your code costs money every time.

A recorded video has a fixed production cost and a distribution cost close to zero.

Whether a hundred people watch it or ten thousand, nothing changes for whoever produced it.

A professional who opens your project, reads it and explains where you went wrong costs exactly what their time is worth, multiplied by the number of times they do it.

Every price in this industry follows from that, and understanding it puts you in a different position when you negotiate.

When two offers carry the same price and one promises twice the hours, it is not giving you twice as much: it is telling you those hours cost less, and the hours that cost less are always the same ones, the hours in which nobody is looking at you.

Inside the price of an intensive programme there are also items that have nothing to do with your training and that nobody ever itemises: the platform, the careers service, the sales team that called you and, above all, the cost of acquiring you as a customer.

That last one deserves a moment. In an industry that competes through advertising, a substantial share of what you pay goes towards reaching the next person.

It is not a scam, it is how any market with high margins and cold selling works. But it explains why two programmes with the same content can carry very different prices: sometimes the difference is not in the teaching, it is in the advertising.

With that lens in hand, the four things on offer stop being a confusing list and become four distinct business models, each with its own logic and its own ideal buyer.

• Subscriptions to video platforms: low cost, enormous catalogue, zero individual attention. They work brilliantly for one thing, which is looking something specific up when you already know what you are after. As a way of learning from scratch they have a completion rate that the people selling them know and do not publish.
• Recorded courses with a structure: they cost more than a subscription and in return they give you an order to follow, which is worth something. The limit is the same: the material is identical for everyone, so it cannot adapt to the exact point where you got stuck.
• Intensive bootcamps: the range runs from 5,000 to 15,000 euros. What you are mainly buying here is a calendar and a group, two tools against dropping out, which is the real enemy of anyone studying alone. How much individual attention is inside varies enormously from one offer to the next, and the price does not tell you.
• Programmes with one-to-one support: they cost more for the same duration, for the arithmetical reason above. They are the only model where what you pay grows with the number of times someone looks at your work, and therefore the only one where the provider has a physical limit on how many people it can take.

That last point is also the quickest test for working out who you are dealing with.

If an organisation can take on an unlimited number of students without changing anything, it is selling you material.

If it has a capacity, it is selling you somebody's time.

These are two different trades using the same vocabulary.

The practical consequence for you is a single one: price is not an indicator of quality, neither upwards nor downwards.

There are expensive programmes that are mostly marketing and cheap ones that are mostly video. Telling them apart means looking at a different number, and that is what the next section is about.

The cost per hour of attention: the only number that counts

Take the price of the course. Divide it by the hours a professional will spend looking at your work, yours, not the sample project everybody gets.

That number is the real price of what you are buying.

Everything else, however well packaged, is material that already exists and will carry on existing whether you pay or not.

Run the calculation on a real offer and the answer jumps out. A 6,000 euro programme with forty hours of individual review costs you 150 euros per hour of attention.

The same programme without individual review does not cost you 6,000 euros for zero hours: it costs you a figure that cannot be calculated, because you are dividing by zero.

Placed side by side, two offers that look like twins on the quote behave like this:

This is exactly why two people come out of apparently similar programmes with results that cannot be compared.

They did not buy the same thing. One bought content, the other bought corrections.

And the whole difference sits there, because content today is the least scarce resource on the planet.

The official documentation for any technology is free, better than almost any course and updated faster.

What remains rare, and therefore expensive, is somebody who reads what you wrote and tells you why it does not work.

When you run this calculation, ask for the number precisely and do not settle for the reassuring answer.

They are two different products that cost the provider two different amounts, and the word used to sell them is the same.

The exact questions to ask are three, and they are short: how many hours, with whom, and whether those hours are spent on your code or on an exercise identical for everyone.

If the answer comes back vague, you already have the information you needed.

An organisation that sells human attention knows exactly how much it delivers, because it is its main cost item and it keeps count.

An organisation that sells video does not.

Job guarantees: what the contract you are about to sign really promises

The job guarantee is the most effective sales argument in the industry, and I understand perfectly why it works: it removes precisely the fear that keeps you awake, spending everything and ending up where you started.

That is exactly why it deserves closer reading than any other part of the offer.

Not because there is always something wrong with it, but because it is the clause your decision rests on, and nobody decides well on a promise they have never read in full.

The point is that a guaranteed outcome, to be sustainable for whoever offers it, has to be bounded somewhere.

The boundaries always exist, they are legitimate, and they are written in the contract rather than on the sales page.

Here is what to look for, and these are things you ask in writing before signing, not after.

• Which jobs count as a job: does an internship fall under the guarantee? A zero-hours contract? A technical support role that involves no code at all? The definition of a "successful placement" decides everything, and it is almost always broader than the one in your head.
• Which salary counts: is there a minimum threshold below which an offer does not discharge the obligation? If there is not, the guarantee is satisfied by a proposal you would turn down.
• Which distance counts: do you have to accept a position in another city? Are you required to apply to a minimum number of vacancies each month to keep the right?
• What happens if you refuse: in most cases, turning down a qualifying offer ends the guarantee. That is reasonable from their point of view, and it is why the three points above matter so much.
• What you get back: is the refund full or partial, in cash or in training credit to spend with them? The second arrangement is far more common than the sales pages suggest.

None of these is a hostile question and no serious provider takes offence. On the contrary, the way they answer tells you more about their organisation than any video testimonial.

One fact remains that no clause can change, though, and it is the one that interests me most.

Even the most honest guarantee takes you into the segment of the market with room for someone who has just finished a course: small agencies, maintenance of existing websites, roles where you execute.

It is a way in, and for many people that is perfectly fine.

The problem starts when the guarantee is bought as though it were a finish line rather than a threshold, because in that segment you compete on price, and the only lever you have is your willingness to cost less than whoever arrives after you.

You have just seen that even the most honest guarantee on the market still opens the door to the segment where people compete by undercutting each other.

The question is not whether you will find work: it is which arena you enter.

On the Web Development Course we do not promise a job within six months, but we do promise that by the end you will be able to defend your technical choices in front of whoever is hiring you. That is less common than it sounds.

Our programme does not guarantee you any job: it puts you in a position to turn one down.

Accreditation and funding: when the official stamp really saves you money

"Accredited course" is one of the most misunderstood phrases in the industry, and the misunderstanding almost always favours the seller.

Accreditation is an administrative fact.

It says that a provider meets the formal requirements to deliver training and, in certain cases, to issue qualifications that carry weight where such a qualification is asked for: public-sector recruitment, points on an application, access to particular schemes.

It says nothing about how the teaching is done, who does it, or what you will be able to do at the end.

It is the same distance that separates a restaurant with all its licences in order from a restaurant where the food is good: the first is necessary, the second is why you go.

That said, there is one case where accreditation is worth real money, and it is when it opens a funding channel that would otherwise be closed to you.

The most relevant one for people already in work is employer training funds: schemes financed by a slice of the payroll contributions your company pays anyway, which can cover training for employees in whole or in part.

If you are on a payroll, your training can be paid for with money your employer is already setting aside without realising it, and in a great many small companies nobody in the back office has ever looked into it.

It is one of the few levers where asking costs nothing and the return can be the entire amount.

The question to put to your manager is short: which training fund is the company signed up to, and is there anything left in our training account.

Alongside this there are other channels that change over time and from one region to another: regional grants, training vouchers, schemes tied to youth employment or reskilling, and tax relief on training costs.

I am not giving you figures and deadlines, because they would be wrong within months, and an article that hands you a percentage that no longer applies does you more harm than good.

I am giving you the method, which does not expire: before paying out of your own pocket, always check three things:

One warning, though, because it is the mistake I see most often: funding is a terrible way to choose.

Picking a programme because it is the fundable one, rather than because it is the right one, means spending zero to get nothing.

It is still a loss, you simply do not see it leave your bank account.

How much time a web developer course actually takes

Open the syllabus of a course costing thousands and the first week is "Introduction to HTML".

The second is "Building a form with CSS".

The third is the main tags.

You are paying in euros, but the real cost of those three weeks is something else: they are three weeks of your life spent on material you can master in a few days with free and better resources.

And time, in this trade, is not a motivational metaphor.

It is the resource you are investing, because almost everyone who follows a serious programme does it while working, while raising a family, while living a life that does not pause.

The study hours you have are not elastic: they are what they are.

There is a precise commercial reason why syllabuses open this way, and it is the least noble one available. A programme has to look approachable to someone who is weighing it up, otherwise they do not buy it.

Starting from HTML is reassuring, it makes people feel they can do this, it reduces drop-out in the first weeks, which is the metric anyone selling online training watches every morning.

You pay for it later: those comfortable early weeks are the same ones missing at the end, when the topics arrive that needed time and attention, and you watch them go past in two lessons.

A programme's calendar, in short, reads like a set of accounts: you look at where the resources are allocated.

If the easy part takes a quarter of the total hours and the hard part takes a tenth, that programme is telling you its goal is to get you to the end, not to make you good.

How many hours a week does a programming course need? The sum nobody does

There is a sum almost nobody does before signing up, and it is the one that should come first: how many hours a week you actually have.

It is the number that decides whether that programme fits your life or only your wishes.

Take an ordinary week, not the ideal one you picture while signing.

Subtract work, commuting, sleep, meals, family, and those two or three hours when you are awake but your head has stopped working.

What is left is your real budget of hours, and it is almost always between six and ten, not the twenty you had in mind.

Now compare that number with the workload the programme takes for granted.

If they do not match, it is not a motivation problem and discipline will not fix it: it is an arithmetic problem, and arithmetic always wins.

The predictable result is that after six weeks you fall behind, falling behind turns into frustration, and frustration turns into yet another course abandoned halfway.

So the right question to ask during the sales conversation is not how long the programme lasts. It is how many hours a week it assumes, and what happens to someone who has half that.

A serious answer to this question exists, and it involves longer programmes with the same content.

An evasive answer is telling you that the model only works for people who are not working.

Always ask to see the full breakdown of hours before signing, not the list of topics.

Anyone can write the list. The breakdown, not so much.

If your calculation came out at six or eight hours a week, the problem is not your motivation: it is that almost no programme is built for people who work.

The Web Development Course is structured so you can fit the study around your commitments, because the people we work with have a job, a family and a life that does not pause.

Why a badly made course costs you more than an expensive one: the time spent unlearning

There is a cost that appears on no quote and that I have seen weigh more than all the others put together: the time it takes to shake off what you learned badly.

In software, habits are muscular.

After a few months you write a certain way without deciding to: you put things where you have always put them, you structure the way you have always structured, and you do not think about it, exactly as you do not think about where to put your feet going down stairs.

If you picked up those habits by copying code that worked without ever asking why it was written that way, you have built reflexes on foundations that do not hold.

And the trouble with reflexes is that studying does not correct them: they are corrected only when somebody points them out while you are using them.

Someone arriving from a year of badly made courses takes longer than someone starting from zero.

Not because they know less, but because they have two jobs instead of one: learning the right thing and stopping doing the wrong one.

The second of the two is the slow one, and it is the one nobody puts on the quote.

Set side by side, the two starting points behave like this:

It is also why the order in which you learn matters more than the quantity.

Wrong foundations do not sit quietly underneath: they hold up everything you build on top, and when they give way, so does the rest.

The economic consequence is counter-intuitive: the most expensive course is not the one that costs the most, it is the one you will have to do again.

A 1,500 euro course that leaves you with habits to unpick is more expensive than a 6,000 euro one that puts you in a position to carry on alone, and the difference is measured in months.

If you are already working and suspect you are in this situation, there is a quick way to check that costs nothing.

Open a class you wrote six months ago and try explaining out loud why every piece is where it is: why that dependency arrives through the constructor instead of being created with new inside the method.

Wherever you stop, or wherever you hear yourself say "that is just how it is done", there is a reflex rather than a choice.

The six questions to ask before signing up for a web developer course

By now you have worked out where the value sits. What remains is turning that into a conversation, because in a few days somebody will be on the phone answering everything with confidence.

These are the questions I use myself when someone sends me an offer and asks what I make of it.

They are phrased to make a generic answer difficult, and they should be asked in this order.

• Who will review my code, by name, and what have they shipped to production? Not "our team of tutors". A name, and a real system that person put online and maintained. Someone who has never handled an emergency in production can teach you the theory, not what you do when the theory runs out.
• How many hours of individual review are included, and what happens when I use them up? This is the number from the previous section. If there is no number, there is no service.
• How many people does each tutor look after at the same time? This is the question nobody asks and it explains everything: the same promise with ten people per tutor or with a hundred describes two different products.
• Can I see the full syllabus with the breakdown of hours, before paying? A no to this question is already an answer. The syllabus is the easiest thing to show and the hardest to defend.
• What happens if I fall behind? Do I join a later cohort, get individual catch-up, or simply lose the thread while the group moves on? It is the most likely scenario for anyone studying alongside a job, and the one never discussed during the sale.
• What is not included? Asked exactly like that, blunt, without suggesting answers. It is the only question on the list with no rehearsed version, and for that reason it tells you the most about the person in front of you.

A serious organisation answers all six within ten minutes, with numbers.

Not because it is more honest by nature, but because it already knows those numbers: they are its costs, and anyone who does not carry them in their head is not selling training, they are selling enrolments.

Put those same six questions to me as well: if the answers do not add up, you have saved yourself money, which is a good outcome all the same.

You have read the six questions. Now use them on us, no discounts.

Whoever reviews your code has a name, and we will tell you which systems they have put into production; the number of hours of individual review on the Web Development Course is written down, not "included"; and how many people each tutor follows we will tell you on the phone in ten minutes.

I run the live sessions myself; that is why the capacity is what it is.

What choosing the wrong course costs: the bill run up by someone who has done three

The typical person who writes to me has not done zero courses. They have done two or three.

An annual subscription to a video platform, of which they completed eighteen per cent.

A recorded course bought on offer, finished halfway.

And one more structured programme, the real one, seen through to the end with effort and without much changing afterwards.

Added together they come to a figure that none of the three decisions, taken on its own, ever looked like.

That is how it works: nobody ever decides to spend that amount, you arrive at it one piece at a time, and every piece looked reasonable at the time.

The most expensive part is not the money, though, and this is where the bill turns serious. It is the two years those attempts took up.

Not two empty years: two years in which you studied, so with a clear conscience and the feeling of being on the right road.

It is far harder to notice you are standing still when you are moving every day, and that is exactly why the cycle repeats: the alarm never sounds, all that arrives is an interview that goes badly now and then.

If you recognise yourself in this description, there is something I want to say before going on, because it matters more than the numbers: this was not your mistake.

You bought a promise that was worded to look like the thing you were after.

The fact that you fell for it three times says nothing about you, it says something about how the message is built.

It does say one other thing, though, less comforting and more useful: the fourth attempt, made with the same criteria as the first three, will end the same way.

How to measure the return without kidding yourself

An investment is judged by its return, and with technical training almost everyone measures it in the worst possible way: by counting how much they have studied. Hours logged, modules completed, certificates collected.

These are all activity metrics, not outcome metrics, and they have the worst property a metric can have: they go up regardless, even when you are getting nowhere.

The return on a training programme is measured in one currency only: things you can do now that you could not do before, verifiable by somebody other than you.

The test is simple and you can apply it every two months.

Take a problem you have never faced, inside your field but outside the examples you have seen. Try it alone, without looking for a ready-made solution.

If you get to something that works and you can explain why you structured it that way, those two months produced value.

If you need to find somebody who has already solved that exact problem, you have accumulated material, not ability.

Applied honestly, this test exposes any programme within four months. And that is why it is worth doing early: four months can be recovered, two years cannot.

And since we are talking about money with a certain frankness, we may as well go all the way: there are situations where the right answer is to buy nothing, and whoever sells training ought to tell you what they are.

If you are already inside a company where someone better than you is willing to read your code, you already have the thing you were about to pay for.

Your problem is not buying a programme: it is organising that willingness so it becomes systematic rather than occasional, which you do by asking to be included in code reviews and bringing something to be pulled apart every week.

It costs nothing and it is worth more than any course.

If instead you have a method problem, meaning you start things and do not finish them whatever the subject, a more expensive programme makes it worse: it adds financial pressure to a mechanism that is not financial.

That gets solved first, and elsewhere.

And if the spending would put you in real difficulty, the answer is to wait.

Not out of moralising: because studying with the anxiety of having spent money you needed is the most effective way of learning nothing.

The right moment for a training investment is when you can afford for it to go badly.

There is a second indicator, less measurable and more reliable than any other: the quality of the questions you find yourself able to ask.

At the start you ask how something is done. After a while you begin asking why it is done that way and not another.

When you notice you are asking what happens to the system if the choice is that one, you have become a different person professionally, and usually you realise it before the people around you do.

On the numbers at the other end of the investment, meaning what that programme can be worth in your pay packet, I am telling you nothing here: the market bands and how to read real pay are written up in how much a web developer earns, with the figures by level.

And if what you are missing is not what to buy but in what order to study, the technical sequence with the timings is in how to become a web developer in 2026.

What I want to leave you with is one thing only, and it concerns money only in passing.

Every programme you have bought so far sold you content, and content today costs nothing.

What you have been missing, and will carry on missing until you decide to pay for it, is somebody who looks at what you do and tells you where you are going wrong.

On the Web Development Course that somebody has a name, and the hours they spend looking at your code are counted one by one.

In two years you will be two years older either way: the only variable is whether you get there with three more courses on your CV or with somebody who has taken your work apart often enough to make you good.

The criteria are the variable, not the effort.

You already have the effort.