> 🌐 中文版本 / Chinese version: [SALES_VALUE_PROPOSITION.md](SALES_VALUE_PROPOSITION.md)

# Role-Based Value Propositions and Sales Pitches

Last updated: 2026-05-13

## 1. Official Program Name

Recommended external Chinese name:

> 企業 AI 轉型成熟度診斷與導入方案 (Enterprise AI Transformation Maturity Diagnosis and Implementation Program)

English supporting name:

> TigerAI AI Transformation Maturity Program

## 2. External Naming for L1-L5

| Level | External Name | Tools / Platforms | Client-Facing Language |
| --- | --- | --- | --- |
| L1 | Controlled AI Access | OpenWebUI | Let employees start using AI safely |
| L2 | Knowledge Codification | Antigravity / Claude Code / Codex | Turn individual experience into departmental capability |
| L3 | Workflow Automation | n8n | Let AI integrate with systems and enter the process |
| L4 | Autonomous Agent | Hermes Agent | Give AI knowledge memory, the ability to absorb documents, track tasks, generate briefings, and retain evidence and human Gates |
| L5 | Multi-Agent Organization | ClawTeam | AI Agent Team collaboration platform |

Recommended external Chinese description of ClawTeam:

> AI Agent Team 協作平台 (AI Agent Team collaboration platform)

## 3. One-Sentence Positioning

We do not merely teach AI tools. We use a questionnaire to diagnose the enterprise's current AI maturity, then configure courses according to L1-L5, produce acceptance-ready assets during the courses, and finally use an eight-stage consulting methodology to produce an AI transformation diagnostic report and an implementation Roadmap.

## 3.5 Future-State Story Before Class

Sales conversations and course openings should show the future before explaining the tools.

Use this version:

> Before we talk about tools, imagine how your company works three months from now. Every employee has their own AI workspace, and managers can see permissions and data boundaries. Expert methods become Skills, so new employees can follow the same standard. Customer complaints, reports, CRM updates, and ERP queries no longer rely on manual copy-paste; n8n turns them into workflows. Hermes Agent produces daily briefings, follow-up lists, evidence, and items that require human approval. When the company works on a new product, quality improvement, or customer engagement, multiple Agents can collaborate like a team. The L1-L5 curriculum is the path that moves the company toward this state.

Clients should map the story to these capabilities:

| Level | Future Capability in Client Language | Course Mapping |
| --- | --- | --- |
| L1 | Employees use AI safely, each with their own account and chat workspace | OpenWebUI enterprise enablement |
| L2 | Expert methods become departmental Skills and help new employees ramp up faster | Antigravity / Claude Code / Codex Skill training |
| L3 | AI connects systems and workflows start running automatically | n8n Workflow AI |
| L4 | Agents read data, produce briefings, keep evidence, and wait for approval | Hermes Agent |
| L5 | Multiple Agents form a cross-functional AI Team | ClawTeam |

This story should come before the questionnaire and course introduction. Once clients understand the future state, they are more willing to answer the maturity questionnaire and understand why courses are layered, and why each layer needs deliverables and Stage Gates.

## 3.6 Procure AI, Don't Buy a System (The Key L4-L5 Reframe)

At L4-L5, what the boss must change is not the tools — it is the **mindset**.

Many bosses see AI the way they "buy a system": compare features, compare license prices, calculate software ROI. But L4-L5 AI is not software — it reasons, acts autonomously, and uses tools; functionally it does what a knowledge worker does. So the right mindset is **"procuring AI"**: like recruiting, onboarding, managing, and governing a talent.

A sales conversation can lead with:

> Are you "buying a piece of AI software," or "procuring an AI workforce"? If it's the latter, the question is not "what features does it have" but "how much workload does it take off me, how do I manage it, and who governs it?"

Key points (especially effective with CEOs / executives):

- **ROI doesn't disappear — the measuring stick changes**: don't use the "buy software" stick (features, seats, annual fees); use the "hire a worker" stick (how much workload it takes off, how much capacity it amplifies).
- **At L1-L3 you are legitimately buying tools / equipment / systems** — that is reasonable and verifiable; the "procure AI" reframe applies only to L4-L5.
- **It is a management-posture analogy, not a claim that "AI is human"** — precisely because AI ≠ human, it needs the governance framework that humans build, and governance is the core of our service.

## 4. Role-Based Value Propositions

### 4.1 CEO

What the CEO cares about: whether AI investment can be turned into business outcomes.

What we provide:

- A clear, understandable AI maturity map.
- An objective assessment of where each department currently sits.
- Which AI scenarios have the strongest ROI.
- A three-phase Roadmap.
- Trackable KPIs and Stage Gates.

How we explain it to the CEO:

> This program will show you exactly where your company stands on AI today, where your next investment should go, and which scenarios are most likely to deliver results within 90 days.

### 4.2 COO

What the COO cares about: whether processes become faster, more stable, and have less rework.

What we provide:

- As-Is process inventory.
- Inventory of manual rework points.
- Integration scenarios for Gmail, Sheets, Notion, CRM, API, and ERP.
- n8n Workflow PoC.
- Cross-departmental process improvement recommendations.

How we explain it to the COO:

> We will move AI from being a personal chat tool to being part of real operating processes, prioritizing the most repetitive, time-consuming, and error-prone work.

### 4.3 CIO / IT

What the CIO / IT cares about: data security, access control, operations, audit, and system integration.

What we provide:

- Assessment of cloud AI / Hybrid / fully on-premise deployment.
- Inventory of credentials, APIs, access rights, and logs.
- Hermes Agent's available tools, Wiki memory, indexing, logs, and permission boundaries.
- Human review and exception handling mechanisms.
- Governance and operations recommendations.

How we explain it to CIO / IT:

> This is not about letting each department wire up tools on their own. It brings AI usage, process automation, and Agent permissions into a governable architecture.

### 4.4 HR / Training Function

What HR cares about: whether the way people work actually changes after the course is over.

What we provide:

- Pre-course maturity diagnosis.
- Course design segmented by department.
- Prompts, Skills, Workflows, and Agent task cards produced during the course.
- Post-course capability inventory.
- Departmental Skill Libraries and training tracking.

How we explain it to HR:

> This is not a one-off AI course; it turns training outcomes into reusable departmental work assets.

### 4.5 Department Heads

What department heads care about: whether the team can do less repetitive work, achieve more consistent quality, and onboard new hires faster.

What we provide:

- Inventory of the department's high-frequency tasks.
- Skill-ification.
- Workflow PoC.
- Hermes Agent task cards, briefings, and tracking lists.
- Departmental KPI recommendations.

How we explain it to department heads:

> We will first identify the work your department does most often, that takes the most time, and that is most error-prone, and convert it into Skills, Workflows, or Agent tasks.

## 5. 30-Second Sales Pitch

For most enterprises today, the issue is not that AI is unused. It is that everyone is using it on their own, results are scattered, processes are unchanged, and ROI is unclear. We first use a questionnaire to diagnose enterprise AI maturity, then configure the L1-L5 course mix accordingly, produce Prompts, Skills, Workflows, and Hermes Agent evidence during the course, and finally use an eight-stage consulting methodology to deliver an AI transformation diagnostic report so the enterprise knows where it stands, what to do next, and which processes can be automated first.

## 6. 3-Minute Sales Pitch

The most common state when enterprises adopt AI is that employees have already started using ChatGPT, Claude, or Gemini, but the company as a whole sees no organizational capability. Some people can write Prompts, some organize data, some want to integrate with CRM or ERP, but there is no shared architecture.

We segment AI maturity into five levels. L1 is OpenWebUI Chat AI, which lets employees start using AI safely. L2 is Skill AI, which uses Antigravity, Claude Code, and Codex to turn personal experience into departmental Skills. L3 is n8n Workflow AI, which integrates Gmail, Sheets, Notion, CRM, API, and ERP, so that AI enters the process. L4 is Hermes Agent, which gives AI Wiki memory, the ability to absorb documents, call tools, generate briefings, and prove results with logs and evidence. L5 is ClawTeam, the AI Agent Team collaboration platform that supports cross-departmental tasks.

Our service has three phases. The first uses a questionnaire to rapidly diagnose which level the enterprise is at today. The second configures the course mix based on the diagnosis, so clients produce Prompts, Skills, Workflows, Hermes Agent PoCs, and Stage Gate evidence during training. The third uses the eight-stage consulting methodology to consolidate the current state, gaps, core issues, To-Be blueprint, Roadmap, and ROI.

What the client buys is not a single AI course, but a path that goes from AI learning to enterprise transformation implementation.

## 7. 10-Minute Presentation Storyline

### Slide 1: Enterprises are not without AI; AI is just scattered

Employees each use their own tools, managers cannot see ROI, IT worries about security, and departments do not know how to land it.

### Slide 2: AI transformation is a maturity evolution

From L1 Controlled AI Access to L5 Multi-Agent Organization, each level has different management focus and governance capability.

### Slide 3: The L1-L5 model

- L1 OpenWebUI: individual productivity.
- L2 Knowledge Codification: departmental capability.
- L3 n8n: process automation.
- L4 Hermes Agent: a knowledge-oriented Agent with Wiki memory, briefings, tool calls, and evidence.
- L5 ClawTeam: AI Agent Team collaboration platform.

### Slide 4: Diagnose first, then train

Use a 10-question or 25-question questionnaire to determine maturity, company attributes, deployment mode, and priority scenarios.

### Slide 5: The course is not a fixed menu

Configure the L1-L5 ratio according to maturity, industry, deployment mode, and system conditions.

### Slide 6: Bring AI into systems and processes

Use n8n to integrate Gmail, Sheets, Notion, CRM, API, and ERP, so AI does not only answer questions but actually gets work done for the company.

### Slide 7: From Workflow to Agent

Hermes Agent can call Skills and Workflows, organizing documents, SOPs, FAQs, research material, and process outputs into a traceable Wiki memory, and periodically generates briefings, tracking lists, and human review reminders.

### Slide 8: From Agent to AI Team

ClawTeam lets Agents for marketing, product, sales enablement, customer service, and finance collaborate on enterprise-level tasks.

### Slide 9: Post-course consulting diagnostic report

Use the eight-stage methodology to consolidate current state, gaps, core issues, To-Be design, Roadmap, ROI, and governance.

### Slide 10: 90-day implementation route

Phase 1: Skill-ification. Phase 2: Workflow PoC. Phase 3: Agent and governance expansion.

## 8. Common Objections

### Q1: We already have people using ChatGPT. Do we still need this?

Yes. Individuals using AI does not equal the company completing AI transformation. The difference lies in whether usage can be distilled into Skills, threaded into Workflows, brought under governance, and tracked against ROI.

### Q2: Our data cannot be on the cloud. Can we still do this?

Yes. The program first determines cloud AI, Hybrid, or fully on-premise deployment. Highly sensitive data can remain on-premise; lower-sensitivity tasks can use the cloud per policy.

### Q3: Once the course is over, is that it?

No. The course is only capability building. After the course, we move into the consulting diagnostic report, which delivers a Roadmap and PoCs that can be implemented.

### Q4: Will it be hard for IT to maintain?

We incorporate credentials, permissions, logs, human review, Owners, and operational responsibility into the design. Departments will not be left to wire things up on their own.

### Q5: How do we measure ROI?

We prioritize tracking time saved, error rate, response speed, process throughput, knowledge accumulation, new-hire ramp time, and PoC-to-production conversion rate.

### Q6: We can just buy the AI tools ourselves — why do we need a consultant?

At L1-L3, you are indeed buying tools and equipment — and even just getting OpenWebUI, Skills, and n8n integrated with your CRM / ERP to actually run is not a low technical bar. At L4-L5 it is different again: that is not "buying a piece of software," it is "procuring an AI workforce that works autonomously" — it needs responsibility definitions, a governance framework, HITL, and accountability, which tools cannot buy and which a consultant builds with you (see §3.6).
