Sales / Sales Engineering Live
User Story Generation
Paste discovery notes and get them turned into user stories with acceptance criteria — and an explicit list of what the notes do not say clearly enough to write.
- Run on demand
- ~6 credits per run
- v1.0.0
What does User Story Generation do?
User Story Generation is a production AI agent in the sales section of the Leverge agent store, built for the sales engineering process. Paste discovery notes and get them turned into user stories with acceptance criteria — and an explicit list of what the notes do not say clearly enough to write. It runs on demand, works through 2 steps and returns 4 outputs, including user stories.
What it needs
-
Discovery notes or transcript
What the customer said about how they work today and what they need.
-
Story settings
What it does
- Writing the stories
- Writing the backlog note
What you get back
- User stories
- Acceptance criteria — highest priority story
- Backlog note
- Cannot write these yet
After each run it asks: “Would a delivery team accept these stories?”
When it runs
Run on demand
Oversight
Runs under scoped, least-privilege credentials with every action written to an audit log. Anything that moves money, alters a contract or reaches a customer requires human approval before it executes.
Sales Engineering
Other agents in sales engineering
Pipeline, proposals, renewals and the CRM hygiene underneath them
-
Acceptance Test Generation
Turn agreed requirements into acceptance tests the customer would sign off — each traceable to a requirement, prioritised, with the untestable ones named.
-
Requirements Clarity Check
Take rough requirements from a discovery call and turn them into ones an engineer could build against — with everything still ambiguous written as a question rather than resolved by guessing.
-
Solution Blueprint
Describe what the customer needs and get a solution architecture written against your own standards, with every component justified and every deviation from standard called out.
-
Solution Recommendation
Score which solution components actually fit a customer's requirements, by feasibility rather than by what would be nice to sell.
-
Account Plan Review
Check an account plan against what a plan is supposed to contain — whether its actions have owners, whether its targets are grounded, and whether it says anything the data does not support.
-
Account Risk Monitor
Name an account and get external signals searched for anything that changes your plan — funding, restructures, leadership moves, regulatory news — with what is corroborated separated from what is rumour.
Next Step
Deploy User Story Generation, or adapt it
It runs as-is against the inputs above. Most deployments diverge — a different source system, a different tolerance, a different approval path. A 30-minute technical call establishes which.