How to Price IT Services: Models, Rates and Proposals

To price IT services well, work out your real cost per billable hour, choose a pricing model that puts risk where it can be managed, check where your rate sits in the market and present the price as clear options tied to outcomes. Most pricing problems in IT companies come from skipping the first step and guessing a rate, or from offering fixed prices on work that has not been defined yet. This guide covers each step, with rate data from the Trusted IT Firms directory to help you position yourself.

Step 1: know your cost per billable hour

Your rate has to cover far more than salaries. Add up everything the business spends in a year:

Then estimate realistic billable hours. Paid hours are not billable hours: holidays, training, internal work, sales support and gaps between projects all reduce the time you can charge for. The basic formula is:

• Break-even rate = total annual cost divided by realistic billable hours across the team.
• Target rate = break-even rate plus the profit margin you need to invest and grow.

Run the numbers for your own business. If your target rate is above what clients in your niche pay, the answer is usually to specialise, improve utilisation or change your delivery model, not to cut the rate and hope.

Step 2: choose a pricing model

Many firms combine models: a fixed-price discovery phase, then time and materials or fixed-price phases for the build, then a monthly retainer for support.

What government contracting rules teach about risk

Public procurement rules are useful here because they state plainly how each model shares risk. The US Federal Acquisition Regulation says a firm-fixed-price contract places upon the contractor maximum risk and full responsibility for all costs and the resulting profit or loss. It says fixed prices suit work where fair and reasonable prices can be established at the outset, for example because there are reasonably definite specifications or past comparable purchases.

For time-and-materials contracts, FAR 16.601 says they may be used only when it is not possible at the time of placing the contract to estimate the extent or duration of the work, or to anticipate costs, with any reasonable degree of confidence. Such contracts must include a ceiling price, and the buyer is expected to monitor the work because the model gives the contractor no built-in profit incentive to control cost.

The lessons for an IT company are straightforward:

• Offer a fixed price only after the scope is clearly defined, ideally after a paid discovery phase.
• On time and materials, agree a not-to-exceed amount per phase and report progress against it, which gives the client the control the ceiling price provides.
• Write down every assumption behind a fixed price, so changes become change requests rather than free work.

Step 3: position your rate in the market

On Trusted IT Firms, companies choose an hourly rate band for their profile. At the time of writing, 261 of the 435 published companies show a band: 133 choose $25 to $75, 92 choose $1 to $25 and 36 choose $75 to $250. The spread differs by country:

These are bands companies choose for themselves, not audited prices, but they show what buyers see when they compare vendors. Buyers can browse directly by band, for example $1 to $25, $25 to $75 or $75 to $250 per hour. If you sit in a higher band, your profile, case studies and reviews need to show why.

Step 4: estimate without underpricing

1. Break the work down into tasks small enough to estimate, including design, development, testing, deployment and project management.
2. Estimate in ranges: best case, likely case and worst case for each task.
3. Add contingency based on how uncertain the scope is, and show it as a separate line rather than hiding it.
4. List assumptions and exclusions, such as who provides content, which browsers and devices are supported and what third-party costs the client pays.
5. Define a change process: how new requests are estimated, approved and billed.

Step 5: present the price clearly

• Offer options: for example a core version, a recommended version and an extended version, each with a clear scope.
• Tie price to outcomes: explain what the client gets, not only how many hours it takes.
• Separate one-time and recurring costs, including hosting, licences and support.
• Set payment terms: a deposit, milestone payments on fixed-price work, monthly billing in advance for retainers.
• State how long the quote is valid, so you are not held to an old price months later.

Pricing support and maintenance

Support is where many IT companies quietly lose money, because it is sold as an afterthought. Price it as a service in its own right:

• Define the service: what is covered, such as bug fixes, security updates, monitoring and small changes, what is not, and the hours support is available.
• Set response times by severity: how quickly you respond to a site that is down compared with a cosmetic issue.
• Choose a structure: a fixed monthly fee for a set number of hours, a fee per user or device for managed IT, or a pay-as-you-go rate for occasional work.
• Decide what happens to unused hours: whether they roll over, expire or can be used for small improvements.
• Price out-of-hours work separately if you offer it.

Write these terms into a short service agreement so both sides know exactly what the monthly fee buys.

Handling discount requests

Buyers often ask for a lower price, and a blunt yes or no rarely helps either side. Better responses keep the price tied to scope:

• Reduce scope, not rate: offer a smaller first phase or move features to a later release.
• Trade for something of value: a longer commitment, faster payment terms or a larger initial scope.
• Change the team mix: more work done by mid-level developers with senior review, if the project allows it.
• Explain what the price covers: testing, project management and support are often what a cheaper quote leaves out.

If you do agree a discount, show it as a separate line with a reason, so your full rate stays visible for future work.

Raising rates and avoiding common mistakes

When and how to raise your rates

Review your rates at least once a year against your costs and your win rate. If you win almost every proposal, your price may be too low. Apply new rates to new clients first, give existing clients written notice before a change, and link increases to added value such as senior staff, faster response times or new capabilities.

Pricing mistakes to avoid

• Setting rates by copying a competitor without knowing your own costs.
• Fixed prices on vague scopes.
• Forgetting non-billable time, tools and sales costs.
• Discounting to win work you cannot deliver profitably.
• Hiding contingency, then absorbing overruns.
• Leaving your rate off your public profiles, so buyers who filter by budget never see you.

Show your rate where buyers compare

Once you know your rate, make it visible. List your company on Trusted IT Firms for free, choose the hourly rate band that covers most of your work and explain your pricing models in your description. Then browse the directory to see how companies in your niche present their rates.

Frequently asked questions

What is the best pricing model for IT services?

It depends on how well the scope is defined. Fixed price suits clearly defined work, time and materials suits evolving scope, and retainers suit ongoing support.

How do I calculate my hourly rate as an IT company?

Divide your total annual costs by realistic billable hours to get a break-even rate, then add the profit margin you need.

What hourly rates do IT companies list on Trusted IT Firms?

Of 261 companies that show a band, 133 choose $25 to $75, 92 choose $1 to $25 and 36 choose $75 to $250. These bands are self-selected.

Should we offer fixed prices to new clients?

Only once the scope is clearly defined. A paid discovery phase followed by a fixed-price build is a common way to manage the risk.

How often should an IT company review its rates?

At least once a year, against your costs and win rate. Apply new rates to new clients first and give existing clients written notice.

Sources

• FAR Subpart 16.2 Fixed-Price Contracts (Acquisition.gov)
• FAR Subpart 16.6 Time-and-Materials, Labor-Hour, and Letter Contracts (Acquisition.gov)