Stop Selling Hours. Start Selling Outcomes. Here's What Actually Changes.

This is part two of a six-part series on rebuilding the agency model for the autopilot era. We work with founder-led agencies at $1M-$10M on exactly this transition at Agency Focus.

Every agency founder I know says they sell outcomes. Almost none of them actually do.

Here is the test. If your client fires half their team tomorrow, does your invoice go down? If yes, you are selling an activity. You might call it a retainer. You might call it a monthly engagement. You might even call it "value-based pricing." But if the number on the invoice is tied to how many people touch the work, you are selling hours under a different label.

This is not a branding problem. It is a structural problem. And the distinction matters now more than it ever has, because the services-as-software wave I wrote about last week is going to separate the agencies that price on outcomes from the ones that price on effort. The ones pricing on effort will watch their margins compress as AI makes the effort cheaper. The ones pricing on outcomes will see their margins widen as AI makes delivery cheaper while the outcome remains just as valuable to the client.

Same market. Same clients. Completely different economics depending on which side of the pricing line you are standing on.

I have watched dozens of agencies try to move to outcome-based pricing. Most of them do the same thing. They take their hourly rate, multiply it by the number of hours they think the project will take, add a margin, and call it a flat fee. Then they put "outcome-based" on the proposal.

That is not outcome pricing. That is time-and-materials with a hat on.

Real outcome pricing starts from the other direction entirely. You start with what the client actually wants. Not deliverables. Not reports. Not campaigns. The thing behind all of that. The thing they would pay for if they could buy it directly without hiring you to produce it.

For a demand gen agency, the outcome is pipeline. Meetings. Revenue. For a brand agency, it might be a measurable shift in perception or a launch that hits its numbers. For a dev shop, it is working software that does the thing the business needs it to do. Not the code. Not the sprints. The thing.

When you price backward from the outcome, the math looks completely different. The client does not care how many hours it took. They do not care how many people touched it. They care about the result and whether they can trust you to deliver it consistently.

The problem is that most agency founders have never actually sat down to define the measurable outcome of their work. They define deliverables. They define scope. They define activity. But the outcome, the thing the client would write on a napkin if you asked them, "What are you actually buying from us?" that stays fuzzy. And fuzzy outcomes lead to fuzzy pricing, which leads to scope creep, which leads to the conversation every agency founder hates: "Can you just add one more thing to the retainer?"

I work with a framework I call Plinko Pricing. The name comes from the game show. You drop the chip at the top, and it bounces through a series of pegs before landing in a slot at the bottom. The slot it lands in determines what you win.

Agency pricing works the same way. A prospect comes in at the top. The series of pegs they bounce through, their budget, their timeline, their complexity, and their readiness determine which offer they land on. Not what hourly rate you charge, but which offer.

The structure that works for most agencies in the $2M to $5M range has three components.

First, a setup fee. This covers onboarding, discovery, and the initial build. It is a one-time payment that funds the work you do prior to the recurring engagement starting. Most agencies undercharge for this or skip it entirely, which means they are subsidizing onboarding out of their retainer margin. Stop doing that. The setup fee should cover your actual cost of getting a new client operational, plus margin.

Second, a monthly retainer tied to a defined outcome metric. Not tied to hours. Not tied to deliverables. Tied to the thing the client actually wants. For a demand gen engagement, that might be a guaranteed minimum number of qualified meetings per quarter. For a dev engagement, it might be a shipping cadence with defined acceptance criteria. The retainer is the floor. It covers your cost of delivery plus your margin at the baseline level of output.

Third, a performance layer on top. When you exceed the target, you earn more. This is not a bonus. It is a pricing mechanism that aligns your incentive with the client's incentive. If you book 40 meetings and the target was 30, the extra 10 are priced at a premium. The client is happy because they got more than they paid for. You are happy because your effective margin just went up.

This structure does three things that hourly pricing cannot do.

It shifts the conversation from effort to value. The client is not asking how many hours something took. They are asking whether the number went up.

It protects you from scope creep. The scope is defined by the outcome, not by a list of tasks. If the client asks for something outside the scope of the outcome, it is a new engagement, not a favor.

It creates a natural expansion path. When the outcome is measurable and improving, the client wants more of it. You do not need to sell them on a bigger retainer. The results sell it for you.

Pricing on outcomes only works if the client can see the outcome happening in real time. This is where most agencies fall apart. They price on outcomes but report like a services firm. Monthly PDF. Quarterly business review. Maybe a call every two weeks where someone reads the slides out loud.

That cadence worked when you were selling hours because the client was buying your time and the report was proof you spent it. When you sell outcomes, the report is proof the number moved. Different purpose, different format, different cadence.

What works is three layers of visibility.

A live dashboard that the client can check at any time. Not a monthly snapshot. A live feed. Pipeline created this week. Meetings booked. Conversion rates. Whatever the outcome metric is, it should be visible without the client needing to ask you for it. If you are running demand gen, the client should be able to open a browser tab and see how many meetings you booked this month the same way they check their bank balance.

A weekly update from the account owner. Short. Three things that worked this week. One thing that did not. What we are doing next week. No slide deck. No thirty-minute call unless there is something to discuss. This update is for the client-side operator who needs to know that the work is running.

A quarterly conversation with the decision-maker. This is not a business review. It is a strategic conversation. Here is what we learned about your market this quarter. Here is what we think you should do differently. Here is what the next quarter looks like if we keep going versus if we adjust. This conversation is where the judgment lives, where you demonstrate that you are not just running a system but thinking about their business.

That reporting stack, live dashboard, weekly written update, and and quarterly strategic conversation make the client experience feel like SaaS even though the delivery is services. And that is the whole point. Retention in a services business starts to look like SaaS retention when the client experience resembles SaaS.

You will still get prospects who ask for your hourly rate. You will get procurement departments that need a day rate for their spreadsheet. You will get CFOs who want to compare your cost per hour against doing it in-house.

You have two options with these buyers.

Option one: You educate them. You walk through the outcome, the metric, the reporting, the performance layer. You show them that the comparison is not your hourly rate versus an employee's hourly rate. The comparison is your outcome versus the cost of building an internal team, buying tools, managing the process, and accepting the risk that it won't work. Most of the time, your flat-fee outcome is cheaper and lower-risk than the alternative, and smart buyers will see it.

Option two: you walk away. Not every buyer is your buyer. The prospect who cannot get past the hourly rate conversation is telling you something about how they value the work. They are buying labor, not outcomes. And labor buyers will always push your price down because they are comparing you to the cheapest version of the same input. You do not want to be in that conversation.

Walking away from a bad-fit prospect is not lost revenue. It is margin protection. Every hour you spend trying to convince a labor buyer to think differently is an hour you did not spend serving a client who already gets it.

I learned this one the hard way. I spent thirteen years running an agency where we would bend our pricing to fit whatever the client wanted to pay. Custom scopes for every deal. Different rate cards for different clients. It worked until it didn't, because the clients who beat you down on price are also the clients who expand the scope without expanding the budget. The correlation is almost perfect.

Moving from hourly to outcome pricing is not a slide deck change. It rewires four things inside your agency.

Your sales process changes. You stop scoping projects by hours and start scoping by outcomes. The first call with a prospect sounds different. Instead of "here is what we do and here is what it costs per hour," it becomes "what is the outcome you are trying to buy, and what is that outcome worth to your business?"

Your delivery changes. You need to actually measure the outcome, which requires infrastructure. Dashboards. Tracking. Attribution. Most agencies do not have this because they never needed it when they were selling hours. Now you need it because the outcome is the product.

Your hiring changes. You need fewer people doing the work and more people designing the systems that do the work. The delivery operator matters more than the senior strategist who touches every account. The technical person who builds the reporting layer matters more than the project manager who tracks hours.

Your client relationships change. The clients who loved you for being responsive and flexible might not love the new model. The clients who stayed because "we have a great relationship" might leave when you stop being available for every ad hoc request. That is fine. The clients who stay are the ones who value the outcome, and those relationships are stickier, more profitable, and more fun to serve.

Pull up your current client roster. For each client, write down the answer to one question: What is the measurable outcome this client is paying us for?

If you can answer it in one sentence, you are closer to outcome pricing than you think. If it takes a paragraph, you are selling activity and calling it something else. If you cannot answer it at all, start there. Because the pricing model is not the first thing that needs to change. The clarity about what you actually deliver is.

Next week, I am going to walk through what the delivery stack looks like when the systems do the work. The hiring order. The documentation discipline. And the founder ceiling problem stalls the whole transition if you do not get out of the way.