ROI Case File No.519: Training Ended, But the Field Didn't Move
Training ended, but the field didn't move
Chapter 1: We Thought Training Alone Would Change Something
"We ran company-wide AI training. The field still isn't moving."
Takumi Fukazawa, Sales Operations Manager at Globex Corporation, said this as he showed the training report. Company-wide AI training conducted in 2025. The attendance rate reached 96%, but post-training application stalled. "The directive from leadership is to use AI in the field. Training is over. But proposal creation and customer research are still manual."
"And the CRM migration is also in progress?" Claude asked.
"We're switching from Genie to Zoho CRM between July 2026 and June 2027," Fukazawa replied. "I want to embed AI agents and AI tools at the timing of the CRM migration. But I can't judge which tools are optimal. Sales reps' skills vary widely, and top sellers' know-how isn't shared with the rest. CRM and SharePoint are siloed; customer data and proposal materials aren't connected."
"The challenge isn't just tool selection—it's spread across the entire organization," I noted.
"Leadership says 'streamline with AI,' the field says 'what should we use and how,' IT says 'which tool do we deploy,' HR says 'how do we close the skill gap'—everyone is looking at a different problem," Fukazawa replied. "The problem's outline straddles the whole organization."
"If it's organization-wide, let's break it down with 7S," I responded.
Chapter 2: 7S Asks to See the Organization in Seven Elements
"This case calls for 7S."
Claude wrote seven words on the whiteboard. Strategy, Structure, Systems, Shared Values, Style, Staff, Skills.
"7S is a framework proposed by McKinsey that analyzes the organization as seven interdependent elements," I explained. "Three Hard elements (Strategy, Structure, Systems) and four Soft elements (Shared Values, Style, Staff, Skills). On cross-organizational themes like AI utilization, advancing tool selection alone won't produce results if the other six elements don't move. The design must align all seven simultaneously."
"Let's measure current costs first," Gemini said, opening ROI Polygraph. Fukazawa's data went in.
"Monthly opportunity-loss costs are out," Gemini read. "Sixty sales reps' proposal creation labor averages 1,200 hours monthly at 4,800 yen/hour, or 5.76 million yen/month—a domain where AI could substantially shorten work. Customer research labor averages 480 hours monthly, or 2.304 million yen/month. Information integration labor from the CRM-SharePoint silo averages 360 hours monthly, or 1.728 million yen/month. Opportunity loss from sales variance because top sellers' know-how isn't shared: 3.2 million yen/month. Opportunity loss from training investment not converting to operational outcomes: 900,000 yen/month. Cost of migration outcomes unmet due to AI tool selection delay: 600,000 yen/month. Total: 14.492 million yen/month. Annualized: roughly 173.9 million yen."
Fukazawa looked at the numbers. "Sixty sales reps' proposal labor was larger than I'd thought. The figure for training investment not connecting to outcomes is also large."
"Now let's design with 7S," I continued.
[Strategy — Redefining the purpose of AI utilization]
"First, Strategy," Claude said. "Make the vague 'streamline with AI' strategy concrete. Define the sales organization's AI utilization strategy on two axes: 'double proposal speed' and 'equalize proposal quality to top-seller level.' Sync with CRM migration."
[Structure — Locating AI governance]
"The Structure perspective," Gemini continued. "Which organization owns AI utilization? IT alone can't drive it; sales alone can't see the whole. Place AI utilization responsibility with sales operations, with IT providing technical support and HR providing skill development—make roles explicit."
[Systems — Centering on Zoho CRM for integration]
"The Systems perspective," I continued. "Reposition the Zoho CRM migration not as mere CRM replacement but as the central foundation of AI utilization. Integrate SharePoint proposal materials, email data, and the AI assistant around Zoho CRM. Resolve the information silo."
[Shared Values — Organizational stance toward AI utilization]
"The Shared Values perspective," Claude continued. "Establish the shared value 'AI is not a threat; it's a tool for sales' across the organization. From leadership to field, tie AI utilization to performance evaluation, positioning it as recommended behavior. Values are culture, not initiatives."
[Style — Compatible with bottom-up leadership]
"The Style perspective," Gemini continued. "Beyond top-down directives, build a mechanism to surface AI utilization cases from the field. Establish regular meetings where sales director-class hear from the field. Combining top-down and bottom-up draws out the field's initiative."
[Staff — Top sellers as drivers]
"The Staff perspective," I continued. "Appoint three top sellers as AI utilization ambassadors. The outcomes their AI use produces become a wave effect for juniors and mid-level staff. Plus, bring in one external AI utilization specialist for hands-on support. Staffing on both internal and external sides."
[Skills — Spreading top-seller know-how laterally through AI]
"The Skills perspective," Claude continued. "Train the AI assistant on top sellers' proposal patterns, customer interactions, and closing techniques. A design where the AI functions as a 'pseudo top seller' for juniors. Bridge the skill gap through AI."
[Estimating investment recovery]
"Let's run ROI Proposal Generator," Gemini proposed.
- Initial cost: AI feature build inside Zoho CRM, SharePoint integration, top-seller knowledge AI-ization, AI utilization responsibility structure, ambassador program, external specialist engagement, and field training: 14.2 million yen total
- Monthly cost: AI operation and external specialist ongoing contract: 780,000 yen/month combined
- Monthly savings: Proposal creation labor reduction = 2.88 million yen/month (50% reduction assumed), customer research labor reduction = 1.38 million yen/month, information integration labor reduction = 1.04 million yen/month, revenue contribution from sales variance resolution = 2 million yen/month, conversion of training investment to operational outcomes = 600,000 yen/month. Total: 7.9 million yen/month
- Net monthly savings: 7.9 million yen − 780,000 yen = 7.12 million yen/month
- Payback period: 14.2 million yen ÷ 7.12 million yen = approximately 2.0 months
"Two months to recover," Gemini summarized. "What matters is the design aligning all seven elements simultaneously. Tool selection alone repeats the same structure that left training without outcomes."
Fukazawa checked the numbers. "We'd had the mindset of 'training and you're done,' 'select a tool and you're done.' We didn't have the view of seeing the organization in seven elements."
"7S is a tool to see the organization in three dimensions," I responded.
Chapter 3: Organizational Redesign Synced with the CRM Migration
"Let's lay out the path," I said at the whiteboard.
"Months 1–2: Redefine the AI utilization strategy; build the responsibility structure; appoint three top-seller ambassadors. Month 3: Design integration with the Zoho CRM migration project; design SharePoint integration. Months 4–5: AI-ize top-seller know-how; build AI features inside Zoho CRM. Month 6: Sync production launch with CRM migration; roll out to all sixty sales reps. Month 7: Begin ambassador-led internal workshops. Month 8 onward: Continuous improvement from usage data feedback; codify field-generated cases into organizational knowledge."
"Is it safe to advance the Zoho CRM migration and AI utilization at the same time?" Fukazawa asked.
"They should advance together," Claude responded. "Miss the CRM migration timing and a year after Zoho CRM lands, you're running AI utilization as a separate project. That doubles the burden on the field. Embedding both as an integrated mechanism settles faster."
Fukazawa took notes. "I'd learned about 7S in business strategy textbooks. I hadn't imagined it applied to such concrete promotion design."
Chapter 4: The Day the Seven Elements Locked Together
Twelve months later, Fukazawa's report arrived.
Proposal creation time, four months after the Zoho CRM AI features went live, was down 48% versus prior. Monthly working hours of about twenty per sales rep were freed. "Sales reps who used to work weekends on proposals can now finish during the week and go home," Fukazawa wrote.
The biggest change showed up in the resolution of sales variance. With the AI trained on top sellers' know-how, juniors and mid-level reps could now deliver proposal drafts at the same level, lifting proposal quality across the organization. "The customer evaluation 'if you land that rep, you get a good proposal' became 'whichever rep you land, it's consistent,'" the report noted.
CRM-SharePoint integration also produced results. Customer data, proposal materials, and email history became viewable on one screen in Zoho CRM, dramatically improving sales-prep efficiency. "Time bouncing between separate systems before a meeting disappeared," Fukazawa wrote.
The ambassador program functioned too. Three top sellers surfaced field cases and shared them in monthly internal presentations. "Not the abstract 'streamline with AI' from leadership, but top sellers' specific 'I used it this way and closed' moved the field's hearts," the report noted.
Recovery on training investment was also realized. Knowledge gained from the previous year's company-wide training converted to operational outcomes through the AI features in Zoho CRM. "Knowledge that ended at training only became outcomes once embedded in operational systems. We needed to design training and operational systems as a set," Fukazawa wrote.
A side effect: field-generated AI utilization cases exploded. Cases shared at internal sales presentations exceeded 150 cumulatively. "'This is convenient,' 'this works too' spread by word of mouth, and utilization grew faster than the promotion staff's planned rollout," the report said.
The gap between leadership and the field also narrowed. From a state where leadership voiced abstract expectations and the field carried concrete doubts, they shifted to a relationship of debating next moves while looking at the same data. "Executive meeting topics shifted from 'what can we do with AI' to 'what should we grow with AI,'" Fukazawa wrote.
The contract with the external AI specialist also continued. The initial six-month support contract led to expanded scope into more advanced utilization domains as organizational learning speed rose. "The first specialist did basic hands-on support; the second year and beyond is hands-on in applied domains—phased utilization is working," the report noted.
At the end of the report, Fukazawa wrote: "Running training didn't move the organization. Selecting tools didn't move the organization. The moment 7S aligned the seven elements simultaneously, the organization started moving. Organizational transformation won't advance if you strengthen one element and the rest don't catch up."
The organization that had thought training alone would change something started moving through simultaneous optimization of seven elements, and on that day, AI utilization had shifted from a training topic to operational routine, he wrote.
"Debates about moving organizations often skew toward a single element. Running training will change things. Adding a tool will change things. Changing the evaluation system will change things. All end in partial optimization. 7S asks for the view of seeing the organization as an interdependent system of seven elements. Strategy, Structure, Systems on the Hard side, and Shared Values, Style, Staff, Skills on the Soft side—when they mesh together, the organization moves forward. In an organization that had thought training alone would change something, on the day the seven elements aligned simultaneously, what changed wasn't individual skills—it was the very way the organization moves."
Related Files
Tools Used
- ROI Polygraph — Visualizing proposal labor, sales variance opportunity loss, and unutilized training investment
- ROI Proposal Generator — Investment recovery simulation for seven-element simultaneous-optimization AI utilization promotion
