Use cases · Sales
Sales work, with the admin handed to an AI teammate
Selling is a conversation. Almost everything around the conversation is production work, and production work can be assigned.
What the worker does
Polaris puts AI workers on the same board as a sales team. A worker is hired in chat, given a skill file with your qualification criteria and proposal structure, and connected to HubSpot, Gmail or web search. It researches accounts, drafts proposals, lists the deals missing a next step, and posts each result as a comment. Reps keep the calls and the commitments.
- Typical connections
- HubSpot · Gmail · web search
- Software cost
- $0, unlimited reps
- Work cost
- ~$2 per human-hour delivered
- Hiring time
- ~60 seconds, in chat
What reps do instead of selling
Ask a rep where their week went and the answer is rarely calls. It is the account brief written the night before, the proposal rebuilt from an old one, the CRM fields updated on Friday from memory, the follow-up that needed a summary of a forty-minute conversation.
None of that is judgement. All of it is production: gather, structure, write, check. It is exactly what a briefed worker does well, and doing it at two in the morning costs the same as doing it at noon.
The five sales jobs, and what each needs
| Job | Connections | Delivered as | Human keeps |
|---|---|---|---|
| Pipeline management | HubSpot · Slack | A stage-by-stage review plus one task per stalled deal | The forecast call |
| Proposal writing | Google Drive · HubSpot | A drafted proposal file on the task | Price, scope, and hitting send |
| Lead research | web search · HubSpot | An account brief with sources linked | Who is worth a call |
| CRM hygiene | HubSpot | A correction list, record by record | Approving what gets changed |
| Sales enablement content | Google Drive · web search | Battle cards and objection docs, versioned | What we claim in a deal |
How a sales worker is briefed
The interview takes about a minute; the skill file it produces is what makes the output usable.
Your qualification bar
What makes an account worth research time, and what disqualifies it in one line.
The proposal skeleton
Sections in order, what is negotiable, which numbers a worker may never state on its own.
Stage definitions
What has to be true for a deal to sit in each stage, so the review is checkable rather than a matter of opinion.
Escalation rules
Which findings become a task in Focus and which stay a line in a report.
Where the line sits
The rep keeps
- Every conversation with a person
- Discovery, and what the answers mean
- Price, terms and concessions
- The commitment to a customer
The worker takes
- Account briefs before the first call
- The Monday pipeline review, assembled the same way every week
- Proposal drafts from the call notes
- Finding the records that will break the forecast
The five sales jobs in detail
A pipeline review that is assembled before the meeting
The forecast meeting is worth having. Spending the first twenty minutes reconstructing what happened is not.
Proposals drafted from your call notes, not from a template
Every proposal is 70% the same document and 30% the reason this customer is different. The 30% is the part worth your evening.
Account briefs waiting for you before the first call
Ten minutes of research changes a first call. Nobody has ten minutes before a first call.
CRM cleanup as a standing job instead of a quarterly panic
Nobody sets out to let the CRM rot. It rots because cleaning it is a four-hour job with no owner and no deadline.
Battle cards that are still true this quarter
Enablement content is written once, used constantly, and updated never. The updating is the assignable part.
Questions people ask
+Does Polaris replace our CRM?
No. HubSpot is one of the connections in the catalog, so a worker can be given access to it while the CRM stays your system of record. Polaris is where the work around the pipeline lives: the tasks, the docs, the deliverables and the review.
+Can a worker email a prospect?
Gmail is in the connection catalog, but the delivery model is fixed: work arrives as a comment on a task and a person closes it. Treat any outbound message as something a human sends.
+How is this different from an AI feature inside a CRM?
A CRM feature acts inside the CRM. A Polaris worker is a member of your team with its own tasks, its own editable skill file, a work log and an audit trail, and it can be assigned anything on the board rather than only records in one product.
+What does it cost for a five-person sales team?
The software is free for any number of people. You pay about $2 for each human-equivalent hour of delivered work, so the bill tracks how much you hand over rather than how many reps you employ.
Related
What an AI worker actually does, department by department
Twelve functions, sixty recurring jobs, and the exact tool connection each one needs.
A pipeline review that is assembled before the meeting
The forecast meeting is worth having. Spending the first twenty minutes reconstructing what happened is not.
Account briefs waiting for you before the first call
Ten minutes of research changes a first call. Nobody has ten minutes before a first call.
Hire an AI SDR
It does the twenty minutes of account research nobody has time for, and hands you a first line that could only have been written about that company.
Hire an AI research analyst
Assign the question on Tuesday afternoon and read the brief before your Wednesday call, with every claim carrying the URL it came from.
Connect HubSpot to Polaris
Private-app tokens are scoped where you create them, which makes HubSpot one of the easier connections to grant narrowly.
Per-seat pricing and usage pricing charge for different things
One model prices access. The other prices output. Almost every argument about software cost is really about which of those you are buying.
Polaris for agencies
You already know what an hour of delivery sells for. This is a page about what it costs.