Why day-rate-focused IT frameworks cost more in the long run

IT frameworks savingsMost large enterprises typically operate IT frameworks focused on accelerating project award and execution. Typically, the selection criteria for these frameworks include size and scale, industry, and technology experience. However, the most weightage is usually assigned to the day rate.

Once an IT framework is awarded to successful bidders, individual projects are either awarded through a mini-tender or granted directly to specific vendors.

This day-rate-driven IT frameworks approach has many flaws, for example:

  1. For the successful framework partner, the number of days spent on delivering a project is directly proportional to the revenue, and this results in:
    • Not exploring prebuilt products/solutions that can deliver the same (or similar) outcomes with fewer days of consulting.
    • Customising the solution rather than the standard configuration.
    • Not challenging the business requirements that require custom development.
  1. SMEs unable to tick all the boxes during procurement – because tenders are not granular enough – miss out by default.
  1. There is a heavy focus on project milestones while the overall software quality and long-term cost of running software get ignored.
  1. Every (extra) day of development results in higher software customisation and higher TCO. This also builds excessive dependency on the framework partner(s).

Striking the right balance between minimising time spent on vendor selection and optimising the IT spend is complex, but the following steps can help:

  1. Strong internal IT architecture team – a strong internal or outsourced IT architecture team (separate from the delivery partner) plays a key role in verifying a standard solution’s or add-on’s ability to deliver the requirements. Strong architecture governance helps ensure that additional developments are only done as the last resort.
  1. Strong project and design governance – quality checks of the code being developed and related documentation are almost always forgotten or done retrospectively. Project governance should ensure that this is prioritised, to minimise building excessive dependency.
  2. Outcome or milestone-based projects – it takes more effort to agree on delivery milestones and desired outcomes prior to starting a project, but doing so is worth the effort – to ensure everyone remains focused on the outcome rather than the journey.
  1. Granular IT frameworks including specialist SME companies – a more granular IT framework can help ensure that there are good quality responses on the table.

Increasingly, enterprises are realising that IT services are not a commodity hence day-rate-driven procurement is slowly changing; companies begin to recognise that a lower day rate does not always translate to better outcomes in the longer run.

What is your experience, and how do you think enterprises should overcome this challenge?

On Device Solutions is a niche IT consultancy and an SAP Gold Partner. To find out more about how we can help your business, please get in touch with us now.

SUBSCRIBE TO OUR MAILING LIST

FOLLOW US:

Share
Tweet
Share
Mail

Thanks for your enquiry. A member of the On Device team will be in touch shortly.

Request a free Trial

Thanks for your enquiry. A member of the On Device team will be in touch shortly

I would like to request a trial of

Contact Us

Thanks for your enquiry. A member of the On Device team will be in touch shortly

Request a Demo

Thanks for your enquiry. A member of the On Device team will be in touch shortly

I would like to see a demo of

Request a Demo

Thanks for your enquiry. A member of the On Device team will be in touch shortly

I would like to see a demo of