Archives: Documents

Client Onboarding Experience Journey

Goal

Make the client feel confident, informed, and excited from the moment they sign the deal until delivery execution begins — turning handoff into a seamless partnership experience.

Phase 1: The Warm Handoff

  • Trigger: Deal signed in CRM.
  • Actions:
    • Sales sends a warm thank-you note + “what’s next” outline.
    • Sales → Delivery Handoff Call scheduled internally.
    • Handoff Pack prepared (Discovery notes, MEDDPICC, Proposal, Scope, Key Contacts).
  • Client Experience: Feels valued and reassured → “They know me, I’m not starting over.”

Phase 2: Kickoff Preparation (Internal)

  • Trigger: Internal sync after contract.
  • Actions:
    • Delivery Manager reviews scope, timeline, and resources.
    • Pre-Sales (if needed) validates technical commitments.
    • CRM opportunity migrated to Project Tool (tasks, milestones, owner assignment).
  • Client Experience: They don’t see this yet — but internally, we’re making sure everything is ready before facing them.

Phase 3: Client Onboarding Meeting (Kickoff)

  • Trigger: Client kickoff scheduled (within 5 working days of signing).
  • Agenda:
    • Welcome & introductions (Delivery Team meets Client Team).
    • Recap of client goals, challenges, and agreed scope.
    • Walkthrough of delivery plan, milestones, and collaboration tools.
    • Communication norms (Slack/email cadence, escalation paths).
    • Open Q&A to align expectations.
  • Client Experience: Confidence boost → “These people are structured, professional, and invested in our success.”

Phase 4: Post-Kickoff Communication

  • Trigger: Immediately after kickoff.
  • Actions:
    • Send Kickoff Summary Email (meeting notes, timeline, responsibilities).
    • Share access to collaboration tools (Slack channel, project dashboard, shared folders).
    • Introduce Client Success/Account Manager as ongoing point of contact.
  • Client Experience: Smooth start → “I know who to talk to, I can see progress already.”

Phase 5: Scope Confirmation & Lock-In

  • Trigger: After kickoff & alignment.
  • Actions:
    • Delivery validates final scope document.
    • Client signs off on confirmed scope (no ambiguity).
    • Any change requests moved into Change Control process.
  • Client Experience: Trust → “We’re all on the same page; no surprises ahead.”

Phase 6: Transition to Project Execution

  • Trigger: Scope confirmed + tools ready.
  • Actions:
    • CRM opportunity officially closed → Project Tool becomes system of record.
    • Delivery takes full ownership.
    • Sales role shifts to relationship support (check-ins, upsell/cross-sell).
  • Client Experience: Reassurance → “This project is in capable hands; the journey has begun.”

Client Journey Snapshot

Sales Closure → Warm Handoff → Kickoff Prep → Client Kickoff → Post-Kickoff Communication → Scope Confirmation → Project Execution Transition.

How-To: Presenting Case Studies

Purpose

To guide Sales Representatives and Pre-Sales Consultants in presenting case studies effectively during client conversations, ensuring they are relevant, persuasive, and aligned with client pain points.

Step-by-Step Instructions

  1. Select the Right Case Study
    • Access the Case Study Repository.
    • Choose based on:
      • Industry relevance (e.g., fintech, healthtech, SaaS).
      • Similar challenge (e.g., scaling infra, reducing costs).
      • Deal size alignment (SMB vs. enterprise).
  2. Prepare Before Meeting
    • Review the full case study (not just highlights).
    • Extract 2–3 key metrics (ROI, cost savings, user growth).
    • Practice summarizing in 60–90 seconds.
  3. Presentation in Conversation
    • Introduce Context: “A client in your industry faced a similar challenge…”
    • Highlight Challenge: Frame the pain point clearly.
    • Explain Solution: Summarize how we solved it (focus on outcomes, not deep technical detail).
    • Show Results: Quantify results wherever possible.
    • Optional Visual: Open relevant slide from Master Deck (see How-To: Using Master Deck).
  4. Engage the Prospect
    • Pause and ask: “Does this sound similar to what you’re experiencing?”
    • Use client’s response to transition back to their specific problem.
  5. Avoid Common Pitfalls
    • Do not overwhelm with too many case studies at once.
    • Do not share client names/logos without approval.
    • Do not exaggerate metrics beyond verified outcomes.
  6. After the Meeting
    • Send PDF or one-pager only if approved for external sharing.
    • Upload version shared in CRM notes.
    • Update opportunity with “Case Study Presented” activity.

Example Scenario

  • Client: SaaS startup with AWS cost concerns.
  • Case Study Presented: Retail SaaS migration with 25% infra savings and 30% faster deployments.
  • Outcome: Prospect validated similarity and agreed to move forward with proposal stage.

How-To: Sharing Proposals Securely

Purpose

To guide Sales Representatives on how to share proposals with clients in a secure, professional, and trackable way — ensuring confidentiality, version control, and compliance.

Step-by-Step Instructions

  1. Finalize Proposal
    • Ensure proposal is approved as per Proposal Creation & Approval SOP.
    • Save as PDF → ClientName – Proposal – vX – Date.
    • Store editable file in Repository → Proposals folder.
  2. Choose Secure Sharing Method
    • Email (Preferred for SMB/SMEs)
      • Send PDF as attachment.
      • Use professional email template with cover note.
    • Secure Link (Preferred for Mid-Market/Enterprise)
      • Upload PDF to secure storage (SharePoint, Drive, or CRM Doc Send).
      • Set permissions: View Only → disable download/edit unless approved.
      • Add password or expiry if deal sensitivity is high.
  3. void Risky Methods
    • Do not share editable files (PPTX, DOCX) unless explicitly requested.
    • Do not use personal cloud storage (e.g., personal Google Drive/Dropbox).
    • Do not send via unsecured messaging apps.
  4. Enable Tracking (If Tools Available)
    • Use CRM-integrated document sharing (HubSpot, Zoho, Salesforce).
    • Enable notifications for when proposal is opened/viewed.
    • Record client activity in CRM notes.
  5. Client Communication
    • Email subject line: “[ClientName] – Proposal for [Service/Project]”.
    • Cover note should:
      • Thank client for their time.
      • Summarize key highlights (problem → solution → outcomes).
      • Mention proposal validity period.
      • Suggest next-step meeting for review.
  6. Post-Sharing Action
    • Update Commercial Proposal Tracker with submission date.
    • Log “Proposal Sent” activity in CRM.
    • Schedule follow-up within 3–5 business days.

Example

  • Scenario: Proposal sent to ABC Fintech (USD 120,000 Cloud Migration project).
  • Method: Shared via CRM DocSend with view tracking enabled, expiry set to 14 days.
  • Outcome: Client opened proposal 3 times in 48 hours → follow-up call booked.

SOP: Repository Maintenance

1. Purpose

The purpose of this SOP is to ensure that all sales enablement assets (proposals, case studies, decks, brochures, trackers) are stored, organized, and maintained in a central repository for easy access, version control, and compliance.

2. Scope

This SOP applies to:

  • All Sales, Pre-Sales, Delivery, and Marketing assets used in the sales cycle.
  • Sales Ops and Marketing teams responsible for managing repository structure.
  • Sales Representatives and Managers accessing or contributing to repository content.

3. Definitions

  • Repository: Central digital library (SharePoint, Google Drive, CRM, or DAM system) for storing approved sales assets.
  • Version Control: Process of maintaining the latest version of assets while archiving outdated ones.
  • Tagging/Indexing: Categorization of assets for easy retrieval by type, industry, or use case.

4. Step-by-Step Process

A. Repository Structure

  1. Repository must be organized into top-level folders:
    • Proposals (templates, approved proposals)
    • Case Studies
    • Decks & Presentations (Master Decks, Custom Decks)
    • Brochures & One-Pagers
    • Trackers & Templates
    • Archived Assets
  2. Each folder must have a README/index file explaining usage.

B. Upload & Tagging

  1. All new/updated assets uploaded within 48 hours of approval.
  2. Naming convention:
    • AssetType – Client/Use Case – Version – Date
    • Example: “CaseStudy – ABCFintech – v2 – Aug2025”.
  3. Tag asset with:
    • Industry (e.g., Fintech, Healthtech)
    • Asset Type (Case Study, Deck, Template)
    • Owner/Creator

C. Version Control

  1. Outdated assets moved to Archived Assets folder.
  2. Latest version clearly labeled “Final” or “Approved”.
  3. Maintain changelog file for significant updates (date, owner, summary of change).

D. Access & Permissions

  1. All Sales & Pre-Sales staff have read-only access to repository.
  2. Only Marketing & Sales Ops may upload/edit/delete.
  3. Delivery Managers may contribute drafts, subject to Marketing approval.
  4. Permissions reviewed quarterly.

E. Periodic Maintenance

  1. Sales Ops conducts monthly check:
    • Remove duplicates.
    • Archive outdated material.
    • Validate file naming compliance.
  2. Quarterly review with Head of Sales & Marketing to refresh core templates and decks.

5. Roles & Responsibilities

  • Sales Ops: Maintains repository structure, version control, tagging.
  • Marketing: Approves design/branding of assets, ensures repository hygiene.
  • Sales Rep: Uses only approved assets; requests updates via Asset Request SOP.
  • Delivery Manager: Provides input for technical accuracy of assets.
  • Head of Sales/Marketing: Provides oversight and governance.

6. Governance, Violations & Consequences

  • Uploading assets without approval → immediate deletion + warning.
  • Using outdated/archived assets → non-compliance, flagged in performance review.
  • Repository left unmanaged → escalated to Head of Sales/Marketing.

7. Review & Ownership

  • Document Owner: Sales Ops Lead.
  • Review Cycle: Monthly hygiene check; quarterly strategic review.
  • Version Control: Repository index maintained by Sales Ops.

SOP: Sales Asset Request

1. Purpose

The purpose of this SOP is to define a standardized process for requesting new or updated sales assets (e.g., case studies, decks, brochures, one-pagers). This ensures requests are tracked, prioritized, fulfilled on time, and aligned with branding and sales needs.

2. Scope

This SOP applies to:

  • All Sales, Pre-Sales, and Delivery team members requesting sales collateral.
  • Marketing and Sales Ops teams responsible for developing and maintaining assets.
  • Sales assets used in proposals, demos, outreach campaigns, and repositories.

3. Definitions

  • Sales Asset: Any collateral used in the sales process (case studies, proposal templates, master decks, brochures, videos).
  • Request Portal: Defined channel (form, CRM, or ticketing tool) through which requests are submitted.
  • Asset Repository: Central library where all approved and updated assets are stored.

4. Step-by-Step Process

A. Submitting a Request

  1. Submit asset request through official channel:
    • Asset Request Form (preferred) OR
    • CRM/Project tool ticket (if integrated).
  2. Fill mandatory fields:
    • Requester Name & Role
    • Asset Type (deck, case study, brochure, etc.)
    • Purpose/Use Case (e.g., upcoming proposal, demo, campaign)
    • Deadline/Expected Date
    • Special Notes (branding, industry, customization required)

B. Request Review & Prioritization

  1. Sales Ops/Marketing reviews requests weekly.
  2. Requests are prioritized based on:
    • Deal urgency/value (linked to CRM opportunity).
    • Reusability of asset (one-off vs. reusable collateral).
    • Alignment with sales enablement goals.
  3. Assign owner (Marketing, Pre-Sales, or Delivery input).

C. Asset Development

  1. Draft created using existing templates/brand guidelines.
  2. Reviews conducted:
    • Pre-Sales → technical accuracy.
    • Marketing → brand consistency.
    • Sales Manager → sales narrative alignment.

D. Delivery & Storage

  1. Completed asset delivered to requester by due date.
  2. Final copy stored in Repository with proper tags (industry, asset type, date).
  3. CRM updated with link to asset (if tied to an opportunity).
  4. Notify requester + Sales channel (Slack/email) of asset availability.

E. Post-Use Feedback

  1. Requester provides feedback on usefulness.
  2. Marketing logs learnings for continuous improvement.

5. Roles & Responsibilities

  • Requester (Sales/Pre-Sales/Delivery): Submits detailed request, provides context.
  • Sales Ops/Marketing: Reviews, prioritizes, and develops asset.
  • Pre-Sales Consultant: Validates technical content if applicable.
  • Sales Manager: Approves alignment with sales strategy.
  • Head of Sales/Marketing: Oversees process and resolves conflicts.

6. Governance, Violations & Consequences

  • Requests made outside official channel → not processed.
  • Using outdated/unapproved assets → escalated to Sales Manager.
  • Missed deadlines by Marketing without justification → escalated to Head of Sales.

7. Review & Ownership

  • Document Owner: Head of Marketing.
  • Review Cycle: Quarterly, aligned with sales asset refresh cycles.
  • Version Control: Request logs maintained in CRM/ticketing system.

SOP: Demo & Deck Customization

1. Purpose

The purpose of this SOP is to ensure that client demos and sales decks are customized consistently and professionally, while maintaining alignment with the master templates and brand guidelines. This ensures relevance to the client’s context without compromising brand integrity or accuracy.

2. Scope

This SOP applies to:

  • All sales demos and decks used in client meetings, workshops, or presentations.
  • Sales Representatives, Pre-Sales Consultants, Delivery Managers (when involved), and Marketing.
  • Assets drawn from the official Sales Repository.

3. Definitions

  • Master Deck: Company-approved presentation with standardized slides (see How-To: Using Master Deck).
  • Custom Deck: Client-specific version of the master deck with tailored slides, case studies, and industry examples.
  • Demo Environment: Configured product or solution environment used for live demonstration.

4. Step-by-Step Process

A. Preparation

  1. Sales Rep identifies need for a demo or presentation as part of opportunity progression.
  2. Retrieve the latest Master Deck and Demo Guidelines from Sales Repository.
  3. Align with Pre-Sales/Delivery for scope and demo setup.

B. Deck Customization

  1. Client Branding Context
    • Add client name/logo (only if approval/permission exists).
    • Highlight industry relevance.
  2. Slide Selection
    • Keep mandatory slides: Introduction, Services, Differentiators, Case Studies.
    • Replace or add slides relevant to prospect’s needs.
    • Remove irrelevant technical/service details.
  3. Case Studies Integration
    • Pull relevant case studies from Case Study Repository.
    • Add as appendix or embedded slide, depending on prospect stage.
  4. Compliance Check
    • Ensure disclaimers (confidentiality, NDA clauses) included.
    • No modification of brand-approved design elements.

C. Demo Environment Customization

  1. Pre-Sales configures demo environment (if product/SaaS demo required).
  2. Include client-specific scenarios (sample data, workflows).
  3. Dry run internally 24 hours before client presentation.

D. Review & Approval

  1. Sales Rep circulates customized deck/demo flow internally.
  2. Pre-Sales validates technical accuracy.
  3. Marketing checks brand compliance (optional for high-value deals).
  4. Sales Manager signs off before client-facing use.

E. Delivery & Storage

  1. Deliver demo/deck to client during scheduled session.
  2. Store final version in Repository → ClientName – Deck/Demo – Date.
  3. Update CRM opportunity notes with deck/demo version reference.

5. Roles & Responsibilities

  • Sales Rep: Owns customization, coordinates approvals.
  • Pre-Sales Consultant: Validates solution accuracy, configures demo.
  • Delivery Manager: Provides feasibility checks if delivery is showcased.
  • Marketing: Ensures brand and visual compliance.
  • Sales Manager: Approves final client-facing material.

6. Governance, Violations & Consequences

  • Use of outdated decks → flagged during review, escalated to Sales Manager.
  • Customization without approvals → non-compliance, deal support withdrawn.
  • Sharing demo data without confidentiality checks → escalated to Head of Sales.

7. Review & Ownership

  • Document Owner: Head of Sales (with Marketing & Pre-Sales).
  • Review Cycle: Quarterly, aligned with product/service updates.
  • Version Control: Decks maintained in Sales Repository under “Custom Decks.”

SOP: Proposal Creation & Approval (Sales Collateral)

1. Purpose

The purpose of this SOP is to ensure that all sales proposals are created using standardized templates, reviewed for brand and commercial compliance, and approved through a structured workflow before being shared with prospects. This safeguards consistency, quality, and compliance across all proposals.

2. Scope

This SOP applies to:

  • All proposals created for opportunities in CRM.
  • Sales Representatives, Sales Managers, Pre-Sales, Delivery, Marketing, and Finance teams.
  • IT Services & SaaS proposals across SMB, mid-market, and enterprise clients.

3. Definitions

  • Proposal Collateral: Standardized documents (cover letters, decks, templates) maintained in the Sales Repository.
  • Proposal Tracker: Central system (CRM or shared sheet) that logs proposal status (see Commercial Proposal Tracker Template).
  • Approval Matrix: Defined authority thresholds for proposal sign-off (see EPIC 5 SOP).

4. Step-by-Step Process

A. Proposal Initiation

  1. Sales Rep identifies proposal need after Discovery/Demo stage.
  2. Retrieve latest Proposal Template from Repository (see Repository Maintenance SOP).
  3. Complete draft with client details, opportunity context, and commercials.

B. Proposal Drafting & Compliance

  1. Ensure mandatory sections included:
    • Executive Summary
    • Problem Statement & Solution Overview
    • Scope of Work (SOW)
    • Pricing & Commercials
    • Timeline
    • Case Studies (if relevant)
    • Terms & Conditions (standard clauses)
  2. Check formatting against brand guidelines (logo, fonts, disclaimers).
  3. Add proposal ID (linked to CRM opportunity).

C. Internal Review & Approval

  1. Sales Manager → Validates completeness, sales narrative, and accuracy.
  2. Pre-Sales Consultant → Validates technical/functional scope.
  3. Delivery Manager → Validates feasibility and resource impact.
  4. Finance (if needed) → Approves pricing/margins if discount applied.
  5. Head of Sales → Signs off per Proposal Approval Matrix.

D. Versioning & Storage

  • Save proposals as PDF + editable format.
  • Use naming convention: ClientName – Proposal – vX – MonthYear.
  • Store in Sales Repository under Proposal folder, tagged with opportunity ID.
  • Update Proposal Tracker with status (Draft, Approved, Submitted).

E. Client Submission

  • Only approved proposals may be shared externally.
  • Send via secure method (see How-To: Sharing Proposals Securely).
  • Record submission date and next step in CRM.

5. Roles & Responsibilities

  • Sales Rep: Draft proposal, ensure accuracy of client context.
  • Sales Manager: First-line reviewer and approver.
  • Pre-Sales Consultant: Validate solution scope.
  • Delivery Manager: Validate delivery feasibility.
  • Finance: Approve pricing and discount policy.
  • Head of Sales: Final authority for high-value/strategic deals.
  • Marketing: Ensure brand alignment and formatting.

6. Governance, Violations & Consequences

  • Proposals bypassing approval → automatically invalid.
  • Non-standard templates/logos → rejected by Marketing.
  • Discounts without Finance approval → deal rollback.
  • Sharing draft versions with clients → formal escalation.

7. Review & Ownership

  • Document Owner: Head of Sales (with Marketing & Pre-Sales input).
  • Review Cycle: Quarterly or after significant pricing/branding updates.
  • Version Control: Repository maintained by Sales Ops.

SOP: Case Study Development

1. Purpose of Document

The purpose of this SOP is to standardize the creation of client case studies for use in sales enablement. Case studies serve as proof of expertise, build credibility, and provide persuasive content for proposals, demos, and outbound campaigns.

2. Scope

This SOP applies to:

  • All client success stories and internal initiatives selected for external publication.
  • Sales, Marketing, Pre-Sales, and Delivery teams contributing to case study creation.
  • Case studies used across proposals, master decks, campaigns, and repositories.

3. Definitions

  • Case Study: A structured success story highlighting a client problem, solution delivered, and measurable outcomes.
  • Repository: Central library (Drive/SharePoint/CRM) where all case studies are stored.
  • Collateral: Sales assets including case studies, decks, brochures, and one-pagers.

4. Step-by-Step Process

A. Selection of Case Study Candidate

  1. Sales Rep or Delivery Manager identifies a successful project.
  2. Ensure client has given consent (written or verbal) to use details.
  3. Prioritize case studies that highlight:
    • High ROI / measurable impact.
    • Unique technical solution.
    • Competitive differentiation.

B. Case Study Development Workflow

  1. Data Collection
    • Use standard Case Study Brief Form (fields: client background, challenge, solution, results, quotes).
    • Interview Delivery Lead and Client (if approved).
    • Collect metrics (e.g., % cost savings, uptime improvement, user growth).
  2. Draft Creation
    • Structure:
      • Client Background
      • Challenge
      • Solution (aligned to services)
      • Results/Outcomes (quantified if possible)
      • Client Quote/Testimonial (if available)
    • Use approved brand tone and formatting.
  3. Internal Review
    • Sales Manager reviews alignment with sales narrative.
    • Marketing edits for clarity, grammar, and design layout.
    • Delivery validates technical accuracy.
  4. Client Approval (Optional)
    • If client-facing logo/testimonial is included, secure written approval.
    • Store approval email/document in repository.
  5. Finalization & Publishing
    • Save final PDF and editable version in Case Study Repository.
    • Tag with industry, service line, and deal size for easy retrieval.
    • Announce availability via Sales Ops/Marketing channel.

C. Usage in Sales Process

  • Attach in proposals (see Proposal Creation SOP).
  • Include in Master Deck (see How-To: Using Master Deck).
  • Share via email/social campaigns when targeting similar industries.

5. Roles & Responsibilities

  • Sales Representative: Identify candidate projects, initiate request.
  • Delivery Manager: Provide project details and validation.
  • Marketing Team: Draft, edit, design, and publish case studies.
  • Sales Manager: Approve case study for use in active opportunities.
  • Client (optional): Approve logo/testimonial usage.

6. Governance, Violations & Consequences

  • Case studies without approval → cannot be used externally.
  • Unbranded or off-template case studies → rejected by Marketing.
  • Sharing unapproved or draft case studies with clients → performance escalation.

7. Review & Ownership

  • Document Owner: Head of Marketing (with input from Head of Sales).
  • Review Cycle: Quarterly to ensure repository remains updated.
  • Version Control: Editable + PDF stored in repository; new versions replace outdated ones.

Framework: Objection Handling

This framework equips Sales teams with structured responses and guidance for managing client objections across pricing, scope, competition, and risk. It ensures consistency, reduces stalled deals, and strengthens negotiation outcomes.

1. Purpose

To provide a standardized framework for handling objections raised during proposal or negotiation phases, ensuring objections are addressed constructively without unnecessary concessions.

2. Scope

Applies to:

  • All Sales Representatives and Account Managers handling client negotiations.
  • Pre-Sales and Delivery teams when objections relate to technical feasibility or timelines.
  • IT Services & SaaS proposals across all client segments.

3. Objection Handling Principles

  • Listen first → never interrupt or dismiss objections.
  • Clarify root cause → ask probing questions before responding.
  • Reframe to value → redirect conversation to ROI, outcomes, and differentiation.
  • Use evidence → case studies, metrics, or references instead of generic claims.
  • Trade, don’t concede → exchange concessions for commitments (e.g., longer contract).

4. Objection Handling Matrix

Objection TypeClient Statement (Example)Recommended ResponseRole Guidance
Pricing Too High“Your proposal is 20% higher than competitor.”Reframe on ROI/value → “Our approach reduces infra costs by 25% annually, ensuring faster payback.” Offer phased scope instead of discount.Sales Rep: lead discussion; Finance: validate margins
Unclear ROI“I’m not convinced this will deliver real savings.”Present case studies, client testimonials, ROI calculator.Sales Rep: present data; Pre-Sales: quantify impact
Timeline Concern“We need this live in 2 months, but your plan says 3.”Explore phased delivery; prioritize quick wins.Sales Rep: manage expectations; Delivery: validate feasibility
Scope Doubt“This doesn’t cover integration with X system.”Clarify inclusions/exclusions in SOW; explore add-ons.Pre-Sales: confirm technical feasibility; Sales Rep: update proposal if needed
Competition Comparison“Competitor offers similar service for less.”Differentiate via SLA, support, security, or expertise. Highlight long-term TCO (Total Cost of Ownership).Sales Rep: defend differentiators; Pre-Sales: technical positioning
Internal Approval Delays“Procurement/legal will take months.”Map decision process (from MEDDPICC), involve champion to push internally, offer legal template.Sales Rep: coordinate; Legal: support with templates
Trust & Risk Concerns“How do I know you’ll deliver as promised?”Share references, certifications, proof of delivery. Offer pilot engagement if aligned with policy.Sales Rep: share evidence; Delivery: commit on execution readiness

5. Objection Handling Process (Step-by-Step)

  1. Acknowledge → Show understanding (“I see why that’s a concern”).
  2. Clarify → Ask follow-ups to identify real issue (“Is it budget or perceived risk?”).
  3. Respond → Provide tailored, value-based answer using playbook matrix.
  4. Validate → Confirm if objection resolved (“Does this address your concern?”).
  5. Document → Record objection + response in CRM opportunity notes.

6. Roles & Responsibilities

  • Sales Representative: Primary handler of objections, records responses in CRM.
  • Pre-Sales Consultant: Supports with technical feasibility and ROI evidence.
  • Delivery Manager: Provides timeline/resource clarity for scope/timeline objections.
  • Sales Manager: Coaches reps on complex objection scenarios, reviews CRM entries.

7. Governance, Violations & Consequences

  • Failure to document objections in CRM → flagged in pipeline review.
  • Offering discounts or concessions without approval → escalated under Pricing & Discount Approval SOP.
  • Mishandling objections leading to client escalations → subject to performance review.

8. Review & Ownership

  • Document Owner: Head of Sales.
  • Review Cycle: Bi-annually or after major negotiation cycles.
  • Version Control: Maintained in CRM knowledge base.

Playbook: Negotiation Strategy

This playbook equips Sales Representatives and Managers with structured tactics, role-specific guidance, and reference frameworks for managing negotiations effectively. It ensures consistency, protects margins, and builds long-term client trust.

1. Purpose

To provide sales teams with structured strategies for handling client negotiations — covering pricing, scope, terms, and competitive positioning — while safeguarding company value and ensuring win–win outcomes.

2. Scope

Applies to all negotiation scenarios:

  • Commercial (pricing, discounts, payment terms)
  • Technical (scope, timelines, delivery model)
  • Legal/Contractual (compliance, liability, IP, SLAs)

3. Negotiation Principles

  • Preparation is key → enter every negotiation with clarity on walk-away points.
  • Value over price → focus on business outcomes, not just cost.
  • Trade, don’t concede → offer conditional value (longer contract, case study rights) instead of direct discounts.
  • Document everything → update CRM notes and proposal tracker.
  • Collaborative stance → position negotiation as partnership, not conflict.

4. Negotiation Framework (BATNA + MEDDPICC Alignment)

StepActionExampleOwner
1Define BATNA (Best Alternative to Negotiated Agreement)Walk away if deal < 10% marginSales Manager
2Validate client Decision Criteria (from MEDDPICC)Client values “fast time-to-market” more than costSales Rep
3Prepare trade-offsOffer 3-year deal discount instead of upfront % cutSales Rep + Finance
4Identify risks & escalation pointsScope creep risk flagged to DeliveryDelivery Manager
5Document in CRM & TrackerUpdate approval notesSales Rep

5. Negotiation Tactics & Role Guidance

ScenarioRecommended TacticRole Guidance
Client pushes for heavy discountReframe to ROI/value; propose phased engagement; apply approval matrixSales Rep: defend value, Sales Mgr: escalate for approval
Client questions scope/timelinesBreak down phases; clarify exclusions; involve Delivery for feasibilitySales Rep: manage expectations, Delivery Mgr: validate effort
Client compares competitor pricingHighlight differentiators (quality, SLA, support); offer non-monetary incentivesSales Rep: lead positioning, Pre-Sales: highlight tech strengths
Client delays decisionUse MEDDPICC Champion to push internally; reset timeline with urgency triggerSales Rep: chase with value reminder, Manager: escalate if stuck
Client raises legal/compliance concernsInvolve Legal early; position standard MSA/NDA templatesSales Rep: coordinate, Legal: respond formally

6. Pre- and Post-Negotiation Checklist

Pre-Negotiation

  • Review MEDDPICC completeness.
  • Confirm Approval Matrix for pricing/discounts.
  • Prepare trade-offs (scope, term length, references).
  • Align with Delivery and Finance.

Post-Negotiation

  • Update CRM with outcomes.
  • Revise proposal version (if required).
  • Notify Finance/Delivery of changed terms.
  • Record lessons learned for team review.

7. Roles & Responsibilities

  • Sales Representative: Leads negotiation, defends value, documents discussions.
  • Sales Manager: Provides guidance, escalates approvals, coaches rep.
  • Pre-Sales Consultant: Supports technical clarifications.
  • Delivery Manager: Validates scope/timeline feasibility.
  • Finance: Confirms margin impact for commercial concessions.
  • Legal (if required): Provides compliance and contractual inputs.

8. Governance, Violations & Consequences

  • Discounts or concessions outside Pricing & Discount Approval SOP → invalid and escalated.
  • Failure to log negotiation outcomes in CRM → deal excluded from forecast.
  • Misrepresentation of scope or terms → subject to disciplinary action.

9. Review & Ownership

  • Document Owner: Head of Sales.
  • Review Cycle: Bi-annually or after major deal negotiations.
  • Version Control: Maintained in CRM knowledge base.