Prioritize your accounts for the week
Images on this page are for illustrative purposes only. Example outputs in this play are illustrative — the structure, fields, and format reflect real Lusha connector, Gmail, and Calendar output, but were not pulled from a live session. Run the prompt with your own account list and connectors to see live results. Personal details in any live examples are masked or abbreviated for privacy.
Most reps start Monday by working accounts in whatever order comes to mind. This Claude prompt scores every account against three live inputs — Lusha buying signals, open Gmail threads, and upcoming Google Calendar meetings — and returns a P1–P4 ranked list with one specific action per account. Run it Monday morning. Work through the list in order.
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
It's the start of the week and I want to know which accounts to prioritize — not by gut feel or alphabetical order, but based on what's happening at each account right now, what's sitting open in my email threads, and what's coming up in my calendar.
My accounts:
- Account list: [PASTE COMPANY NAMES AND PRIMARY CONTACTS — one per line]
- What I sell: [PRODUCT / SOLUTION]
- Current pipeline stage for each: [PASTE DEAL STAGE OR "VARIES"]
</context>
<task>
1. For each account, use Lusha to check for buying signals in the last 14 days:
- New exec hire in the relevant function?
- Funding event?
- Headcount surge?
- Any structural change that creates urgency?
2. Search Gmail for thread status per account:
- Is there an unanswered outbound email sitting open?
- Did the contact reply recently but I haven't responded?
- Is there an open commitment I made that hasn't been followed through?
3. Check Google Calendar for upcoming meetings with each account:
- Is there a call in the next 7 days?
- Is there a meeting that needs prep?
4. Score and rank each account for this week:
- P1 — ACT TODAY: live signal + unanswered thread or meeting this week
- P2 — REACH OUT THIS WEEK: live signal, no open thread
- P3 — FOLLOW UP: open thread with no reply, no signal
- P4 — MONITOR: no signal, no open thread, no meeting — nothing urgent this week
5. Return a weekly account priority list:
- Accounts ranked P1 → P4
- For each account: signal (if any), thread status, next meeting (if any), recommended action
- One specific action per account — not "follow up" but what exactly to do
- Total: X accounts need action this week, X can wait
</task>
<constraints>
- P1 requires both a signal AND an open thread or upcoming meeting. Don't over-assign P1.
- One specific action per account — not generic advice.
- P4 accounts get one line maximum — don't pad the output.
- If an account has a meeting this week but no signal and no open thread: P3, not P2.
</constraints>What you'll get back
The situation: An AE runs this Monday morning for 7 active accounts. Mix of prospects and customers at various pipeline stages.
Weekly priority list — week of May 26
P1 — ACT TODAY
Dunmore Analytics · Series B 18 days ago · Open thread: T.K. asked pricing question 54 days ago, no reply sent → Email T.K. today. Reference the funding and the unanswered pricing question in the same message — “With the Series B just closed, the conversation is probably more relevant now.”
Crestline Software · New CRO 12 days in · Meeting Thursday 10am → Prep Thursday’s call today. New CRO is still forming opinions on the stack. Open with a question about the current setup, not a pitch.
P2 — REACH OUT THIS WEEK
Ashford Platforms · Sales headcount up 28% in last 30 days · No open thread → Cold outreach this week. Lead with the hiring surge: “Your SDR headcount is growing fast — data quality is the first thing that breaks at this scale.”
P3 — FOLLOW UP
Briarwood SaaS · No signal · D.R. replied 11 days ago — no response sent → Reply to D.R.’s email today before the thread goes fully cold.
Greenway Cloud · No signal · Open commitment: integration doc promised 3 weeks ago, not sent → Send the integration doc with a one-line note. Overdue.
P4 — MONITOR
Halcyon Data — no signal, no open thread, no meeting. Last touch 8 days ago. Check again next week. Elmont Systems — discovery booked in 2 weeks. No action needed this week.
5 accounts need action this week · 2 can wait
Illustrative example — fictional company names used. Run with your own account list to see live results.
Why use Lusha in Claude
The P1 classification requires two inputs — not just a signal, not just an open thread, but both together. Dunmore has a Series B AND an unanswered pricing question: the signal creates the urgency, the thread creates the angle. Crestline has a new CRO AND a meeting Thursday: the signal shapes the prep, the meeting creates the deadline. Without this scoring, both accounts look like “should follow up” on a flat list. With the scoring, both are “act today before the window closes.” The P4 output is equally useful — knowing Halcyon and Elmont need nothing this week means the time saved on those accounts goes to the ones that actually do.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
What if most accounts come back as P4?
A P4-heavy list is accurate data — most accounts don’t need action every single week. Work the P1–P3 accounts and check P4 accounts again next Monday. If P4 accounts persist for 3+ weeks with no signal and no thread activity, consider whether the accounts are still active or whether a re-qualification is needed.
What if I have 30+ accounts?
Run the prompt with all accounts — the scoring works regardless of list size. For a large territory the P4 list will be long by design. P4 accounts need nothing this week; the list confirms that rather than creating work where none is needed.
Can I share this list with my manager?
Yes — the summary line “5 accounts need action this week, 2 can wait” is designed for exactly that. The P1 details give a manager visibility into the most urgent items without reading the full output.
How is this different from the open commitments scan?
The open commitments scan digs into each active deal and surfaces specific promises made in email threads — case studies not sent, questions not answered, intros not scheduled. This prompt is a higher-level weekly triage across all accounts — it tells the rep which accounts deserve attention this week and why. Use this one Monday morning for the priority ranking, use the commitments scan before specific high-stakes calls.
Why does a meeting alone make an account P3 rather than P2?
A meeting this week requires prep — that’s genuine action needed. But without a signal or an open thread, the account isn’t urgent in the same way a signalled account is. P3 means “handle this before the meeting.” P2 means “reach out proactively this week because the signal window is open.” The distinction prevents treating a routine check-in call with the same urgency as a post-funding outreach.
Ready to build this?
Get started with Lusha and set up this play in minutes.
