How to price AI services: value-based pricing

Time: about 30 min reading + 35 min practice

Every dollar amount in this lesson is a made-up example to explain the method, not an income forecast and not market data. Set your own price for your own market; you already saw the basic step-by-step version in the lesson How to set a price.

The gist

A mechanic charges $200 for a repair that took him 20 minutes. You're not paying for his time. You're paying for a car that runs. Value-based pricing (pricing based on the value you deliver, not on your costs) follows the same logic: you price by the result the client gets, not by the hours you spent.

Key concepts

• Value-based pricing: price by the result, not by the time
• First projects: a free trial and a money-back guarantee
• Scope and contract: put everything in writing before the work starts
• The growth path: freelancer → consultant → agency

Theory

The core principle: price by the result

🎨 Picture this: value-based pricing is like selling a house instead of bricks. Ten thousand bricks are boring to count. A $200K house is clear, and people want it. You're selling the result, the house, not the bricks.

Why hourly billing holds you back:

If you charge $50/hour and a job takes 10 hours, you get $500. If tomorrow you become twice as efficient (with AI tools, that happens) and the job takes 5 hours, you get $250. Your income went down even though you got better.

How value-based pricing works:

A made-up example calculation:

• The client spends 10 hours a week processing orders by hand
• Their time is worth $50/hour
• Yearly impact: 10 × 50 × 52 = $26,000 a year
• You build the automation for $3,000 (about 12% of the yearly impact; more on the 10-30% range below)
• Payback for the client: about a month and a half, and the savings continue after that
• You spent 15-20 hours on the work = an effective rate of $150-200/hour

The client is happy: they get a strong ROI (return on investment). You're happy: your effective rate is well above the $50 an hour from the hourly example. Everybody wins.

Rates for "writing prompts" and rates for building systems (automations and AI agents, meaning programs that carry out a task step by step on their own) can differ several-fold: a client values a system that works without you more than a one-off piece of text. These lessons are about the second path: building systems, not just writing prompts.

How to calculate the value for the client:

Step 1: Find what you're automating
For example: handling incoming email requests

Step 2: Measure the current cost
Hours per day × days per month = X hours/month
X hours × hourly cost = Y dollars/month

Step 3: Estimate how much the automation covers
Full replacement = 100% savings
Partial (AI helps, a person finishes the job) = for example, 60-70% savings

Step 4: Calculate the yearly impact
Y × the savings share from step 3 × 12 = yearly value

Step 5: Set your price at 10-30% of the yearly value (a rule of thumb, not a law)
(10% = an aggressive price for a quick sale, 30% = when the ROI is obvious and fast)

First projects: lowering the barrier to entry

🎨 Picture this: your first client is like your first jump off the high dive. Everyone knows there's water down there, but it's still scary. A money-back guarantee is the lifeguard on duty: it's what makes the jump possible.

First clients are afraid of taking a risk. "What if it doesn't work? What if I'm paying for nothing?" Easing that fear is your job.

Option 1: a free trial

"I'll build the first version for free. We'll launch it and you'll see it in action.
If you like it and it saves you time, we'll agree on payment.
If not, the automation is still yours, no strings attached."

What it gives you:

• A real project for practice and for your portfolio (your collection of finished work)
• A testimonial from a real client
• A good chance the client pays once they see the result (though not a certainty)

What it gives the client:

• Zero risk
• A concrete result before any decision about money

Option 2: a money-back guarantee

"If after 30 days you don't see any time savings,
I'll refund the full amount, no questions asked."

That sounds risky for you. But when the product really works, refund requests tend to be uncommon. The guarantee removes the fear before the purchase, not after it. Only offer it if you can afford to honor it.

A price ladder for your first projects:

The amounts depend on your region, niche and market; for a concrete example with numbers, see the Quick reference below (made up).

Scope and contract: protection for both sides

🎨 Picture this: scope creep (the amount of work quietly growing beyond what you agreed to) is like a home remodel without a written estimate. "While we're painting, let's do the ceiling too." "Since we're doing the ceiling, let's redo the floor." A month later the bill has tripled, the timeline has doubled, and everyone's unhappy. A scope document is a fixed estimate before the work starts.

Scope creep is one of the most common problems freelancers run into. The client asks for a "small addition," then another one, then another. In the end, you've done three times the work for the same price.

The fix: put the scope (what's included in the job) in writing BEFORE the work starts.

A minimal scope document (this is a structure, not a legal document; have a lawyer look over your client contract):

## Project: Order Processing Automation
**Client:** [Name]  
**Date:** [Date]  
**Budget:** $2,500  
**Timeline:** 3 weeks

### Included in V1:
- Automatically reading incoming orders from Gmail
- Sorting them by type: new order / question / complaint
- Automatic reply to new orders with a confirmation
- Slack notification when a complaint comes in

### NOT included in V1 (Backlog):
- CRM integration (could be V2)
- Reports on order statistics
- Multilingual support

### What the client can expect:
- A weekly progress update
- A demo in week 2
- Final delivery with documentation

### Payment terms:
- 50% deposit before work starts
- 50% after the final demo and sign-off

This document protects you: a "small addition" is now clearly Backlog, not V1.

Separating V1 from the Backlog:

V1 is what you're building now for the agreed price. The Backlog is a list of ideas for future versions. A clear line between them lets you:

• Finish the project on time and on budget
• Have a ready-made list for continuing the work (upsell)

The growth path

🎨 Picture this: the three stages are like a cook's career. Freelancer = cooks everything alone in a small kitchen. Consultant = a chef with a narrow specialty and a waiting list for tables. Agency = the restaurant owner who no longer cooks and runs the place instead.

Stage 1: Freelancer (small projects)

You work alone, take on anything you can do, build your portfolio and get to know the market.

Focus: quality of the work, speed, testimonials.

Stage 2: Consultant (bigger projects)

You have a specialty, for example "automation for e-commerce" or "AI assistants for real estate brokerages." You take on fewer projects, but you charge more.

Focus: positioning, niche expertise, recurring revenue.

Recurring revenue is the key to stability:

🎨 Picture this: a one-off project is like selling a dresser. A maintenance contract is like renting out an apartment. You sell once, and the money comes in every month without you having to find a new buyer.

A one-off project is good. A monthly maintenance contract is better.

A made-up example:
Automation project: $5,000 (one-time)
Maintenance contract: $500-1,000/month
→ Updates and improvements
→ Monitoring and fixing problems
→ Advice on new tasks

Arithmetic, not a forecast: 10 clients × $750/month = $7,500/month. How many clients you'll have, and whether you'll have any at all, depends on your niche, your market and your work.

Stage 3: Agency (large projects)

You hire other people (or build a team of agents), take on large corporate projects and delegate the hands-on work.

Positioning yourself in the market

How to talk about what you do:

❌ Technically accurate, but nobody understands it: "I build Claude Code workflows with MCP integration through Trigger.dev"

✅ Talk in terms of results:

• "I automate repetitive tasks in your business using AI"
• "I take the busywork out of your day"
• "I free up the 10-20 hours a week you spend on manual work"

Specific examples of how to say it:

• "I automate how incoming requests are handled, so routine questions get answered without your team"
• "I build a system that reads email, sorts it and sets priorities without a person in the loop"
• "I create an AI assistant that prepares reports and briefs for you"

Your positioning should include:

1. Who you help (a niche, or a broad audience)
2. What specific problem you solve
3. A measurable result in hours or dollars

Example: "I help small business owners automate routine correspondence and task management. It usually frees up 10-15 hours a week." (Only quote numbers like these once your own projects back them up.)

An ROI calculator for the client

🎨 Picture this: an ROI calculator shows the client that they put in $1 and get $10 back. Without the calculator, all they see is the $1 they're handing over. With it, they see the $10 they get.

When you present a project, show the numbers. With numbers, a decision about money is easier to make:

Current situation:
• 3 hours a day on email × 20 days = 60 hours/month
• Cost of your time: $40/hour
• Monthly loss: $2,400
• Yearly loss: $28,800

Our solution:
• Project cost: $3,500 (one-time)
• Busywork reduced by: 80%
• Hours freed up: 48 hours/month
• Yearly savings: $23,040
• Payback: under 2 months

After payback: $23,040/year in savings

In a real calculation, subtract the client's ongoing costs for the system from the savings: paid services, and maintenance if you charge for it.

Practice

Exercise: calculate the ROI for a potential project

1. Pick one business owner you know, or a potential client, whose problem you understand. (You'll build the full list of such people, your Trust Map, in the First clients lesson, which comes later.)

2. Fill in the ROI table:

   You

   Task we're automating: _____________
   Hours per week spent on it: ___
   Hourly cost (estimate): $___
   Weeks per year: 52
   Yearly loss: ___ × ___ × 52 = $___
   
   Project price: $___
   Expected workload reduction: ___%
   Yearly savings: $___
   Payback period: ___ months

3. Write a scope document for this project (using the template from this lesson): what's in V1, what goes to the Backlog

4. Set the price using the "10-30% of yearly value" rule

5. Write 2-3 versions of your offer in terms of results (not technical language)

Common mistakes

• Pricing by the hour instead of by the result. Say AI lets you finish a job in 5 hours instead of 50. If you charge $50/hour, you get $250 for work that's worth $10,000 to the client. Always calculate the client's ROI, not your own hours.
• Not showing the client the ROI calculation. If the client doesn't see the numbers, the client has doubts. Show a simple calculation: "what the problem costs per year" → "what the solution costs" → "payback in X months." Without ROI you're selling "a thing." With ROI you're selling an investment.
• Being afraid to name your price. If you've done the ROI math and the solution pays for itself in 2-3 months, the price is easy to justify with numbers. Staying vague about the price costs you trust.
• Not separating V1 from the Backlog. Scope creep eats your margin. The client asks for a "small addition" 5 times = you do 2x the work for 1x the price. The scope document is your protection.

Quick reference: price levels (a made-up example)

Rule of thumb: price = 10-30% of the yearly value for the client. The more obvious the ROI, the closer to 30%.

Related lessons

• → Packaging: the previous lesson, on turning price levels into three clear packages: Basic, Pro and Enterprise
• → Monetization case studies: ROI calculations for different types of projects
• → Pricing strategy: a deep dive: the next lesson, on plans and prices for AI products sold by subscription

Tools and resources

• Notion / Google Docs: for scope documents and contracts. notion.com/templates
• Wave or Invoice Ninja: invoicing. Both have a free plan (as of October 2026; see their websites for the limits). Wave only serves businesses in the US and Canada
• Stripe: stripe.com. Accepts online payments. It isn't available in every country; Stripe's site has the list
• Paddle: paddle.com. For selling software and digital products (not services): Paddle acts as the seller and takes care of sales taxes in different countries for you
• Gumroad: gumroad.com. For selling digital products (templates, courses, workflows)
• Calendly: calendly.com. Professional call booking without the back-and-forth
• Claude API pricing: platform.claude.com/docs: pricing. So you know exactly what the API costs when you calculate your margin. Current prices and versions: What's current

Key takeaways

Price by the result, and you can earn more for fewer hours. Price by the hour, and you put a ceiling on your own income.

Put the scope in writing before the work starts. It's not a sign of distrust toward the client; it's respect for both of you. Without that document, scope creep is almost certain.

Maintenance contracts are one path to steadier monthly income. Every one-off project is a potential long-term client.

Next lesson

→ How to price an AI product: value, tiers, packaging