AgentSkillsCN

nimble-pre-sales

Nimble 咨询方案的技术售前与解决方案设计。适用于创建或填充一页纸文档、起草工作范围或 SOW 方案、明确团队构成与规模、为销售发现电话做准备、撰写面向客户的方案章节，或向客户解释成本、时间表、团队结构时使用。触发短语包括“一页纸”、“方案”、“SOW”、“工作范围”、“售前”、“销售发现”、“团队构成”、“解决方案设计”、“Nimble 方案”。

SKILL.md
--- frontmatter
name: nimble-pre-sales
description: >
  Technical pre-sales and solution design for Nimble consulting proposals.
  Use when creating or populating one-pager documents, drafting scope of work
  or SOW proposals, defining team compositions and sizing, preparing for sales
  discovery calls, writing client-facing proposal sections, or explaining costs,
  timelines, or team structures to clients. Triggers include "one-pager",
  "proposal", "SOW", "scope of work", "pre-sales", "sales discovery",
  "team composition", "solution design", and "Nimble proposal".

Nimble Pre-Sales Skill

Context

Nimble is a consulting firm delivering digital products across web, mobile, data, integrations, and infrastructure. This skill supports pre-sales work: one-pagers, proposals, SOWs, team sizing, and client-facing copy.

Key Principles

  • •Client-ready outputs — Assume text will be pasted directly into proposals, decks, or executive emails
  • •Support sales without overselling — Frame trade-offs honestly, emphasize options not ultimatums
  • •Justify costs and timelines — Explain why something costs more or takes longer
  • •No seniority exposure — Nimble doesn't expose seniority levels to clients; we sell teams, not individuals
  • •Goal: Make the right decision feel obvious

Priority Order

When instructions conflict, follow this hierarchy:

  1. •Explicit user instructions
  2. •Consistency with existing material
  3. •Client clarity
  4. •Consulting best practices

Surface conflicts and propose resolutions.

One-Pager Document

When asked to create or populate a One-Pager, follow the template in assets/one-pager.md.

The One-Pager is the standard internal document where the sales team consolidates all relevant information about a project opportunity.

Team Roles & Sizing

When proposing team compositions or explaining roles, refer to references/team-roles.md.

Key principles:

  • •Every project needs a Product Manager and Engineers
  • •UX/UI Designer is included for user-facing projects
  • •Solution Architect and Program Manager are reserved for complex engagements
  • •Business Analyst is used for enterprise clients or heavy discovery phases

Scope of Work (SOW)

When drafting a Scope of Work or proposal document, follow the structure in assets/scope-of-work.md.

The SOW template includes:

  • •Standard document structure (Description, Solution, Team, Deliverables, Tools)
  • •Boilerplate text for Methodology, Development process, and Communication
  • •Design process outline
  • •Action plan/timeline format