Surface the post-event budget window

<context>
I want to know when my existing customer's budget reopens for new vendor commitments — the structural moments inside the next 6-12 months when expansion proposals will land inside an active budget window, not outside it.

My customer:
- Customer name / domain: [CUSTOMER]
- My current contract scope and renewal date: [SCOPE + DATE]
- The expansion I want to propose: [ADDITIONAL SEATS / NEW REGION / CROSS-SELL PRODUCT]
</context>

<task>
1. Use Lusha's signals layer to scan the customer's last 12 months and surface the structural events that create budget windows:
   - Funding rounds (round size and date — budget allocation typically lands 60-90 days post-close)
   - IPO events (newly public companies typically have 6-12 months of investor-mandated growth spending)
   - M&A as the acquirer (acquired entities get vendor-rationalized within 12 months post-close)
   - Executive hires in the buying group (CRO, CFO, CMO, CTO — new leaders scope mandates inside their first 60-90 days)
   - Executive departures (creates a transition window where committed budget is uncertain — avoid this window for expansion)

2. For each event, calculate the budget window:
   - Open date: when the budget conversation becomes possible
   - Peak window: when budget allocation decisions are actively being made
   - Close date: when the window narrows back to normal procurement cycles

3. Cross-reference with the customer's likely fiscal year structure (most major public companies follow calendar year; many private SaaS companies follow Feb-Jan or Apr-Mar fiscal years). Surface the next fiscal year boundary and what it means for budget timing.

4. Output a budget calendar:
   Event | Window opens | Peak window | Window closes | Status | Recommended action

5. Assign a status per window:
   - OPEN NOW — window is currently active, propose this month
   - OPENING SOON — window opens in the next 30-60 days, prepare proposal
   - CLOSED — window has passed
   - HOLD — transition or risk event makes this window unsuitable for expansion

6. At the bottom, list the 2-3 highest-value windows to act on this quarter.
</task>

<constraints>
- A budget window is structural — it's created by a specific event. Generic "next quarter would be a good time" is not a window.
- Different windows have different durations. A new CRO mandate window is 60-90 days. A post-funding window is 90-180 days. An IPO window is 6-12 months.
- Executive departures create HOLD windows — budget authority is in flux until the successor settles in. Do not propose expansion inside a HOLD window.
- Do not invent events or windows. Surface only what Lusha returns.
</constraints>

Input: Customer — MongoDB. Current contract scope — sales productivity tooling for the corporate sales vertical. Renewal date — Q4. Expansion proposed — extend to the EMEA team plus a cross-sell to the marketing intelligence product line.

Output: 4 distinct budget windows surfaced over the next 12 months. 1 OPEN NOW, 1 OPENING SOON, 1 CLOSED (informational), 1 HOLD. Below is the real result from running the prompt against the live Lusha connector.

Detailed read

OPEN NOW — Incoming CRO mandate window Ryan Mac Ban starts as Chief Revenue Officer on April 27, 2026, hired to “support next phase of growth.” A new CRO has approximately 60-90 days to scope budget priorities for the GTM stack. The window is materially open from late April through July 2026. Past mid-July, the new CRO’s stack decisions start to lock and procurement enters execution mode for the new fiscal year.

Recommended action: Schedule a pre-empt briefing with the incoming CRO in May or early June. Position the existing engagement’s impact metrics and frame the EMEA expansion as the natural scope extension of the proven US deployment. Wait past July and the EMEA decision gets evaluated against newly preferred vendors, not the existing one.

OPENING SOON — Next fiscal year planning cycle MongoDB’s fiscal year ends in January, so the FY27 planning cycle starts in October 2026 and concludes by year-end. This is the structural budget moment for annual contract scope discussions and cross-sell evaluations that don’t fit inside a smaller mid-year mandate.

Recommended action: The marketing intelligence cross-sell is best timed for the October-December planning cycle. It’s a larger, multi-stakeholder decision than the EMEA expansion and benefits from sitting inside the formal budget planning rather than a mid-cycle ask.

CLOSED (informational) — Fiscal year and CEO transition windows Two budget windows have already passed but are worth knowing about for context. The fiscal year crossover ran Feb-Apr 2026 — the moment major contract decisions for the current fiscal year were being made. The CEO transition window (Dev Ittycheria stepping down November 2025, CJ Desai succeeding) created a 3-month period where committed budget was being re-evaluated. Both windows are closed; their outcomes have shaped the current procurement posture.

Two highest-value windows to act on this quarter

1. Incoming CRO mandate (OPEN NOW through late July) — propose the EMEA expansion within the next 45 days. The window narrows fast.
2. FY27 planning cycle (OPENS October) — prepare the marketing intelligence cross-sell brief now; deliver in late September for inclusion in the planning cycle.

The signal data and event dates reuse the buying signal scans already verified earlier in the gallery. Zero additional credits consumed.