Pricing models: hourly, project, retainer and value-based

0:00 Pricing models

Here's a strange thing about hourly pricing. The better you get, the less you earn. If AI tools help you finish in three hours what used to take ten, and you bill by the hour, you've just cut your own income by seventy percent. In this lecture, you'll learn the four main pricing models, hourly, project, retainer and value-based, when each one fits, how AI efficiency changes the argument, and how to structure a retainer and a value-based price that clients understand and accept.

0:37 Why it matters

Why does this matter? Because your pricing model shapes how you work, who you attract, and how much you can earn. Hourly pricing rewards slowness and caps your income. Project pricing rewards efficiency, if you scope tightly. Retainers give you predictable income and clients ongoing value. And value-based pricing links your fee to what the outcome is worth, which has nothing to do with how long it took you. Here's the key idea. Choose the model that rewards you for results, not for hours, while staying honest and transparent with clients.

1:17 The transport analogy

Here's an analogy. Think about how people pay for transport. A taxi meter charges by time and distance. That's hourly pricing. A fixed fare to the airport is agreed upfront, whatever the traffic. That's project pricing. A monthly travel pass gives unlimited journeys within a zone. That's a retainer. And a chauffeur for an important client meeting might charge a premium because arriving on time is worth a lot. That's value-based pricing. Same car, same road. Four ways to charge, each suiting a different customer and situation.

1:55 The four models

Let's look at each. Hourly or day rates are simple, and fair when scope is genuinely unknown, like ongoing support or consulting. But they cap income, invite micromanagement and punish efficiency. Project pricing sets a fixed fee for a defined scope. Clients like the certainty. You keep the benefit of working efficiently, but you carry the risk of underestimating, so scope and change control matter. Retainers are a monthly fee for defined ongoing work, like content, maintenance or reporting. And value-based pricing sets the fee by the value of the outcome, which needs good discovery and trust.

2:37 AI and pricing

Now, how AI changes the argument. If you bill hourly and AI makes you faster, you earn less for the same result. Project, productised and value-based pricing let you keep the benefit of efficiency, and pass some of it to clients through faster delivery. But be honest. You're not charging for AI. You're charging for the outcome, your expertise and your accountability. If a client asks how you use AI, explain it plainly. And if a client insists on hourly billing, bill real hours honestly. Padding hours is dishonest, and it destroys trust when discovered.

3:18 Worked example 1: one project, three prices (illustrative)

A simple worked example: the same project, three prices, all illustrative. A small business wants a website redesign. Priced hourly at forty pounds an hour for sixty hours: two thousand four hundred pounds, and the client worries about overruns. Priced as a fixed project with defined pages, two revision rounds and a timeline: three thousand two hundred pounds, and the client values the certainty. Priced on value: the site is expected to produce enough extra bookings to be worth far more over a year, so a package including conversion tracking and a three-month optimisation plan is priced at five thousand five hundred. Each price is legitimate. The difference is what you're selling.

4:07 Retainers done properly

Now retainers, done properly. A retainer isn't just a monthly fee. It's a defined service. Set a minimum term, like three months, then monthly with thirty days' notice. Bill in advance, on the first of the month. List what's included each month, with quantities. Set service levels, like replies within one working day, and define urgent. Cap capacity, in hours or requests, and say that unused capacity doesn't roll over. List what's out of scope and handle it by change order. And review results quarterly. That structure turns a retainer from an open-ended commitment into a predictable, valuable service.

4:50 Worked example 2: Aisha in Dubai (illustrative)

Now the realistic scenario, illustrative. Aisha is an automation specialist in Dubai. She used to charge hourly to set up CRM and email automations for small agencies, and clients haggled over every hour. In discovery with a recruitment agency, she asks what the problem is costing. Recruiters spend around eight hours each a week copying candidate data between systems, and slow follow-ups lose candidates to competitors. With six recruiters, that's a lot of time. She proposes a fixed project to build the automations, priced as a share of the time saved in the first year, plus a monthly retainer for monitoring and improvements. The client sees a clear return and signs.

5:38 Watch me: a value-based price

Watch me build a value-based price. I use the five questions from the lesson in discovery. What's this problem costing you each month? What would change if it were solved, and how would you measure it? What have you already spent or tried? What would it cost to solve another way? And what's the timeline? Say the answers suggest the solution is plausibly worth thirty thousand pounds a year to the client. I might price the project between six and nine thousand pounds, which leaves them a clear return. Then I check it's above my floor rate for the effort involved. If it isn't, I reduce scope rather than my price.

6:26 Currency and regions

What about currency and regional pricing? If you serve clients in several countries, price in a stable currency that the client is comfortable paying, often their own or US dollars, and state who pays transfer fees. Don't price only by your local cost of living. A UK client values the outcome in UK terms. At the same time, some local clients need smaller packages, so you might have different offers for different markets, each above your floor. And be consistent within each market, because clients do compare.

7:04 Common mistakes

Let's list the common mistakes. Defaulting to hourly for everything. Fixed prices with vague scope. Retainers with no defined deliverables or capacity. Value-based pricing without real discovery, which feels like guessing. Letting AI efficiency quietly cut your income. Padding hours, which is dishonest. And discounting to win work, instead of adjusting scope. Remember, you can combine models. A common hybrid is a monthly retainer for a defined core, plus project fees for bigger pieces of work.

7:37 Recap and try this now

Let's recap. There are four main models: hourly, project, retainer and value-based. Hourly punishes efficiency, so as AI speeds up your work, move towards project, productised, retainer or value pricing, while staying honest. Structure retainers with terms, inclusions, service levels, capacity and reviews. Build value-based prices from discovery, check them against your floor, and cut scope, not price. Your try this now: take a recent project and price it three ways, then write a retainer structure for one of your ongoing services using the template. Next, we'll calculate your floor rate.