Tag: AI Strategy

Pendo’s Summer Release: How I Reimagine Onboarding, Support, and Expansion in the SaaS + AI Era

I’ve been reflecting on How Pendo’s Summer Release reimagines onboarding, support, and expansion in the SaaS + AI era, and it resonates deeply with the product-led playbooks my team and I use every day. The core promise is simple and powerful: “These three best practices aren’t new, but how you achieve them is.” That framing captures the shift I see across high-performing product organizations—same outcomes, radically upgraded execution through AI, in-app experiences, and unified analytics.

For onboarding, I prioritize accelerating user activation with clear product tours, in-app guides, and great UX writing that removes cognitive load. The difference now is how precisely we personalize these moments: segmentation driven by product usage, CRM integration, and experiments (A/B testing with a disciplined minimum detectable effect) help us craft paths that meet users where they are. When onboarding is instrumented this way, it becomes a scalable engine for product-led growth rather than a one-time setup task.

Support is undergoing an equally meaningful transformation. Contextual, in-app help combined with agentic AI can diagnose issues, surface relevant knowledge, and guide users without forcing channel switches. I’m bullish on this, but only when it’s anchored in privacy-by-design, AI risk management, and strong data governance—trust is the prerequisite for any customer support AI strategy. When done right, support shifts from reactive ticket resolution to proactive value delivery.

Expansion, to me, is the earned outcome of consistent product value. In the SaaS + AI era, we can use unified analytics to identify readiness signals—feature adoption, outcomes achieved, and time-to-value—and trigger timely, ethical nudges in-app. The best motions align offers with real customer milestones, whether that’s consumption SaaS pricing upgrades, role-based add-ons, or advanced capabilities unlocked through demonstrated need. This is product-led growth at its most customer-centric.

Underpinning all three motions is measurement discipline. I push for a unified analytics platform that ties together behavioral data, retention analysis, funnels, and cohorts with downstream CRM integration. That allows product trios to make fast, informed decisions and connect activation, support efficiency, and expansion to business outcomes. Whether your stack includes Pendo, Amplitude analytics, or custom pipelines, the principle is the same—one source of truth that informs action.

Execution matters as much as strategy. Empowered product teams working in tight product trios can ship small, valuable increments, run clean experiments, and learn faster than the market shifts. Strong stakeholder management and clear product roadmapping keep leadership aligned on outcomes vs output OKRs, so we’re funding what works and pruning what doesn’t. In my experience, this operational rigor is what turns promising ideas into durable competitive differentiation.

If you’re looking to operationalize these ideas, start by defining activation and expansion milestones that map to your value proposition. Instrument your in-app guides and product tours to support those milestones, and commit to an experimentation cadence with well-defined MDE. Layer in agentic AI carefully—pilot in the support surface where context is rich and stakes are clear—and enforce privacy and governance from day one. Finally, close the loop with unified analytics so every improvement compounds.

Pendo’s Summer Release highlights a broader reality: our industry isn’t inventing new destinations, we’re modernizing the routes. Onboarding, support, and expansion remain the pillars—but AI, in-app experiences, and integrated data make them smarter, faster, and more human. That’s the shift I’m leaning into—and the one customers feel immediately.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
Build the Cake, Then the Frosting: 3 Elements of a High‑Performing AI Strategy That Wins

Over the past few years leading product at HighLevel, I’ve watched too many teams rush to demo flashy agents before they’ve built a reliable foundation. The metaphor I use in every AI roadmap review still hits home: “Think of AI readiness as a three-layer cake. Most companies are trying to build the fancy frosting (the agent interface) without bothering to bake the actual cake underneath.” If we want durable impact, we have to bake first, frost later.

When I design an AI Strategy, I anchor on three elements that map directly to that cake: a data and instrumentation foundation, a governance and risk layer, and finally the agent experience itself. This sequence isn’t theory—it’s how we de-risk delivery, accelerate product-market fit, and create competitive differentiation without compromising trust.

Layer 1 — Data and instrumentation: The base of the cake is clean, well-instrumented data flowing through a unified analytics platform. I start with a clear event schema, rigorous data quality checks, and tight CRM integration so we can connect outcomes to users, accounts, and journeys. Privacy-by-design is nonnegotiable: we minimize PII, define retention, and ensure consent flows are explicit. With this in place, gen ai features have the context they need—retrieval works, grounding holds, and feedback loops from production inform continuous improvement.

On top of that, I build measurement in from day one: activation, retention, task success, latency, and satisfaction. Every AI interaction is observable. We run A/B testing with a well-defined minimum detectable effect, pair quant with qualitative review, and feed human-in-the-loop judgments back into ranking and prompt libraries. This is how we avoid “demo-ware” and deliver real, repeatable value.

Layer 2 — Governance and risk: Before scaling, I formalize AI risk management and data governance. That includes model evaluation against safety and quality thresholds, red-teaming for jailbreaks, and threat detection and response for prompt injection and data exfiltration. We establish policy for model and provider selection, versioning, and rollback; we log prompts, responses, and decisions for auditability; and we define escalation paths when the system is unsure. These controls don’t slow us down—they create the confidence needed for faster iteration and board management alignment.

I also align legal, security, and product early on a taxonomy of risks—bias, hallucinations, privacy, IP leakage—so we can write tests and guardrails once and reuse them across features. The result is fewer surprises in customer pilots and a far smoother path through enterprise procurement.

Layer 3 — The agent experience: Only now do we invest in the frosting—the agent interface and workflows. Here I focus on clear jobs-to-be-done, crisp UX writing, and transparent system behavior. We design agentic AI flows that show reasoning steps when helpful, ask for clarification when confidence is low, and gracefully hand off to humans in customer support scenarios. Product tours, in-app guides, and tooltips reduce the learning curve and accelerate user activation.

Crucially, we measure the interface, not just the model. Agent Analytics tracks intents, tool use, fallbacks, and user corrections so we can tune prompts, tools, and policies. This closes the loop from experience back to data and governance, and it directly informs product roadmapping and sprint planning. When the cake is baked this way, go-to-market becomes easier: we can prove ROI with hard numbers, fine-tune pricing, and scale adoption with product-led growth tactics.

If your AI roadmap feels stuck, start with an honest readiness audit against these three elements. Shore up instrumentation and data pipelines, codify governance, then refine the agent interface with real user telemetry. Bake first. Frost last. That’s how we ship AI that customers trust—and keep winning after the first demo high fades.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
4 Costly Misconceptions About AI Agents—and What Product Leaders Must Do Instead

Building AI agents looks deceptively simple right now. After leading multiple agentic AI initiatives, I’ve learned that the difference between a demo and a dependable product comes down to disciplined product discovery, ruthless scoping, and a clear AI Strategy that aligns with business outcomes. Here are four common misconceptions I correct early with stakeholders—and the practices I use to avoid expensive detours.

Misconception 1: “An LLM plus a few prompts is a production-ready agent.” In reality, production-grade agents require orchestration and rigor: tool-use and retrieval, memory design, state management, deterministic fallbacks, and continuous evaluation. I instrument Agent Analytics from day one to trace tool calls, latency, error codes, and cost per task; then I use A/B testing with a clear minimum detectable effect (MDE) to validate improvements before broad rollout. This is where product roadmapping and sprint planning matter—sequencing capabilities so we avoid building speculative features that don’t move outcomes.

Misconception 2: “More autonomy is always better.” The right autonomy level is contextual and risk-adjusted. For high-stakes workflows, I design for human-in-the-loop and role-based guardrails, grounded in privacy-by-design and data governance. Policies like least-privilege access, audit logs, and reversible actions reduce operational risk while still delivering leverage. In practice, this hybrid approach also controls cost: narrower scopes, clearer prompts, and bounded tool access reduce hallucination surface area and improve reliability—key to AI risk management.

Misconception 3: “If we build it, users will adopt it.” Adoption is earned with thoughtful onboarding and in-app guidance, not promised by a feature launch. I pair agent launches with targeted product tours, contextual tooltips, and progressive disclosure to drive user activation and product-led growth. Increase revenue, cut costs, and reduce risk with Pendo’s Software Experience Management platform. Optimize the entire software experience to drive adoption and improve engagement. Whether you use Pendo or a comparable solution, the principle stands: instrument the experience, run experiments, and iterate quickly based on evidence, not intuition.

Misconception 4: “Security, compliance, and governance can wait.” Deferring controls is a false economy. I embed AI risk management from day zero: prompt injection defenses, PII redaction, DLP, grounding and citation strategies, and threat detection and response. Clear data retention policies, vendor diligence, and model evaluation standards keep leadership, security, and legal aligned. This is the crux of building trust—and it’s far easier to design up front than to retrofit under pressure.

How I execute in practice: start with a tightly framed use case tied to a measurable outcome; define outcomes vs output OKRs; build a slim vertical slice to validate feasibility; instrument Agent Analytics from the first commit; ship behind feature flags; and operationalize learning loops across support, success, and GTM. The result is a durable path to product-market fit for agentic AI—one that compounds learning while minimizing blast radius.

The leaders who win with AI agents won’t be the ones who move fastest in a demo. They’ll be the ones who manage risk transparently, learn in public with their users, and turn continuous insight into competitive differentiation. If you’re planning your next agent milestone, align the roadmap to outcomes, treat governance as a feature, and make adoption your North Star.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
WTF is MCP? The powerful protocol giving enterprise AI agents real-world autonomy

I get asked this constantly by boards, CIOs, and product teams: WTF is MCP, and why does it matter for enterprise AI? Here’s my straightforward take from the trenches of rolling out agentic AI across complex, regulated environments—and why it changes how we design, govern, and scale autonomous capabilities.

“Model Control Protocol gives your AI agents arms and legs to go do stuff with your data.” That framing resonates because it’s both simple and accurate. MCP turns passive “chatbots” into active agents that can safely take action within defined guardrails.

In practice, MCP is the connective tissue between models and the tools, systems, and workflows we trust. It standardizes how agents request permissions, execute tasks, and report outcomes—so enterprises can move from demos to durable operations. The benefit isn’t just autonomy; it’s autonomy with accountability, aligned to our AI Strategy and data governance obligations.

When I pilot agentic AI in production, I start with a narrow scope: which systems the agent touches (for example, CRM integration via HubSpot), what actions it can take (read, write, or propose), and what evidence it must log (inputs, outputs, and approvals). That discipline keeps us compliant with privacy-by-design while unlocking real business impact.

Great MCP use cases emerge where read-write actions compress time-to-value. Think: pulling Amplitude analytics cohorts to personalize outreach, auto-generating Pendo in-app guides based on feature adoption, or triggering customer support workflows with predefined playbooks. Each action is observable, reversible, and measured—because in the enterprise, repeatability beats novelty.

From a product management leadership perspective, I treat MCP-enabled agents like any other product surface. We define clear outcomes, not outputs: success rate per task, mean time to resolution, quality score, and safety incidents. We validate uplift with A/B testing and a minimum detectable effect (MDE) before scaling. Then we feed results into an Agent Analytics dashboard, just as we would for product-led growth funnels.

Governance is where MCP earns trust. I enforce least privilege, time-boxed credentials, environment isolation, and tamper-evident audit logs. Every tool call is tied to a business purpose, owner, and SLA. We integrate with existing threat detection and response processes so cybersecurity teams see the same telemetry they’re used to—no shadow AI, no surprises.

There’s also an adoption playbook that works: start with a contained domain, ship a sandboxed agent, require human-in-the-loop approvals, then progressively relax controls as accuracy and alignment improve. Document the boundaries in plain language, and instrument everything from day one. This is how we de-risk AI risk management while accelerating impact.

The most exciting shift is cultural: teams move from asking “Can the model do this?” to “What outcomes should the agent own—and what guardrails make that safe?” That mindset unlocks empowered product teams, clearer ownership, and faster iteration. MCP is simply the operational backbone that lets those choices stick.

If you’re evaluating where to start, pick one workflow with high frequency, clear rules, and measurable outcomes. Wire it to MCP with tight scopes, ship it to a friendly cohort, and learn aggressively. Autonomy isn’t the end goal—reliable, governed value is. MCP just makes that scalable.

Inspired by this post on Pendo – Best Practices.

October 25, 2025
6 Hard Questions Your AI Agents Must Answer to Win: Performance, Risk, and Real ROI

“Do you know how your AI agents are performing?” I ask this question in every review because it exposes whether we’re managing by outcomes or by anecdotes. Too often, teams point to latency, token counts, or completion rates and call it a day—useful signals, but not the story.

In my role, shipping agentic AI into production means I need decision-quality evidence, not vibes. That starts with Agent Analytics built on a unified analytics platform and instrumentation that lets me trace behavior, quantify value, and manage risk. Below are the six questions I use to separate novelty from durable impact.

1) What outcome are we optimizing for—and how do we measure it? If we can’t map the agent’s work to outcomes vs output OKRs, we’re optimizing noise. I anchor on task success rate, time-to-resolution, containment rate (no human handoff), cost per successful outcome, and downstream business impact (retention, conversion, NPS/CSAT) to keep us honest.

2) Are the right guardrails in place for AI risk management and data governance? I expect documented policies for prompt injection defenses, PII redaction, access control, and auditability. Every tool call should be permissioned, every data boundary explicit, and every failure mode observable. If we can’t demonstrate compliance by design, we’re scaling risk instead of value.

3) Can I explain every decision the agent made? Agentic AI needs traceability: prompts, intermediate reasoning, tool calls, retrieved context, and final outputs. I route key events into Amplitude analytics so product, engineering, and risk can slice behavior end to end. If we can’t reconstruct the path to an answer, we can’t debug, improve, or trust it.

4) What is the true cost per successful outcome? Raw token spend is misleading. I model total cost of ownership across retries, tool usage, escalations, and human review time—then benchmark against a consumption SaaS pricing lens. If cost per resolution trends up as volume grows, we haven’t built a scalable system; we’ve built a demo.

5) How does the agent learn without breaking what already works? My bar is a disciplined experimentation loop: offline evals, online A/B testing with clear guardrails, and a rollback plan. We predefine a minimum threshold for improvement before rollout and track regressions by persona, task type, and channel so we can localize fixes quickly.

6) Where is this agent creating durable differentiation? I look for capabilities competitors can’t easily copy: unique data advantages, superior tool orchestration, or workflows that compound learning. If the edge is just a base model prompt, the moat will evaporate; if it’s embedded in product workflows and proprietary signals, we’re building advantage.

Answering these six questions turns agentic AI from a novelty into a managed system. With Agent Analytics feeding a unified analytics platform, we can tie behavior to business outcomes, enforce governance, and make portfolio trade-offs grounded in evidence. The result is a product management leadership motion that prioritizes real ROI over vanity metrics—and scales with confidence.

If you’re not satisfied with the answers today, start by instrumenting the journey end to end, aligning metrics to OKRs, and setting clear risk thresholds. The compounding effects show up quickly when every iteration is measurable, explainable, and accountable.

Inspired by this post on Pendo – Best Practices.

October 24, 2025
SaaS + AI Is Here: How Our Summer 2025 Release Builds an Intelligent Foundation to Win

Leading product at HighLevel, I’m watching the convergence of SaaS + AI reshape how we build, price, and scale software. The winners will combine a sharp AI Strategy with disciplined product management leadership to ship real outcomes, not just demos. That’s why my team and I have been focused on giving you pragmatic ways to move fast without breaking trust. Give your company an intelligent foundation for the SaaS + AI era with our Summer 2025 Release. When I set priorities for this release, I optimized for three things: speed with quality, responsible AI, and measurable business impact. Practically, that means enabling agentic AI and gen ai workflows where they actually create leverage, unifying analytics so teams can make decisions from a single source of truth, and hardwiring data governance and privacy-by-design into every layer. If you’re wondering how to keep up, here’s what’s working for us and our customers: tighten product roadmapping and sprint planning around clear outcomes, not outputs; align teams with simple, observable OKRs; and empower product trios to run lean product discovery loops. These practices reduce cycle time while raising confidence, especially when introducing AI into core experiences. On the go-to-market side, I’m doubling down on product-led growth—shipping value into the product with in-app guides, thoughtful product tours, and frictionless onboarding. Pair that with rigorous retention analysis and A/B testing, and you’ll see which AI-powered moments actually move activation, adoption, and expansion. Don’t overlook the fundamentals either: smart SaaS pricing (including consumption models where it fits) can unlock the economics that sustain AI investments. My goal is to give you a foundation that is both ambitious and accountable—a platform you can trust to scale responsibly while your teams iterate quickly. If you’re planning your 2H roadmap, this release is built to help you ship faster, de-risk AI, and create outsized customer value in the moments that matter most.

Inspired by this post on Pendo – Perspectives.

October 24, 2025
Prioritize, Build, and Measure AI with Confidence: Lessons I Apply from PendomoniumX NYC

AI is moving faster than any product wave I’ve seen in my career, and that urgency demands rigor. At HighLevel, I anchor our AI Strategy around measurable outcomes, responsible delivery, and pragmatic execution—principles that a recent PendomoniumX NYC customer discussion reinforced for me. “Three product leaders sat down with Pendo to discuss how they’re balancing AI investments, building their AI roadmap, and measuring success.” When I decide what to fund, I start with outcomes vs output OKRs. If an initiative cannot tie to a defensible customer outcome—time-to-value reduction, revenue expansion, retention lift, or cost-to-serve efficiency—it doesn’t make the cut. From there, I pressure-test feasibility and risk through data governance and AI risk management lenses: model choice, training data readiness, privacy-by-design, security posture, and responsible use guardrails. Building the roadmap is where discipline meets speed. I use empowered product teams—product trios across PM, design, and engineering—to run tight discovery sprints. We validate desirability and viability with gen ai for product prototyping, then graduate concepts into delivery using product roadmapping and sprint planning habits that prioritize smallest shippable value. I’ve found the try do consider framework helpful to stage bets from low-risk utilities to higher-impact, agentic AI workflows. Measuring impact is nonnegotiable. I define success up front with a minimum detectable effect (MDE), then instrument adoption and behavioral change via Pendo and Amplitude analytics. A/B testing gives me causal confidence, while retention analysis tells me if AI features are durable value, not novelty. If we can’t attribute improvement to a metric that matters, we iterate or retire. Governance is a product requirement, not an afterthought. We maintain data governance standards, threat detection and response controls, and clear model evaluation criteria before anything reaches customers. That operating model helps us move quickly without compromising trust—a cornerstone in any product-led growth motion. For go-to-market and adoption, I rely on in-app guides, product tours, and contextual tooltips to shorten the learning curve. We measure feature discovery, task completion, and ongoing engagement to ensure the experience is intuitive. The goal is to make AI feel like a natural extension of the workflow, not a science project bolted onto the product. My simple playbook: prioritize by customer outcomes and risk posture, build with validated learning and smallest shippable value, and measure with rigorous analytics and OKRs. Repeat that loop, and AI stops being a buzzword—it becomes a compounding advantage.

Inspired by this post on Pendo – Perspectives.

October 24, 2025
3 Powerful Ways AI Is Reshaping Cybersecurity—from Ruthless Attacks to Rapid Defense

Every week, I watch the cybersecurity landscape bend under the pressure of AI. The pace isn’t linear—it’s compounding. What worked for IT teams last quarter often needs a rethink today, and the difference between merely coping and truly competing lies in how quickly we adapt our strategy, tooling, and operating rhythms.

Learn the ways in which AI is transforming both cybersecurity offense and defense for IT teams.

From my vantage point leading product strategy, I see three shifts that matter most right now: AI is supercharging attackers, accelerating defenders, and reshaping governance. Together, they redefine how we prioritize investments, measure risk, and align product and security roadmaps.

First, AI has leveled up the offense. Large language models can industrialize social engineering—hyper-personalized spear-phishing at scale, deepfake voice notes that spoof executives, and highly convincing support chats that trick users into bypassing controls. Code-generation tools lower the barrier to crafting polymorphic malware and automating reconnaissance. The net effect is ruthless efficiency: more credible lures, faster campaigns, and broader reach with fewer human operators. I now assume adversaries have an AI co-pilot—and plan defenses accordingly.

Second, AI is accelerating the defense. Modern detection and response stacks are moving beyond rules to behavioral analytics—correlating identity signals, endpoint telemetry, and network events to spot subtle anomalies that signature-based tools miss. Copilot-style assistants are augmenting SecOps by summarizing incidents, explaining probable root cause, and proposing next steps. The aim isn’t blind automation; it’s decision acceleration—shrinking mean time to detect and respond while reducing analyst toil. On the build side, AI-assisted code scanning and dependency analysis help teams shift security left, catching vulnerabilities earlier and turning secure defaults into muscle memory.

Third, governance is being rewritten in real time. As AI models ingest sensitive data and generate code and content, data governance and privacy-by-design move from compliance checklists to active risk management. We’re formalizing AI risk management alongside traditional AppSec: model inventories, usage policies, red-teaming prompts, and guardrails against prompt injection and data leakage. Identity remains the control plane—zero trust principles, least privilege, and continuous verification become nonnegotiable. I’ve found that aligning security, product, and IT leadership on a single policy-as-code backbone prevents drift and keeps audits predictable.

Practically, I guide teams to start with a crown-jewel inventory: What data and systems would materially impact customers, revenue, or brand if compromised? Map data flows, instrument comprehensive telemetry, and prioritize detection coverage where it matters most. Choose AI to augment before you automate—prove the loop with humans in the middle, then graduate to higher autonomy levels with clear rollback paths and audit logs.

Culturally, this is a product problem as much as a security one. We bring empowered product teams and SecOps into the same room, set measurable objectives (signal-to-noise ratio, mean time to contain, escaped defect rate), and iterate with the same cadence we use for product features. When security outcomes are treated as customer outcomes, adoption soars and friction recedes.

The takeaway: AI has tilted the field, but not inevitably against defenders. With a clear AI strategy, disciplined data governance, and pragmatic automation, IT leaders can turn reactive security into a proactive advantage—meeting attackers’ speed with speed, and outlasting them with better judgment.

Inspired by this post on Pendo – Perspectives.

October 24, 2025
4 Hidden AI Risks Every CIO Must Tackle Now—and a Proven Playbook to Mitigate Them

Across enterprises, I’m watching AI sprint from lab experiments to business-critical workflows. That velocity is exciting—and it’s also where risk compounds. In my role partnering with CIOs and IT leadership, I’ve learned that winning with AI is as much about disciplined risk management as it is about breakthrough use cases.

Learn about the risks that AI poses to IT teams, and how they can mitigate them.

I frame the challenge as “4 AI risks for CIOs (and a guide to solve them)”: data governance and compliance, model reliability and bias, security and supply chain exposure, and operational cost/ROI drift. Below, I outline the risks I see most often and the concrete actions I take to de-risk them without slowing innovation.

Risk 1: Data governance and compliance. The fastest way to stall an AI Strategy is to overlook consent, lineage, and access controls. I establish privacy-by-design from day one: data minimization, clear retention policies, role-based access control, and auditable logs for training, inference, and feedback loops. I also insist on defensible vendor reviews (DPA, SOC2/ISO, regional data residency), PII classification, and internal model cards that document sources, sensitivities, and acceptable-use constraints. This makes IT leadership comfortable scaling from prototype to production.

Risk 2: Model reliability, hallucinations, and bias. AI that fabricates or skews output erodes trust and creates downstream risk. I operationalize quality with evaluation harnesses, golden datasets, human-in-the-loop review for high-impact actions, and red-teaming for safety. Retrieval-augmented generation with citations, content filters, and grounded prompts reduce error rates. To quantify progress, I define precision/recall targets and a minimum detectable effect (MDE) for experiments so we know when a change is truly better—not just different.

Risk 3: Security and AI supply chain. New surface area invites prompt injection, data exfiltration, and compromised dependencies. I apply zero-trust principles: strict allow/deny lists for tools and connectors, secrets isolation, egress controls, sandboxed environments for agents, and output validation before execution. Every model and plugin goes through threat modeling, dependency scanning, and vendor security reviews. For agentic AI patterns, I gate high-risk actions behind explicit approvals and granular scopes.

Risk 4: Operational cost and ROI drift. AI workloads can balloon with hidden inference costs, shadow IT, and duplicated platforms. I put governance around spend using consumption SaaS pricing guardrails, usage caps by environment, tagging by app/team, and a unified analytics platform to monitor latency, quality, and cost per transaction. This lets me reallocate budget toward the highest-impact use cases while sunsetting low-yield experiments.

Your 90-day playbook. Days 0–30: Inventory AI use cases, classify data sensitivity, choose one or two critical business workflows, and stand up core guardrails (access, audit, red-teaming). Days 31–60: Pilot with a cross-functional product trio (PM, design, engineering), define OKRs, instrument evaluations, and enable human-in-the-loop. Days 61–90: Productionize the winning flow, set usage and spend policies, enable observability dashboards, and roll out training for frontline teams with clear escalation paths.

The organizational layer matters as much as the technical one. I align stakeholders early, empower product trios to iterate quickly within boundaries, and deploy forward deployed engineers to embed with the business. This keeps trust high, reduces handoffs, and ensures that governance accelerates value rather than blocking it.

Done well, these practices turn AI risk into a competitive moat. By pairing disciplined governance with pragmatic experimentation, we capture the upside of gen ai while protecting customers, teams, and the business. That’s how I’ve helped enterprises move from scattered pilots to measurable, scalable impact—safely.

Inspired by this post on Pendo – Perspectives.

October 24, 2025
Implementing Agentforce the Smart Way: My Proven Playbook for Salesforce Agentic Success

Implementing Agentforce isn’t a feature rollout—it’s a strategic shift. In my role building AI-driven products, I treat Agentforce as its own product with clear outcomes, rigorous governance, and disciplined iteration. The objective is to create durable operational leverage inside Salesforce without compromising trust, data integrity, or customer experience.

Learn the ways in which Pendo helps companies design and iterate on their agentic strategy for Salesforce.

I start with product discovery. That means selecting the right use cases, defining the target user, and aligning on measurable outcomes rather than outputs. In practice, I prioritize use cases across sales, service, and marketing using an impact–effort–risk lens, then set crisp success metrics—response time, deflection rate, case resolution, win rate lift, and user adoption. This keeps everyone focused on value creation, not just model novelty.

Next, I design the agentic system with guardrails. I specify agent roles, tools, and policies; define when to escalate to humans; and embed privacy-by-design and data governance from day one. I also build an evaluation harness with offline tests and live A/B testing, ensuring we have a minimum detectable effect that’s meaningful for the business. The goal is to measure outcomes reliably and course-correct quickly.

When building the first slice, I scope narrow and ship fast. For example, start with a constrained service workflow—classify the case, propose a response, and take a safe action—with clear affordances in Salesforce so users understand what the agent did and why. I instrument the experience end-to-end and use Pendo for in-app guides, surveys, and behavioral analytics to reduce onboarding friction and capture real-time feedback at scale.

Iteration is where value compounds. I run weekly reviews of conversations, error taxonomies, and edge cases; adjust prompts and tool access; and maintain a steady experiment cadence. We track outcomes vs output to avoid vanity metrics, and we document learnings to de-risk the next use case. This steady drumbeat builds credibility with stakeholders and confidence with frontline users.

Change management is non-negotiable. I align leaders early, set expectations on what the agent can and cannot do, and define SLAs for humans-in-the-loop. I use product tours to teach new behavior, highlight quick wins, and establish transparent feedback channels. This combination of enablement and accountability accelerates adoption and creates a culture that embraces agentic AI responsibly.

Finally, I scale thoughtfully. Once the first use case demonstrates value, I standardize patterns, unify analytics, and evolve governance as usage grows. I review risk regularly, align OKRs with the roadmap, and keep a tight feedback loop between product, ops, and go-to-market teams. Treating Agentforce as an evolving product—not a one-off project—maximizes impact while protecting the customer experience.

Inspired by this post on Pendo – Perspectives.

October 24, 2025
Inside Pendo’s Decision: Replacing the Website Chatbot With an AI Agent to Boost ROI

Traditional website chatbots promised instant answers but rarely delivered the depth, context, and actionability modern buyers expect. After seeing patterns of high drop-off and shallow engagement, I stepped back and reframed the problem: We did not need another scripted bot—we needed an AI Agent capable of understanding intent, personalizing responses, and taking meaningful actions in the flow of discovery.

That is why Pendo replaced the website chatbot with an AI Agent. From a product management lens, the decision hinged on three criteria: accelerate time-to-value for visitors, reduce operational overhead through automation, and improve the quality of demand captured at the top of the funnel. An agentic AI approach met all three.

Increase revenue, cut costs, and reduce risk with Pendo’s Software Experience Management platform. Optimize the entire software experience to drive adoption and improve engagement.

This statement crystallizes the business case. An AI Agent can translate product intent into measurable outcomes by connecting to knowledge sources, analytics, and workflows. Instead of handing off a prospect to a form or a static knowledge article, the agent can surface relevant guidance, qualify interest, book meetings, and even trigger product tours—closing the loop between marketing, product, and customer success.

We anchored the implementation in data governance and privacy-by-design. That meant carefully curating training corpora, instituting role-based access controls, applying guardrails for sensitive topics, and designing graceful human-in-the-loop fallbacks. The result was not just a smarter front door, but a safer one—critical for regulated buyers and enterprise stakeholders.

To validate impact, we ran disciplined A/B testing with a clearly defined minimum detectable effect across conversion, engagement depth, and time-to-response. We also monitored secondary signals such as escalation rate to human support, session quality, and downstream product adoption. Early signals showed more qualified conversations, fewer dead ends, and faster paths to value—exactly the outcomes a product-led growth motion requires.

The experience uplift did not stop at the website. By aligning the agent with in-app guides and product tours, we created continuity from pre-signup exploration to onboarding and activation. Visitors received consistent, contextual help before and after they became users, which strengthened our product positioning and reduced friction across the journey.

Operationally, the shift lowered the marginal cost of each high-quality interaction while improving reliability. Agent handoffs to sales or support became intentional rather than reactive, and insights from conversations fed directly into product discovery. That closed feedback loop informed roadmap decisions and sharpened our go-to-market strategy.

If you are considering a similar move, start with a clear AI Strategy tied to measurable outcomes, a robust governance model, and a pragmatic rollout plan. Focus the agent on high-intent moments first, surround it with analytics and experimentation, and let the data guide expansion. The goal is not to replace humans—it is to elevate them by letting the AI Agent handle the repetitive, high-volume work so your teams can focus on complex, high-value interactions.

Inspired by this post on Pendo – Perspectives.

October 24, 2025
Ultra‑Personalized AI Product Experiences: How I Push the Limits Without Crossing the Line

Every week I meet teams eager to unleash AI-driven personalization across their products—and I share the same excitement. The promise is magnetic: experiences that feel tailor‑made, delivered at scale, and continuously optimized. Yet sustainable differentiation doesn’t come from turning every dial to eleven; it comes from clarity of intent, responsible design, and disciplined execution.

AI has us on the verge of a new age of ultra-personalized digital product experiences. But don't swing too big too early.

When I think about “how far is too far,” I anchor on user trust, explainability, and measurable value. If a personalization can’t be explained in a sentence, verified through A/B testing, or opted out of without friction, it’s a risk to both brand and product-market fit. The goal isn’t maximal personalization—it’s meaningful personalization that compounds retention and strengthens the value proposition.

I start with product discovery basics: who are the core segments, what jobs-to-be-done matter most, and where does personalization remove friction or accelerate time-to-value? That focus informs pragmatic AI Strategy. Instead of boiling the ocean, I’ll select one high-traffic, high-intent flow and define the precise outcome we want to move. Then I set outcomes vs output OKRs and instrument the path so I can track lift, variance, and trade-offs in real time.

Data governance is non-negotiable. Consent, transparency, and data minimization create the foundation for scalability. I document what signals power personalization, how long they persist, and who can access them. Strong governance isn’t a brake; it’s an enabler, letting us expand confidently without rework or reputational drag.

From there, I validate with A/B testing and clear minimum detectable effect (MDE) thresholds. Holdouts, guardrail metrics, and cohort analyses keep me honest. I’ll use Amplitude analytics to examine funnel impacts, retention analysis, and segment-level effects—especially to ensure we’re not improving conversion while harming long‑term engagement or fairness for smaller segments.

Early wins often come from onboarding and in-app guides. Personalizing the first five minutes—recommended next steps, contextual tooltips, or a tailored product tour—can deliver a step-change in activation with minimal risk. This is where product-led growth shines: relevant, timely nudges that shorten the path to the “aha” moment without feeling intrusive.

As we scale, gen ai and agentic AI open new frontiers. I’ve had success with assistants that proactively summarize account health, suggest next actions, or auto-draft content using the customer’s tone. But I always ship with transparency (“Why am I seeing this?”), controls (easy snooze or opt-out), and fallbacks (graceful degradation if signals are sparse). The human is still the hero; AI should play the role of a reliable, explainable copilot.

My implementation roadmap follows a crawl‑walk‑run arc. Crawl: rules‑based personalization in one journey; clear metrics and opt‑out. Walk: contextual recommendations using embeddings and feedback loops; continuous A/B testing. Run: agentic workflows that take multi‑step actions with approval gates and audit trails. Each phase is gated by evidence, not enthusiasm.

Finally, I treat personalization as a living system. I review dashboards weekly, continuously prune features that add complexity without durable lift, and socialize learning across product trios and empowered product teams. When personalization stays grounded in outcomes, ethics, and craftsmanship, it stops feeling “creepy” and starts feeling inevitable.

Personalization is not a stunt; it’s a capability. Build it with intention, measure with rigor, and earn the right to go deeper over time.

Inspired by this post on Amplitude – Perspectives.

October 24, 2025