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.