AI Product Leader · Product strategy & growth

Turning complex technology into products that matter.

Hi, I’m Frances 👋 I’m an AI product leader who connects technical depth, customer insight, and commercial strategy. I lead new product launches, cross-team platform strategy, and adoption growth, with experience spanning AI agents, enterprise governance, and usage-based monetization.

AI product strategyEnterprise trust & adoptionMonetization & growth
GitLab · Agentic AI

Duo Developer & Agent Harness

350% paid-user growth in one quarter

Product DRI for GitLab’s coding agent across remote execution and CLI; owned product direction for platform primitives and the shared agent harness, alongside quality, onboarding, and adoption improvements.

Platform scope included execution, orchestration, context management, memory, and reusable subagents.
PagerDuty · Product ownership

AIOps Operations Console

80%+ daily enterprise-account usage

Owned the 0→1 Console launch, giving operations teams a central view of incidents, prioritized signals, and remediation actions.

Paid enterprise accounts with daily Operations Console usage.
PagerDuty · Monetization & GTM

Consumption-based AIOps SKU

Multimillion-dollar ARR

Led the AIOps SKU launch, owning monetization strategy, billing readiness, and go-to-market execution.

Reached multimillion-dollar ARR and exceeded targets by the end of the second quarter.
Deloitte Digital · Omnia AI

McKinsey's Data Platform

30K+ users in one quarter

Led a 20+ person engineering and data-science team building an ML-driven company-intelligence platform, turning public company data into enriched profiles and research insights.

McKinsey was the client of TWG, acquired by Deloitte Digital; project details are kept high-level.

Experience: GitLab · PagerDuty · Deloitte Digital · Loblaw Digital · PwC Strategy&

Greater Seattle Area · Principal / Senior AI Product Manager opportunities

01 / Selected Product Leadership

Complex problems. Clear decisions. Measurable impact.

Here are a few stories from my work, including the decisions I owned, the teams I worked with, and what we learned along the way.

01 · GITLAB · CODING-AGENT QUALITY

Build agent quality that scales across model families

SIGNAL

Coding-agent quality depended on the model, context management, tool execution, and customer environment. Benchmark results alone could not tell us where to invest.

DECISION

I made the call to prioritize context compaction after reviewing failure patterns and trade-offs with Engineering, focusing investment on shared agent reliability.

RESULT / EVIDENCE

Shipped context-compaction and tool-result handling improvements; task completion improved during the quality work. The paid-user growth above reflects broader quality, onboarding, and adoption improvements.

Root-cause analysis · SWE-bench Pro & Verified · Production feedback

My role, trade-offs, and measurement

As Product DRI for Duo Developer, I worked with Engineering to distinguish model limitations from context, tool, and execution issues. I made the prioritization call for compaction after reviewing the evidence, rather than relying only on more available context or future model improvements. The trade-off was investing in shared context management while protecting information that longer coding tasks depend on.

I tracked task completion weekly and used SWE-bench Pro and Verified alongside latency, costs to us and customers, production telemetry, and developer feedback. Real repositories and execution environments could reveal problems that standardized benchmarks missed.

My focus was the product judgment behind the investment: where shared infrastructure would improve developer outcomes, and how to keep learning as models and production needs evolved.

I evaluated compaction frequency and cost when deciding how to support it across deployment models, prioritizing a consistent implementation over deployment-specific forks. This connected agent reliability with operating cost and implementation complexity.

Related decision: routing economics and billing

I influenced the direction toward token-based or hybrid billing rather than pure request-based pricing. My contribution connected model selection and task routing with quality, latency, and inference economics. A request alone could hide substantial differences in the work an agent performed; the pricing discussion needed to account for that variability.

02 · GITLAB · ENTERPRISE AI GOVERNANCE

Give enterprises control without slowing agents down

SIGNAL

Ahead of general availability, enterprise customers needed stronger governance to deploy coding agents with confidence.

DECISION

I advocated keeping essential controls and configuration in the base Duo Agent Platform, while positioning advanced AI policy and risk detection in the AI Governance offering. The trade-off was paid differentiation versus a usable, secure starting experience.

RESULT / EVIDENCE

Delivered GA-critical access and security controls to address enterprise adoption blockers and help advance enterprise opportunities.

Enterprise security · Customer adoption · GA readiness

What I led

As the sole Product Manager for Agent Foundation, partnering with 25+ engineers before the reorganization, I owned enterprise AI governance strategy. After the reorganization, I owned Duo Developer and the Flow Component team within Agent Foundation.

I pushed to retain composite identity, basic prompt-injection protections, administrator-configurable human oversight, audit logs, and session details in the base platform. Builders, users, and administrators needed meaningful control from their first experience. I positioned advanced AI policies, policy-violation detection, and shadow-AI capabilities as the differentiated governance scope, rather than making foundational controls a prerequisite purchase.

Alongside governance, I established a cross-team observability roadmap spanning developer debugging, administrator oversight, execution traces, failure analysis, usage, and auditability.

03 · PAGERDUTY · 0→1 AIOPS

Prove value in an MVP. Then build the platform.

SIGNAL

PD Live, built with a solutions consultant, attracted paying enterprise customers before we committed to a production platform.

DECISION

Used paid customer validation to build the investment case and financial model, then owned strategy, roadmap, and production launch of the AIOps Operations Console.

RESULT / EVIDENCE

Launched the Operations Console as a core product for incident monitoring and remediation. In a separate commercial workstream, I led the consumption-based AIOps SKU launch.

Paid MVP → Investment case → Production

From PD Live to the core product

As product DRI, I partnered with a solutions consultant to build and validate PD Live with paying enterprise customers. I then led the business case and financial model to secure investment and bring the concept into PagerDuty’s AIOps Operations Console, a centralized experience helping operations teams monitor incidents, prioritize signals, and identify remediation actions.

Consumption-based AIOps SKU: launch and monetization

I led the launch of the consumption-based AIOps SKU, owning monetization strategy, billing readiness, and go-to-market execution. I partnered with Solutions Engineering and Customer Success to translate the offering into enterprise value conversations and adoption plans.

About GitLab and PagerDuty

GitLab builds a software-development platform used by teams and their AI agents. Its company-wide reach includes 50M+ estimated registered users (June 2026). Company source ↗

PagerDuty provides digital operations and incident-response software. Its company-wide customer reach includes 68% of the Fortune 100. Company source ↗

I’d welcome a conversation about the decisions, trade-offs, and lessons behind these projects. Some implementation details and commercial figures remain confidential.

02 / My Journey

Curiosity has shaped every chapter.

My trajectory has been toward deeper ownership of increasingly complex technology. I started in commercial analysis and strategy, moved into digital products and ML, and grew into enterprise AIOps and agentic AI. The direction has stayed consistent: understand harder systems and connect customer, technical, and business decisions.

How I got here

PwC Strategy& taught me how to frame the problem. Leading market-entry, operating-model, and digital transformation work taught me to question assumptions and turn ambiguity into a direction.

Loblaw Digital taught me to connect data science with customer outcomes. I worked with Data Science and ML Engineering to bring classification, segmentation, and personalized recommendations into production for a grocery business serving millions of active users.

Deloitte Digital, Omnia AI, taught me to turn direction into systems. I led a 20+ person engineering and data-science team delivering McKinsey’s ML-driven company-intelligence platform. I owned the roadmap and ML feature priorities, partnering with Data Science on experiments and ML Engineering on production data pipelines.

PagerDuty and GitLab expanded my end-to-end ownership. From paid MVP validation and AIOps monetization to coding-agent quality and enterprise governance, I grew into decisions that connect the product, the platform, and the business.

What I’m exploring

What’s next

I’m building my next chapter in the Greater Seattle Area. I’m looking for a team where I can keep tackling meaningful AI problems, invest deeply in the work, and build lasting relationships with people who care about what they create.

Greater Seattle Area · Authorized to work in the U.S. without employer sponsorship

03 / How I Lead & Build

Connecting the dots. Moving fast with purpose.

I like working close to the problem and close to the team. I bring customer insight, data, and business context into technical conversations, and build prototypes to validate ideas and make trade-offs tangible. Working hands-on with Engineering helps me turn strategy into focused bets we can ship, evaluate, and improve together.

Clarity when the path is uncertain

There rarely is a complete roadmap in fast-moving AI. I start with the customer problem, make assumptions explicit, and align on the next decision or experiment. At PagerDuty, paying MVP customers helped shape the investment case; at GitLab, failure patterns helped shape quality priorities.

Technical judgment at the systems level

I look beyond individual features to understand how decisions affect the whole product: reliability, enterprise trust, customer experience, and economics. At GitLab, that meant connecting agent identity, delegated permissions, execution, and observability so teams could make platform decisions that worked together. I use evaluations and production feedback to weigh quality, latency, cost, and developer experience.

Hands-on enough to make ideas tangible

I build prototypes to validate ideas and accelerate decisions. Working alongside Engineering, I test product and technical trade-offs and contribute small, scoped code changes through merge requests. It helps me bring something concrete to the conversation, learn from implementation constraints, and refine the direction with the team.

Empathy paired with evidence

Customer conversations and data belong in the same room. I want engineers and designers to understand the human problem behind the work, not just the requested feature.

Trust is how difficult work gets done

I invest in lasting partnerships with engineering managers, engineering leaders, designers, and engineers. Honest debate, shared ownership, and showing up for one another make difficult decisions easier, and better work possible. Those colleagues can speak directly to how we worked together.

“I ask better questions to find what matters, connect the dots others might miss, and help teams turn complexity into meaningful progress.”