Outcome-Based Pricing: How to Price Results as a Service

Outcome-based pricing charges for a finished result instead of for access, seats or hours. The customer pays when the agreed outcome happens: a support conversation resolved, a qualified lead delivered, an appointment booked, a chargeback recovered. It is the pricing model behind Results as a Service (RaaS), and AI has made it practical for far more kinds of work.

This guide shows how software companies price outcomes in 2026, the five pricing structures you can choose from, and how an agency can set a fair price per result for a client.

How software companies price outcomes in 2026

The table below lists published examples. Prices change often, so each row links to its source; all were checked on October 29, 2026.

Two patterns stand out. First, in every row the result is something the vendor can see in its own records, such as a conversation marked resolved or a call logged against an ad. Second, several vendors, including Fin, Zendesk and Salesforce, pair the per-outcome fee with a plan, licence or monthly minimum.

Kyle Poyar's 2025 State of B2B Monetization survey matches that picture: hybrid pricing became the most common primary model (41% of companies surveyed), outcome-based pricing was primary for 5%, and 25% expected to use it by 2028 (Growth Unhinged).

Five ways to structure outcome-based pricing

For a first results offer, base fee plus per result is the easiest place to start. The base fee pays for setup, monitoring and reporting; the per-result fee ties the rest of the bill to what the client actually received.

How to set the price per result

Work from two numbers, then choose a price between them.

1. What one result is worth to the client. Ask for their own figures: average sale value and how often a result turns into a sale. A med spa that sells a $1,500 treatment plan to 30% of booked consultations values each booked consultation at about $450 ($1,500 × 0.30). These are illustrative figures; use the client's.

2. What one result costs you to deliver. Add up software, phone and messaging usage, AI usage and your team's time for the month, then divide by the results you expect. Include the time to review and report results, not just the time to produce them.

The price per result sits between those two numbers: comfortably above your cost so slow months stay healthy, and comfortably below the client's value so the deal is an easy yes. In the med spa example, a fee per booked consultation in the $50 to $100 range leaves the client most of the value while covering delivery.

Then add two guardrails:

• A monthly cap on billable results, so the client's budget stays predictable.
• A base fee or minimum, so your fixed work is covered in a quiet month.

The contract terms that make it work

Outcome-based pricing lives or dies on definitions. Put these in writing before the pilot:

1. The result. "A new-patient appointment booked through the agency's booking page or phone line and attended."
2. The source of truth. Which records count: the calendar, call log, CRM record or payment.
3. Attribution. How a result is tied to your work: a tracked number, a dedicated form, a booking page.
4. Counting rules. The billing period, how duplicates are merged and what happens to cancellations.
5. Review window. The client can question any counted result within, say, seven days of the monthly report.
6. Caps and minimums. The monthly ceiling and the base fee.
7. Client responsibilities. Calendar availability, response times for handoffs and access to the accounts you need.

How to measure results you can bill

Every billable result should point to a record anyone can open. In a CRM that brings calls, messages, forms, calendars and payments onto the same contact, that is straightforward: the appointment, the call that produced it and the contact's source sit together on one timeline.

In Chirply, an agency can run each client in its own client account under the agency's brand. Call attribution ties a call to the tracking number or campaign that produced it and marks it as a conversion by call duration, a webhook or manual confirmation. An AI receptionist answers, takes messages, transfers and books, and each call keeps its transcript and outcome. Booking pages record booked, completed and no-show appointments. The monthly report is then a filtered list of records, each one a result both sides can check, and the agency bills the count through its own invoices.

Common mistakes to plan around

• Counting activity instead of outcomes. Calls made and emails sent are inputs. Bill for the appointment, the payment or the resolved request.
• Defining the result after launch. Agree the definition first; changing it later feels like moving the goalposts.
• Leaving out the client's part. A booked appointment depends on the client's calendar having openings. Write that dependency down.
• Pricing from your costs alone. Start from the client's value per result so the price reflects what the result is worth to them.

Next steps

• RaaS vs SaaS compares the two models and works through a pricing example.
• Results as a Service examples lists offers with a suggested unit for each.
• How to switch from SaaS to RaaS is a 30-day plan for your first pilot.

Sources

• Fin, pricing and billable outcomes, checked October 29, 2026.
• HubSpot, pay when the task is complete, 2026.
• Zendesk, pricing, checked October 29, 2026, and outcome-based pricing announcement, August 28, 2024.
• Salesforce, Agentforce pricing, checked October 29, 2026, and Flex Credits announcement, May 15, 2025.
• Google Ads Help, Local Services Ads lead charging, checked October 29, 2026.
• Chargeflow, pricing, checked October 29, 2026.
• Growth Unhinged, 2025 State of B2B Monetization, June 4, 2025.