Sales
Review lost proposals with the call notes beside them.
Agents read your call notes and past proposals and show what the lost ones share, with the passages behind each finding. They draft proposals from your terms and your wins. Every version waits for a person before a buyer sees it.
Or Book a demo
Lost-proposal research
Starts: By hand, with the question you want answered
- Read calls, an agent
- Read proposals, an agent
- Group findings, an agent
- Decide changes, waits for you
- Next proposals, a teammate
Waiting for you
What do we change in the next proposal?
A shared pattern doesn’t establish why deals were lost. The sales director checks the passages before deciding what to change.
- An agent
- A teammate
- Someone outside
- Waits for you
Checking loss reasons against the original notes.
A CRM loss reason gives you a starting point. The call notes, follow-up emails and proposal contain the buyer’s questions and the terms they were offered.
Agents compare those records across won and lost deals, then link the findings to the passages they came from. Your sales lead can check the evidence before changing how the team sells.
Five sales procedures to start from.
These examples include review of research findings, proposals and follow-ups. Proposal revisions require approval; you choose where other work waits.
An integration agent builds connections to the systems your team uses from their API docs. How connections are set up
-
- Read calls, an agent
- Read proposals, an agent
- Group findings, an agent
- Decide changes, waits for you
- Next proposals, a teammate
Agent work
Find won and lost deals in HubSpot, read their Gong call transcripts and PandaDoc proposals, and group recurring buyer questions or terms. Link each finding to the deal and source passage.
Waits for you
What do we change in the next proposal? A shared pattern doesn’t establish why deals were lost. The sales director checks the passages before deciding what to change.
-
- Read the notes, an agent
- Similar wins, an agent
- Draft proposal, an agent
- Approve, waits for you
- Buyer signs, someone outside
Agent work
Read the Gong call transcript and HubSpot deal notes, find similar won deals, and draft a proposal using your PandaDoc template and approved terms.
Waits for you
Send this proposal? Check the scope, fee and dates before sending. Each version needs approval from someone other than its author.
-
- Client signs, someone outside
- Brief from notes, an agent
- Book kickoff, an agent
- Accept handoff, waits for you
Agent work
Gather the signed PandaDoc proposal, HubSpot deal history and Gong call notes. Create the delivery project in Productive with a handoff brief, and prepare the kickoff invitation.
Waits for you
Does delivery accept what sales promised? The person who’ll run the work reads the promises before the client hears from them.
-
- Find today’s calls, an agent
- Account history, an agent
- Write a brief, an agent
- Pick questions, waits for you
Agent work
Read today’s Salesforce meetings, account and contact history, and any earlier opportunities for the company. Draft a brief with suggested questions for the rep.
Waits for you
Which questions do you want to ask? The suggestions come from the research. The rep knows which ones fit this buyer.
-
- Find no reply, an agent
- Reread the call, an agent
- Draft follow-up, an agent
- Send, waits for you
Agent work
Find unsigned PandaDoc proposals with no reply in the past week’s Pipedrive deal history. Read the deal’s call notes and draft a follow-up for its owner.
Waits for you
Send this follow-up? It goes to a buyer under the rep’s name, and the rep may know why they’ve gone quiet.
What arrives for sales review.
- Findings you can check
- Every one links to the call note or proposal it came from.
- Proposals someone else checked
- Every change makes a new version, and only an approved version can go to the buyer. The approver can’t be whoever wrote it.
- Handoffs delivery accepts
- The brief carries what the buyer actually said on the call.
- A brief for the first call
- Account and contact history, earlier opportunities and suggested questions.
You choose where work waits for a person.
Every proposal and revision waits for a person before a buyer sees it. You decide whether anything else does.
How approvals and tool limits work- Automatic learning
- Every edit or correction to agent work becomes a lesson automatically. Agents use relevant lessons on future jobs, with no separate training task.
- Your data and procedures
- Your business keeps its data, procedures and the knowledge built from corrections. The details of how your team works stay in your workspace.
- Choose review steps
- Add, remove or move a review step. You can try the draft on past jobs before publishing the change.
- Calls ask first
- Every call through a connection waits for a person until someone decides it can run on its own. No agent can make that decision.
- Keys stay sealed
- An agent knows a connection only by its name. The key is added on the server as each call goes out.
- Run records
- Each run keeps its steps, calls and answers. A hash-chained record makes changes to recorded events detectable.