74 lines
2.1 KiB
Markdown
74 lines
2.1 KiB
Markdown
# S-22 Slide Design V1
|
|
|
|
## Status
|
|
|
|
- Status: production-light design.
|
|
- Source page: P22.
|
|
- Page title: 销售武器库：从立场文件到作战工具.
|
|
- Line: production-light.
|
|
- Review: none.
|
|
- Write policy: append-only; overwrite allowed: no.
|
|
|
|
## Design Purpose
|
|
|
|
S-22 是行动收束页。它要把整套“为什么是我们”的立场，转成后续可建设、可复用、可训练的销售工具体系。
|
|
|
|
核心判断：
|
|
|
|
> 销售武器库越成熟，销售越有底气。
|
|
|
|
## Visual Concept
|
|
|
|
画面是“销售武器库成熟度地图”。左侧是一份已经亮起的立场文件，中间是正在建设的销售工具区，右侧是未来可复制的销售作战系统。
|
|
|
|
三层结构：
|
|
|
|
- 立场层：一句话定位、三句话版本、标准回答
|
|
- 证明层：案例、样板、评测、成果数据
|
|
- 作战层：问答库、话术卡、自检表、不适合客户清单
|
|
|
|
每个工具像一件装备或卡片入库，已具备的亮起，待补齐的半透明。
|
|
|
|
## Text / Typography Plan
|
|
|
|
Title:
|
|
|
|
> 销售武器库：从立场文件到作战工具
|
|
|
|
Subtitle:
|
|
|
|
> 哪些已经有，哪些正在补，哪些决定我们能不能复制
|
|
|
|
Core judgment:
|
|
|
|
> 销售武器库越成熟，销售越有底气
|
|
|
|
Layer labels:
|
|
|
|
> 立场层 / 证明层 / 作战层
|
|
|
|
Tool labels:
|
|
|
|
> 一页纸定位 / 平台差异 / 开发公司差异 / 样板库 / 案例页 / 评测页 / 问答库 / 话术卡 / 不适合客户 / 自检表
|
|
|
|
Bottom line:
|
|
|
|
> 今天先把立场讲清楚，后面把立场做成武器
|
|
|
|
## Layout
|
|
|
|
- Top: title, subtitle, core judgment.
|
|
- Left: current stance file, glowing.
|
|
- Center: sales tools under construction.
|
|
- Right: repeatable sales operating system.
|
|
- Three horizontal layers or stacked bands: 立场层 / 证明层 / 作战层.
|
|
- Background: deep navy-black operation map and arsenal wall.
|
|
|
|
## Constraints / Avoid
|
|
|
|
- Do not make it look militaristic or violent.
|
|
- Do not use literal weapons as the main subject; use business tool cards / equipment metaphor.
|
|
- Do not include long final-consensus paragraph in the image.
|
|
- Do not turn the page into a task checklist only.
|
|
- Keep action energy and visual closure.
|