Welcome & Why We Built This
This is where every sales hire at Senzary starts. Not a tutorial — a working briefing. You are walking into a company where Eric tracks the pipeline in five buckets, where GOVBIDS triage runs every morning, where Apollo, HubSpot and Jira are stitched together with skills, and where the biggest sin is surfacing a stale deal inside a clean-looking summary.
Everything you do in sales here follows three laws:
1. **Every claim ships with a link.** A HubSpot deal update isn't real until the record URL is in the message. An Apollo prospect isn't a contact until it lives in HubSpot. A bid isn't triaged until it has a next-step owner. 2. **Skills do the structural work, you do the judgment.** `commercial-manager`, `inside-sales-manager`, `partnership-discovery`, `agenda-manager` — these do the heavy lifting. You decide what matters. 3. **No generic next steps.** "Keep an eye on it" is not an answer. Every item in your pipeline has a next action with an owner and a date or it gets escalated.
By the end of this chapter you will know the five-bucket pipeline model, the four core skills that power the sales motion, and the exact prompts Eric uses every morning to drive his own day.
How Eric talks about this
“sales morning brief now”
The morning brief is the single most-used prompt in the sales motion. Eric does not start the day without it. It loads commercial-manager and inside-sales-manager together so you get one consolidated view — hottest accounts, what's overdue, what changed overnight. If you catch yourself opening HubSpot first, you're working out of order.
“pipeline by 5 buckets and tell me what's missing”
The five buckets are non-negotiable: Direct leads, Distributor leads, Partner search, Ongoing proposals, Bids pending. Every deal lives in exactly one bucket. When Eric asks "what's missing," he means gaps in the bucket — a Distributor lead without a partner attached, an Ongoing proposal without a follow-up date, a Bid pending without a Jira GOVBIDS ticket. That gap list is the work.
“update hubspot deal and show the link”
"Show the link" is the rule. Eric corrected me here more than once — you cannot tell him a deal was updated without pasting the HubSpot record URL. The link is the proof. If you can't paste it, the update didn't happen. This applies to every system: HubSpot deals, Jira SF tickets, Confluence pages, Google Drive proposals.
“triage govbids and tell me what matters”
GOVBIDS volume is high and most of it isn't worth pursuing. Triage is ranking by deadline × fit × actionability. The output is not "here are 30 bids" — it's "here are the 4 that fit Senzary, with the next step and the owner." If your triage list still feels like a haystack, it isn't triage yet.
“no generic 'keep an eye on it' entries”
Eric corrected me here. Early in the GOVBIDS workflow I tried to mark bids "monitor weekly" without a concrete next step. He killed that pattern. Every bid in the queue has either (a) a date for next action with an owner, or (b) it gets dropped from the queue. "Keep an eye on it" hides the decision instead of making it.
“run the follow-up sweep”
The follow-up sweep finds threads where the ball is on our side and drafts the next touch. The sweep does not invent promises — it preserves the dates and commitments already made in earlier emails. If the sweep ever produces a draft that contradicts a promise Eric already made to a customer, that's a hard failure.
Try these exact phrasings
Try it yourself
Pick any deal in HubSpot you have access to. In ≤300 words: name which of the five pipeline buckets it belongs in, name the skill you would load to advance it, name the next action with an owner and a date, and paste the HubSpot record URL as proof.
- Names exactly one of the five buckets (Direct leads, Distributor leads, Partner search, Ongoing proposals, Bids pending)
- Names a real Senzary skill (commercial-manager, inside-sales-manager, partnership-discovery, agenda-manager, or proposal-manager)
- Next action has both an owner and a date — not 'monitor' or 'keep an eye on it'
- Includes the HubSpot deal URL as link proof
Quick check
1. Which is the correct order to start a sales day at Senzary?
- a. Open HubSpot, scan deals manually, then ask for a summary
- b. Run 'sales morning brief now', then act on the briefing
- c. Check Apollo for new prospects first
- d. Read GOVBIDS RSS feed and triage from there
Reveal answer
The morning brief is the single load-everything prompt. It pulls commercial-manager + inside-sales-manager together with overnight changes. Starting in HubSpot or Apollo means working without the consolidated view and missing what changed.
2. A teammate marks 5 GOVBIDS as 'monitor weekly' with no other notes. What's wrong?
- a. Nothing — monitoring is the correct first step
- b. They should have triaged into Jira GOVBIDS instead
- c. 'Monitor' has no owner or date — every queued bid needs both
- d. 5 bids is too many to track
Reveal answer
The Senzary rule is no generic next steps. "Monitor weekly" hides the decision. Every bid in the queue either has a concrete next action with an owner and a date, or it gets dropped from the queue.
3. You tell Eric 'I updated the HubSpot deal.' What's the next thing he expects in the same message?
- a. The customer's email address
- b. The HubSpot record URL
- c. An export of the deal as a PDF
- d. Nothing — your word is enough
Reveal answer
Show the link. Eric's standing rule: an update isn't real until the record URL is in the message. The link is the proof, every time.
Built 2026-07-31 · 6 teaching moments · 4 prompts