Output-based Contracting

Stop paying your software suppliers for hours. Pay them for delivered functionality. We help organisations move their agile development and maintenance from time & materials to an output-based contract based on NPR 5333, step by step, with a trial period before any money depends on it.

No sales pitch, no strings attached. We look at your current contracts and suppliers together, and you leave with a clear view of whether output-based contracting fits your situation.

Book a free 30-minute call

Time & materials is the industry's bad practice

Most organisations still buy software development by the hour. Everybody knows the problems, yet the same approaches are used again and again:

  • Paying for presence. Under T&M you pay for people showing up, not for what they deliver. You know the budget, but not the value you got for it.

  • Selecting suppliers on hourly rate. The lowest rate wins, so you compete on price per hour instead of productivity and quality. Pay peanuts, get monkeys.

  • Rewarding low productivity. More hours means more revenue for the supplier. A team that works slower earns more. Nobody intends this, but the contract rewards it.

  • Using story points and velocity as contract metrics. Story points are subjective, differ per team and are easy to inflate. They are fine for planning inside a team, but they cannot be compared between suppliers or used to pay for output.

  • Hiring individual people into your own teams. Mixed teams of client and supplier staff mean nobody owns the result. When things go wrong, all risk stays with you.

How output-based contracting turns this around

In an output-based contract you pay a fixed price per function point delivered that meets the agreed quality standards. The supplier delivers complete teams and takes ownership of quality and productivity. Higher productivity gives the supplier a better margin and you a sharper price. Professional suppliers stop competing on hourly rate and start competing on productivity and quality. You pay for what you get.

NPR 5333 in brief

NPR 5333:2025 is the Dutch practice guideline for output-based measuring, steering and contracting of agile software development and maintenance. It was developed by more than 50 experts from 35 organisations using the NEN consensus model. An English version is expected at the end of 2026.

  • 17 core metrics within a set of 46, in four output categories (Faster, Cheaper, Better, Happier) plus flow and DORA metrics for stability and recovery.

  • Apply or explain: use every core metric, or explain explicitly why not.

  • Three implementation levels: 1. basic predictability, 2. quality and satisfaction under control, 3. productivity and output measured in function points. Output-based contracting requires level 3.

Where we go further than the NPR

NPR 5333 allows story points for velocity and load, and lists the hourly rate as a core metric. We think that is where the guideline falls short. Our position is simple: never story points or hourly rates in a tender or contract. Story points make bids impossible to compare, and an hourly rate pulls the evaluation back to input. Whoever selects on hourly rate gets T&M behaviour back, even in an output-based contract. We measure velocity and load in function points; story points stay inside the team. That is exactly what "apply or explain" allows.

Function points: the objective measure of output

Functional size measures what the user gets, independent of technology, team or supplier. Six ISO standards exist for it. The newest and simplest is Nesma Easy Functional Sizing (EFS, ISO/IEC 25986:2026): four pages of rules instead of more than a hundred, three basic components and fixed weights. It is quick to learn and easy to verify, which makes it suitable for contract agreements. Every function can be traced to documentation, so business and IT share one view of what is being delivered. The discussion is then about the price per function point, not about how much work something is.

What organisations that succeed with output-based contracts do differently
  1. They measure a baseline first. They size what was delivered in recent releases and know what they pay per function point today, before anything is negotiated.

  2. They base the price per function point on data. Price per FP = productivity (hours per FP) × average rate + surcharges for non-FP work, risk and margin. A difference of 10 hours per FP already moves the price by €700 to €1,000 per FP. Benchmark data from comparable projects shows what is realistic.

  3. They agree what is in and out of the price. The contract fixes the function points to deliver per quarter, the price per FP, which products and activities are included, and the quality criteria and target values for each metric. Migration, transition, handover and technical debt are priced separately.

  4. They price realistically, not optimistically. A price per FP that is too high loses the tender; one that is too low makes the supplier lose money, and that comes back to the client as delays, quality problems and a contract that has to be re-tendered.

  5. They steer on output from day one. Delivered function points against the agreed throughput line, quality measured continuously with green, amber and red standards, and a mandatory back-to-green plan after two red or amber sprints in a row.

  6. They test the model before money depends on it. A trial period of a few sprints lets both parties see the measurement work in practice.

Most organisations don't have the measurement expertise, the benchmark data or the contract templates to do this themselves. That is where we come in.

The route: four steps, each with a clear result
  • Step 0: Readiness Scan (5 working days). You complete a questionnaire and Harold reviews it personally. You get a readiness verdict, a scorecard across six dimensions and a roadmap.

  • Step 1: Baseline and business case (4 to 6 weeks). We measure your recent sprints with Nesma EFS and compare your price per function point with ISBSG benchmark data. You get a fact base: what you pay per unit of output today, what is realistic, and a clear go or no-go. No function point history? We reconstruct it.

  • Step 2: Contract transition (8 to 12 weeks). We tailor the NPR 5333 contract set, agree the targets with your supplier and run a trial period of about three sprints without financial consequences. You get a signed output-based contract or an addendum, tested in practice.

  • Step 3: Run and review (ongoing). Independent function point counting, quarterly performance reviews and target adjustments, so the numbers stay right for both parties.

Our commitment: if Step 1 shows that output-based contracting isn't a good fit for your situation, we tell you. You keep the baseline and the benchmark results, and you're under no obligation to continue.

Are you a supplier?

More and more clients ask for a price per function point. We help bidders determine a price that wins because it is sharp and demonstrably achievable: we size the scope, benchmark productivity and price per FP against comparable projects, model scenarios for win probability against margin, and help you substantiate the price in your bid. In a large European public tender, the bidder we supported won the contract from more than 20 competitors.

Want to check where you stand first?

Download the free NPR 5333 Readiness Checklist. It shows how ready your organisation is for output-based contracting, and which steps come next. Prefer to do it yourself? Our shop has the complete NPR 5333 contract template set (market consultation, RFI, RFP, scoring workbook and a Master Services Agreement with annexes) and the book Output-based Contracting of Agile Application Development Teams.

Who does the work

Drs. Harold van Heeringen, founder of AgileBenchmark, has more than 25 years of experience in software measurement, estimation and benchmarking. He contributed to NPR 5333 from the start, is President of Nesma and a board member and former President of ISBSG. AgileBenchmark is independent: we don't deliver software ourselves, so we have no stake in either side's numbers. Our measurement and benchmarking work has been used by organisations such as ARAG, Turkcell, Eneco, Coöperatie DELA and a Dutch government ministry.

Frequently asked questions

Is the 30-minute call a sales call?
No. We look at your situation together and you get an honest view. If output-based contracting isn't right for you, we'll say so.

Our supplier will resist. Does this still work?
Usually better than expected. The trial period lets the supplier see how the measurement works before any money depends on it. A good supplier benefits too: productivity becomes visible and can be rewarded.

We have no function point data. Is that a problem?
No. We reconstruct the baseline by sizing functionality delivered in past releases. Nesma EFS was designed to keep that effort low.

We're in the middle of a running contract. Do we have to wait until it expires?
No. The transition can result in an addendum to your current contract instead of a new tender.

We're a public organisation. Does this fit a tender procedure?
Yes. The contract set includes a market consultation, RFI and RFP written for the Dutch and EU context. Your own procurement and legal advisers remain responsible for the procedure.

Is this legal advice?
No. We provide the metrics, measurement and pricing mechanisms. The contract should always be reviewed by your own legal adviser.

Book your free 30-minute call

No strings attached. Tell us about your suppliers and contracts, and you'll get an independent view of what output-based contracting could mean for you.

Book a free 30-minute call with Harold

Contact

Get in touch with us:

Tel: +31 6 523 273 30

© 2026. All rights reserved.

Chamber of Commerce (KvK) nr: 98694650