Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

Outcome-based and KPI-linked software contracts: when they work and how both sides measure them

An outcome-based or KPI-linked software contract works when the KPI can be measured today, the partner controls most of what moves it, and both sides sign the baseline and data source before work starts. This Netbase guide gives the fit test, the KPIs a partner can carry and the measurement charter to sign.

Book a solution review See the related solution

By Huy Nguyen (David), Founder & CEO · Updated · 10 min read

star

This guide is for founders, CFOs, CTOs and procurement leads buying custom software development who want part of the payment to follow results rather than effort. It belongs to the partner-selection series that starts with large or boutique Vietnam IT vendors, and it pairs with the overview of Netbase engagement models.

In this guide

When does a KPI-linked software contract actually work?

A KPI-linked contract ties part of the partner's payment to an agreed number. An outcome-based contract goes further and ties payment to a business result. The GOV.UK risk allocation and pricing guidance defines outcome-based payment as payment that depends, wholly or partly, on the supplier achieving specified outcomes.

Use the five-condition fit test below. If any condition fails, a simpler term will usually serve both sides better.

  1. The KPI is measurable today. The number already exists in a system both sides can read, not in a spreadsheet one side rebuilds each month.
  2. The partner controls most of what moves it. If marketing spend, pricing, seasonality or the buyer's own staff move the number more than the software does, the partner is being paid for luck.
  3. A baseline exists. At least one stable period of the KPI before the change, measured the same way it will be measured after.
  4. The window fits the contract. The KPI moves within the contract term, not a year after the team has left.
  5. Both sides see the same data. One shared dashboard or report, with a named owner for the data and a written formula.

The UK National Audit Office review of payment by results found that outcome-based schemes suit only some services, that poorly designed schemes create perverse incentives, and that buyers should justify the choice against simpler models. The same warning applies to software.

When should you not use one?

Do not link payment to a KPI when the scope is still unknown, when the product has no users yet, when the KPI depends mainly on sales or marketing, or when the data needed to measure it does not exist. In those cases fix the scope first in discovery, then pay by milestone.

Which KPIs can a software partner carry?

Not every number is fair to put money against. The useful split is by how much of the KPI the partner controls.

KPI type Examples Partner control Safe share of payment
Delivery KPIs Milestone accepted on time, defects found after acceptance, change fail rate, recovery time High Can carry a meaningful share
Service KPIs Uptime of the delivered system, response to support tickets, page performance budget High once the partner runs the system Can carry a share under a support scope
Shared KPIs Order completion rate, time to process a document, manual steps removed Partial: depends on adoption and process Small share, with exclusions
Business KPIs Revenue, margin, new customers, market share Low A bonus at most, never the base payment

Delivery KPIs borrow well-tested definitions. The DORA software delivery metrics define change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate, which both sides can compute from the same pipeline data.

The rule of thumb: the less the partner controls a KPI, the smaller the share of payment it should carry and the longer the list of written exclusions. A contract that pays the base fee only on revenue growth is a bet, not a delivery term.

How do both sides set up the measurement charter?

A measurement charter is a one-page annex both sides sign before work starts. It turns "we will hit the KPI" into a number that cannot be argued about later.

  1. Define the KPI in one sentence and one formula

    Name the numerator, the denominator and the unit, for example accepted milestones delivered by their agreed date divided by all milestones due.

  2. Record the baseline

    Measure the KPI over an agreed period before any change, using the same formula and the same data source, and attach the export to the charter.

  3. Name the data source and its owner

    One system of record, one person on each side who can read it, and read access for both sides throughout.

  4. Fix the measurement window

    State when measuring starts, how long it runs and when results are read, so a slow month after launch is not read as failure.

  5. List the exclusions

    Outages caused by third parties, changes requested by the buyer, campaigns, price changes and data errors the partner did not introduce.

  6. Agree the dispute route

    Who recomputes the number, within what time, and who decides if the two results differ, before anyone sends an invoice.

Review the charter at every milestone. If the product changes direction, the KPI should change by written agreement, not by silence.

Where AI fits

AI changes what a buyer can measure, not who is accountable. In a Netbase project, AI helps draft code, tests and documentation and can compute delivery KPIs from the pipeline and ticket data each week. Engineers still check that the formula matches the charter, that excluded events are removed by a person, and that a number which looks too good is traced to its source. Netbase works with the major commercial and open-source AI tools and models, chosen per project, so the charter does not depend on one tool.

The delivered AI feature named with a client is 4over4's recommendation engine, which suggests products from browsing history and previous purchases. Beyond it, Netbase has delivered AI projects for clients that are not named, including retrieval-augmented knowledge assistants, document AI and MLOps pipelines.

What delivery record exists, and what does not

Most Netbase projects are delivered on fixed-price contracts; milestone-based, monthly team retainer and KPI-linked models are also offered. Netbase is a consulting company first: consulting, solutions, custom development and AI-enabled transformation lead, and dedicated teams are a secondary delivery option.

The Netbase delivery lifecycle runs from discovery and strategic alignment through agile execution with outcome-based milestones to rollout and ongoing support. Governance uses weekly reviews, KPI dashboards, a dedicated account manager and project manager, and client dashboards, which is where a measurement charter is read.

In fractional AI leadership work, Netbase uses outcome-based milestones in which each milestone has a written outcome and acceptance criteria agreed before it starts. Outcome-based there means scoped outcomes and acceptance criteria, not a promised business result or a price. For custom development, the client owns the IP created for it.

Netbase also works as offshore development partner on a multi-tenant cloud ERP for a US client that is not named, a long-running product where delivery KPIs are read milestone by milestone.

What does not exist: no published KPI-linked contract result, bonus paid, share of payment at risk or business figure from any Netbase client. This page gives a method a buyer can apply to any partner, not results.

Alternatives: other ways to pay for results

KPI-linked terms are one option among several. Choose by how clear the scope is and how much of the result the partner controls.

Term How payment works Who carries the risk Choose it when
Fixed price by milestone Agreed price paid on written acceptance of each milestone Partner carries delivery risk Scope can be made clear in discovery
Monthly team retainer Fixed monthly fee for an agreed team and service targets Buyer carries scope risk Requirements keep moving after launch
KPI-linked share Base payment plus a share tied to delivery or service KPIs Shared, through the charter The KPI passes all five fit conditions
Full payment by results All payment depends on a business outcome Partner carries most risk and prices it in Rarely in software; only with long windows and full data access

For most first projects, fixed price by milestone already pays for a result: each milestone is accepted against written criteria before it is paid. The milestone-and-proposal view of discovery shows how that scope is set, and dedicated team vs fixed price compares the two most common terms. For AI scope, fixed-price AI projects with model-quality acceptance criteria covers acceptance by evaluation sets.

A KPI-linked share fits best as a second step: after a fixed-price phase has produced a baseline and a shared dashboard, part of the next phase can follow the delivery or service KPIs the first phase made measurable. To measure the buyer's own return after launch, use AI automation ROI after launch.

What are the trade-offs?

KPI-linked terms focus both teams on the number, which is the point and the risk. The GOV.UK note warns that suppliers will focus on the outcomes most likely to result in payment, which may not match the intention, and that proving results can be hard to document. A narrow KPI can crowd out work that matters but is not measured, such as security fixes and documentation. Keep those in the acceptance criteria of each milestone, outside the KPI.

Limits of this guide

  • It is not legal or tax advice; the charter is a commercial annex, and your counsel writes the contract.
  • It does not publish prices, fee splits or share percentages; those depend on scope and are agreed per project.
  • Public-sector rules on payment by results differ by jurisdiction and are outside its scope.

Plan the next step with a Netbase consultant

Frequently asked questions

A KPI-linked contract ties part of the payment to an agreed, measurable number such as milestones accepted on time or system uptime. An outcome-based contract ties payment to a business result such as revenue or cost saved, which the partner controls far less, so it carries more risk for both sides.

Tie payment to a KPI the partner controls and both sides can read from the same data, such as milestones accepted on time, defects found after acceptance or uptime of a system the partner runs. Keep revenue and other business results as a small bonus at most.

Yes. When each milestone has a written outcome and acceptance criteria agreed before it starts, and payment follows acceptance, the buyer pays for delivered results rather than hours. A KPI-linked share can then be added in a later phase once a baseline exists.

The measurement charter decides. It should list exclusions such as third-party outages, buyer-requested changes and campaigns, and name who recomputes the number and who settles a disagreement, so a missed KPI is checked against the agreed rules before any payment changes.

Next step

Bring the KPI you want to pay for and the data behind it, and Netbase will run the five-condition fit test with you: book a solution review.

AI-enabled custom software development built around your workflow AI-enabled custom software development built around your workflow

Netbase provides custom software development for companies whose workflow no off-the-shelf product fits, from discovery through architecture, build, testing and handover, with AI where it removes manual steps and the IP left with you. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to the published USticker case study, design-tool users converted 40% more often.

Learn More
line
AI-enabled digital transformation consulting that ends in a delivery plan AI-enabled digital transformation consulting that ends in a delivery plan

Netbase provides digital transformation consulting for mid-market companies that need a prioritized roadmap with a delivery path, not a deck. We rank every change by value and risk, including where AI removes manual work, and the same team builds it. According to CEO Huy Nguyen (David), Netbase has served 500+ businesses across 80 countries since 2012.

Learn More
line
SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules SaaS product accelerator: launch an AI-ready SaaS on proven Netbase modules

A SaaS product accelerator is a set of reusable Netbase modules for accounts, billing, roles and integrations that helps founders and product teams launch subscription software faster, with room for in-product AI from the first release. Reusing these modules can shorten development time, and the approach is proven on Printcart, Netbase's own web-to-print SaaS.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase