Pricing and quotes

How much to charge for IT support

By The Microtra team · · 5 min read

Decide which promises the support fee contains

A useful IT support price begins with a service boundary. Ask which people, devices, locations and systems the client wants help with. Establish whether you are offering a one-time fix, a defined project or an ongoing support arrangement. The fee should follow those commitments before it follows a familiar pricing unit.

Describe how the client requests assistance and what response you can provide. Separate the time to acknowledge a request from a promise to resolve it. Your staffing and capacity plan must support the arrangement you sell. A clear service window gives the client a better basis for deciding than a broad phrase such as unlimited help.

Build an intake inventory you can maintain

List the devices, relevant applications, accounts and locations within the proposed scope. Record ownership and who can authorize work. Ask about existing providers and the boundaries between their responsibilities and yours. Keep sensitive access information in suitable secure systems; a pricing worksheet only needs enough detail to understand the service.

For ongoing work, identify the recurring tasks you actually intend to provide. These might include user assistance, agreed device checks or coordination with a named vendor. Give each a time and tool allowance. Keep specialized security, recovery or compliance promises within the qualifications and resources of the providers responsible for them, with appropriate professional review.

A device count alone can hide substantial variation. Shared workstations, remote users and different locations can produce different support patterns. Use the count as a customer-facing unit only after estimating the effort and commitments behind it. Record how additions or changes will affect the agreed fee.

Cost the effort and the capacity

For hourly work, include preparation, investigation, active work, documentation and client communication. Account for travel on site-based calls. For an ongoing agreement, estimate expected delivery time and the capacity held available for the service window. Time reserved for a response commitment can affect the other work you are able to accept.

List the tools and business expenses needed for the exact offer. Include your own working pay allowance, staff input, communications, professional services and administration. Where a client buys a subscription directly, distinguish it from the support you provide. Where you supply a service tool, confirm its cost and terms before using it in a packaged quote.

Example: These fictional USD figures illustrate a defined ongoing support scope, not a standard monthly fee. Expected support and administration labor cost $480, service tools cost $120, and allocated overhead is $120. Planning cost is $720. A 20% target margin gives a price of $900 by dividing $720 by 0.80. Applicable taxes require separate review.

The profit margin calculator helps you compare assumptions. Test a busier period as well as the expected workload. An agreement needs a workable way to handle unusual demand, new systems and major changes instead of relying on every client having an easy month at the same time.

Match the fee format to the service

An hourly arrangement can suit troubleshooting when the cause is uncertain. State any minimum, the billing unit and the point at which you will ask for further approval. A defined assessment can be a useful first stage when you need to understand the environment before quoting corrective work.

A fixed project fee works better when you can identify deliverables, dependencies and acceptance criteria. For a device rollout or migration, include preparation, testing, the change window, documentation and handover. Ask the client to confirm decisions and provide access before the agreed work begins. Scope changes should have an explicit route to a revised quote.

For ongoing support, explain what the recurring amount includes and how out-of-scope work is priced. A customer should be able to tell whether a request belongs under the service arrangement or needs a project decision. The pricing unit can be simple while the underlying scope remains precise.

Review risk and agreements with qualified help

Have an appropriately qualified adviser review service terms, access arrangements and promises that create legal obligations. For insurance, licensing and tax questions, consult licensed professionals, the SBA licensing guide, IRS small-business tax center and the relevant state resources. Keep general pricing advice separate from statements about compliance for a particular client or industry.

Price only the services you can substantiate. If the client needs a specialist provider, identify who will deliver that portion and obtain its scoped quote. You can still coordinate a useful service while making responsibilities clear. The quote becomes easier to assess when the client knows who is committing to each result.

For a new client, cost the initial environment review separately from steady-state support. Device records, provider handovers and an agreed list of authorized contacts can require concentrated preparation before the regular request pattern becomes clear enough to price with confidence.

Make the invoice reflect the agreement

Use service descriptions that connect to the client's approved support period, request or project stage. Keep work notes and approvals consistent with those descriptions. Where another provider charges the client directly, make that division clear in the quote so the final bill matches the purchasing arrangement.

Microtra helps with estimates, client notes, time, expenses and invoices for an IT support business. Law & professional services setup uses Case and Client; use a separate specialist support system for the technical work and service processes your offer requires.

Compare actual delivery time, tool costs and unusual requests with the pricing assumptions. Look for the particular source of variation, such as added devices or repeated unplanned site visits. Update the affected scope or allowance with the client before the next commitment. Good IT support pricing stays connected to the environment and service promise you can maintain.

A few good questions

Before you get started.

Should I price IT support per user or per device?

Choose the unit that best reflects your actual scope, then cost the service underneath it. Define shared devices, servers, locations and what happens when the client adds users or equipment.

How do I price an ongoing support arrangement?

Estimate expected work, administration, service tools and the capacity reserved by your response promise. Set service boundaries and a review process, then test the price against actual support demand.

Should a major migration be included in monthly support?

Describe project work separately unless you have explicitly costed a defined migration into the agreement. A scoped project quote helps the client understand the tasks, schedule and approval points.

How much to charge for furniture assembly

Set furniture assembly prices from product details, access, sorting, building, positioning, and packaging removal, with a fictional worked example.

Read the guide

How much to charge for stucco work

Estimate stucco prices from the repair or installation scope, substrate, finish matching, access and visits, with clear allowances for concealed damage.

Read the guide

Life coach pricing: build a sustainable offer

Set life coach pricing from preparation, session time, follow-up and capacity, with clear package boundaries and a practical way to review results.

Read the guide

Software for small business

Unleash your potential.

You do the work. Keep your quotes, invoices and business records together with Microtra. Start your 14-day free trial. No card needed.

Compare plans in USD
Start free trial