Sell to the Head of Procurement

Why Companies Buy Levelpath Levelpath is bought by the head of procurement (a CPO, VP of Procurement, VP of Strategic Sourcing, SVP of Operational Finance and Procurement, or a Director of Category Management) at companies that range from…

Solutions Consulting
Stakeholder Management
Implementation Planning
Value Selling
Product Demo
Discovery
Procurement
Executive Communication
Estimated Time:
45 minutes
Difficulty:Intermediate
Status:Not started
Start this challenge

Create a free account to upload your work. Your progress saves as a draft until you submit.

What You'll Be Doing

Why Companies Buy Levelpath

Levelpath is bought by the head of procurement (a CPO, VP of Procurement, VP of Strategic Sourcing, SVP of Operational Finance and Procurement, or a Director of Category Management) at companies that range from American Airlines to a 47-facility healthcare network. Almost all of them run lean: three or four procurement professionals, sometimes one, carrying thousands of requests a year. They buy for one reason: more throughput without more headcount. Levelpath's own claims are 10x capacity for RFPs, 76% shorter cycle times, $26B+ of spend run through the platform, and 50 to 70% operational efficiency gains. They also buy because it goes live fast (same day to seven days in Levelpath's case studies), and because employees will actually use it: Levelpath's slogan is "delightful procurement," and it means the mobile-first, any-employee front door. IT, finance and legal leaders are the secondary stakeholders: less shadow IT spend, faster AP and reconciliation, more contracts reviewed.

Your Buyer

Dana Ruiz is VP of Procurement at a $900M specialty retailer with 4,200 employees. Her team is three people. About 2,400 purchase requests a year reach them by email and a shared spreadsheet; the median request takes 11 days to become a purchase order, and nobody can say how much spend is going to preferred suppliers. Her CFO has told her to get spend under management up this year and has told her there is no headcount to do it with. She has given you 25 minutes on Thursday. Her Director of IT will join for the second half.

Your Challenge

Bring a product you know well: anything you have sold, implemented or used every day. Do not demo Levelpath; we are not testing what you know about us. Treat your product as what Dana is evaluating. Show her how it gets her team more throughput without more people. Then ask her for a decision, and tell her what the first 30 days after yes look like.

The written piece is short. The video is the meeting. Budget about twenty minutes to prepare, then record.

Constraints to Consider

  • Bring your own product and run it live on your screen. A product you have sold or implemented, or a free account you set up today, both qualify. Screenshots only if live access is impossible, and say so on camera. Levelpath itself is excluded.
  • You are talking to Dana, and later to her Director of IT. Address them by name. Nothing in the video should be addressed to an evaluator.
  • Dana has no headcount coming. Anything you propose runs on her team of three. If your product needs an admin, a data cleanup or a project team to get value, say who does that work and when.
  • Dana's CFO measures spend under management and cycle time. Whatever you promise, say how she will show the CFO it happened within ninety days.
  • You will not be in the room to clarify. Anything you do not say, she does not hear.

How We Assess Communication

Communication presence is part of this role. We assess rapport-building, objection handling, and ability to tailor messaging. Delivery style matters here. We do not assess accent, pace, filler words, or whether English is your first language.

Submission: Upload each deliverable as a separate file directly on the Provn platform: your written artifact and your video (MP4 or MOV).

What You'll Accomplish

Demonstrate discovery in a live demo: connect what you show to a procurement leader's stated problem rather than clicking through features.

Make the case in the buyer's terms: throughput, cycle time, spend under management, no new headcount.

Adjust the pitch when a second stakeholder with different concerns joins the room.

Say what your product does not solve for this buyer, and still ask for the decision.

Turn a yes into a credible first thirty days for a three-person team.

How Your Work Will Be Scored

Discovery & Procurement Problem Framing (30%): A strong submission ties each part of the demo to Dana's stated problem, uses her numbers correctly, and is honest about what the product does not solve.Executive Command & Consultative Delivery (30%): A strong submission holds a procurement leader's attention, shifts register when IT joins, says something she does not want to hear without losing her, and asks for a specific decision.Solution Design & Implementation Ownership (20%): A strong submission describes a first thirty days a three-person team could execute, with owners and a measure the CFO would recognise.Stakeholder Mapping & Adoption Accountability (10%): A strong submission distinguishes what Dana, her Director of IT and her CFO each need, and names the adoption measure that proves the business case.Resume & Background (10%): Scored separately from your uploaded resume, on directly relevant experience, career trajectory, and domain relevance only.

What to Submit

Pre-read Email to Dana

Document · 150 words maximumRequired

Format: .pdf, .doc, .docx, .rtf, .txt, .md

What you would actually send her on Wednesday night. Written for her, not for us. Say what Thursday is for, what you will show, and what you will ask her to decide. The word limit is a hard constraint and part of the assessment.

Sign in to upload files

Video: The Thursday Meeting

Video · 12-15 minutesRequired

Format: .mp4, .mov, .webm

Record as MP4 or MOV and upload directly on the Provn platform. Deliver it as the meeting itself, to Dana. Cover:
(1) Open on Dana's problem, not on your product, about 1 minute.
(2) The demo, 6-7 minutes. Every step tied to something she said.
(3) Her Director of IT has joined. Spend 2 minutes on what IT needs to hear that Dana did not.
(4) Close, 2-3 minutes: say what your product will not solve for her, ask for a specific decision, and walk her through the first thirty days after yes (who on her team of three does what, and what the CFO sees at day ninety).
(5) Step out of the room, 60-90 seconds: tell us about a time you went further for a customer than the job required. What you did, what it cost you, what happened.
Communication presence is part of this role. We assess rapport-building, objection handling, and ability to tailor messaging. We do not assess accent, pace, or filler words.

Sign in to upload files