How to price your first AI service as a fixed package

A worksheet for your cost floor, your scope and your first quote, without guessing and without promising results.

By AI Service Playbook

Disclosure: The worksheet itself has no affiliate links. Near the end there's one small, labeled box of tool links (Make, HighLevel and ElevenLabs), and I may earn a commission if you purchase through my link, at no extra cost to you. There are no example prices in this guide, on purpose: your price depends on your market, your costs and your client, and a number copied from the internet can easily be wrong for all three.

"How much should I charge?" is usually the first question people ask when they start selling AI or automation services, and the answers online tend to be either a single magic number or a vague "charge your worth." Neither helps you write a quote on Tuesday afternoon.

This guide gives you a repeatable way to arrive at a price for one clearly defined service. It won't tell you what you'll earn. It will help you avoid the two most common mistakes: pricing below what the work actually costs you, and promising outcomes you can't control.

Why a fixed package beats an hourly rate

When you bill by the hour for AI-assisted work, two awkward things happen. First, the faster you get with your tools, the less you're paid for the same result. Second, the client has to guess the final bill, which makes saying yes harder.

A fixed package flips both. The client sees one clear price for one clear result, and you benefit when you get more efficient. The trade-off is that you carry the risk if the job takes longer than planned. That's why the scope (Step 5) matters as much as the number.

Hourly billing still has a place: for open-ended discovery work, or for requests that fall outside a package. Just don't make it your main offer.

Step 1: Define the deliverable

You can't price something fuzzy. Write the service as one sentence:

"I deliver ___ for ___ within ___."

Then make it concrete with four short lists:

  • Included: exactly what the client receives. For example: one automated follow-up email and one text message for new web-form leads, a one-page delivery note, and a 30-minute handover call.
  • Not included: the things they might assume. For example: writing new website copy, buying software on their behalf, or ongoing changes after handover.
  • Turnaround: how many working days from receiving everything you need.
  • Revisions: a fixed number of revision rounds, and what counts as a revision versus a new request.

If you find it hard to fill in these lists, the service isn't ready to sell yet. That's useful to discover before a sales call rather than during one.

Step 2: Work out your cost floor

Your cost floor is the price below which you lose money or work for free. It's not your price. It's the line you don't quote under, however nervous you are on the call.

2a. Count all of your hours, not just the build

Beginners usually count only the time spent building. A realistic estimate includes:

  • The sales call and writing the proposal
  • Collecting logins, files and approvals from the client (often slower than you expect)
  • The build itself
  • Testing with sample data, and your quality check
  • Revision rounds
  • Writing the delivery note and running the handover
  • Invoicing and admin

If you've never delivered this service before, you're guessing. Build a sample for a made-up business first and time yourself honestly. Then add a buffer for the unknowns, because first deliveries almost always take longer than a practice run.

2b. Add your hard costs

List every cost the job creates: software subscriptions (or the share of them this client uses), usage fees such as text messages or AI credits, payment-processing fees, and anything you set aside for taxes. Look up each tool's current price on its official pricing page rather than relying on a blog post or video. Prices change.

2c. Put a value on your hour

Decide what an hour of your time needs to be worth for this business to be worthwhile compared with your other options. Only you can set this number. Write it down before the call so the client's reaction doesn't set it for you.

Cost floor = (total hours × your hourly value) + hard costs + buffer

Step 3: Understand what it's worth to the client

Your cost floor is about you. The other side of the price is about the client: what the problem costs them today. Don't guess this or invent it. Ask. Good discovery questions include:

  • "What happens to a new enquiry today, step by step?"
  • "Roughly how many enquiries do you get in a normal week?"
  • "How much time does your team spend on this each week?"
  • "What happens when someone doesn't get a reply?"

Use the client's own answers, in their own words, when you explain your price. "You said your office manager spends a few hours a week chasing these" is honest and concrete. "This will make you X more revenue" is a promise you can't keep, so don't make it.

If the problem is small for this client, a lower-priced, simpler package may fit better, or the service may not be right for them at all. Saying so builds trust.

Step 4: Choose a package shape

Three shapes cover most starter AI services:

ShapeHow it worksGood for
One-off setupOne fixed price for building and handing over a defined deliverable.Content cleanup, message templates, a single automation the client will own and run.
Setup + care planA fixed setup price, plus an optional monthly fee for monitoring, fixes and small changes.Automations that depend on other apps, which can break when those apps change.
Monthly deliverableA fixed monthly price for a repeating output, such as a monthly report or a set number of content pieces.Services the client needs again and again.

For a care plan, write down exactly what's covered (for example, "fixing the workflow if a connected app changes" and "up to two small text edits a month") and what isn't. "Unlimited support" sounds generous and turns into unpaid work.

Some people offer three tiers of the same service. That can work, but only once you've delivered the basic version and know what clients actually ask for. One clear package is easier to sell and deliver at the start.

Step 5: Write the scope in plain language

Turn Step 1 into a short scope section for your proposal. Keep it to one page. It should cover the deliverable, what's included and excluded, turnaround, revisions, what you need from the client and by when, payment terms (for example, part up front and the rest on delivery), and who owns the finished work and accounts.

Also say where AI is used and that a person reviews every output before it reaches the client or their customers. It sets honest expectations and it's part of what you're selling.

Step 6: Quote, listen and adjust

Your first price is a hypothesis. After each proposal, note what happened in your prospect tracker:

  • Did they accept, decline, or go quiet?
  • If they declined, was it the price, the timing, or the service itself?
  • After delivery: how many hours did it really take compared with your estimate?

If every prospect says yes instantly, your price may be low. If the job took far longer than planned, fix your estimate or your scope before the next quote. Change one thing at a time so you can tell what made the difference.

The full worksheet (copy it)

Copy this into a document or spreadsheet and fill it in for one service:

SERVICE I deliver ____________ for ____________ within ____ working days. INCLUDED - ____________ - ____________ NOT INCLUDED - ____________ REVISION ROUNDS: ____ HANDOVER: ____________ HOURS (estimate) Sales call + proposal ......... ____ Collecting access/files ....... ____ Build ......................... ____ Testing + quality check ....... ____ Revisions ..................... ____ Delivery note + handover ...... ____ Admin + invoicing ............. ____ TOTAL HOURS ................... ____ MY HOURLY VALUE ............... ____ HARD COSTS (tools, usage, fees) ____ BUFFER FOR UNKNOWNS ........... ____ COST FLOOR = (total hours x hourly value) + hard costs + buffer = ____ CLIENT'S OWN WORDS ON THE PROBLEM "______________________________________________" PACKAGE SHAPE: one-off / setup + care plan / monthly deliverable CARE PLAN COVERS: ____________ DOES NOT COVER: ____________ FIRST QUOTE: ____ (never below the cost floor) RESULT: accepted / declined (why?) / no reply ACTUAL HOURS AFTER DELIVERY: ____

Pricing traps to avoid

  • Guaranteeing results. You control the quality of what you build, not the client's sales. Promise the deliverable, not the outcome.
  • Revenue-share deals as your only income. Some trainings teach taking a percentage of sales your system generates. It can sound attractive, but you depend on the client's tracking, honesty and sales skills. If you try it, understand the risk and put the terms in writing.
  • Starting work before payment terms are agreed. Get a signed scope and any upfront payment first.
  • Absorbing tool costs silently. If a service needs a paid tool, either the client pays for it directly in their own account, or the cost is in your price.
  • Discounting to win the first client. A small discount for a clearly labeled pilot can be fine. Just write down the normal price on the proposal so the next quote isn't awkward.