SalesTable Discovery Execution Plan
The document is an execution plan authored by Suresh Madhuvarsu, Co‑Founder & CEO of SalesTable, outlining a repeatable, department‑by‑department process for discovering, scoring, designing, and piloting AI/automation use cases. The plan is organized into four weekly phases—Discover (leader and team interviews to map day‑in‑the‑life, pain points, and escalation triggers), Score (evaluate each workflow on Value, Viability, and Velocity), Design (create a scoped pilot plan with baseline, target, owner, and timeline), and Readout (present findings and pilot recommendations to management and IT for go/no‑go decisions). It specifies two interview types per department (Leader Call and Team/Rep Call), a standardized set of capture fields for every workflow, a three‑axis scoring rubric with decision rules, and a defined role for IT (single point of contact, tool/data inventory, security review, and readout participation). The cycle runs over two weeks per department, delivering a workflow inventory, prioritized pilot shortlist, one‑page pilot plans, and a management/IT readout deck. The plan concludes with next‑step actions to select the first department and schedule calls.
Topics
Four‑Phase Departmental AI Use‑Case Discovery Process
A structured weekly cycle—Discover, Score, Design, Readout—applied one department at a time to turn workflow pain into automation pilots.
Dual‑Interview Structure: Leader Call and Team/Rep Call
Two distinct conversations per department: a 30‑45 min leader call to capture goals and escalation sources, and 30‑45 min team calls (3‑5 frontline staff) to map day‑in‑the‑life tasks, tools, and workarounds.
Standardized Capture Fields for Workflow Mapping
Consistent data points collected on every call—task name, frequency, baseline time, tools, participants, blockers—enabling a scoreable workflow inventory.
Three‑Axis Scoring Rubric: Value, Viability, Velocity
Each workflow is evaluated on ROI potential (Value), technical/compliance feasibility (Viability), and speed to impact (Velocity), driving pilot prioritization.
Pilot Decision Framework and Readout
Decision rules translate scores into immediate pilots, planned pilots, or deferred pilots, with findings presented to management and IT for go/no‑go.
IT Engagement Model in the Discovery Cycle
IT provides a single point of contact, maintains a tool and data inventory, conducts security/access reviews, and participates in the readout to ensure pilot viability.
Two‑Week Department Cycle Deliverables
At the end of each cycle the team delivers a workflow inventory, prioritized pilot shortlist, one‑page pilot plans, and a management/IT readout deck.
Next‑Step Action Plan for Initiating the First Department
Guidance to confirm the first department, schedule leader and team calls, and share IT tool/data inventory for viability review.