Potential Partners: Organizations like the Technology Business Management (TBM) Council, FinOps Foundation, as mentioned, or CFO leadership councils, etc. Partnership Value: Co-host events or content which gives credibility and reach. Eg, FinOps Foundation might let RTC experts host a webinar for their members or contribute to their content library. TBM Council (which focuses on IT value management) might allow sponsoring or speaking at their conferences. Structure: Typically these involve membership fees or sponsorship deals, but yield platform to share thought leadership to highly relevant audience. It's less lead referral and more brand-building and soft leads (people see them as partners and trust more). Example: If RTC is sponsor at TBM Council event and perhaps leads a panel on cost optimization, that partnership event can directly lead to new relationships and clients. Implementation of Partnerships: - Create a small partnerships taskforce (maybe one BizDev person focusing part-time on developing these). - Identify top 5 target partners in each category and reach out with partnership proposals highlighting mutual benefits (e.g., "We can help your clients realize more value which reflects well on your service/tool, and well refer clients to use your platform where appropriate"). - Formalize referral mechanisms: NDAs and referral agreements in place to share client info and credit appropriately. Possibly provide training to partners sales on spotting triggers for needing RTC (so they can refer effectively), and vice versa train RTC team on partners offering to spot when to loop them in. - Joint marketing: e.g., do co-branded case studies ("SoftwareOne + RTC helped Client X..."), co-host events, exchange blog guest posts. Integration with Sales Strategy: - If a lead comes via partner, define how its handled in CRM (tag as partner lead, maybe faster track since likely warm). - Provide feedback and success stories back to partners to encourage more referrals. - Possibly offer partners finder's fee or reciprocal referrals (ex: if RTC finds a client needs a SAM tool, they recommend the partners). - For PE, sometimes they will just bring you in without expecting fee (because its for their portfolios benefit), but one might give them top-tier service and maybe volume discount or success arrangement to strengthen relationship. Risks & Mitigation: - Conflict of interest: ensure if partnering with VARs, independence is preserved (we should still advocate best cost even if partner sells the product align expectations). - Quality control: If partnering with smaller consultancies (like others who might bring us in or vice versa), vet them to ensure their values align (we dont want to get burned by a partners poor delivery affecting our brand). - Clear boundaries: e.g., with FinOps software, we dont develop competing software; with VAR, we dont resell product making roles complementary. - Avoid over-reliance on one partner: diversify partnerships so pipeline isnt too tied to one source that could dry up. Metrics for Partnerships: - Number of leads or intros from partner per quarter. - Conversion rate of partnered leads vs other leads (often higher if partner pre-sells your value). - Revenue influenced by partners (maybe track any project where partner was involved or referring source). - Growth of these metrics over time as partnership matures. Strategic partnerships, done right, can become force multipliers they open doors that marketing $$ alone cannot. Especially in an industry where trust is paramount, being endorsed by a known player (a FinOps tool or a PE firm or a top VAR) accelerates trust-building with the client. It effectively leverages 68