Validate the deal before you walk into the signing call
A Claude prompt that takes the contract-review or signing call sitting on your calendar and runs the full pre-close check on everyone attending before it starts. Calendar tells the play which meeting and who’s on it. Lusha validates that the signer still has authority for this deal, that the buying group roles are current, and that nothing has changed at the account that would re-route the contract through a different approval path.
The worst kind of deal slip happens after the contract is sent. A security review opens, the signer left two weeks ago, the acquired entity’s contracts are under freeze. The signing call is the last moment to catch any of it — and it’s exactly when you have the least time to research. This play does the research off the calendar invite, automatically, before you join.
This play runs on Claude with the Lusha and Google Calendar connectors. Once both are connected in Claude, they run in the background — no special syntax needed. Just ask Claude to validate your next signing call.
Images on this webpage are for illustrative purposes only. Any named individuals shown in live demo outputs are real, with last names abbreviated for privacy.
The prompt
<context>
I have a contract-review or signing call coming up. Before I join, I want to validate everyone on it and make sure nothing has changed at the account that would re-route the contract. Use my Google Calendar to find the call and the people on it, and use Lusha to validate them.
My deal:
- The expansion or contract I'm closing: [WHAT'S BEING SIGNED]
- Contract value (annual): [DOLLAR AMOUNT]
- Contract term: [LENGTH]
- Who I think the signer is: [NAME, TITLE — or "find it from the invite"]
</context>
<task>
1. Find my next contract-review or signing call on Google Calendar. Pull the external attendees from the invite.
2. Identify the likely signer from the attendees. Use Lusha to validate them:
- Confirm their current title and that they're still at the company
- Check their seniority against the contract value (a $250K annual contract typically needs VP or higher, $1M+ typically needs C-suite)
- Confirm they're reachable (verified email or phone) in case a pre-call touch is needed
3. Validate the rest of the attendees with Lusha:
- Confirm each one's current title and role
- Flag anyone whose role has changed since the deal started, or who sits in the approval chain but wasn't expected on the call
4. Use Lusha's signals layer to scan the account for structural changes that would re-route the contract:
- Executive departures or hires in the approval chain (CRO, CFO, CSTO, CTO)
- M&A as the acquired party (often freezes contracts)
- Security incidents (may trigger tighter procurement review)
- Major reorganizations (changed reporting lines mean changed approval routing)
5. Return a clear pre-call decision:
- GO IN CLEAN — everyone validated, no structural changes. Run the call as planned.
- GO IN, BUT RAISE ONE THING — minor issue worth confirming on the call itself.
- HOLD THE SIGNATURE — structural change that should be resolved before ink. Surface what changed and the right next move.
</task>
<constraints>
- Validation is binary on each check — the person is at the company or they aren't, the title matches or it doesn't. Don't soften with "probably still there."
- Do not invent contacts, roles, or signals. Surface only what Lusha returns. If an attendee can't be verified, flag them to confirm on the call.
- Keep it to one screen — something I can read in the few minutes before I join.
</constraints>What you'll get back
Input: A signing call on the calendar with Snowflake — closing a $480K, 24-month sales-productivity expansion. The invite has Brian R. (CFO) and two others from the buying group. Last touch was 11 days ago.
Output: HOLD THE SIGNATURE. Everyone on the call validates clean, but a live structural event at Snowflake creates a real risk the contract gets re-routed. Below is the real result from running the prompt against the live Lusha connector.
Pre-call decision: HOLD THE SIGNATURE
Calendar pulled three attendees off the signing invite. Lusha validated all three and then caught the thing that wasn’t on the invite at all — an active security event at the account that changes how this contract will get reviewed.
Who’s on the call (from the invite, validated by Lusha)
| Attendee | Verified title | Status |
|---|---|---|
| Brian R. | Chief Financial Officer | ✓ Signer validated — C-suite, authority fits a $480K deal, verified email and mobile on file |
| Keegan R. | SVP Sales Americas | ✓ Confirmed, same role and scope |
| Dwarak R. | VP and Head of AI Engineering and Research | ✓ Confirmed, title sharpened from earlier notes (“VP AI Engineering”) |
Everyone on the call checks out. The risk is what’s happening around the account.
The structural change Calendar couldn’t see
Active security incident at Snowflake — reported April 2026
Lusha’s signals layer surfaced a live security event — customers reported hit in data-theft attacks following a SaaS integrator breach (April 2026), alongside several investor class-action filings the same month. A live security incident is one of the changes most likely to re-route a vendor contract, because new agreements get pushed through a tighter, often newly-formalized security and procurement review.
Contract impact — a $480K, 24-month contract will almost certainly go through security review. With an active incident in the news cycle, that review is likely stricter than when the deal started. Walking into the signing call and pushing for ink today risks a 30-45 day extension while security signs off on the new path.
What to do with this on the call
Don’t push for signature today. Use the call to confirm the current review path — ask the room directly whether the deal still goes through the standard security review or a tightened one given recent events. If it’s tightened, agree the path on the call instead of discovering it after the contract is sent. You keep the momentum of the meeting without exposing the deal to a silent post-signature stall.
Signer and attendees confirmed live via the Lusha connector on May 21. Snowflake’s security and litigation signals pulled live from Lusha’s signals layer the same session.
Why use Lusha in Claude
A signing call is the highest-stakes meeting in the deal and the one you prep for least, because by then the deal feels done. The calendar invite tells you who’s coming. It tells you nothing about whether the signer’s authority still holds, whether someone’s role shifted, or whether the ground moved at the account while the deal sat in legal. This play reads the invite and answers all three before you join.
Calendar is the trigger, not the intelligence. It knows the meeting is happening and who’s on it — that’s the cue to run the check. Everything that makes the check worth running comes from Lusha: the verified titles, the seniority read against the contract value, the structural signals at the account. The meeting tool tells you when to look. Lusha tells you what’s true.
The validation is binary on every check. The signer is at the company or they aren’t. The title matches or it doesn’t. A real pre-call check doesn’t soften with “should be fine” — it confirms each fact or flags the gap. The most expensive moment to discover a problem is after the signature, and the cheapest is in the few minutes before the call. This play moves the discovery to the cheap moment.
The structural-change scan is the part the calendar can never give you. An active security incident, a new approval owner, an acquisition freeze — none of it shows up on a meeting invite, and all of it can re-route a signed contract into a 30-45 day stall. Lusha surfaces it from the signals layer so you walk into the signing call knowing not just who’s in the room, but what’s moving around the deal. That’s the layer the whole workflow stands on.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
Do I need both Lusha and Google Calendar connected?
Calendar makes it automatic — it finds the signing call and the attendees so you don’t type them in. With only Lusha connected the play still works, you’d just name the meeting and the people yourself. Lusha is the part that does the validation, Calendar is the trigger that saves you the setup.
How does it know which meeting is the signing call?
It looks for the contract-review or signing call you point it at, or the next external meeting that matches. If your calendar titles are vague, name the meeting in the prompt and it’ll pull the attendees from that specific invite. The validation is the same either way.
What if someone on the invite can't be verified?
They get flagged to confirm on the call rather than guessed at. An unverified attendee is honest information — it tells you which one person to clarify when you join, instead of walking in assuming a title that might be wrong.
How is this different from the Lusha-only pre-close play?
Same validation, different trigger. The Claude + Lusha pre-close play is run by hand when you describe the deal — best if you don’t use Calendar. This one runs off the signing call already on your calendar, so the check fires from the meeting itself. Pick the one that matches how you work.
Does it cover M&A and security events, or just people?
Both. The signals scan looks for structural changes at the account — executive moves in the approval chain, M&A as the acquired party, security incidents, reorganizations — alongside validating the people on the call. The structural change is usually the thing that re-routes a contract, and it’s the thing a calendar invite can never show you.
Can I run it the day before instead of right before the call?
Yes. Running it the evening before gives you time to act on a HOLD — make a clarifying touch before the meeting instead of raising it cold on the call. The data is pulled live when you run it, so a day-before check reflects the same verified state.
Ready to build this?
Get started with Lusha and set up this play in minutes.
