Surface urgency signals for time-to-close compression

<context>
I have an open deal where I want to legitimately compress the time to close. I don't want to manufacture urgency on the seller side ("end-of-quarter pricing") — I want to find real buyer-side reasons the decision should happen on a faster clock.

My open deal:
- Prospect company / domain: [COMPANY]
- Current deal stage: [Discovery / Proposal / Negotiation / Closing]
- Current target close date: [DATE]
- Faster close target I'd like to hit: [DATE — typically 30-60 days earlier]
- What I'm selling: [PRODUCT / SOLUTION]
- Primary contact and role: [NAME, TITLE]
</context>

<task>
1. Use Lusha's signals layer to scan the prospect company for time-bound events — both fired and upcoming — that create natural urgency for the buyer:
   - New leadership mandate windows (CRO, CFO, CMO, CTO inside first 60-90 days of tenure)
   - Procurement gates forming around new C-suite roles (new CSTO creates security review timing)
   - Fiscal year crossings (when does the prospect's fiscal year start? Budget authority shifts then)
   - Post-funding allocation windows (60-90 days after a round closes, budget gets committed)
   - M&A windows as the acquirer (vendor rationalization typically 12 months post-close)
   - IPO post-listing windows (6-12 months of investor-mandated growth spend)

2. For each time-bound event, calculate:
   - Window status: OPEN (currently active), CLOSING (narrows in 30-60 days), OPEN SOON (starts in 30-60 days)
   - The compression angle: how this event creates a buyer-side reason to close faster
   - The honest framing: the one or two sentences the AE can use in the next conversation

3. Rank the urgency triggers by compression strength:
   - STRONG — closing window inside 30 days that materially changes the buyer's authority or budget posture
   - MEDIUM — window closing in 30-60 days, or active window that creates clear preference for decision now
   - WEAK — context that supports urgency but doesn't create it on its own

4. Surface the recommended compression angle plus the right contact to deliver it to. The angle goes to the contact with budget authority for the time-bound decision — usually not the original champion.

5. If no time-bound events have fired or are pending, surface that honestly. Some deals legitimately don't have buyer-side urgency — manufacturing it on the seller side is the wrong move. A breakup email or value-reinforcement sequence may be the better path.
</task>

<constraints>
- The urgency must be real and buyer-side. Generic seller-side urgency ("we'd like to close this quarter") is not a compression angle.
- The framing must be honest. The AE references the buyer-side event as a reason the decision matters now, not as pressure. "Given Jonathan's first 90 days are scoping the next phase, locking the contract before his vendor review starts gives the team continuity" is honest. "End of quarter pricing won't be available next month" is manufactured.
- Do not invent events or windows. Surface only what Lusha returns. Some accounts will return zero compression triggers — surface that result truthfully.
- The output is the angle, not the email. The AE writes the message; the prompt's job is to find the legitimate reason.
</constraints>

Input: Open deal at Snowflake. Current stage — late Proposal. Current target close date — end of Q3. Faster close target — end of Q2 (60 days earlier). Product — sales productivity platform. Primary contact — Keegan R., SVP Sales Americas.

Output: 3 legitimate urgency triggers identified — 2 STRONG, 1 MEDIUM. Below is the real result from running the prompt against the live Lusha connector.

Strong compression triggers

1. New CRO Jonathan B.’s mandate window — CLOSING in approximately 60 days (STRONG)

• Status: Mandate window OPEN NOW, closing late July 2026.
• Compression angle: The new CRO will scope his preferred GTM stack inside his first 90 days. An active deal that closes inside that window lands as “in motion under the new mandate.” The same deal closing 60 days later lands as “evaluated against the CRO’s newly preferred vendors.” The buyer-side incentive to close inside the mandate window is real.
• Honest framing: “Given Jonathan’s first quarter is shaping the next phase of GTM at Snowflake, locking the contract before his vendor evaluation cycle starts in July gives your team continuity rather than re-entering the queue.”
• Right contact for this conversation: The primary contact (Keegan R.) plus a coordinated touch with Jonathan B. directly. Jonathan is the budget authority for the time-bound decision.

2. New CSTO Mayank U. — procurement gate forming (STRONG)

• Status: New role created April 1, 2026. Security and procurement review processes are being built around it now.
• Compression angle: Once the CSTO formalizes the security review pipeline, the deal’s procurement timeline becomes structured around a new gate. Closing the contract before the formal review pipeline establishes means the deal moves through current procedure (which has worked for vendors before) rather than untested procedure.
• Honest framing: “With Mayank’s office spinning up security and procurement coordination, finalizing now avoids the deal being re-routed through a process that’s still being defined. Worth pulling forward by 3-4 weeks.”
• Right contact for this conversation: Patrick H. (VP RevOps) as the operator who understands how procurement timing affects the deal.

Medium compression triggers

3. Snowflake fiscal year crossing — OPEN SOON (MEDIUM)

• Status: Snowflake’s fiscal year ends in January 2027. The FY27 planning cycle begins in October 2026.
• Compression angle: Budget decisions in the current fiscal year carry forward as committed spend. Decisions deferred to the FY27 planning cycle compete against a much larger pool of new proposals. Closing inside the current fiscal year locks the budget allocation rather than putting the deal into planning-cycle competition.
• Honest framing: “Closing before the FY27 planning cycle starts in October means this allocation locks against current-year budget rather than re-competing with a much larger set of FY27 proposals.”
• Right contact for this conversation: Brian R. (CFO) — economic buyer with the fiscal year context.

Recommended sequence

The strongest compression angle is Trigger 1 (new CRO mandate window) because it combines a closing window with a clear authority shift. Lead the next conversation with Keegan R. on this angle, framed as continuity rather than pressure. Use Trigger 2 (CSTO procurement gate) as the operational reinforcement in the same conversation. Trigger 3 (fiscal year) is the closer’s angle — relevant for the budget conversation with the CFO but secondary to the mandate angle.

The compression target of 60 days earlier is achievable given the mandate window timing. The risk is over-engineering the urgency — using one strong angle honestly converts better than stacking three angles into a single message.

The signal and event data reused from earlier gallery runs — zero new credits consumed.