likely consumes vendor-specific tips (e.g. he might Google Oracle audit defense strategies or read whitepapers on Negotiating cloud contracts from consultancies). He is active on LinkedIn, following companies that share licensing tips or negotiation case studies. He may use analyst reports (Gartner, Forrester) for pricing benchmarks if available. Short, pointed content like checklists (Top 5 costly mistakes in SaaS contracts) resonate with him. Buying Cycle Behavior: Pete could be the one to initiate contact with RTC when a particularly challenging negotiation looms (e.g. We have SAP coming up, maybe we need extra help). In Awareness, he identifies a knowledge gap or tough vendor. In Consideration, hell evaluate a few specialized firms likely reaching out to ones hes heard of in sourcing circles. Hell get into detailed discussions (evaluation) focusing on how exactly theyd help him in negotiations. He might do a pilot or limited-scope trial (like engage on one contract) to test results. During Decision, hell weigh if giving up a portion of savings is worth it versus doing internally a logical ROI calculation. If he decides yes, hell then integrate RTCs team with his (e.g. share contracts, strategize together). Once engaged, hell be highly collaborative viewing them as extended team if trust is built, maybe letting them draft negotiation scripts or sit in on calls under NDA. Post-engagement, if it went well, he becomes a recurring client for other deals and will recommend to peers privately (though publicly procurement folks are sometimes coy about using consultants as they want credit for savings themselves). Persona: COO Chloe The Operations Optimizer (optional, since prompt mentioned COO): Role & Demographic: Chloe is Chief Operating Officer at a manufacturing company. Early 50s, oversees operations including supply chain, manufacturing, and also IT often reports to her (if no separate CIO, or even if there is, ITs performance affects operations). Shes very efficiency-focused. Goals/KPIs: Ensure smooth operations, product delivery, optimal cost structure in operations. She cares about operational cost ratios, process efficiency metrics, downtime . For IT, her interest is that IT systems reliably support operations at minimal necessary cost. Perhaps tasked with cross- department cost reduction initiatives. Challenges: She sees IT costs rising but doesnt always see the impact on operations improvement proportionally. She might think there are too many tools or complex processes . Example: multiple ERP modules making things clunky a simpler, cheaper setup might streamline ops. Shes frustrated if IT spends limit budget for plant improvements or new machinery. She might not know IT details well, which is frustrating when trying to rationalize budgets. Decision Criteria: Chloe will support cost optimization that doesnt compromise production or quality. Shell ask: will this affect operational continuity? Also, does it free funds for operations improvements? She likes holistic approaches (not silo cost cutting that inadvertently hurts another department). Objections/Fears: She fears any cost cutting that could risk downtime or slow user performance (if IT cuts network costs and factories cant connect reliably, huge problem). Also worried about change management any consolidation or removal of systems could disrupt staff workflows. Motivators: Operational excellence show how reducing IT waste can actually simplify processes and reduce chances of errors (e.g. less software = less complexity). Control she likes knowing things are under control; cost optimization under a structured approach appeals. Results shes very result-driven; quick wins that show up in margin improvements quarter over quarter will motivate her. Also, cohesion shes motivated by initiatives that involve cross-functional improvement (IT and ops working together). 27. 28. 29. 30. 31. 32. 33. 34. 38