Technology decisions

Which technology should we choose? Finding the platform that fits your processes and operating model, and being ready for it before a contract is signed.

From the first demo to a signed contract

Your vendors run their part of the process. Procurement Code works on your side of it.

  1. 01

    Requirements

    With Procurement Code

    Written from the operating model you're moving to, not a description of today's process.

    Your vendors

    Responses and demos

  2. 02

    Proof of concept

    With Procurement Code

    Success criteria agreed first. Procurement Code runs your side of the test with real users.

    Your vendors

    The platform set up for the test

  3. 03

    Readiness Review

    4 to 6 weeks

    With Procurement Code

    Processes, data, controls, integrations and sponsors checked against what the platform will need.

    Your vendors

    Commercial terms and the build plan

  4. 04

    Contract signed

    With Procurement Code

    A decision finance and IT have agreed, with the business case built and the first use cases ready.

    Your vendors

    The build starts

Technology evaluation and proofs of concept

Deciding which platform fits your processes and operating model before a contract is signed. Where a proof of concept is the right test, Procurement Code runs your side of it.

When it helps

A suite renewal is coming up, or the business keeps buying tools procurement didn't choose.

What you get

  • Requirements written from your own processes
  • A proof of concept run on a test you designed
  • A decision finance and IT have agreed

Readiness Review

4 to 6 weeks

A check that your processes, data, controls, integrations and sponsors are ready for a specific platform. It takes four to six weeks, can run alongside a vendor's proof of concept and ends in a recommendation to go ahead, change course or stop.

When it helps

You want the foundations right before the build starts.

What you get

  • The design decisions made before the build
  • A business case built with finance
  • The first use cases agreed

In my last in-house role I brought in procurement platforms and ran proofs of concept across a group of businesses. Procurement Code takes no commission or referral fee from any vendor.

Where technology projects stall

Choosing the platform is rarely where it goes wrong. These are the four places projects stall, and each is easier to settle before the build starts.

The use case

You've seen the demo but not your own process running on it.

What to do

Get your leadership team in a room to choose the first use case from your own data.

The starting point

Nobody has agreed where to start, or what results the first phase is meant to deliver.

What to do

Agree the phases and the value each must deliver, with finance signing off the targets.

Sign-off beyond procurement

Every platform needs other functions to agree, whether that's finance, IT, legal or the teams who will use it. What they hear is a procurement project.

What to do

Name a sponsor in each function the project touches before the build, and write the business case with finance.

The plan for the people

No one can say what the team will do differently, or who runs the platform afterwards.

What to do

Design the operating model and the roles before the build, including who owns the platform.

Not sure which of these fits?

Tell me what you're weighing up and we can work out which of these would help.

Talk it through

Send a short note about the decision in front of you. I reply personally within a working day.

Get in touch