yields clear business value or is minimized if not. A personal goal is to free up funds for strategic investments or to meet quarterly earnings targets without resorting to headcount cuts. Challenges/Pain Points: Carl feels frustration at the opacity of IT spending . He often sees large IT budget proposals with complex justifications he isnt fully comfortable challenging (do we really need all these software licenses?). He worries the company might be overpaying vendors or paying for unused technology . Another pain: unpredictable costs cloud bills sometimes come in 20% higher than forecast, throwing off budgets. Hes also concerned about duplication multiple departments buying similar tools without coordination, causing shadow IT costs. Carl is not an IT expert, so he relies on the CIO for technical insight, but he sometimes feels CIOs are more growth/ innovation oriented and not as aggressive on cost efficiency as hed like. A looming pain point: meeting earnings guidance in a tough market; he needs to trim fat, and IT seems a promising area if done right (but he lacks detail to do it himself). Decision Criteria: Carl will green-light initiatives that have clear ROI and low risk . For an external partner like RTC, he looks for evidence of credibility (track record, other CFO testimonials) and a financially sound proposal . Key criteria: Projected savings vs. cost (he likely expects at least a 5:1 return), guarantees or contingency (he loves when consultants share risk), impact on operations (must assure that cost cuts wont harm business continuity or growth he doesnt want cut IT and then systems go down). He also values speed (savings realized within the fiscal year is ideal to hit targets) and compliance (no legal issues from recommendations). Objections & Fears: Carl might object: We already have an internal procurement team; why pay someone externally? or Consultants cost too much what if their fee eats most of the savings? His risk factors: fear that external folks wont understand their business context and might cut muscle instead of fat (loss aversion he fears losing essential capabilities). He might also worry about vendor relationships e.g. if pushing vendors too hard could jeopardize partnerships or service quality (trust and continuity concerns). Another possible objection: confidentiality sharing sensitive contract info with a third party and trust they maintain secrecy. Motivational Triggers: Loss aversion is big: showing him how much money is being left on the table or wasted (e.g. Carl, 30% of your software spend might be going unused thats like throwing away $3M a year ). This will trigger his drive to act to avoid that loss. Trust and credibility : references to success at similar companies (especially if a peer CFO endorses). Control: giving him line of sight and control mechanisms (reporting) over IT costs will appeal to his need for financial governance. Hes also motivated by personal achievement being the CFO who championed an initiative that significantly improved margins (prestige among his peers and maybe a bonus tied to cost reductions). Media & Content Habits: Carl reads financial press (WSJ, The Economist) and industry-specific CFO forums. He likely attends CFO network events or listens to webinars on cost management and enterprise performance. He might browse Gartner or McKinsey insights if forwarded by his team. Hes not likely trolling tech blogs, but he will read a concise case study or one-pager that quantifies results. If RTC produces a CFOs Guide to Optimizing IT Costs whitepaper with clear financial language, that would attract him. He also might get information via his network e.g. a fellow CFO telling him about how they saved money using an external FinOps advisor. Buying Cycle Behavior: Carl is usually not the one initiating a search for a cost consultant (the CIO or procurement might bring it up), but once aware, he becomes a key sponsor. In the Awareness stage , Carl might realize internal cost-cutting efforts stalled and become receptive to new ideas. During Consideration , hell instruct his team to gather options (likely asking CIO or procurement to vet and bring proposals). He then gets involved in Evaluation , scrutinizing ROI projections and contract terms. At Decision , hell present to CEO if needed and sign off. If he feels confident in the 4. 5. 6. 7. 9 8. 9. 34