Skip to content

Morning signal sweep with sales handoff budget

Each morning it reads every new account signal against your written ICP, stage rules and plays, and proposes which ones become a sales handoff, with the evidence cited. Sales never gets more handoffs than the weekly budget, and nothing is sent or written to the CRM.

SalesWorks with Claude Code · Cursor+1Community example

What it does

  • Reads new signals with the matching account files and CRM export
  • Checks each against the ICP, stage rules and plays, citing the source lines
  • Proposes a handoff only when recipient, owner and a dated reason are all known; gaps stay gaps
  • Caps handoffs at the weekly budget and reports only the ones that need a person
  • Records your approve, edit or reject verdict and turns repeated corrections into rule changes

Your approval boundaries

Creates drafts

These actions always wait for your yes:

  • Approving each handoff decision before anyone acts on it
  • Any write to the CRM, which the skills never do themselves

You decide what happens next.

More about this workflow

This setup is for founders and small sales teams who want more time for real conversations. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads new signals with the matching account files and CRM export. Next, it checks each against the ICP, stage rules and plays, citing the source lines. Then it proposes a handoff only when recipient, owner and a dated reason are all known; gaps stay gaps. After that, it caps handoffs at the weekly budget and reports only the ones that need a person. Finally, it records your approve, edit or reject verdict and turns repeated corrections into rule changes. It works with your CRM, docs and git host, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before approving each handoff decision before anyone acts on it and any write to the CRM, which the skills never do themselves, and says plainly if a step cannot be undone.

“Skills never send and never write to a CRM.”
jnkliberty jnkliberty on GitHub · Oct 28, 2026
Before you startCRM · Docs accessScoped permissionsClaude Code or Cursor
Explore required tools and model recommendations

Tools and access

  • HubSpot CRM

    Handles the crm part of this job. Grant read scopes, plus notes write.

    API required: Yes. Needs a HubSpot private app or OAuth app with the CRM scopes you choose.

  • Google Docs

    Handles the docs part of this job. Grant one folder, create and edit only.

    API required: Yes. Needs a Google Cloud OAuth app with the Docs API turned on.

  • GitHub

    Handles the git host part of this job. Grant a fine-grained token, read code and write comments.

    API required: Yes. Needs a GitHub App or a fine-grained personal access token scoped to the repos it needs.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

Claude Sonnet 5.5

Good balance of speed and quality for briefs and drafts.

$2 per million input tokens, $10 per million output tokens.

Anthropic docs as of October 11, 2026

Cheaper backup

GPT-6 Luna

Very low cost per token for simple research summaries.

$0.10 per million input tokens, $0.50 per million output tokens, for prompts up to 272K tokens.

OpenAI docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

who you sell to and who fails the cut

2Your prompt

4 of 4 still empty
Fill these in before you run it: [ICP: who you sell to and who fails the cut] [STAGES AND HANDOFF RULES] [WEEKLY HANDOFF BUDGET] [CRM EXPORT PATH] You are the Morning signal sweep with sales handoff budget agent. Each morning it reads every new account signal against your written ICP, stage rules and plays, and proposes which ones become a sales handoff, with the evidence cited. Sales never gets more handoffs than the weekly budget, and nothing is sent or written to the CRM. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads new signals with the matching account files and CRM export - Checks each against the ICP, stage rules and plays, citing the source lines - Proposes a handoff only when recipient, owner and a dated reason are all known; gaps stay gaps - Caps handoffs at the weekly budget and reports only the ones that need a person - Records your approve, edit or reject verdict and turns repeated corrections into rule changes What you must never do without a yes from a person: - Approving each handoff decision before anyone acts on it - Any write to the CRM, which the skills never do themselves Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Code, Cursor, Claude Desktop with MCP

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect HubSpot CRM with its own login, not yours. Grant read scopes, plus notes write.
  2. 2Connect Google Docs with its own login, not yours. Grant one folder, create and edit only.
  3. 3Connect GitHub with its own login, not yours. Grant a fine-grained token, read code and write comments.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access24 / 30

Writes drafts and notes inside your tools, nothing leaves on its own.

Human approval30 / 30

Waits for a yes on: approving each handoff decision before anyone acts on it, any write to the crm, which the skills never do themselves.

Undo and logs17 / 20

Leaves drafts you can throw away, with a record of what it made.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 87.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Morning signal sweep with sales handoff budget](https://trustcase.dev/badge/morning-signal-sweep-with-sales-handoff-budget.svg)](https://trustcase.dev/use-cases/morning-signal-sweep-with-sales-handoff-budget)
HTML
<a href="https://trustcase.dev/use-cases/morning-signal-sweep-with-sales-handoff-budget"><img src="https://trustcase.dev/badge/morning-signal-sweep-with-sales-handoff-budget.svg" alt="Trustcase trust score for Morning signal sweep with sales handoff budget" height="20"></a>

Other workflows that use the same tools

  • Daily request intake and client progress page

    Operations. Each morning it reads the latest meeting transcript, recent client emails and a drop folder, files every document and turns every request into a task on one list. Before the next meeting it builds a short what's new page from the progress since the last one.

  • Weekly ops report

    Operations. Writes the Monday numbers summary so you do not build it by hand.

  • Contract renewal watch

    Operations. Warns you before contracts auto renew.