Leansight Sales Methodology
S.A.L.E.S
Leansight Sales Methodology Framework
Story · Attentions · Leading · Energy · Social
Five dimensions, one mindset. Fusing the CEO Headline product philosophy — context determines meaning, attention to the invisible, autonomous discovery, double helix —
making every sale a meticulously designed campaign.
CORE ESSENCE
Stories aren't told for the ears to hear — they're planted in the customer's mind. First understand the context — what the industry is experiencing, what the role is anxious about, what human nature desires — then weave a differentiated story within that context, letting the customer "see" the picture of the solution in their own mind.
✦ CEO Headline Insight · Context Determines Meaning
CEO Headline doesn't just tell you "yield dropped 2%" — it continuously builds scenario context, mining the invisible meaning behind the data
Similarly, sales isn't about listing product features — "we have OEE, EAM, MIL" — this is like just saying "yield dropped 2%," without context, without meaning.
Context determines meaning: "OEE" from a generic BI vendor is just a metric; from Leansight, it's a "decision-making weapon that helps the GM see true production line efficiency every morning at 8 AM, drilling down six layers to find bottlenecks." The same product, placed in different contexts, means completely different things.
The core capability of sales, just like CEO Headline — continuously build scenario context, making product features produce irreplaceable meaning within that context.
🎭
Create Context
- Industry context: In the wave of manufacturing digital transformation, enterprises don't lack data — they lack the ability to "see the truth behind the data"
- Role context: IT managers understand technology but not business, operations VPs understand business but not technology, GMs want results not process — three-way disconnect
- Human nature context: Decision-makers desire "a sense of control" — being able to see the truth of the production line at 8 AM every day is an extension of power and a release of anxiety
📖
Weave the Story
- Differentiation based on pain points: Not "we sell BI tools," but "we help the GM see the truth every morning at 8 AM"
- The story unfolds in their mind: Describe using scenarios the customer can feel, letting them mentally picture "what it looks like after having a control tower"
- Explain the product thoroughly: Differentiation isn't about product parameter differences, it's about customer pain point differences. Explaining one pain point thoroughly beats listing ten features
Leansight Case · Customer M
That Morning in 2017
GM → IT Manager
"Build me a dashboard. I want to see production line data every morning at 8 AM."
The IT manager spent three months building a large display screen. The GM looked at it for three days, then stopped looking — because he couldn't understand the numbers on the screen, and didn't trust them. Behind this story are three layers of context:
Industry context: Made in China 2025, digital transformation anxiety everywhere, everyone is building dashboards, but no one has thought clearly about "who is it for, what do they look at, and what do they do after looking."
Role context: The IT manager was executing a task he didn't even understand himself — he wasn't on the production line, didn't know which data was important; the GM thought "seeing data" equaled "controlling production," but the data was untrustworthy, so seeing was the same as not seeing.
Human nature context: What the GM wanted wasn't a "dashboard," but "certainty." Sitting in his office at 8 AM every day, he wanted to know what happened on the production line last night and whether there would be problems today. This is an anxiety about the "unknown."
Leansight's differentiated story: Not "we'll help you build a dashboard," but "we let you see trustworthy truth at 8 AM every morning, and tell you what to do about it." A control tower isn't a data display tool — it's a decision support system. Trustworthy data, metric drill-down, root cause analysis — these three things turn "seeing" into "controlling."
"
A story without context is a sales pitch.
A story with context is resonance.
Understand the context first, then start telling the story
Self-Check · Story
☐
Have I spent time researching the customer's industry's current transformation stage and pain points?
☐
Do I understand the respective anxieties and needs of different roles within the customer's organization (IT/Operations/Management)?
☐
Does my story have a specific scenario the customer can "see" in their mind?
☐
Is my differentiation based on customer pain points, or on my own product parameters?
CORE ESSENCE
The ability to focus on what not to do is just as important as the ability to focus on what to do. Don't pursue low-value customers, don't build products unrelated to the core business. Select industries and customers, capture customer attention, communicate pain points, articulate product differentiation. Fail to plan = Plan to fail — every meeting must have a defined goal and follow-up action.
✦ CEO Headline Insight · Pull-Based (Headline-Driven) vs Traditional Push
Traditional data governance is push-based — govern first, then find scenarios; CEO Headline is pull-based — use scenarios to pull governance, with precise investment
Sales also has push-based and pull-based approaches:
Push-based sales (traditional): Push all features to the customer — "we have full-chain OEE, EAM equipment management, MIL material management, a metric system library of 867 metrics..." Feature stacking, where the customer doesn't know which relates to them, and forgets everything after hearing it.
Pull-based sales (CEO Headline style): First use customer scenarios to pull the solution — "You mentioned yield fluctuation is your biggest concern, let's first look at how CEO Headline autonomously discovers the root cause of yield anomalies, then look at how OEE drills down to the equipment level to locate bottlenecks." Scenario-driven, precisely targeted, the customer can actually take it in.
Focusing on what to do is essentially pull-based thinking: Don't play all your cards at once — first see what cards the customer holds (scenarios/pain points), then play precisely.
- Don't pursue low-value customers: Enterprises without digital transformation willingness — accompanying them is a waste of time
- Don't build products unrelated to the core business: Don't take on financial industry report outsourcing, don't do pure data visualization projects
- Don't pursue non-manufacturing customers: Leansight's DNA is in discrete manufacturing — cross-industry dilutes expertise
- Don't make blind pitches without mapping the decision chain: Not knowing who makes the final call means the visit was wasted
- Don't attend unprepared meetings: A visit without a communication plan is worse than not going
- Select industries and customers: Focus on discrete manufacturing such as semiconductors, electronics, and automotive parts
- Capture customer attention: Spend the first 5 minutes on customer pain points, not on company introductions
- Communicate pain points: First ask "what's your biggest concern right now," then connect to the product
- Articulate product differentiation: vs generic BI, vs traditional MES — where are the differences
- Set goals and follow-up actions for every meeting: One meeting, one goal, one next step
- Memos and communication plans: Send meeting minutes and follow-up plans within 24 hours after the meeting
📋 One-Page Communication Plan (Required for Every Meeting)
Customer Pain Point Hypotheses
List 3 customer pain points you anticipate, then validate or revise during the meeting
Product Differentiation
vs generic BI / traditional MES — where Leansight's control tower differs
Meeting Goal
1 clear goal: Schedule technical exchange / Arrange POC / Introduce to senior management
Next Follow-up Action
1 specific action: Send proposal by next Wednesday / Arrange factory visit
Leansight Case · Lesson Learned
The Meeting Without a Follow-Up Action
On one occasion, a sales rep visited the IT manager of a semiconductor customer with a beautiful PPT. During the one-hour meeting, the product was presented comprehensively, and the customer nodded frequently. The sales rep said "feel free to reach out if you have any questions," and the customer said "sure, sure."
Two weeks later, following up, the customer said "we chose another vendor." The reason: the other vendor's sales rep sent a customized proposal addressing the customer's pain points the very next day, and proactively scheduled a meeting with the VP of Operations.
Retrospective: No clear meeting goal was set (was it to schedule a technical exchange? Or to introduce to senior management?), no follow-up action was set (when, who contacts whom, what's the next step). A "great chat" meeting, because there was no plan, became a "wasted trip" meeting.
Fail to plan = Plan to fail. Since then, the Leansight sales department mandated: before every customer meeting, a "one-page communication plan" must be submitted; within 24 hours after the meeting, meeting minutes and a follow-up plan must be sent.
"
One meeting, one goal, one next step.
A meeting without a follow-up action is a meeting that didn't happen.
Fail to plan = Plan to fail
Self-Check · Attentions
☐
Is this customer within our target industry and target profile?
☐
Have I prepared a "one-page communication plan" (pain point hypotheses / differentiation / goal / follow-up)?
☐
In the first 5 minutes of the meeting, what am I going to say to capture the customer's attention?
☐
Will I send meeting minutes and a follow-up plan within 24 hours after the meeting?
CORE ESSENCE
Be the referee — proactively guide the direction of customer projects: bidding standards, processes, and the system of power moves that influence the project. Rules matter more than effort. A强者 mindset is always superior to a victim mentality. At the same time, pass the spark — sales ignites the "System 1" flame, the team handles the "System 2" combustion; conversion is achievement.
✦ CEO Headline Insight · Autonomous Discovery
CEO Headline doesn't wait for users to ask — it autonomously patrols 24/7, proactively turning unknown unknowns into known knowns
Sales should also practice autonomous discovery like CEO Headline, rather than passively waiting for customer questions:
Passive sales: Customer asks "what can you do" → Sales answers "we can do A, B, C..." → Customer says "let me think about it" → Sales waits for a reply
Autonomous discovery sales: After researching the customer's industry, sales proactively says "I looked at your recent public data and noticed your Q2 yield fluctuation is 3 percentage points higher than Q1 — this could be caused by upstream process parameter drift. Our CEO Headline can provide early warning of this kind of drift 72 hours in advance. Would you like to see how?"
Pierce through the veil of gray zones, illuminate the black zones with a searchlight. For pain points the customer knows about (gray zones), sales must have the courage to use data to pierce through — "This issue has gone unsolved internally because cross-departmental data isn't connected; we can help you connect it." For risks the customer doesn't know about (black zones), sales must have the ability to illuminate — "You may not have noticed this yet, but based on industry patterns, this hidden risk will erupt in 72 hours."
This is leading — don't wait for the customer to discover you; you discover the customer first.
⚖️
Be the Referee
- Proactively guide project direction: Don't wait for the customer to set bidding standards — proactively propose an evaluation framework
- Define bidding standards and processes: Turn "who's cheaper" into "who better fits the architecture standards"
- System of power moves that influence projects: Influence evaluation dimensions, scoring weights, and shortlisting thresholds
- Rules matter more than effort: Winning within someone else's rules is luck; winning within your own rules is strength
🔥
Pass the Spark
- Sales passes the "spark" (System 1): Ignite the "data-driven operations" flame in front of the customer, making them excited
- Team handles the "combustion" (System 2): The technical team goes deep into implementation, turning excitement into a landed solution
- Conversion is achievement: The value of sales isn't in burning bright themselves, but in how many fires they ignite
- System division of labor: System 1 is responsible for "wanting," System 2 is responsible for "achieving"
- Customer says "budget is only 500K" → "Then I'll discount to 500K for you"
- Customer says "you're too expensive" → "I can apply for a discount"
- Customer says "competitors are cheaper" → "We can also lower our price to match"
- Wait for the customer to set bidding standards, passively respond to bids
- Complain that "the customer doesn't understand our value"
- Customer says "budget is only 500K" → "Here's what 500K can and can't do — let me help you prioritize"
- Customer says "you're too expensive" → "Expensive because it's worth it — let me calculate the ROI for you, and you decide if it's worth it"
- Customer says "competitors are cheaper" → "Cheap or expensive doesn't matter — what matters is who better fits the standards"
- Proactively propose an evaluation framework, letting the customer choose based on your standards
- Guide customer cognition — "the customer doesn't understand" is the sales rep's responsibility
Leansight Case · Customer M
Turning "Compare Price" into "Compare Architecture"
In the Customer M project, the customer originally planned to compare prices — three suppliers would submit quotes, and the lowest would be chosen. The Leansight sales rep didn't quote directly, but proactively proposed a "Control Tower Four-Layer Architecture" evaluation framework:
Layer 1 · Autonomous Discovery Layer (CEO Headline): The system proactively discovers problems, rather than people looking at reports
Layer 2 · Intelligent Control Layer: AI root cause analysis + PDCA closed loop, rather than just displaying data
Layer 3 · Lean Collaboration Layer: Cross-departmental metric drill-down, rather than siloed data islands
Layer 4 · Agile Foundation Layer: Low-code data integration, rather than heavy custom development
The customer discovered: competitors could only achieve Layers 3 and 4, with Layers 1 and 2 completely blank. So the evaluation criteria shifted from "who's cheaper" to "who has more complete architecture." Leansight not only won the project but also won the power to define the standards.
Passing the spark: The sales rep presented the "7 Iron Rules and 5 Red Lines" data-driven operations methodology in front of the customer, igniting the customer's desire to "do data-driven operations like Customer M" (System 1). Then the technical team came in, using the full-chain OEE solution and the Control Tower Four-Layer Architecture to turn desire into a landable solution (System 2). Sales ignites the spark, the team handles the combustion, conversion is achievement.
"
The 强者 mindset asks "how to prioritize,"
the victim mentality asks "how much discount."
Rules matter more than effort
Self-Check · Leading
☐
Am I responding to bids within the customer's rules, or am I guiding the customer to choose based on my standards?
☐
When faced with "too expensive / not enough budget," am I cutting prices or helping the customer calculate ROI and prioritize?
☐
Have I successfully ignited the "System 1" desire in front of the customer?
☐
Have I brought in the technical team in a timely manner to let "System 2" take over the combustion?
CORE ESSENCE
Win-win infectious power — passion is always the weapon for capturing the customer's System 1. When you walk into the customer's office with genuine conviction, what the customer feels is not "this person wants to sell me something," but "this person truly understands our pain." At the same time, eliminate negative energy — everything has two sides; look from multiple perspectives and find the bright side.
✦ CEO Headline Insight · Double Helix Mutual Generation
CEO Headline and data governance are like a DNA double helix — the headline discovers problems that drive governance, governance improves quality that feeds back into the headline, spiraling upward
The relationship between sales and customer is also a double helix:
First spiral: Sales uses passion and story to ignite customer demand (System 1) → The customer starts to act, raising deeper questions → Sales gains new industry insights from this → Uses more precise stories to move the next customer. Demand drives evolution, evolution feeds back into demand.
Second spiral: Sales passes the spark (System 1) → The technical team comes in to combust (System 2) → The customer sees results, trust deepens → The customer becomes a case study, feeding back into the sales rep's passion and stories → Stronger passion infects the next customer.
Passion isn't one-way output, but a bidirectional spiral. You infect the customer, and the customer infects you. When you truly help a customer solve a problem, the light in their eyes gives you even stronger energy in return. This is the essence of win-win infectious power — mutual generation, spiraling upward, perpetual evolution.
⚡
Win-Win Infectious Power
- Passion captures System 1: System 1 is emotional, fast, automatic — passion is the shortest path
- Driven by genuine conviction: Not performing passion, but truly believing the control tower can help the customer
- Win-win, not zero-sum: Not "I'm making money off you," but "let's make data-driven operations happen together"
- Methodology IS energy: Using the 7 Iron Rules, 5 Red Lines, and the OPS Pyramid to talk about data-driven operations — the customer is infected by the professionalism
🔄
Eliminate Negative Energy
- Everything has two sides: The customer says "we've tried many BI tools and they all failed" — this actually shows the customer has demand, has budget, and has lessons learned
- Multiple perspectives: Turn "failure experience" into an argument for "why you need a different solution"
- Turn negative into positive: Competitors are present → means the customer has budget and willingness → our differentiation is stronger
- Emotion management: The sales rep's emotional state is contagious to the customer — if you're anxious, the customer is anxious; if you're composed, the customer is composed
Leansight Case · Energy Transformation
"We've tried many BI tools and they all failed"
Customer VP of Operations
"We've deployed two BI systems before, spent a lot of money, and they both ended up as decorations. What makes you say you're different?"
✕ Victim mentality response
"Our product is really different, the features are more powerful, the service is better..." (Defensive justification, low energy)
✓ 强者 mindset response
"It's precisely because generic BI failed that you need a control tower. BI shows you data; a control tower helps you use data. Those two BI systems became decorations not because BI is bad, but because they were missing the 'autonomous discovery' and 'intelligent control' layers — the system doesn't proactively tell you where the problems are; you still have to find them yourself. The first two layers of the control tower's four-layer architecture are exactly what you were missing before."
Energy transformation: When the customer says "failed," they're not rejecting you — they're giving you an argument for "why you need us." What sales needs to do isn't to justify "we're different," but to help the customer understand "why it failed before" and "how we fill that gap."
Passion infection: When the sales rep walks in with the "7 Iron Rules and 5 Red Lines" — the data-driven operations methodology that Customer M spent tens of millions in tuition to acquire — the customer doesn't feel "this sales rep wants to sell me something," but "this company is serious, they truly understand the pain of manufacturing." Passion is the shortest path to capturing System 1.
"
When the customer says "tried and failed,"
you say "precisely because you failed, you need something different."
Everything has two sides — sales must find the bright side
Self-Check · Energy
☐
When I walk into the customer's office, am I carrying genuine conviction and passion, or just "completing a visit task"?
☐
When faced with negative feedback ("too expensive / tried and failed / no budget"), can I transform it into a positive argument?
☐
Is my delivery infectious — using cases, stories, and methodology, rather than dry product introductions?
☐
Am I conveying a "win-win" signal, making the customer feel we're comrades rather than a buyer-seller relationship?
CORE ESSENCE
Lean — the capability of senior operations leaders; concentrate effort, identify the customer's power dynamics map, and find the primary stakeholder. Link — build "relationship hub" type connections, reaching customers and partners through hubs: regional agents, industry agents, application agents. Don't try to meet a hundred people — meet the one person who knows a hundred people.
✦ CEO Headline Insight · Cross-Departmental Boundaries in Gray Zones
CEO Headline breaks through gray zones — automatically identifying cross-departmental correlations, quantifying each department's influence weight, turning disputes from "discussion" into "decision"
The customer's internal gray zones — problems everyone knows about but no one solves — are often stuck at cross-departmental boundaries: the quality department and production department pass the buck to each other, IT and operations each tell their own story. The "gatekeepers" of these gray zones are precisely your primary stakeholders.
Why? Because the people standing at cross-departmental boundaries are in the most pain. They're caught between both sides — upper management demanding results on one side, departments not cooperating on the other. They most desperately want someone to help them break the deadlock with data. When you use CEO Headline's "cross-departmental correlation analysis" capability to help them quantify each department's influence weight, you're not selling a product — you're helping them win a battle they can't win alone.
The essence of a relationship hub, just like CEO Headline — isn't about building more connections, but finding the "node that connects the most pain points." Find them, concentrate your effort, and leverage a thousand pounds with four ounces.
🎯
Lean: Attack the Primary Stakeholder
- Identify the power dynamics map: User → Evaluator → Decision-maker → Approver — a four-layer structure
- Find the primary stakeholder: Not the highest person, not the lowest person, but the person who connects demand and budget
- Concentrate your effort: Don't distribute effort evenly — invest 80% of your energy in the primary stakeholder
- Capability of senior operations leaders: Conversing with executives neither humbly nor arrogantly, using business logic rather than technical parameters
🔗
Link: Find Relationship Hubs
- Relationship hub type connections: Don't build one-to-one relationships — link to the person who "knows a lot of people"
- Regional agents: Channel partners deeply rooted in specific geographic areas
- Industry agents: Technical advisors of semiconductor associations, industry association experts, etc.
- Application agents: Consulting advisors or system integrators with influence in specific application scenarios
- Reach through hubs: One hub → reach ten customers, tenfold efficiency improvement
Customer Power Dynamics Map · Semiconductor Customer Example
Line Supervisor
USER
Cares about ease of operation
→
IT Manager
EVALUATOR
Cares about technical compatibility
→
VP of Operations ★
DECIDER · Primary Stakeholder
Cares about management efficiency improvement · Connects demand and budget
→
GM
APPROVER
Cares about return on investment
Why is the VP of Operations the primary stakeholder? The line supervisor only has usage opinions but no decision-making power; the IT manager has evaluation power but no budget power; the GM has approval power but won't dive into solution details. The VP of Operations — he understands business pain (management efficiency), has budget influence (raises requests to the GM), and can evaluate solution value (he understands ROI). Find him, concentrate 80% of your effort.
Leansight Case · Relationship Linking
One Hub Opens Ten Doors
Leansight's breakthrough in the semiconductor industry didn't come from cold-calling one by one, but through an "industry agent" — a technical advisor at a semiconductor industry association.
Linking path: Industry agent (knows 10+ semiconductor customer VPs of Operations) → Introduces Leansight → The VP of Operations is willing to spend 30 minutes listening to you → Because the introduction comes from a trusted person, defenses are low → Use the "7 Iron Rules" to move System 1 → The technical team comes in for System 2
Efficiency comparison: Cold visits → conversion rate approximately 5%, averaging 6-8 contacts needed; through industry agent introduction → conversion rate approximately 40%, averaging 2-3 contacts to enter the solution phase.
The essence of relationship hubs: Don't spend time meeting a hundred people — spend time finding the one person who knows a hundred people. The cost of maintaining one hub relationship is far lower than maintaining a hundred one-to-one relationships.
"
Don't try to meet a hundred people —
meet the one person who knows a hundred people.
Strike the snake at its seven-inch mark — attack the customer's primary stakeholder
Self-Check · Social
☐
Have I mapped the customer's power dynamics (user/evaluator/decision-maker/approver)?
☐
Have I identified the primary stakeholder and concentrated 80% of my energy on them?
☐
Do I have regional/industry/application agents as relationship hubs?
☐
Am I continuously investing in maintaining hub relationships, rather than only reaching out when I need something?
Social
CEO Headline breaks through gray zones — automatically identifying cross-departmental correlations, quantifying each department's influence weight, turning disputes from "discussion" into "decision"
Why? Because the people standing at cross-departmental boundaries are in the most pain. They're caught between both sides — upper management demanding results on one side, departments not cooperating on the other. They most desperately want someone to help them break the deadlock with data. When you use CEO Headline's "cross-departmental correlation analysis" capability to help them quantify each department's influence weight, you're not selling a product — you're helping them win a battle they can't win alone.
The essence of a relationship hub, just like CEO Headline — isn't about building more connections, but finding the "node that connects the most pain points." Find them, concentrate your effort, and leverage a thousand pounds with four ounces.
Lean: Attack the Primary Stakeholder
Link: Find Relationship Hubs
Customer Power Dynamics Map · Semiconductor Customer Example
One Hub Opens Ten Doors
Leansight's breakthrough in the semiconductor industry didn't come from cold-calling one by one, but through an "industry agent" — a technical advisor at a semiconductor industry association.
Efficiency comparison: Cold visits → conversion rate approximately 5%, averaging 6-8 contacts needed; through industry agent introduction → conversion rate approximately 40%, averaging 2-3 contacts to enter the solution phase.
The essence of relationship hubs: Don't spend time meeting a hundred people — spend time finding the one person who knows a hundred people. The cost of maintaining one hub relationship is far lower than maintaining a hundred one-to-one relationships.
meet the one person who knows a hundred people.
Self-Check · Social