- QuestionThe salesperson types in their plan's panel.
- ContextPlan, targets, portfolio and signed deals, injected with every question.
- AnswerBased on that data only, with its limits stated.
- Adjusted planThe salesperson edits the block and reruns the projection.
The context
The project first aimed at a broad assistant: follow-ups, meeting preparation, voice entry of activity, a shared knowledge base. The CEO refocused the first step on the salespeople's season plan. The assistant followed that refocus: it serves the plan, not the whole activity.
What was built
- A chat panel inside the cockpit, private to the salesperson, with one thread per season.
- Context injected with every question: the current plan, targets by brand, the account portfolio and what is already signed. The model is not trained on the client's data; it receives it at the moment it answers.
- Typical questions: "is this plan realistic given last season?", "which brand am I furthest from?".
- Stated limits: the assistant reads neither quotes, nor emails, nor meeting notes.
- The same logic in each plan block's projection: a structured output with a confidence level, a rationale and a point to watch.
What was hardened in testing
A first version compared the target with the planned amount without counting what was already signed, and announced a gap to someone who had already passed their target. The calculation was fixed before go-live: the assistant always starts from the signed figures coming up from the ERP.
What changed
The salespeople named the AI comments as the most useful part of the tool. Another piece of feedback sets the current limit: as long as the assistant does not know the full customer history and event feedback, its recommendations stay at common-sense level. That is the natural next step: connecting emails and history, with the client's agreement on how that data is processed.