← All work
04

Enterprise product leadership

Turning account planning into a living, human-reviewed system

At Cisco, I owned the day-to-day product work for AI-powered account planning: bringing scattered research into a generated draft that sellers could improve with their own account knowledge.

How the work connected

AI-first account planningCisco · 2025–2026
  1. Assemble internal account context and public company developments

  2. Generate a first master plan for the account team to review

  3. Capture role-specific input and approve contributions for the next iteration

  4. Export adjustable plans and internal or customer-facing presentation outputs

The product decision behind this workflow

I treated the generated plan as the beginning of a workflow. Account-team members needed places to contribute their knowledge, an approval step, and a new iteration that incorporated accepted input. The product reduced manual assembly work while keeping the account team responsible for the plan.

Case-study reconstruction from my experience—not an employer screenshot or live product demo.

RoleDay-to-day product owner and execution lead
PeriodMarch 2025 – January 2026
Case contextCisco · 2025–2026

01 / Context

The operating problem

The previous Quip-based process could take account teams more than 20 hours of research and writing per plan. Useful context was scattered across internal systems and public information such as company news, investor updates and executive changes. Sellers needed a head start without losing ownership of the strategy.

02 / Judgment

The decision behind the interface

I treated the generated plan as the beginning of a workflow. Account-team members needed places to contribute their knowledge, an approval step, and a new iteration that incorporated accepted input. The product reduced manual assembly work while keeping the account team responsible for the plan.

03 / System

How the account-planning workflow worked

  1. 01

    Assemble internal account context and public company developments

  2. 02

    Generate a first master plan for the account team to review

  3. 03

    Capture role-specific input and approve contributions for the next iteration

  4. 04

    Export adjustable plans and internal or customer-facing presentation outputs

Product narrative

A visual language for the system around the screen.

How the work connected

AI-first account planningCisco · 2025–2026
  1. Assemble internal account context and public company developments

  2. Generate a first master plan for the account team to review

  3. Capture role-specific input and approve contributions for the next iteration

  4. Export adjustable plans and internal or customer-facing presentation outputs

The product decision behind this workflow

I treated the generated plan as the beginning of a workflow. Account-team members needed places to contribute their knowledge, an approval step, and a new iteration that incorporated accepted input. The product reduced manual assembly work while keeping the account team responsible for the plan.

Case-study reconstruction from my experience—not an employer screenshot or live product demo.

16,000+sellers the platform was intended to support

The 20+ hours describes the previous manual process, not a measured time-saving claim. Intended seller reach is not a count of active users.

Next story · 05Guiding enterprise change at 100,000-user scale