A week on autopilot
A plan for your week, one recurring task at a time. Schedule each task in your AI assistant, or run it by hand. Each run reads from your tools and writes drafts. Anything that would change a record, send a message or spend credits waits for your OK.
8 rep tasks · 4 manager tasks · 5 change data after your yes
Download the checklist (.md) Rep reminders (.ics) Manager reminders (.ics)
- A scheduled run only reads and drafts. Each prompt that could change data or spend credits tells the assistant not to change, send, post or delete anything when it runs on a schedule, and not to spend credits.
- Tasks marked "Changes data" end with drafts or a numbered list. Review the output. To approve and apply changes, open a new chat, paste in the task's prompt and the list, then reply with the numbers you approve.
- Tasks marked "Uses credits" stop before any lookup. In the new chat, the assistant tells you how many lookups it will run (each may use credits) and waits for your OK.
- For any scheduled task that can change data, keep your assistant's approval prompts on, so it asks before it acts instead of approving actions by itself. Keep the approval lines in each prompt as they are.
The week at a glance
- Call prep for today's meetings7:30 AMRead only
- Monday 1:1 prep7:30 AM ManagerRead only Uses credits
- Monday pipeline review8:00 AMRead only
- Monday team pipeline digest8:30 AM ManagerChanges data
- Tuesday nudges for quiet deals8:00 AMRead only
- Tuesday news on my target accounts9:00 AMRead only
- Wednesday CRM cleanup8:00 AMChanges data
- Wednesday job-change check9:00 AMChanges data Uses credits
- Wednesday fix-it list for each rep10:00 AM ManagerChanges data
- Thursday follow-up sweep8:00 AMChanges data
- Friday forecast summary9:00 AMRead only
- Friday forecast roll-up and manager digest10:00 AM ManagerRead only Uses credits
Rep track
For SDRs and AEs. Start with one or two tasks, then add more once the runs look right.
Call prep for today's meetings Read only
A short brief for each customer meeting on today's calendar, ready before your first call.
Suggested time: every weekday at 7:30 AM. Change it to fit your week.
Tools it needs
- Your calendar
- Google Calendar uses: “list_events”
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “organizations”, “deals”, “activities”
- Attio uses: “records search (read only)”
- Web research (optional)
- Perplexity uses: “perplexity_search”
Look at my calendar for today and find the meetings with people outside [my company domain]. Skip internal meetings. For each meeting, write a short brief: the time and attendees, the company, and from my CRM the open deal, its stage, the next step and the last activity with its date. If web research is connected, add up to two news items about the company from the last [30] days, with sources and dates. End each brief with three questions to ask. If the CRM has nothing for a meeting, write "nothing logged" instead of filling it in. Read only: don't change anything in my tools.
From the prompt packs: Today's meetings at a glance · One-page brief for my next meeting
Full recipe: Pre-meeting brief from CRM + web · Morning plan: today's meetings, overdue follow-ups and emails waiting on you
Monday pipeline review Read only
Every open deal you own, with the ones that need work this week at the top.
Suggested time: every Monday at 8:00 AM. Change it to fit your week.
Tools it needs
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “deals”, “activities”
- Attio uses: “records search (read only)”
List my open deals in my CRM. For each one: name, stage, amount, close date, days since the last activity, and the next step if one is logged. Show a table sorted by close date. Flag deals with a close date in the past, no next step, or no activity in [14] days. End with the three deals I should work on first this week, and say why for each one. Read only: don't change anything in my tools.
From the prompt packs: My pipeline this week · Deals that have gone quiet · Close dates that have slipped
Tuesday nudges for quiet deals Read only
Draft check-in emails for open deals with no recent activity. You send the ones you like yourself.
Suggested time: every Tuesday at 8:00 AM. Change it to fit your week.
Tools it needs
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “deals”, “activities”, “notes”
- Attio uses: “records search (read only)”
Find my open deals with no logged activity (calls, emails, meetings or notes) in the last [14] days. Take up to [5], closing soonest first. For each one, show the stage, close date and last activity, then write one short check-in email (under 80 words) for the main contact. Give a reason to reply that comes from the record, like an open question or something we offered to send. Don't use "just following up" or "circling back". Show me the drafts here. Don't send anything. Read only: don't change anything in my tools.
From the prompt packs: Deals that have gone quiet · A nudge for a deal that went quiet
Tuesday news on my target accounts Read only
Recent news on the accounts you're working, so you have a reason to reach out.
Suggested time: every Tuesday at 9:00 AM. Change it to fit your week.
Tools it needs
- Web research
- Perplexity uses: “perplexity_search”
Here are my target accounts: [paste 5 to 10 company names and websites]. For each account, search for news from the last [7] days: funding, new executives, layoffs, acquisitions, new offices or big hiring pushes. List each event under its account, with the date and source link. Check that each source is about the right company by matching the website domain. Put accounts with no news at the bottom, marked "nothing found". Read only: don't change anything in my tools.
From the prompt packs: Trigger events for my account list · Account snapshot in five minutes
Full recipe: Trigger-event scoring: rank today's accounts by funding, hiring or leadership change
Wednesday CRM cleanup Changes data
A numbered list of fixes for your open deals. Nothing changes until you approve each one.
Suggested time: every Wednesday at 8:00 AM. Change it to fit your week.
Tools it needs
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “deals”, “activities”
- Attio uses: “records search (read only)”
- Your CRM, to update deals (any one of) Changes data
- HubSpot uses: “creates and edits CRM records (contacts, companies, deals, tickets, etc.)”
- Salesforce uses: “creates, updates and deletes Salesforce records (platform/sobject-all server)”
- Pipedrive uses: “creates and updates deals”
- Attio uses: “creates, updates, upserts and merges CRM records”
Find my open deals in my CRM where the close date is in the past, the next step is empty, or any of these fields is empty: [for example: amount, primary contact]. For each problem, suggest one fix: the deal, the field, the current value, the new value and why, based only on what the record shows. Number the fixes so I can approve them by number. When this runs on a schedule, don't change, send, post or delete anything, and don't spend credits. Stop after the list. When I reply with the numbers I approve, change only those fields. Don't change any field I didn't approve. Don't delete any records. Wait for my yes before you change anything.
Check each fix: the right deal, the old value and the new value. Close date and stage changes feed reports and forecasts, so make sure they're real.
From the prompt packs: Deals missing key fields · Open deals with no next step · Update next steps and close dates (changes data)
Wednesday job-change check Changes data Uses credits
Find key contacts who changed jobs. The check uses credits, so it waits for your OK first.
Suggested time: every Wednesday at 9:00 AM. Change it to fit your week.
Tools it needs
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “deals”, “organizations”, “persons (contacts)”
- Attio uses: “records search (read only)”
- A prospecting database (any one of)
- Your CRM, to update or add contacts (any one of) Changes data
- HubSpot uses: “creates and edits CRM records (contacts, companies, deals, tickets, etc.)”
- Salesforce uses: “creates, updates and deletes Salesforce records (platform/sobject-all server)”
- Pipedrive uses: “creates and updates contacts (persons) and organizations”
- Attio uses: “creates, updates, upserts and merges CRM records”
From my CRM, list up to [20] contacts on my open deals and on customers who bought in the last [12] months. Show name, company and title. When this runs on a schedule, don't change, send, post or delete anything, and don't spend credits. Stop after the list. To check them, tell me how many lookups you'll run (each may use credits) and wait for my OK. When I say OK, look up each contact in my prospecting database. For anyone whose title or company changed, propose CRM changes: 1. Same company, new title: propose a title update on their contact. 2. New company: don't edit their old contact. Propose a new contact at the new company, and a new company record if it isn't in my CRM yet. Search my CRM by the new company's website domain first, so you don't create a duplicate. Number the proposed changes so I can approve them by number. For each one, show the contact, the change (update or new), the field, the current value, the new value and where the new value came from. When I reply with the numbers I approve, make only those changes. Don't merge any records. Don't delete any records. Wait for my yes before you change anything.
Check the number of lookups before you say OK. Then check that each match is the same person (same name and a matching work history), and that a new company isn't already in your CRM under a slightly different name.
From the prompt packs: Check a sample of contacts for decay · Update contacts who changed jobs (changes data)
Full recipe: Champion job-change follow-up: reach past champions at their new company
Thursday follow-up sweep Changes data
Emails waiting on your reply and overdue next steps, with draft replies and tasks to approve.
Suggested time: every Thursday at 8:00 AM. Change it to fit your week.
Tools it needs
- Your email
- Gmail uses: “search_threads”
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”, “activities”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “persons (contacts)”, “deals”, “activities”
- Attio uses: “records search (read only)”, “tasks”
- Your CRM, to create tasks (any one of) Changes data
- HubSpot uses: “logs activities (calls, emails, meetings, notes, tasks)”
- Salesforce uses: “creates, updates and deletes Salesforce records (platform/sobject-all server)”
- Pipedrive uses: “creates and updates activities”
- Attio uses: “creates, updates and deletes tasks”
Find emails from the last [7] days from people outside [my company domain] where I haven't replied yet, and match each sender to an open deal in my CRM if there is one. Also find my open deals with an overdue next step: an open task or activity on the deal whose due date has passed. For each email, write a one-line summary of what they asked for and a short draft reply. Show the drafts here: I'll send them myself. For each overdue task or activity, suggest a new CRM task with a title, a due date and the related deal. Number the tasks so I can approve them by number. When this runs on a schedule, don't change, send, post or delete anything, and don't spend credits. Stop after the list. When I reply with the numbers I approve, create only those tasks in my CRM. Don't delete any records. Wait for my yes before you change anything.
Check each task's due date, owner (you) and related deal. Skip tasks that belong to the buyer. Read each draft reply before you send it from your own email.
From the prompt packs: Emails waiting on my reply · Turn next steps into CRM tasks (changes data)
Full recipe: Inbox triage: prospect emails waiting on you, matched to open deals with nudge drafts
Friday forecast summary Read only
A short update on your commit deals for your manager, drafted for you to check and send.
Suggested time: every Friday at 9:00 AM. Change it to fit your week.
Tools it needs
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “deals”
- Attio uses: “records search (read only)”
Write my forecast update for my deals in the forecast category [Commit] that close in [this month]. If my CRM has no forecast category, use the stages [stage names] instead. Include: the commit total and each commit deal with its amount, my total open pipeline, commit deals at risk and why, close dates that moved this week if the CRM shows it, and my next steps for next week. Keep it under 200 words. Use only numbers from my CRM, and list the deals you used. Show me the draft here. Don't send or post it. Read only: don't change anything in my tools.
From the prompt packs: Forecast summary for my manager · Reality check on my commit deals · Close dates that have slipped
Full recipe: Forecast reality check: flag Commit and Best Case deals with no recent activity
Manager track (optional)
For sales managers. Use it with the rep track or on its own.
Monday 1:1 prep Read only Uses credits
An agenda for each 1:1 this week, built from the rep's deals (and calls, when run by hand). On a schedule it skips Gong. Run it by hand to check calls in Gong, which uses credits, so it waits for your OK first.
Suggested time: every Monday at 7:30 AM. Change it to fit your week.
Tools it needs
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “deals”, “activities”
- Attio uses: “records search (read only)”
- Your call recorder (optional, any one of)
Prep my 1:1s this week with [rep names]. For each rep, list their open deals from my CRM with stage, amount, close date and last activity. Flag any with a close date in the past, no next step, or no activity in [14] days. Take each rep's [3] largest open deals. If a call recorder is connected, ask how the recent calls on each one went: whether a next step was agreed, who from the buyer joined, and which questions or objections came up. Say which deal each answer is about. When this runs on a schedule, don't change, send, post or delete anything, and don't spend credits. In a scheduled run, skip Gong and say so. Before you use Gong, tell me how many lookups you'll run (each may use credits) and wait for my OK. If an answer comes from Gong, it's a summary, not a quote: label it that way, and say which call it came from if Gong shows it. If no call recorder is connected, skip this and say so. Turn it into one agenda per rep: two things that are working, one or two things to talk through (framed as questions), the CRM cleanup list, and a blank slot for the rep's own topics. Don't add talk ratios, scores or comparisons with other reps. Read only: don't change anything in my tools.
Check the number of lookups before you say OK. Gong lookups use credits based on how many calls and emails they analyze.
From the prompt packs: Prep a 1:1 with a rep · Save the 1:1 agenda to Notion (changes data)
Full recipe: 1:1 coaching agenda: call habits from Gong and CRM cleanup for each rep, saved to Notion
Monday team pipeline digest Changes data
Last week's pipeline changes for your team, drafted for Slack. It posts only after your yes.
Suggested time: every Monday at 8:30 AM. Change it to fit your week.
Tools it needs
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “deals”, “activities”
- Attio uses: “records search (read only)”
- Slack, to post Changes data
- Slack uses: “sends and schedules messages”
Make a short pipeline digest from my CRM for my team ([rep names]) for the last [7] days: new deals, deals that moved stage, and deals closed won and lost. Add open deals with no activity in [14] days. Include amounts and links to the records if you have them. Draft it as a Slack message to [channel name or person], and show me the exact message and where it will go. When this runs on a schedule, don't change, send, post or delete anything, and don't spend credits. Stop after the draft, and wait for my yes before you post or send anything.
Check the channel or person, and that the numbers match your CRM. Deal amounts may be sensitive, so think about who can read that channel.
From the prompt packs: Post a pipeline digest in Slack (changes data)
Full recipe: Weekly pipeline digest to Slack
Wednesday fix-it list for each rep Changes data
Each rep's deals that need cleanup, with a Slack message for each rep to approve.
Suggested time: every Wednesday at 10:00 AM. Change it to fit your week.
Tools it needs
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “deals”, “activities”
- Attio uses: “records search (read only)”
- Slack, to post Changes data
- Slack uses: “sends and schedules messages”
For each rep on my team ([rep names]), find their open deals with any of these problems: close date in the past, no next step, no activity in [14] days, or amount missing. Group the list by rep, with the deal and the problem. Then draft a short, friendly Slack direct message for each rep with their own list, and show me every message and who it goes to. When this runs on a schedule, don't change, send, post or delete anything, and don't spend credits. Stop after the drafts, and wait for my yes before you post or send anything.
Check each person and their message. Send direct messages, not a channel post, so nobody's list is shared with the team.
From the prompt packs: CRM hygiene list for each rep · Send each rep their fix-it list in Slack (changes data)
Full recipe: CRM hygiene sweep: send each rep their own fix-it list in Slack
Friday forecast roll-up and manager digest Read only Uses credits
Your team's commit deals checked against the calls when you run it by hand, plus a short digest for your own manager. On a schedule it skips Gong. Run it by hand to check calls in Gong, which uses credits, so it waits for your OK first.
Suggested time: every Friday at 10:00 AM. Change it to fit your week.
Tools it needs
- Your CRM (any one of)
- HubSpot uses: “CRM search (read only)”
- Salesforce uses: “SOQL query (soqlQuery) and SOSL search (find)”
- Pipedrive uses: “deals”
- Attio uses: “records search (read only)”
- Your call recorder (optional, any one of)
List my team's deals in the forecast category [Commit] that close in [this quarter]. If my CRM has no forecast category, use the stages [stage names] instead. Group the deals by rep. If a call recorder is connected, check each deal's most recent buyer conversation: did the buyer confirm the timeline, is the decision maker involved, and is a next meeting booked? Mark each deal "supported", "at risk" or "no evidence", and show what you based it on. When this runs on a schedule, don't change, send, post or delete anything, and don't spend credits. In a scheduled run, skip Gong and say so. Before you use Gong, tell me how many lookups you'll run (each may use credits) and wait for my OK. If an answer comes from Gong, it's a summary, not a quote: label it that way, and say which call it came from if Gong shows it. If no call recorder is connected, use only the CRM and say so. End with a digest for my manager, under 200 words: the commit total, deals at risk and why, and what changed this week. Show me the draft here. Don't send or post it. Read only: don't change anything in my tools.
Check the number of lookups before you say OK. Gong lookups use credits based on how many calls and emails they analyze.
From the prompt packs: Reality check on my commit deals · Deal review with evidence
Full recipe: Forecast reality check: flag Commit and Best Case deals with no recent activity
How to schedule a task
Paste the task's prompt as the instructions, then choose how often it runs. Each assistant offers different schedule options; the ones below come from each vendor's docs, checked Oct 22, 2026.
Claude
- Scheduled tasks are on all paid plans (Pro, Max, Team and Enterprise), in Claude Cowork and in the new Claude experience. On Team and Enterprise, admins control Cowork access. (support.claude.com)
- In the new Claude experience, create one from any conversation: describe the task and how often it should run (for example, every Monday at 8 AM). Review the task name, schedule and instructions Claude proposes, then click Schedule. (support.claude.com)
- In Cowork, click Scheduled in the left sidebar, then New task. Choose Create with Claude, or Set up manually. (support.claude.com)
- Set up manually asks for a task name, the prompt, the approval mode and how often the task runs: hourly, daily, weekly, on weekdays, or manually. (support.claude.com)
- Scheduled tasks can use the same connected tools as regular Cowork tasks. They run remotely, so they run on their cadence even when your computer is asleep or the Claude desktop app is closed. A task that needs local files or apps only runs locally. (support.claude.com)
- Each scheduled task runs as its own Cowork session, and you review the results when they're ready. Click Scheduled in the left sidebar to see upcoming and past runs, and to pause, resume, delete or run a task on demand. (support.claude.com)
ChatGPT
- Create a scheduled task from a chat on the web, and manage its runs from Scheduled. (learn.chatgpt.com)
- Scheduled tasks on the web can use the connected tools available to that chat. (learn.chatgpt.com)
- A standalone task starts a new chat for each run. A task inside a chat returns to that chat, so it keeps the earlier context. (learn.chatgpt.com)
- OpenAI suggests testing the prompt in a regular chat first, then reviewing the first few runs and adjusting the prompt, tools or cadence. (learn.chatgpt.com)
Zapier
- Schedule by Zapier can start a Zap every month, week, day or hour. The schedule step doesn't count toward your task usage. (help.zapier.com)
n8n
- The Schedule Trigger node runs a workflow at fixed intervals and times. Save and publish the workflow for it to run. (docs.n8n.io)
Zapier and n8n start a workflow, not a chat. Use them only if you already build workflows there, and keep the scheduled steps to reading and drafting.
Using another assistant? Run the prompt by hand, or check your assistant's settings for scheduling. The calendar file below adds a reminder with the prompt in it.
Download
Get the plan as a Markdown checklist, or add reminders to your calendar. Each calendar event repeats at the suggested time and has the prompt in its description, so you can copy it into your assistant. The events are only reminders: they don't run anything.
Download the checklist (.md) Rep reminders (.ics) Manager reminders (.ics)
The events have no time zone attached (floating time), so each reminder shows at its suggested local time, such as 8:00 AM, wherever you are. They repeat weekly from the week of Oct 26, 2026. To stop the reminders, delete the events in your calendar.
What each tool can do comes from its StackMCP listing, which links the source for each fact. Vendors change their servers and assistants change their scheduling, so if a step doesn't work, check the linked page. The prompts are starting points: edit them to fit how your team works.
Hear when the plan changes
New prompts, skills and recipes by email, plus connectors that changed or broke.