Undercharging is the most expensive mistake IT consultants make. Not because a single low quote costs you money — but because the habit compounds. Once a client knows your rate, it anchors every future conversation. Once you have built a practice around a certain price point, raising it feels like starting over.
Most IT consultants underprice for the same reason: they learned to price from other underchargers.
This is a framework for breaking that pattern.
Generate your proposal with Qwoter
Turn a 30-second brief into a polished, client-ready proposal. Built for IT consultants and agencies across APAC.
Try Qwoter freeWhy IT consultants undercharge
Before the mechanics, understand the psychology. Undercharging is rarely about not knowing your worth. It is about three things:
Fear of rejection. A lower number feels safer. If you quote $30,000 and they say no, it hurts more than if you quoted $15,000 and they said yes. But the $15,000 yes is the outcome you should be afraid of — because you just committed six weeks of work at below-market rates.
Pricing based on time, not outcome. "This will take me about 40 hours" multiplied by an hourly rate is not a project price. It is a cost estimate with no margin for unknowns, no reflection of the value delivered, and no room for the non-billable hours that surround every project.
Anchoring to the wrong market. Freelance marketplaces and junior consultants set rates that experienced IT consultants compare themselves against. They should not. Your reference point is the outcome you deliver, not the cheapest alternative.
The four pricing models — and when to use each
1. Hourly rate
Best for: Discovery engagements, advisory work, unpredictable scope.
Hourly is the simplest model to sell and the easiest to underprice. The problem is transparency — clients see every hour as a line item and start managing your time instead of your output.
Use hourly for engagements where scope genuinely cannot be defined upfront. For everything else, move toward fixed fees.
2. Fixed project fee
Best for: Defined deliverables with clear scope — web applications, system integrations, migrations.
Fixed fees require accurate scoping upfront, which is the hard part. In exchange, you take on the risk of scope overrun — which is why your fixed fee should be higher than your hourly estimate would produce.
A fixed fee signals confidence. It tells the client you have done this before and you know what it takes.
3. Monthly retainer
Best for: Ongoing support, maintenance contracts, fractional CTO arrangements.
Retainers are the most valuable model for long-term business stability. A client paying $3,000 per month provides more financial predictability than five separate $3,000 projects.
Price retainers based on committed availability, not anticipated hours. If a client needs you on-call for 48 hours per month, your retainer price should reflect the value of that availability — not just the hours you expect to use.
4. Value-based pricing
Best for: High-stakes projects where the outcome has a measurable financial value to the client.
If you are building a system that will save the client $500,000 per year in operational costs, your fee should be anchored to that number — not to your hours. Charging $40,000 for a project that delivers $500,000 in value is not overcharging. It is appropriate pricing.
Value-based pricing requires confidence in your outcome, the ability to quantify client benefit, and a client relationship mature enough to have that conversation. It is the highest-margin model and the hardest to apply consistently.
How to calculate your floor price
Your floor price is the minimum you can charge without losing money. Most consultants who underprice have never calculated this number.
The formula:
Floor hourly rate = Annual revenue target ÷ Billable hours per year
Work backwards from what you need to earn. If your target is $180,000 per year:
- Billable hours per year: Not 2,000. Account for non-billable time — sales calls, proposal writing, admin, professional development, holidays. A realistic billable target for a solo IT consultant is 1,000–1,200 hours per year.
- Floor rate: $180,000 ÷ 1,100 hours = $163/hr minimum
That is your floor — the number below which you cannot sustain your practice. Your market rate should be above this, not below it.
Run this calculation before your next proposal. Most IT consultants are surprised to discover their effective hourly rate — total revenue divided by total hours worked including non-billable — is significantly lower than their quoted rate. The gap is what you are giving away for free.
How to price a fixed-fee project
A fixed project fee has four components:
1. Base estimate Estimate the hours required for each deliverable honestly. Not optimistically — based on how long similar work has actually taken you.
2. Contingency buffer (20–30%) Every project has unknowns. A client brief always contains assumptions that turn out to be wrong. Scope creep is not the client's fault — it is the result of under-scoping. Price it in.
3. Project overhead (15–20%) Every project requires time that does not show up in the deliverable list: client meetings, status updates, revision rounds, deployment coordination. Add this to your estimate.
4. Market check Before finalising, check your number against what the market bears for this type of project. If your calculated fee is significantly below market, raise it. If it is above, review your estimate — but do not simply discount it without understanding why.
Example:
Web application development, 8-week project.
- Estimated hours: 160 hrs × $150/hr = $24,000
- Contingency (25%): $6,000
- Project overhead (20%): $4,800
- Total: $34,800
Presented to client as: $35,000 fixed fee
Note what this is not: it is not 160 hours at $150. The client does not need to know your hour count. They need to know what the project costs and what they get for it.
How to present pricing in a proposal
The way you present pricing affects how clients receive it. Three principles:
Show value before showing price. Your pricing section should come after your solution, your methodology, and your outcomes. By the time the client reaches the investment figure, they should already understand what they are buying. Price without context is just a number to resist.
Never apologise for your price. The language around pricing reveals confidence. "Our investment for this project would be $35,000" reads differently from "We would be looking at approximately $30,000 to $35,000, depending on scope." The second version signals uncertainty. Price with precision.
Offer two options, not three.
The conventional wisdom is to offer three tiers — good, better, best. In practice, three options create decision paralysis for IT projects. Two options work better: a standard scope and a premium scope. The standard scope is your recommended solution. The premium scope includes additional deliverables that address the client's stated secondary priorities.
The second option also anchors the first. A $35,000 proposal looks different when the alternative is $52,000.
Never present a single price without context. A standalone number gives the client nothing to evaluate except whether the number feels high or low. Two options with clear scope differences give them a decision to make instead.
The most common pricing mistakes
Discounting before being asked. Some consultants build a discount into their opening quote so they have room to negotiate. This trains clients to negotiate on every engagement. If your price is right, present it without a built-in retreat.
Hourly billing for fixed-scope work. If the scope is defined, price it as a fixed fee. Hourly billing on defined work transfers the risk of your own estimation errors to the client — which creates friction every time an invoice arrives.
Not revisiting your rates annually. Your rate from three years ago was priced for your skills and market position three years ago. Your rates should increase as your experience increases. If you have not raised your rates in the past 12 months, you are effectively taking a pay cut every year.
Pricing to win the project instead of pricing to deliver it well. A project priced too low will be delivered under pressure. You will cut corners you should not cut, resent the client, and damage a relationship that could have been profitable long-term. Price to deliver excellent work.
Before the next proposal goes out
Pricing is inseparable from how your proposal is structured. A well-priced project presented in a poorly structured proposal still loses. The pricing section needs to sit within a proposal that has already built the case for your solution — so that by the time the client reaches the investment figure, they are evaluating fit, not sticker price.
For the full proposal structure that sets up your pricing correctly, read our IT consulting proposal template.
Present your pricing with confidence
Qwoter generates complete IT consulting proposals — including a structured pricing section that presents your investment in context, not isolation. Try it free, no credit card required.
Try Qwoter free