foodsmart - VP, Partnerships

• Referral Growth StrategyDesign and own the multi-year referral growth roadmap across all partnership verticals. Establish a shared volume framework that connects FQHC referrals, food ecosystem partnerships, and community enrollment into a unified measurement system. Identify which channels represent the highest-leverage bets by market and by population, and allocate resources accordingly. • Institutional Partnership DevelopmentPersonally lead the identification and structuring of new partnerships with Federally Qualified Health Centers (FQHCs), Community Health Centers (CHCs), pharma organizations, hospital systems, FindHelp, UniteUs, and other SDOH-adjacent platforms. These are complex, multi-stakeholder negotiations requiring fluency in clinical workflows, procurement processes, and population health goals. • Team Leadership & Development Serve as a visionary leader and mentor to a high-performing team. Foster a culture of high performance, accountability, and continuous professional development, while thoughtfully expanding team capacity to meet future growth demands. • Food & Retail EcosystemProvide executive oversight for Foodsmart's food vendor partnerships and marketplace strategy, including national retailer relationships (Walmart, Amazon, Instacart) as well as community-level food bank and SDOH organizations. Work with the Sr. Director of Food Partnerships to build a differentiated marketplace value proposition that deepens member engagement and drives referral volume. • Distribution & Channel PartnershipsDevelop and manage relationships with distribution and channel partners — including supplemental benefit platforms (Soda Health, Nations Benefits), benefit management platforms (Lynx), and others — that create access to new member populations at scale. This requires an understanding of how benefit platforms price, structure, and distribute services. • Operating Cadence & Pipeline ManagementBuild the operational infrastructure for this team: a shared CRM-based pipeline, segment-level performance tracking, a partner health scorecard, and a forecasting methodology that can be trusted by leadership. The VP will bring rigor and accountability to this function. • Cross-Functional AlignmentWork closely with the CGO, Chief Clinical Officer, product, and payer/provider sales teams to ensure partnership structures are consistent with clinical quality standards, network requirements, and member experience expectations. Referral volume only creates value if it converts to engaged, retained members. • ## What Great Looks Like: • In Year 1, the VP of Partnerships will: • Develop and present a partnership strategy that prioritizes channels by market, population type, and conversion potential with near-term and long-term growth targets • Provide mentorship to the current team and map out a thoughtful capacity-building plan to support long-term partnership growth • Stand up a shared pipeline management system and partner performance framework • Directly secure or re-structure at least 2–3 high-value institutional referral partnerships • Assess and sharpen the food vendor marketplace strategy • Establish operating norms and team accountability frameworks, and a strong management culture focused on coaching and enablement • A Partnership Architect — not a manager of existing relationships, but a builder of new ones. You identify structural opportunities and create the frameworks that make them repeatable. • Mission-Aligned — genuinely motivated by the intersection of food access, health equity, and healthcare delivery. You can speak to SDOH fluently because you care about it. • Strategically rigorous with executional discipline — you can move between market-level strategy and pipeline spreadsheet accountability in the same meeting. • Highly politically fluent — able to navigate the complexity of FQHC leadership teams, retail procurement organizations, pharma corporate affairs teams, and community health stakeholders with equal ease. • Leader, strong builder and developer of talent — you elevate the people around you and create clarity, not dependency. • Comfortable with ambiguity at scale — you can design structure where none exists and iterate quickly without losing direction.