Bellwether
Pipeline integrity officer. Bellwether owns forecast integrity: no deal sits in the committed number unless the evidence in the CRM supports it.
- Price
- $20
- Displaces
- RevOps analyst, about $125,000 loaded
- In the box
- 7 skills, 7 routines
- Connectors
- HubSpot or Salesforce (one, never both), Slack, Google Sheets, Gmail
Who it displaces
A RevOps analyst, about $95,000 in salary and about $125,000 fully loaded. Bellwether takes the part of that role that is scoring every deal against the same evidence standard every week, and saying out loud when the CRM and the calendar disagree.
Bellwether is $20, less than that analyst costs per hour, and priced so you do not have to think about it.
What is in the box
Skills
Seven skills.
/evidence-scoreScores deals against the seven proofs and produces dollars at risk./reality-checkThe disagreement skill. The CRM records what a rep entered; meeting objects and invitation metadata record what happened, and the two get compared./push-auditPush count is the field your CRM does not have. This skill builds it and keeps it./calibrateReplaces the stage probability an admin typed in 2023 with what actually happened./forecast-callThe deliverable. Three cases with reasoning and the evidence-weighted number./rep-briefThe adoption skill. Everything else can be right and this one being wrong kills the rest./margin-band-readThe edge skill, and the only place Bellwether opens a file it does not own.
Routines
Seven routines. Times are in the time zone you set.
| Routine | Cadence |
|---|---|
| Monday forecast call | Every Monday at 07:10 |
| Tuesday rep briefs | Every Tuesday at 08:30 |
| Daily slip watch | Monday to Friday at 06:45 |
| Monthly calibration refresh | First business day of each month at 05:20 |
| Friday next-period coverage | Every Friday at 16:00 |
| Period close and accuracy freeze | 06:00 on the first business day after a period closes |
| Edge E3 read and expiry sweep | Monday to Friday at 06:20. Edge only |
Connectors
HubSpot or Salesforce, one and never both. Slack, Google Sheets, Gmail. Bellwether reads Gmail and only reads it. It writes to the CRM only with approval.
Grok Bot has no first-party Google Calendar plugin, so every meeting signal comes from CRM meeting objects and Gmail invitation metadata. SETUP.md says so before you fill anything in, because it decides how much of one pipeline proof the bot can see.
Working with Backstop
Bellwether consumes one optional edge, E3. When a co-located Backstop publishes an account margin band, Bellwether reads it and nothing more. Bellwether publishes no contract file and produces nothing another bot consumes. It needs Backstop under the same Grok Bot member for the edge to exist at all, and it runs complete with no other bot installed.
What it never does
Bellwether never contacts a customer, never spends, never signs, and never changes a production record on its own. Its only write is to the CRM, and only with a named human's approval for that exact change. Gmail is read only. Every consequential action needs approval that covers the exact action, target and scope, never inferred from silence or a previous yes.
A placeholder you leave unfilled gets quoted back to your sales leader verbatim on Monday morning. That is deliberate. The bot does not guess at your thresholds.
What you receive
By email from Lemon Squeezy, within about a minute of payment:
- The share link, in a text file beside the ZIP. Add the bot to your Grok Bot account and its instructions, skills and routines come with it.
- Six documents, as a ZIP.
BOT.md, the instruction block and the placeholder table.SKILLS.md, all seven skills in full.ROUTINES.md, all seven with schedule, input, result and approval boundary.SETUP.md, the connector order and the Config tab the skills read thresholds from.WORKSPACE.md, the file contract and the E3 edge.EVAL.md, the acceptance tests. - The acceptance tests in
EVAL.md. Run them on day one, before the first Monday forecast call goes to anyone. They are also the condition of the 14-day refund.
No call, no name on the documents, no 24-hour wait. Open SETUP.md first. It gives the connector order and what the first hour looks like.