• Diversify the DTC funnel. • Define and execute the strategy for scaling paid social and other paid channels alongside our existing paid-search acquisition. • Make Brightside resilient against single-channel concentration risk. • Personalize the funnel by channel and intent. • Lower-intent prospects from one channel shouldn't be treated the same as higher-intent prospects from another. • Design differentiated creative, landing experiences, and — where the data supports it — different funnel flows for different audiences. • Orchestrate the messaging journey alongside the funnel. • Partner with lifecycle marketing to design and test the email and SMS touchpoints that move prospects through to conversion and activation — with the same channel-and-intent-aware lens as the on-site funnel. • Conversion doesn't only happen on-site; it happens between sessions. • Sharpen targeting on our largest paid channel. • Replace today's more generic approach with tactics that differentiate by prospect CAC:LTV. • Move from "more traffic" to "better-economics traffic." • Lift partner and health-system referrals. • Build for the operations team, too. • Run rigorous experiments. • Define hypotheses, design A/B tests, interpret results, and ship the wins. • Partner with engineering to make the funnel dynamic.

• Lead end-to-end product delivery for new verticals — Games, Influencers, Retail, Telecom — from strategy through specs to partner launch. • Own the page auto-generation system for millions of dynamically-generated pages: UGC integration, SEO automation, sitemap generation, Schema.org structured data, and 26-language localization. • Define and instrument KPIs across all Pages plugins (claim rate, conversion, indexation, partner adoption); build dashboards with the analytics team. • Own ELIAA attribution integration end-to-end — technical design, alignment with the ELIAA team, integration into the XLA Pages architecture. • Manage the Pages product backlog across multiple Jira projects (SB, XPF, XPM, XLAPAGES, EXM); run sprint planning, dependency tracking, deadline management. • Partner with engineering, design, SEO, BD, and partner-facing teams to ship with quality and speed. • Serve as the subject-matter expert for Pages across the Xsolla org — translate executive vision into engineering execution.

• Own the product roadmap and execution for the TPO business line. • Research, validate, and build product foundations for new residential business models. • Identify and evaluate opportunities in adjacent residential energy markets. • Work with Finance & Revenue Operations to develop and implement pricing models. • Apply deep product thinking to identify core business and partner friction points. • Work closely with Engineering, Go-to-Market, and Operations to ensure product alignment.

• Own the long-term vision and roadmap for Panorama's platform capabilities, including shared services, foundational infrastructure, developer tooling, and operational standards. Drive alignment across engineering and product leadership on platform priorities, sequencing, and investment levels. Translate business strategy into platform architecture decisions that hold up over years, not quarters. • Serve as the connective tissue between platform and product teams, ensuring shared infrastructure accelerates rather than constrains. Define how platform capabilities are built, documented, and adopted across the organization. Establish the standards and patterns that other teams build on, raising the bar for quality, consistency, and velocity across the board. • Lead platform strategy discussions with engineering leadership, SRE, data, security, and legal. Drive alignment on complex, multi-team initiatives where priorities and tradeoffs cut across organizational boundaries. Represent the platform perspective in executive conversations and company-level planning. • Own the definition of what "platform health" means at Panorama and drive the initiatives that get us there, covering performance, resiliency, cost efficiency, and operational maturity. Balance near-term delivery with the longer-term investments that prevent compounding technical risk. Own the framework for triaging reactive and unplanned work — ensuring the team can respond to operational demands without losing sight of strategic priorities. • Define what "done" looks like for platform initiatives and hold that line with rigor. Manage competing pressures between engineer-identified improvements, business-driven priorities, and reactive demands. Keep projects from expanding indefinitely by establishing clear completion criteria and making tradeoffs explicit. Build shared discipline around scope so the team moves with focus rather than accumulating open-ended work. • Partner with security and legal leadership to shape how platform capabilities support Panorama's security, privacy, and compliance obligations at a strategic level. Ensure risk reduction is embedded in platform thinking from the start, not bolted on at the end. • Own how platform strategy is communicated to senior leadership and the broader organization. Provide clear, compelling narratives about platform investment, progress, and tradeoffs that connect technical decisions to business outcomes.