💵 Pricing AI and IT services

Most new AI and IT businesses charge too little, by the hour, for open-ended work. That combination leaves them busy and broke. The fix is not a magic number. It is a structure: a paid first step, a fixed-price build, and a monthly plan, each with a written scope. This guide covers that structure, how to set the numbers, what marketplaces pay compared with local clients, and how to get paid on time.

All prices below are examples or ranges from the sources named. They are not market rates for your town. Use them to check that your own numbers are in a sensible range, then set your prices from your costs, your hours and what the work is worth to the client.

The shape that works: setup plus a monthly plan

Almost every service in this section has two parts. There is a setup: you learn the client’s process, configure tools, build automations, train staff. Then there is upkeep: apps change, logins expire, staff leave, AI models get updated, and someone has to notice when things break. Price them separately.

The setup is a fixed price for a defined result: "intake form to CRM to approved reply, tested and documented, live in two weeks." Clients like fixed prices because there is no meter running. You benefit too: as you repeat similar builds, you get faster and the price stays the same.

The monthly plan (often called a care plan or a retainer) covers monitoring, fixes, small changes, and a set amount of improvement work each month. It is the part that makes income predictable. A business with ten clients on $300 plans starts each month with $3,000 already committed before any new project.

Agency and freelancer price guides put small automation builds at about $1,000 to $5,000 and monthly plans at about $150 to $1,500. Those figures come from vendor and agency blogs, not surveys, so treat them as a rough range. Fiverr’s own cost guide lists maintenance retainers at $50 to $500 a month, which shows where the low end of the global market sits.

Value pricing versus hourly

Hourly pricing feels fair and is easy to explain. Its problem is that it punishes you for getting good. An automation that took you 20 hours the first time takes 6 hours the fifth time, and an hourly price falls by 70% just as your work gets better. It also makes clients nervous, because every question costs money.

Value pricing sets the price by what the result is worth to the client, then checks it against your costs. If a flow saves an office manager 5 hours a week, and her time costs the business about $30 an hour including payroll taxes, that is about $150 a week or roughly $7,500 over a 50-week year. A $2,500 build pays for itself in under five months, and the client can see why the price is reasonable.

Two cautions. First, the value number is the client’s to confirm, not yours to invent. Ask in the discovery session: "How many hours does this take now? What does that person cost?" Write their answer down. Second, do not put a savings figure in your marketing or contract as a promise. The FTC has brought cases against AI sellers for savings and accuracy claims they could not support. Say what you will build and what you will measure; let the client’s own numbers make the case.

Hourly still has a place: for work outside the agreed scope, for open-ended troubleshooting, and as a fallback rate written into every contract. A typical structure is a fixed price for defined work and an hourly rate for everything else.

Paid discovery

The first meeting with a serious prospect should usually be free and short: 20 to 30 minutes to see whether there is a fit. The second step should be paid. A paid discovery session (or process review, or assessment) is two to four hours where you sit with the owner and staff, map one process step by step, and hand back a short written plan: what to fix, in what order, and what each fix costs.

Charge a modest fixed fee and credit it toward the build if they go ahead. This does three things. It filters out people who want free consulting. It pays you for real work, because the map is useful even if they never hire you. And it makes your build quote accurate, because you have seen the process instead of guessing.

How to offer it. "Before I quote the build, I’d like to spend about three hours with you and Jen walking through how a new tenant inquiry moves today. You’ll get a one-page map and a fixed quote for the fixes. The review is $400, and if you go ahead with the build, the $400 comes off the price."

Packages, retainers and per-user IT pricing

Packages make buying easy. Three tiers is common: a small entry option, the one you expect most people to choose, and a larger option for clients who want more. Name them by what they do, not "bronze, silver, gold."

These are example prices for a U.S. operator selling locally, matching the sample automation page in this section. For workshops, the research behind this section found no credible source for a typical day rate, so price from your preparation time, the group size and what local trainers charge.

Retainers. A retainer is a monthly fee for a set amount of availability or work. Be specific about what it buys: response time (for example, next business day), a number of included hours or tasks, and what happens to unused hours. Rolling unused hours forward for one month is generous; rolling them forever creates a debt you will eventually have to work off for free. If a client keeps going over, move them to a bigger plan rather than billing overages every month.

Per-user IT pricing. IT support for small offices is usually priced per user per month, sometimes per device. The price covers a defined list: help desk support, account setup and removal, security settings, updates, backup monitoring. Projects (a new office, a migration) and hardware are billed separately. One 2026 vendor guide reported an average of about $145 per user per month for full managed IT, with a range of about $100 to $250, citing a survey of 412 providers and buyers. Lighter work, such as Microsoft 365 or Google Workspace administration without full support, sells for less; the research behind this section estimated $15 to $40 per user per month but found no survey for it. Set a monthly minimum so that a three-person office still covers your fixed costs.

Example: a 12-person office on a light admin plan at $35 per user is $420 a month. If two staff leave and two join, the count stays at 12. If the office grows to 15, the plan grows with it, which is one reason per-user pricing is popular with both sides.

A worked example

Take a property management office with 12 staff. The office manager spends about 6 hours a week sorting tenant inquiries and maintenance requests by hand. The owner confirms she costs about $30 an hour including payroll taxes. That is about $180 a week, or $9,000 over a 50-week year. You propose:

Your time: about 6 hours for the review, 30 hours for the build, and about 4 hours a month on the care plan, or 48 hours over the year. That is 84 hours in all, so the first year pays about $86 an hour ($7,200 divided by 84). Billed hourly at $75, the same 84 hours would have brought $6,300, and every speed-up would have cut your income further.

Two points to take from it. The client gets a price below the value they confirmed, so the decision is easy. And most of your income from this client is the care plan, so it is worth more to keep a client happy for three years than to win a large one-time build.

This example does not include your costs (software, insurance, marketing) or taxes. See Pricing and margins for how to build those in, and set aside a share of each payment for income and self-employment tax (Small business taxes).

What marketplaces pay versus local clients

Freelance marketplaces are a real source of work, but their price levels are set by global competition. Local clients who meet you, trust you and need you on site pay differently. The table compares the ranges in our research.

Platform fees come off the top. Upwork charges freelancers a variable service fee of 0% to 15% per contract. Fiverr takes 20% of each order according to third-party summaries of its terms; we did not confirm that on Fiverr’s own pages. More on choosing channels is in the launch and marketing playbook.

The gap between the marketplace rows and the local rows is the price of trust, presence and accountability. A local dental office cannot judge your automation skill, but it can judge whether you showed up, explained things clearly and answered the phone. That is what the higher price buys, and it is why selling locally is worth the slower start.

Raising prices

Your first prices will be too low. That is normal, and fixing it is routine. Raise prices for new clients first; it costs nothing to quote the next prospect 15% higher and see what happens. If most new prospects accept without hesitation, you are still underpriced.

For existing clients, put an annual review in the contract from the start ("prices are reviewed each January"). Give at least 30 to 60 days’ notice in writing, say what the new price is and when it starts, and tie it to something real: more tools covered, faster response, a year of improvements. Some owners keep early clients at the old price for a set time as a thank-you. Do not apologize for raising prices, and do not raise them in the same month a problem happened.

Signs you are underpriced: you are fully booked and still not earning what you planned; nobody ever pushes back on a quote; you dread opening the care-plan inbox. Signs you are overpriced, or your proof is weak: proposals stall after the call, and prospects ask for references you do not have yet.

Invoicing, late payment and scope creep

Get paid at the start. For builds, ask for a deposit, commonly 50%, before work begins, and the balance on delivery. For care plans, bill monthly in advance, with automatic card or bank payment if you can. Paying in advance is normal for subscriptions and owners accept it.

Invoice the same day. State the amount, what it covers, the due date and how to pay. Short terms such as 15 days are reasonable for small clients. Use your accounting software’s reminders so you do not have to chase by hand.

Write the late-payment terms into the contract. Say what happens if a payment is late: a reminder at a set number of days, a pause in non-urgent work at a later point, and a late fee only if your contract says so and your state allows it. Pausing work is usually more effective than a fee. Never hold a client’s systems or data hostage; set things up so their accounts are in their name from the start, which also keeps you on the right side of any dispute.

Scope creep is the steady addition of "small" requests to a fixed price. Every one sounds reasonable. Together they turn a profitable project into unpaid work. Three habits prevent it:

1. A written scope. List what is included and, just as important, what is not. "Includes the three flows listed. Does not include new forms, website changes or staff training beyond one walkthrough."

2. A change request. When a new request comes in, reply the same day: "Happy to do that. It’s outside this project, so it would be $X or Y hours at our hourly rate. Want me to add it?" Most clients respect this. A few will drop the request, which is also fine.

3. A home for small requests. The care plan’s monthly improvement is where small requests go. "Good idea; I’ll put it in next month’s improvement." That turns scope creep into a reason to keep the plan.

More on contract terms is in the contracts and AI rules guide and Leases and contracts.

Questions people ask

Marketplace rates and fees (Upwork, Fiverr) and the survey figure for managed IT were checked in November 2026. Most price ranges here come from vendor and agency blogs, not surveys; treat them as rough guides and check what local providers charge before you quote.