Bottom line: the fastest interface for a rep between dials is a sentence. The sales assistant takes "generate a one-pager for acme.com" and produces the asset, or takes "what did we make for Northwind" and finds it.
Two Jobs, Both Constant
A rep working a list does two things over and over, and both are slow in a normal interface:
- Generate something for this prospect. Normally: navigate to the right playbook, open the right screen, fill a form, choose a format, submit.
- Find something we already made. Normally: remember which playbook it was under, scroll history, squint at dates.
The assistant collapses both to one line of text, from wherever you already are in the workspace.
Generating: It Asks for What Is Missing
You rarely have every field ready when the thought occurs. The assistant is built around that.
Give it what you have:
- "Generate a one-pager for acme.com" — it knows the format and the company, and asks for the contact.
- "Create a call script for Northwind, Jane Doe, VP Ops, Austin" — it has everything and generates.
- "Make some collateral" — it asks what kind and who for, rather than doing nothing.
That last case is the one that matters. A vague request is the most common request a rep actually makes, and most tools answer it with silence or an error. The assistant answers it with a question.
Requests are answered one or two things at a time, not as an interrogation. The goal is a short exchange, not a form in disguise.
Finding: Search Across Every Playbook
Assets accumulate fast. Two hundred accounts into a quarter, "did we already build something for this company" is a real question with a slow answer.
Ask in plain language — what have we made for a company, show me everything for a domain — and the assistant searches across your playbooks by company name, contact, website or location, and returns the matches as cards you can open directly.
For a rep picking up an account another rep touched three weeks ago, this is the difference between reusing an asset and regenerating one that already exists.
Why a Chat Panel Rather Than Another Screen
| The screen-based path | The assistant path |
|---|---|
| Know which playbook holds the account | Say the company name |
| Navigate to the right page | Stay where you are |
| Fill every field before submitting | Give what you have, get asked for the rest |
| Search history manually | Ask what exists |
The assistant does not replace the tables and the history views — those are better when you are working a list methodically. It wins when you have one thought, between two calls, and eleven minutes.
What It Generates
The same materials as everywhere else, from the same playbook: pitch deck, one pager, landing page, infographic, elevator pitch, cold call script and email outreach. Results come back as cards in the thread with the share link attached.
Because it generates against your saved product playbook, an asset produced from a one-line chat request is as on-brand and as well-positioned as one produced from the full interface.
Honest Limits
- It is not a general chatbot. It generates and finds sales materials. It will not write your forecast or summarize a meeting.
- It does not send anything. Assets come back as links you copy into your own email, LinkedIn or sequencer.
- Context still matters. A request with a website, a named contact and a role produces a better asset than a company name alone — the assistant will ask, but it cannot invent what nobody told it.
Try the Two Sentences
Next time you are between calls, type "generate a one-pager for" and the domain of the account you just spoke to. Then, later in the week, ask what you already made for them.
Start with the GTM pilot at edithly.com/gtm — 50 free credits, every format, no credit card required.
