Sales Copilot
The State of Stick Sales Copilot is an internal sales-intelligence and drafting workspace. It helps the team prepare more consistently across prospects while keeping every material business decision under human control.
What it supports
Section titled “What it supports”The copilot can assist with:
- account briefs and approved-source research;
- vertical and connected-product fit;
- use-case and campaign recommendations;
- meeting preparation and discovery questions;
- extracting decisions, commitments, and open questions from notes;
- recommended next actions;
- follow-up and objection-response drafts;
- proposal outlines and proposal review;
- account and opportunity pipeline summaries.
Account-centered context
Section titled “Account-centered context”Copilot work is associated with the existing sales record rather than stored as an isolated chat. Context may include the account, contacts, opportunity, interactions, sales tasks, approved research sources, recommendations, and proposal drafts.
Each saved recommendation preserves:
- the associated account and opportunity;
- source references;
- task and prompt version;
- provider and model;
- generation time;
- review and approval state;
- human edits or reviewer notes.
Approved knowledge
Section titled “Approved knowledge”The copilot is designed to work from approved State of Stick materials and account-specific research. Relevant knowledge can include:
- platform and capability documentation;
- product and connected-media definitions;
- vertical guidance and public case studies;
- approved pilot structures and proof points;
- pricing rules used only within authorized workflows;
- security distinctions and prohibited claims.
Only approved source material is supplied as factual grounding. Missing facts should become questions or assumptions requiring confirmation, not invented details.
Human-control boundary
Section titled “Human-control boundary”The Sales Copilot does not:
- send email, submit forms, schedule meetings, or contact a prospect;
- create an account or accept terms on an outside service;
- set or approve pricing, discounts, delivery dates, or production scope;
- promise performance, exclusivity, affiliation, authentication, or legal terms;
- approve a proposal or customer deliverable;
- publish customer-facing material.
The expected flow is:
account history + approved sources ↓ copilot draft ↓ claim and source review ↓ human edits and approval ↓ separate authorized business actionFuture customer value
Section titled “Future customer value”The same governed foundation can support customer-facing planning tools when a product includes them. For example, an approved brand team could use its own connected-product data and brand materials to prepare campaign plans, product stories, retailer pitches, or engagement recommendations.
That future use remains customer-scoped, permission-aware, and subject to the same grounding and publishing controls. The internal Sales Copilot is not a promise that every customer receives an autonomous sales system.
See Capabilities and Evidence for the language used to distinguish a supported system capability from a customer pilot or production deployment.