• Define and own the product roadmap, aligning it with company goals and priorities. • Gather and analyze business requirements, transforming them into clear, actionable user stories with defined acceptance criteria. • Prioritize the product backlog based on business value, technical complexity, and customer impact. • Facilitate communication and alignment across tech, product, and business stakeholders. • Collaborate closely with Engineering, Design, QA, and DevOps teams to ensure timely, high-quality product delivery. • Perform acceptance testing and validation of new features before release. • Monitor and analyze product performance using tools such as Power BI or similar; iterate based on data and user feedback. • Contribute to post-launch processes, including documentation, knowledge sharing, and product training. • Own and manage the payments squad covering Argentina, Chile and other markets, ensuring roadmap alignment across all countries. • Monitor and manage payment acceptance rates with providers and merchants in each market, proactively identifying and addressing drops or anomalies in performance. • Maintain active product-level relationships with payment providers in the countries we operate, collaborating with their product teams to align on roadmaps, integrations, and new capabilities. • Ensure compliance with local payment regulations in Argentina, Chile and other markets, staying up to date on regulatory changes that may impact product strategy.

Drive product strategy and pricing decisions to achieve profitability targets, analyze market opportunities, and implement product changes while collaborating with experts to enhance customer experience and ensure compliance with regulations.

• Lead product management for Icario’s platform evolution, including new capability development, legacy platform migration, and modernization of core product workflows. • Own roadmap planning and prioritization for platform capabilities, balancing business value, client impact, technical feasibility, operational readiness, scalability, and strategic importance. • Partner closely with Engineering leadership to define buildable product requirements, clarify scope, sequence delivery, manage tradeoffs, and drive execution. • Translate business, client, operational, and technical needs into clear product requirements, user stories, acceptance criteria, and roadmap priorities. • Ensure new capabilities are designed as reusable platform patterns rather than one-off client-specific solutions wherever possible. • Apply thin-slice MVP discipline to platform and capability development, ensuring work is broken into focused, high-value increments that reduce scope creep and accelerate learning. • Define the minimum viable version of new capabilities, including clear problem statements, success criteria, must-have requirements, and intentional exclusions. • Sequence platform investments in a way that delivers business value early while preserving the ability to scale, extend, and improve capabilities over time. • Push back on over-scoped requirements, premature complexity, and edge cases that should not block initial delivery. • Partner with Engineering to balance speed, scalability, maintainability, and iteration when defining MVP scope and future enhancement paths. • Lead product discovery and requirements definition across cross-functional stakeholders, including Engineering, Product Operations, Operations, Client Success, Commercial, Support, Data, Analytics, and implementation teams. • Drive clarity around what should be built, why it matters, what problem it solves, how it should work, and how success will be measured. • Support the migration from legacy platforms to the new platform by identifying capability gaps, sequencing migration priorities, reducing dependency on legacy workflows, and ensuring continuity for clients and internal teams. • Partner with Product Operations and Operations to ensure new platform capabilities are operationally ready, supportable, and scalable. • Partner with Support and Client Success to identify recurring product friction, production issues, workflow gaps, and opportunities to improve platform stability and usability. • Create stronger product discipline around requirements quality, backlog readiness, prioritization, release planning, and cross-functional decision-making. • Use Jira and Confluence effectively to create visibility into roadmap priorities, backlog readiness, sprint/release scope, dependencies, decisions, risks, and delivery progress. • Establish strong Jira and Confluence discipline across the Product Management team, ensuring product work is well structured, well documented, and easy for Engineering and stakeholders to understand. • Act as a true player-coach by leading the Product Management team while also directly contributing to discovery, requirements definition, backlog refinement, prioritization, and delivery execution.

• Own product discovery, requirements definition, prioritization, and delivery for data, analytics, reporting, and intelligence capabilities within Icario’s platform. • Partner closely with Engineering, Data Engineering, Analytics, and Architecture teams to define buildable requirements, clarify technical dependencies, and support execution. • Translate business, operational, client, and user needs into clear product requirements, user stories, acceptance criteria, workflow definitions, and success measures. • Prioritize product work based on business value, client impact, platform scalability, data quality, technical feasibility, and alignment to product strategy. • Support the evolution of Icario’s new platform by defining capabilities that improve data visibility, reporting accuracy, analytics usability, performance measurement, and decision-making. • Work with cross-functional stakeholders to understand current reporting and analytics pain points, workflow gaps, data dependencies, and opportunities for platform improvement. • Partner with Engineering to refine scope, sequence delivery, resolve ambiguity, and make informed tradeoff decisions throughout the product development lifecycle.