Check whether the proposal addresses what the prospect asked for

<context>
I'm about to send a proposal. Before it goes out, I want to check whether it actually addresses everything the prospect asked for, raised as a concern, or was promised during the sales process. I don't want the prospect to reply pointing out something I missed.

My proposal:
- Prospect name and company: [NAME, COMPANY]
- Proposal doc: [GOOGLE DRIVE LINK OR "SEARCH DRIVE FOR LATEST PROPOSAL FOR [COMPANY]"]
- Thread to check against: [GMAIL THREAD SUBJECT OR "CHECK GMAIL FOR ALL THREADS WITH [COMPANY]"]
- What I sell: [PRODUCT / SOLUTION]
</context>

<task>
1. Search Gmail for all threads with this prospect and company:
   - Every specific question the prospect asked that needs to be answered
   - Every concern or objection raised — even if addressed verbally on a call
   - Every commitment made by the rep — "I'll include X in the proposal", "we'll show Y pricing"
   - Any competitor mentioned that should be addressed
   - Any specific technical requirement stated

2. Pull the proposal from Google Drive:
   - Read the full document
   - Identify all sections and what each one covers

3. Cross-reference thread against proposal:
   For each item extracted from Gmail, check whether the proposal addresses it:
   - COVERED: the proposal addresses this clearly
   - PARTIAL: the proposal mentions it but doesn't fully address it
   - MISSING: the proposal does not address this at all

4. Return a pre-send gap report:
   - COVERED items: brief confirmation — no action needed
   - PARTIAL items: what's missing from the section and suggested addition
   - MISSING items: what needs to be added before sending, with suggested language

5. Overall verdict:
   - READY TO SEND: all items covered or minor partials only
   - NEEDS UPDATES: specific gaps that should be fixed before sending
   - DO NOT SEND: critical item missing that would likely cause the prospect to reject or question the proposal immediately

6. Use Lusha to confirm the send-to contact is still at the company in the same role before anything goes out.
</task>

<constraints>
- Every MISSING item must have a specific suggested addition — not just "add a section about X."
- If a concern was raised on a call but not in email: flag that it may be in the proposal already since it was discussed verbally. Don't assume it's missing.
- DO NOT SEND is reserved for critical omissions — a missing pricing section, a missing integration the prospect specifically required, a missing term they said was a dealbreaker.
- Under no circumstances send the proposal if Lusha shows the contact has left the company.
</constraints>

The situation: An AE has a proposal ready to send to D.R. at Ashford Platforms. The deal has been through two discovery calls and multiple email threads. Running the pre-send check before hitting send.

Items extracted from Gmail threads

1. D.R. asked: “Does this integrate natively with HubSpot?”
2. D.R. asked: “Can you show a pricing breakdown by user tier?”
3. Rep committed: “I’ll include a Z***I*** comparison section since you mentioned evaluating them.”
4. D.R. raised: “Our legal team will need to review the data processing terms before we sign.”
5. D.R. stated: “GDPR compliance is a hard requirement — we have EU customers.”

Gap report

✅ COVERED — GDPR compliance: Section 4 of the proposal covers data processing, EU data residency, and includes the GDPR certification link. Fully addressed. — HubSpot integration: Section 3 confirms native HubSpot integration with connector documentation referenced. Covered.

⚠ PARTIAL — Pricing by user tier: Section 5 includes pricing but shows only the standard tier. D.R. specifically asked for a tier breakdown. Add a table showing the per-user price at 50, 100, and 200+ seat levels before sending.

❌ MISSING — Z***I*** comparison: The rep committed to including this. No competitive section appears in the proposal. Suggested addition: “Add a one-page comparison table to the appendix covering data coverage, verification methodology, and pricing. Reference: ‘We evaluated Z***I*** and chose Lusha for X, Y, Z.'” — Data processing terms for legal review: The proposal doesn’t include or link to the DPA (Data Processing Agreement). D.R. flagged the legal team needs to review this before signing. Suggested addition: “Add a line in Section 6: ‘A Data Processing Agreement is available for review at [link]. Our legal team is available to schedule a review call with your team.'”

Verdict: NEEDS UPDATES

Two items must be addressed before sending: the pricing tier breakdown and the missing Z***I*** comparison section. The legal/DPA gap is the most critical — D.R. flagged it as a pre-sign requirement and the proposal currently gives the legal team nothing to review.

Contact status (Lusha): D.R., Head of Sales Strategy and Operations, Ashford Platforms ✓ — confirmed, same role. Safe to send once updates are made.

Illustrative example — fictional company names used. Run with your own proposal and thread data to see live results.