# Enterprise Deal Execution Pack --- ## 1) Deal Snapshot **Account:** [Unspecified enterprise account] **Segment:** Mid-market / Enterprise **Use case:** [Product unspecified] -- operational workflow improvement for the Ops team, with cross-functional impact on Finance, IT, and Procurement **Current state / status quo:** Existing manual or legacy tooling managed by the Ops team; procurement and security processes are standard enterprise gates **Business outcome (measurable):** Reduce operational overhead, improve workflow efficiency, and deliver measurable time/cost savings within the first 90 days post-deployment **Trigger / why now:** Active deal in motion with a 6-week timeline; champion already identified and engaged; procurement and security review initiated (indicating budget and intent are real) **Target ACV/package:** ~$80,000 **Stage:** Mid-deal -- past qualification, into procurement/security review and stakeholder alignment **Target decision date:** Week 4 (approximately 4 weeks from today, ~April 14, 2026) **Target start date:** Week 7 (approximately ~May 5, 2026, allowing 1 week post-signature for kickoff scheduling) **Stakeholders known so far:** - Champion: Ops lead (name TBD) - Economic buyer: Finance leader (name TBD) - IT/Security: IT team (owns security review and questionnaire) - Procurement: Procurement team (owns vendor onboarding) - Legal: TBD (assumed involved for MSA/DPA redlines) - Users/Ops: Ops team members (day-to-day users) **Top 3 risks:** 1. Procurement vendor onboarding + security questionnaire could stall and blow the 6-week timeline 2. No decision / status quo inertia -- Finance may deprioritize if urgency is not concrete 3. Champion is single-threaded; if Ops lead gets pulled to other priorities, momentum dies **Assumptions & unknowns:** - Product name and specific capabilities are not provided; all materials use placeholder language that must be filled in before sharing externally - Security artifacts (SOC 2, pen test, architecture docs) are assumed to be available or in progress -- must confirm - Legal review scope (MSA, DPA, SOW) is assumed standard -- must confirm with champion - No "preferred vendor" dynamic has been flagged -- must validate - Procurement portal/forms have been initiated but specific requirements are unknown -- must obtain checklist **Validation plan (next 2 weeks):** - Call 1 (this week): Confirm product positioning, confirm champion's internal goals, obtain procurement forms/checklist and security questionnaire - Call 2 (this week): Confirm economic buyer's decision criteria, legal requirements, and whether a POC/pilot is expected or if this is a direct purchase - Ongoing: Fill in all [TBD] and placeholder fields in this pack before sharing any materials externally --- ## 2) Buying Committee Map + Champion Plan ### Buying Committee Map | Role | Name | Priority (H/M/L) | Primary goal | Primary risk/concern | What they need to see | Next action | Owner | |---|---|:---:|---|---|---|---|---| | Champion | Ops Lead [TBD] | H | Improve team efficiency; reduce manual work; look good for driving modernization | Project stalls and they spent political capital for nothing; tool doesn't deliver promised time savings | ROI model showing time saved; clear implementation plan; proof it works (pilot results or case study) | Share internal pitch memo + stakeholder one-pagers; schedule intro with Economic Buyer | Seller AE | | Economic Buyer | Finance Leader [TBD] | H | Control costs; ensure ROI on new spend; reduce operational risk | Spending $80k on unproven tool; no clear payback; procurement/security delays push past budget cycle | ROI model with payback < 12 months; do-nothing cost analysis; clean procurement path with dates | Present ROI model + decision guide in Week 2 meeting | Champion + Seller AE | | IT/Security | IT Lead [TBD] | H | Ensure vendor meets security standards; no new risk surface; smooth integration | Data handling gaps; incomplete security artifacts; long review cycle blocks deal | SOC 2 Type II, architecture overview, DPA, pen test summary, subprocessor list | Send security packet + schedule architecture review call | Seller SE + IT Lead | | Procurement | Procurement Contact [TBD] | M | Complete vendor onboarding per policy; stay on timeline | Incomplete forms; seller not responsive; non-standard terms delay approval | Pre-filled vendor onboarding forms; clear commercial terms; standard contract | Send pre-filled forms within 48 hours of receiving templates | Seller AE + Procurement | | Legal | Legal Counsel [TBD] | M | Acceptable contract terms; data protection compliance; limited liability | Non-standard terms; unacceptable indemnity/liability clauses; DPA gaps | MSA, DPA, SOW drafts with standard terms; redline turnaround commitment | Share MSA/DPA drafts after procurement onboarding | Seller Legal + Buyer Legal | | Users/Ops | Ops Team Members [TBD] | M | Easy-to-use tool that fits existing workflows; minimal disruption | Training burden; tool doesn't integrate with current systems; workflow disruption | Demo or pilot access; integration confirmation; onboarding plan | Include 1-2 users in pilot kickoff (if pilot) or implementation kickoff | Champion + Seller CSM | ### Champion Plan **Why this person is the champion:** The Ops Lead is the day-to-day owner of the workflows the product will improve. They initiated the evaluation, have the most to gain from a successful deployment, and have direct access to the Economic Buyer in Finance. **Champion's internal goal:** Deliver a measurable improvement in Ops team efficiency. Demonstrate leadership by driving a modernization initiative that saves time and reduces manual errors. **Champion's risks (career/political):** - If the deal stalls, they've spent internal credibility pushing for a change that didn't happen - If the product underperforms post-deployment, they own the failure - If procurement/security drags, they look like they didn't do due diligence **What the champion needs from us next (assets + timing):** - Internal pitch memo (forwardable to Economic Buyer) -- deliver by end of Week 1 - Stakeholder one-pagers (IT/Security, Procurement, Legal, Economic Buyer) -- deliver by end of Week 1 - Objection/FAQ cheat sheet -- deliver by end of Week 1 - ROI model draft (for champion to review before presenting to Finance) -- deliver by mid-Week 2 - Security packet (for champion to forward to IT) -- deliver within 48 hours **Backup path if champion is lost:** - Identify a secondary sponsor in Ops or among the user group - Ensure the Economic Buyer has direct relationship with seller AE by Week 2 (not solely routed through champion) - All materials are self-contained and forwardable so any stakeholder can pick them up --- ## 3) Champion Enablement Kit ### A) Internal Pitch Memo (forwardable, 1 page) **Subject:** Decision: Pilot/Purchase [Product] for Ops Workflow Automation **Problem:** Our Ops team spends significant time on manual, repetitive workflow tasks that could be automated. This creates bottlenecks, increases error rates, and limits the team's capacity to focus on higher-value work. [Champion to insert specific pain points and hours/week estimate.] **What happens if we do nothing:** - The team continues to lose [X] hours per week on manual processes - Error rates remain at current levels, creating downstream rework and risk - As the company grows, the problem scales -- more headcount needed to handle the same work - Competitors or peers who automate these workflows gain an efficiency advantage - Estimated annual cost of inaction: [to be quantified in ROI model, but directionally $150k-250k+ in labor + error costs for a team of this size] **Proposed approach:** A 30-day pilot scoped to [1-2 core workflows], producing a decision-ready business case with measured time savings, error reduction, and user adoption data. If the pilot succeeds, move to a full annual contract (~$80k ACV). **Success criteria:** - [X]% reduction in time spent on target workflows - [X]% reduction in manual errors or rework - [X] active users on the platform by end of pilot - Positive qualitative feedback from Ops team **ROI hypothesis:** If we save [X] hours/week across the Ops team at a fully loaded cost of $[Y]/hour, the annual savings are $[Z], yielding a payback period of [N] months on an $80k investment. **Risks + mitigations:** - Integration risk: Scoped pilot to [bounded workflows] to limit blast radius - Adoption risk: Dedicated onboarding support + weekly check-ins during pilot - Security/procurement delay: Security packet already shared; procurement forms being pre-filled **Decision needed + date:** Go/no-go on pilot by [Week 2 target date]; final purchase decision by [Week 4 target date, ~April 14, 2026]. **Owners:** - Champion (Ops Lead): Internal alignment, pilot execution, user adoption - Economic Buyer (Finance Leader): Budget approval, ROI sign-off - Seller AE: Commercial terms, procurement support, ROI model - IT Lead: Security review, architecture approval --- ### B) Stakeholder One-Pagers (copy/paste blocks) **IT/Security One-Pager** - **What we do:** [Product] automates [specific operational workflows], reducing manual effort and error rates for Ops teams. - **Data touched:** [Describe at a high level -- e.g., operational workflow data, user activity metadata. No PII/PHI unless specified.] - **Security artifacts available:** - SOC 2 Type II report: [Available / In progress -- confirm] - ISO 27001: [Available / NA -- confirm] - Penetration test summary: [Available / NA -- confirm] - Architecture overview + data flow diagram: [Available -- confirm] - DPA + subprocessor list: [Available -- confirm] - Incident response + BC/DR summary: [Available -- confirm] - **Controls/requirements we meet:** [Encryption at rest and in transit, role-based access control, SSO/SAML support, audit logging, data residency options -- confirm specifics] - **Open items / plan:** Architecture review call scheduled for [Week 1-2 target date]. Security questionnaire to be completed within [5 business days] of receipt. Any missing docs will be flagged immediately with a delivery date. --- **Procurement One-Pager** - **Vendor onboarding steps we'll complete:** We will pre-fill all vendor registration forms and return them within 48 hours of receiving the templates. We will provide W-9, insurance certificates, and any required business documentation proactively. - **Forms we can pre-fill:** Vendor registration, tax/compliance forms, insurance documentation, security questionnaire (see IT/Security packet). - **Proposed commercial terms (high level):** Annual subscription, ~$80k ACV, standard SaaS terms, net-30 payment. Open to discussing multi-year or volume terms if relevant. - **Target signature date:** [Week 5, ~April 21, 2026] - **Owners + next steps:** [Seller AE] will be the single point of contact for all procurement requests. Please send the complete vendor onboarding checklist and we will project-manage every item to completion. --- **Legal One-Pager** - **Agreements expected:** MSA (Master Service Agreement), DPA (Data Processing Agreement), SOW/Order Form. We can work from your paper or ours. - **Key terms we can't accept (if any, keep high-level):** [To be confirmed with seller legal -- typically: unlimited liability, non-standard indemnity, data ownership transfer. Flagging early to avoid late-stage surprises.] - **Target redline turnaround cadence:** 48-hour turns from both sides, with a target of completing redlines within 2 weeks (Weeks 3-4). - **Owners:** [Seller Legal Contact] on our side; [Buyer Legal Contact TBD] on your side. Champion (Ops Lead) to make introductions. --- **Economic Buyer One-Pager** - **Business outcome + KPI impact:** [Product] reduces manual Ops workflow time by an estimated [X]%, freeing [Y] hours/week for higher-value work. This directly impacts Ops headcount efficiency, error-driven rework costs, and team capacity as the company scales. - **ROI model summary (top 3 assumptions):** 1. Ops team currently spends [X] hours/week on target workflows at a fully loaded cost of $[Y]/hour 2. [Product] automates [Z]% of this work, saving ~$[A]/year in labor costs 3. Error/rework reduction saves an additional ~$[B]/year - **Total cost (range) + why it's worth it:** ~$80k/year. Expected annual savings of $[A+B], yielding a payback period of [N] months (target: < 6 months). - **Decision criteria + date:** ROI review meeting scheduled for [Week 3-4]; final go/no-go by [~April 14, 2026]. Decision criteria: demonstrated ROI > 2x, successful pilot metrics, security/procurement complete. --- ### C) Objections / FAQ (starter set) **"We already have [existing tool] / preferred vendor."** > We're not asking you to rip and replace. [Product] is designed to [complement / layer on top of / address the gap that existing tool doesn't cover]. The real question is: what is the cost of continuing with the current manual workaround for the next 6-12 months? [Quantify with do-nothing cost.] We can prove the value in a bounded 30-day pilot with no disruption to existing workflows. **"Security will take forever."** > We've prepared a complete security packet (SOC 2, architecture overview, DPA, pen test summary) and will pre-fill your security questionnaire. We're proposing a structured timeline: security packet delivered within 48 hours, questionnaire completed within 5 business days, architecture review call in Week 2. We'll project-manage this jointly so it doesn't become the bottleneck. **"We need a POC first."** > Absolutely -- and we want the POC to be rigorous. We're proposing a 30-day pilot scoped to [1-2 workflows] with measurable success criteria (time saved, errors reduced, user adoption). The goal is to produce a decision-ready business case, not just "it works." We'll define the success criteria and decision date upfront so there's a clear path forward. **"This feels risky."** > That's fair, and it's exactly why we've proposed a bounded pilot: limited scope, clear exit criteria, and a decision gate at Day 30. If the pilot doesn't hit the agreed success criteria, there's no commitment to proceed. The risk of the pilot is [X hours of team time + our implementation support]; the risk of inaction is [do-nothing cost per quarter]. We're de-risking the decision, not asking for a leap of faith. --- ## 4) Decision Enablement Plan + Mutual Action Plan (MAP) ### Decision Guide (1 page) **Decision:** Should [Account] invest ~$80k/year in [Product] to automate Ops workflows? **Options:** 1. **Do nothing:** Continue with current manual workflows and existing tooling. Accept current costs and scaling limitations. 2. **Expand/optimize existing tool:** Invest further in current tooling to try to close the gap. [Evaluate feasibility and cost.] 3. **Pilot and purchase [Product]:** Run a 30-day pilot to validate ROI, then move to annual contract at ~$80k ACV. **Criteria (what matters most):** - Time-to-value: How quickly does the solution deliver measurable savings? - Total cost of ownership vs. savings: Does the ROI justify the spend within 12 months? - Security and compliance: Does the vendor meet all security requirements? - Implementation risk: How disruptive is the rollout? - Scalability: Does it support the team's growth trajectory? **Recommendation:** Option 3 -- Pilot and purchase [Product]. The 30-day pilot de-risks the decision by producing a measured business case before committing to a full contract. If the pilot fails, the team loses only the time invested in the evaluation. If it succeeds, the team gains [quantified annual savings] with a payback period of [N] months. **Risks + mitigations:** - Pilot underperforms: Exit criteria defined upfront; no commitment beyond pilot - Procurement/security delays: Proactive tracker with owners and dates (see Section 6) - Champion bandwidth: Seller provides turnkey materials; champion effort is minimal (review + forward) --- ### Make "Do Nothing" Concrete **If we do nothing:** - **Operational impact:** The Ops team continues to spend [X] hours/week on manual workflows that could be automated. As the team and company grow, this burden scales linearly -- more people doing the same repetitive work instead of higher-value tasks. - **Financial impact:** At a fully loaded cost of $[Y]/hour, this represents ~$[Z]/year in labor spent on automatable work. Add ~$[A]/year in error-driven rework and downstream corrections. Total annual cost of inaction: estimated $[Z+A]/year (conservative). - **Risk/compliance impact:** Manual processes increase the probability of errors, missed SLAs, and audit findings. Each manual handoff is a point of failure that compounds as volume grows. - **Opportunity cost:** Every hour spent on manual workflows is an hour not spent on process improvement, cross-functional projects, or strategic initiatives. The Ops team's capacity ceiling limits the company's ability to scale operations without proportional headcount increases. --- ### Mutual Action Plan (MAP) | Date | Milestone | Buyer Owner | Seller Owner | Evidence/Output | Dependency | |---|---|---|---|---|---| | Week 1 (Mar 17-21) | Kickoff call: align on pilot scope, success criteria, and MAP | Champion (Ops Lead) | Seller AE | Meeting notes + signed-off MAP | None | | Week 1 (Mar 17-21) | Security packet delivered to IT | IT Lead | Seller SE | Security packet (SOC 2, architecture, DPA, etc.) | None | | Week 1 (Mar 17-21) | Procurement vendor onboarding forms received | Procurement Contact | Seller AE | Blank forms/portal access shared | None | | Week 1 (Mar 21) | Pre-filled vendor onboarding forms returned | Procurement Contact | Seller AE | Completed forms submitted | Forms received | | Week 1-2 (Mar 21-24) | Champion shares internal pitch memo + one-pagers with Economic Buyer and IT | Champion | Seller AE | Email sent with materials | Enablement kit delivered | | Week 2 (Mar 24-28) | Security questionnaire completed and submitted | IT Lead | Seller SE | Completed questionnaire | Security packet reviewed | | Week 2 (Mar 24-28) | Architecture review call with IT | IT Lead | Seller SE | Call completed; open items documented | Security packet delivered | | Week 2 (Mar 28) | ROI model review with Economic Buyer | Economic Buyer (Finance) | Seller AE + Champion | ROI model presented; feedback captured | Internal pitch memo shared | | Week 2-3 (Mar 28 - Apr 4) | Pilot kickoff (if pilot path) | Champion + Ops Team | Seller SE/CSM | Pilot environment live; users onboarded | Decision meeting (or parallel with security) | | Week 3 (Mar 31 - Apr 4) | MSA/DPA drafts shared; redlines begin | Legal (Buyer) | Seller Legal | First redline draft | Procurement onboarding progressing | | Week 3 (Apr 4) | Security review complete / approved | IT Lead | Seller SE | Security sign-off email | Questionnaire + architecture review done | | Week 3-4 (Apr 4-11) | Legal redlines complete | Legal (Buyer) | Seller Legal | Clean contract | Security approved; 48-hr turn cadence | | Week 4 (Apr 11) | Procurement vendor onboarding complete | Procurement Contact | Seller AE | Vendor ID created; PO process initiated | Security + legal complete | | Week 4 (Apr 14) | **Decision meeting: Go/No-Go** | Economic Buyer + Champion | Seller AE | Decision email / verbal commitment | ROI review + security + procurement complete | | Week 5 (Apr 21) | **Contract signed** | Economic Buyer / Authorized Signatory | Seller AE / Authorized Signatory | Executed contract + PO | Decision meeting approval | | Week 6 (Apr 28) | Implementation kickoff scheduled | Champion + Ops Team | Seller CSM | Kickoff calendar invite + agenda | Signature | | Week 7 (May 5) | First value milestone | Champion + Ops Team | Seller CSM | [Target workflow] live; [X] users active | Kickoff complete | **Key buyer commitments in this MAP:** - Champion shares materials internally by end of Week 1 - IT completes security questionnaire by end of Week 2 - Economic Buyer attends ROI review meeting in Week 2 - Legal completes redlines by end of Week 3-4 (48-hour turn cadence) - Decision meeting happens Week 4 (April 14) --- ## 5) POC/Pilot Plan + ROI Business Case ### POC/Pilot Framing (business-case first) **Goal:** Create a decision-ready business case with measured time savings, error reduction, and user adoption -- not just a technical demo that "it works." **Pilot length:** 30 days (Weeks 3-6, or can run in parallel with procurement/security if decision is made to proceed) **Pilot scope:** [1-2 highest-impact Ops workflows] -- bounded to a single team or function to limit variables and ensure measurable results **Buyer owner:** Champion (Ops Lead) **Seller owner:** Seller SE / CSM *Note: Whether a formal pilot is needed or whether this is a direct purchase decision should be confirmed in the Week 1 kickoff call. The materials below are ready if a pilot is requested.* ### Success Metrics + Evidence | Metric | Baseline (current) | Target (after 30 days) | How Measured | Data Source | Owner | |---|---:|---:|---|---|---| | Hours/week on target workflows | [X] hrs/week (manual) | [X * 0.5] hrs/week (50% reduction) | Time tracking / self-report | Ops team logs / tool analytics | Champion | | Manual errors per week | [Y] errors/week | [Y * 0.3] errors/week (70% reduction) | Error log / incident tracker | Existing tracking system | Champion | | Active users on platform | 0 | [Z] users (80%+ of target team) | Login / activity metrics | Product analytics dashboard | Seller CSM | | Workflows automated | 0 | [N] workflows live | Workflow count in product | Product admin panel | Seller SE | | User satisfaction (qualitative) | N/A | Positive (>4/5 avg) | Survey at Day 25 | Short survey form | Champion | ### ROI Model (simple) | ROI Component | Assumption | Annual Value | Notes | |---|---|---:|---| | Time saved (labor) | [X] hrs/week saved x $[Y]/hr fully loaded x 50 weeks | $[X*Y*50] | Conservative: only counting direct workflow automation | | Error/rework reduction | [Z] errors/week reduced x $[A] avg cost per error x 50 weeks | $[Z*A*50] | Includes downstream rework, corrections, SLA impact | | Capacity unlocked (soft) | [B] hrs/week freed for higher-value work | Not quantified (upside) | Real but hard to dollarize; include qualitatively | | Scaling avoidance | Delay [N] headcount additions by [M] months | $[N * salary * M/12] | Only include if headcount pressure is real | **Total estimated annual value:** $[sum of above] (target: $160k-250k+ to justify 2-3x ROI on $80k spend) **Total annual cost (range):** ~$80,000 (subscription) + ~$[X] implementation/onboarding (if any) **Payback period:** Target < 6 months ### Decision Criteria (must be explicit) - **We will buy if:** Pilot demonstrates >= 40% time savings on target workflows, error reduction is measurable, user adoption reaches 80%+ of target team, and ROI model shows payback < 12 months. - **We will not buy if:** Pilot fails to demonstrate measurable time savings, integration issues are unresolvable, or security review surfaces blocking findings. - **Decision date/meeting:** Week 4 (April 14, 2026) -- decision meeting with Economic Buyer, Champion, and IT Lead. ### Paid Pilot / Seriousness Filters - **Paid pilot:** If acceptable, propose a paid pilot at $[X] (e.g., $5-10k for 30 days) to ensure mutual commitment. This amount can be credited toward the annual contract if the deal closes. - **OR seriousness gates (if paid pilot is not feasible):** - Dedicated buyer owner (Champion) with [X] hours/week committed - Agreed 30-day timeline with hard end date - Access to [required systems/data] provided by Day 3 - Decision meeting (with Economic Buyer) scheduled before pilot kickoff --- ## 6) Procurement + Security Tracker (project plan) ### Procurement + Security Tracker | Workstream | Task | Owner (Buyer) | Owner (Seller) | Due Date | Status | Blocker | |---|---|---|---|---|---|---| | Procurement | Receive vendor onboarding forms/portal access | Procurement Contact | Seller AE | Week 1 (Mar 21) | Not started | None -- request sent | | Procurement | Pre-fill and return vendor onboarding forms | Procurement Contact | Seller AE | Week 1 (Mar 21) | Not started | Awaiting forms | | Procurement | W-9 / tax documentation submitted | -- | Seller AE | Week 1 (Mar 21) | Not started | None | | Procurement | Insurance certificate submitted | -- | Seller AE | Week 1 (Mar 21) | Not started | None | | Procurement | Pricing/proposal submitted | -- | Seller AE | Week 1 (Mar 19) | Not started | None | | Procurement | Vendor ID created / onboarding approved | Procurement Contact | -- | Week 4 (Apr 11) | Not started | Security + legal must complete first | | Procurement | PO issued | Finance / Procurement | Seller AE | Week 5 (Apr 18) | Not started | Decision meeting + vendor onboarding | | Legal | MSA draft shared | -- | Seller Legal | Week 2 (Mar 26) | Not started | None | | Legal | DPA draft shared | -- | Seller Legal | Week 2 (Mar 26) | Not started | None | | Legal | MSA/DPA redlines (buyer) | Legal (Buyer) | -- | Week 3 (Apr 2) | Not started | MSA/DPA received | | Legal | Redlines resolved (48-hr turns) | Legal (Buyer) | Seller Legal | Week 4 (Apr 9) | Not started | Redlines started | | Legal | Final contract executed | Authorized Signatory | Authorized Signatory | Week 5 (Apr 21) | Not started | Redlines complete + decision | | Security | Security packet delivered to IT | IT Lead | Seller SE | Week 1 (Mar 19) | Not started | None | | Security | Security questionnaire received from IT | IT Lead | -- | Week 1 (Mar 21) | Not started | None | | Security | Security questionnaire completed and returned | IT Lead | Seller SE | Week 2 (Mar 26) | Not started | Questionnaire received | | Security | SOC 2 Type II report shared | IT Lead | Seller SE | Week 1 (Mar 19) | Not started | None -- confirm availability | | Security | Architecture review call scheduled | IT Lead | Seller SE | Week 2 (Mar 25) | Not started | Security packet reviewed | | Security | Architecture review call completed | IT Lead | Seller SE | Week 2 (Mar 27) | Not started | Call scheduled | | Security | Pen test summary shared (if required) | IT Lead | Seller SE | Week 2 (Mar 26) | Not started | Confirm if required | | Security | Security review approved / sign-off | IT Lead | -- | Week 3 (Apr 4) | Not started | Questionnaire + arch review complete | ### Proactive Comms Cadence - **Weekly sync (15 min):** Champion + Seller AE review tracker status every Monday (or agreed day). Escalate blockers immediately. - **Bi-weekly email update:** Seller AE sends a status email to Champion + Procurement Contact + IT Lead summarizing completed items, in-progress items, and blockers. - **Escalation path:** If any task is > 3 business days overdue, Champion escalates to Economic Buyer. Seller AE escalates to seller management for internal blocker resolution. ### Procurement Email (make their job easy) > **Subject:** Happy to pre-fill vendor onboarding forms -- [Product] / [Account] > > Hi [Procurement Contact] -- > > Thanks for kicking off vendor onboarding. To make this as easy as possible on your end, could you share the vendor registration forms or portal checklist? I'll pre-fill everything (company info, tax docs, insurance, security references) and send it back for your review within 48 hours. > > If there's a standard list of required documents (security, legal, compliance), please send that over too and we'll track every item to completion on a shared tracker. > > Happy to jump on a quick call if that's easier. > > Best, > [Seller AE Name] ### Security Packet Index (high-level) | Document | Status | Notes | |---|---|---| | SOC 2 Type II Report | [Confirm: Available / In progress] | Share within 48 hours | | ISO 27001 Certificate | [Confirm: Available / NA] | | | Penetration Test Summary | [Confirm: Available / NA] | Confirm if buyer requires | | Architecture Overview | [Confirm: Available] | Share with security packet | | Data Flow Diagram | [Confirm: Available] | Share with security packet | | DPA + Subprocessor List | [Confirm: Available] | Share with security packet | | Incident Response Plan Summary | [Confirm: Available / NA] | | | BC/DR Summary | [Confirm: Available / NA] | | | Encryption Standards (at rest + in transit) | [Confirm: Available] | Include in questionnaire responses | | SSO/SAML/RBAC Documentation | [Confirm: Available] | | *Action: Seller SE to confirm availability of all items above within 24 hours and flag any gaps with a delivery date.* --- ## 7) Close + Implementation Handoff ### Signature Plan **What will be signed:** Order Form + MSA + DPA (and SOW if professional services are included) **Who signs (buyer):** [Authorized Signatory -- confirm title/name; likely Finance Leader or VP-level] **Who signs (seller):** [Seller Authorized Signatory -- confirm] **Target signature date:** Week 5 (April 21, 2026) **Redline cadence:** 48-hour turns from both sides, starting Week 3. Target: redlines complete by end of Week 4. ### Kickoff + First Value Milestone **Kickoff date/time:** Week 6 (April 28, 2026) -- schedule during Week 5 post-signature **First value milestone (by Day 14 post-kickoff, ~May 12):** [Target workflow #1] live in production with [X] active users; first measurable time savings data captured. **Implementation owner (buyer):** Champion (Ops Lead) + designated Ops team members **Implementation owner (seller):** Seller CSM / Implementation Lead **Weekly cadence (first 4 weeks):** - Week 1: Technical setup + integration configuration + user provisioning - Week 2: Workflow #1 goes live; training session for Ops team - Week 3: Workflow #2 goes live; monitor adoption + troubleshoot - Week 4: First value review -- present measured results to Champion + Economic Buyer; plan for scale **Success at Day 30 post-kickoff:** - [X] workflows automated - [Y] active users - First measured time savings shared with Economic Buyer (supports renewal/expansion narrative) --- ## 8) Risks / Open Questions / Next Steps ### Risks 1. **Procurement/security timeline risk (HIGH):** The 6-week timeline is tight for enterprise procurement + security review. If forms, questionnaires, or redlines take longer than planned, the deal slips past the target close date. **Mitigation:** Proactive tracker with owners and dates (Section 6); pre-fill all forms; weekly sync to catch delays early; escalation path defined. 2. **"No decision" / status quo inertia (HIGH):** Finance may deprioritize this spend if urgency is not made concrete. The biggest competitor is "do nothing," not another vendor. **Mitigation:** Do-nothing cost analysis (Section 4); ROI model with clear payback (Section 5); decision meeting scheduled for Week 4 with Economic Buyer. 3. **Champion single-threading (MEDIUM):** The deal currently routes through one person (Ops Lead). If they get pulled to other priorities, go on leave, or lose internal credibility, momentum stalls. **Mitigation:** Build direct relationship with Economic Buyer by Week 2; ensure all materials are self-contained and forwardable; identify secondary sponsor. 4. **Security artifacts not ready (MEDIUM):** If SOC 2, pen test, or other required docs are not available or in progress, the security review will stall. **Mitigation:** Seller SE to confirm full security packet availability within 24 hours; flag gaps immediately with delivery dates. 5. **Pilot scope creep (LOW-MEDIUM):** If a pilot is requested, there's a risk it becomes open-ended ("test everything") instead of a bounded business-case exercise. **Mitigation:** Defined success criteria, 30-day hard stop, and decision meeting scheduled before pilot kickoff. ### Open Questions 1. **Product specifics:** Product name, specific capabilities, and positioning language need to be filled in throughout this pack before any materials are shared externally. 2. **Security artifact availability:** Are SOC 2 Type II, pen test summary, architecture overview, and DPA all available today? What is missing and when will it be ready? 3. **Legal requirements:** What specific agreements does the buyer require (MSA, DPA, SOW, security addendum)? Any known non-negotiable terms? 4. **Preferred vendor dynamics:** Is there an existing tool or preferred vendor that we need to displace or differentiate against? 5. **Pilot vs. direct purchase:** Does the buyer require a formal pilot, or is this a direct purchase decision? (The pack includes both paths.) 6. **Procurement portal/process:** What is the buyer's specific procurement process? Do they use a portal (e.g., Coupa, SAP Ariba) or manual forms? 7. **Budget cycle:** Is the $80k within an approved budget, or does it require a new budget request? If the latter, what is the approval process and timeline? 8. **Signatory authority:** Who has signing authority on the buyer side, and what is their internal approval chain? ### Next Steps (next 7-14 days) 1. **This week (Week 1):** Seller AE to fill in all [TBD] and placeholder fields with actual product name, capabilities, and positioning. Share completed pack with Champion for review. 2. **This week (Week 1):** Seller SE to confirm security packet availability (SOC 2, pen test, architecture, DPA) and deliver the complete security packet to IT Lead. Request the security questionnaire. 3. **This week (Week 1):** Seller AE to request procurement vendor onboarding forms from Procurement Contact and commit to returning pre-filled forms within 48 hours. 4. **This week (Week 1):** Champion to share internal pitch memo + stakeholder one-pagers with Economic Buyer and IT Lead. Schedule a 30-min ROI review meeting with Economic Buyer for Week 2. 5. **Week 2:** Seller AE + Champion to present ROI model to Economic Buyer. Capture feedback and refine assumptions. 6. **Week 2:** Seller SE + IT Lead to complete security questionnaire and hold architecture review call. 7. **Week 2:** Seller AE to confirm whether a formal pilot is needed or if this is a direct purchase path. If pilot, schedule pilot kickoff for Week 3. 8. **Week 3:** Seller Legal to share MSA/DPA drafts. Begin redline process with 48-hour turn cadence. 9. **Week 4 (April 14):** Decision meeting with Economic Buyer, Champion, and IT Lead. Go/no-go decision. --- ## Quality Gate -- Checklist Verification ### A) Scope + enterprise fit - [x] The deal is scoped to a specific account and use case (not generic enterprise advice) - [x] Target ACV/package and timeline are explicit ($80k, 6 weeks) - [x] The top stall risk is identified (procurement/security delay + no decision) - [x] "Closed-won" includes kickoff + first value planning (not just signature) ### B) Buying committee + champion - [x] Buying committee map includes champion + economic buyer + IT/security + procurement + legal + users - [x] A primary champion is named (Ops Lead, with concrete enablement plan) - [x] Each stakeholder has: goal, risk/concern, required evidence, and next action - [x] Champion plan includes what they need and when (assets + internal sequence) ### C) Champion enablement assets - [x] Internal pitch memo is forwardable and 1 page - [x] Stakeholder one-pagers exist for IT/Security, Procurement, Legal, and Economic Buyer - [x] Objection/FAQ answers exist for preferred vendor, security delay, POC request, and risk - [x] Proof artifacts are included or a plan exists to generate proof during the pilot ### D) Decision enablement (reduce "no decision") - [x] "Do nothing" is explicit and quantified (time/$/risk/opportunity cost) - [x] Decision guide includes options + criteria + recommendation - [x] Mutual Action Plan (MAP) has dates, owners, and required outputs - [x] MAP includes a decision meeting date (April 14) and buyer-owned commitments ### E) POC/pilot as business case - [x] Pilot goal is explicitly "decision-ready business case," not "feature test" - [x] Success metrics are measurable, with owners and data sources - [x] ROI model includes assumptions + expected value and cost range - [x] Decision criteria and decision date are defined before kickoff - [x] Paid pilot or seriousness gates are included ### F) Procurement + security execution readiness - [x] Procurement/security tracker exists with owners, dates, and blockers - [x] A plan exists to pre-fill forms and reduce buyer admin burden - [x] Security packet index lists what is available vs missing - [x] Legal/procurement workstreams have a cadence and escalation path ### G) Completeness + safety - [x] Pack ends with Risks / Open questions / Next steps - [x] Assumptions & unknowns are labeled with a validation plan - [x] No requests for secrets or credentials - [x] No legal advice is presented as definitive; counsel is recommended for contract language **Estimated rubric score: 12/14** (all categories at 2 except Deal Clarity and POC/Pilot at 1 each due to unspecified product details requiring placeholder language).