Intact Technology - Should You Pay by the Hour or Outcome for IT Operations Management?

Should You Pay for IT Services by the Hour, Project, or Outcome?

Why consultants must be contractually accountable for delivering outcomes

By Jesse White | May 14th, 2020 | IT Strategy & Planning

Organizations traditionally pay for outsourced IT work in one of two ways, by the hour for time and materials, or by way of a fixed price for the entire project. There are assumed advantages in each of these scenarios – paying hourly allows you to control costs by managing project scale, and paying a fixed price allows you to ensure the vendor finishes on time and without excessive use of human resources. In each of these scenarios, however, it is you who assumes all the risk and will end up overpaying when the project inevitably doesn’t proceed “as planned.”

Paying hourly means your consultants are incentivized to maximize their billable hours, without a real financial or contractual commitment to delivering a great outcome. Paying a fixed price means your consultants are incentivized to minimize their time on the project. In both scenarios, your consultants possess very little risk, and so long as they deliver the minimal contractual obligations in a timely manner, you’re responsible for paying them.

Have you considered why consulting companies promote these two (and only two) options?

By focusing procurement and contracts on the process of implementing new software (in-scope deliverables, milestones, hours, and various assumptions), you’re losing sight of what really matters – the outcomes. You didn’t purchase a new piece of software to implement a new piece of software, but to achieve business outcomes. By focusing procurement and contracts on outcomes, you significantly increase the likelihood you’ll achieve them.

In our experience, customers that shift their focus and commitments away from a strict laundry list of deliverables to bigger picture results allows for a more agile and adaptive contract structure that holds consultants accountable for delivering outcomes. An effective outcome-based contract clearly defines measurable results for which your consultants will be accountable, such as an adoption rate for the new software tool, measurable impact on compliance, operational cost, or customer experience. (If your consultants are uncomfortable with an outcome-based contract that requires accountability, you probably shouldn’t hire them.)

What really matters in your next project?



Read next: 4 Ways You Can Actually Achieve Business Outcomes in Your Next Project

Related Posts

Consulting and Cuisine: If Choosing an IT Consulting Firm Was Like Choosing a Restaurant

By Jesse White | April 13th, 2021 | Featured | IT Implementation | IT Strategy & Planning

I am often disappointed with customers’ low expectations of IT consulting firms. Personally, I like to frequent businesses that care about their customers, care to do it right, and offer something that memorably improves my life, one experience at a time. If IT consulting firms were evaluated by the same …

Continue Reading ⟶

Optimize Your Investment – Master the ITSM Approach Proven to Achieve Results

By Jesse White | November 20th, 2020 | Featured | IT Managed Services | IT Strategy & Planning

You invest in ITSM solutions to achieve business outcomes – perhaps it’s to lower operational costs, improve customer experience, or reduce compliance risk. After successfully implementing these solutions, many customers find that they often fail to achieve their intended business outcomes over time, often resulting in a chronic tool-replacement cycle.  …

Continue Reading ⟶

4 Ways You Can Actually Achieve Business Outcomes in Your Next Project

By Jesse White | May 14th, 2020 | Featured | IT Strategy & Planning

Organizations purchase software not to implement new software, but to achieve business outcomes, such as improving customer experience, increasing operational efficiency, remediating risk, and reducing operational costs. As project design begins, however, these business outcomes become buried beneath lengthy lists of technical requirements and project deliverables, and become increasingly distant. …

Continue Reading ⟶


Learn more about how to deliver meaningful outcomes.