Archives: Documents

1. Purpose

The purpose of this policy is to establish clear standards for how leads are researched, collected, stored, and used in the sales process. Lead research is essential for identifying qualified prospects, but improper collection or misuse of data can lead to:

1. Legal and regulatory violations (e.g., GDPR, CCPA, Privacy Acts).
2. Reputational damage if prospects feel their data was obtained or used unethically.
3. Inefficient targeting occurs when inaccurate or incomplete data enters the CRM.
4. Loss of trust and opportunities due to poor personalization or irrelevant outreach.

This policy ensures that all lead research and data usage practices are ethical, accurate, compliant, and aligned with business needs, protecting both the company and its prospects.

2. Scope

This policy applies to all sales, marketing, and partner teams involved in identifying, collecting, or using lead data.

1. Roles Covered: SDRs, AEs/BDMs, Sales Managers, Sales Operations, Marketing, and any external partners/vendors providing leads.
2. Activities Covered: Lead sourcing, research, enrichment, storage, qualification, and outreach.
3. Data Types Covered: Firmographic data (company size, industry, location), demographic data (job title, role), contact data (email, phone, LinkedIn), and intent/behavioral signals (technology stack, funding, digital engagement).
4. Systems Covered: CRM, enrichment tools (Apollo, LinkedIn Sales Navigator, Clearbit, ZoomInfo), and marketing automation platforms integrated with CRM.

3. Definitions

1. Lead Research: The process of gathering firmographic, demographic, and contact details for potential clients using approved tools and methods.
2. Data Usage: The application of collected data for outreach, qualification, and nurturing within approved systems and workflows.
3. Enrichment: Adding missing or supplemental details (e.g., revenue, tech stack, intent signals) to an existing lead record.
4. Data Accuracy: Ensuring collected lead data is correct, current, and validated before use.
5. Data Compliance: Adherence to privacy regulations (e.g., GDPR, CAN-SPAM) and internal company standards.
6. Data Minimization: Collecting only the information necessary for sales engagement, avoiding unnecessary personal data.

4. Policy Statements

1. Approved Sources Only: Leads must only be researched through company-approved tools (e.g., LinkedIn Sales Navigator, Apollo, Clearbit) and public data. Scraping unauthorized sources is prohibited.
2. Data Compliance: All lead data collection and usage must comply with applicable privacy laws, including GDPR, CCPA, and Do Not Call registries.
3. Accuracy & Verification: Representatives must verify lead details (e.g., email validity, correct role) before entering data into the CRM.
4. Data Minimization: Only relevant information (firmographic, demographic, role-based contact data) may be collected; sensitive personal data (e.g., age, religion, personal phone) must not be captured.
5. Secure Storage: All lead data must be stored only in the company’s CRM or other authorized systems; personal spreadsheets or offline trackers are not allowed.
6. No Unauthorized Sharing: Lead data may not be shared outside the company or used for purposes unrelated to business development.
7. Vendor Accountability: Any external vendor providing lead data must comply with this policy and sign a data processing agreement if applicable.
8. Use for Business Only: Collected lead data may only be used for legitimate business development activities, not for personal or unrelated use.
9. Transparency: If prospects request, the company must disclose how their data was obtained and provide opt-out mechanisms in line with privacy regulations.

5. Roles & Responsibilities

1. SDRs: Responsible for accurate lead research, enrichment, and entry into CRM using approved tools.
2. AEs/BDMs: Validate lead quality before engaging; ensure leads are used only for relevant business purposes.
3. Sales Managers: Monitor lead sourcing practices, ensure compliance, and resolve disputes on data quality.
4. Sales Operations: Maintain tool integrations, enforce field standards, and conduct periodic audits.
5. Marketing Team: Ensure inbound leads meet the same compliance and accuracy standards before routing to sales.
6. Legal & Compliance: Provide guidance on applicable regulations, review vendor contracts, and investigate data misuse.

6. Governance, Violations & Consequences

1. Governance Oversight: The Head of Sales and Compliance jointly governs this policy.
2. Monitoring: Data entry quality and sourcing practices will be monitored through CRM audits and random checks of enrichment records.
3. Examples of Violations:
   • Using unapproved tools or scraping data illegally.
   • Storing lead lists in personal spreadsheets.
   • Collecting or storing sensitive personal data without justification.
   • Sharing lead data externally without authorization.
4. Consequences:
   • Minor Violations: Retraining and written reminder.
   • Moderate Violations: Formal warning and performance impact.
   • Severe Violations: Escalation to HR/Legal, termination, and possible legal action if laws are breached.

7. Review & Ownership

1. Policy Owner: Head of Sales with oversight from Legal/Compliance.
2. Review Cycle: Reviewed annually or earlier if regulations, tools, or processes change.
3. Approval Authority: Sales Leadership and Compliance must approve updates.
4. Training & Awareness: All sales staff must undergo training on compliant lead research during onboarding and annual refreshers.
5. Version Control: All revisions recorded in the Policy Register with date, version, and approvals.

1. Purpose

The purpose of this policy is to define rules and safeguards that prevent abuse of sales incentives, commissions, or target structures. Incentives are designed to reward genuine performance, but unethical behaviors such as gaming targets, misreporting deals, or manipulating CRM data can lead to:

1. Financial losses due to inflated or false commissions.
2. Distorted sales forecasts, harming strategic planning.
3. Damaged team morale when incentives are earned unfairly.
4. Reputational risk if clients experience poor treatment from rushed or falsified deals.

This policy ensures that incentive programs reward genuine performance aligned with company values and long-term client success.

2. Scope

This policy applies to all sales staff, managers, and leadership who participate in or oversee incentive, commission, or target-based compensation programs.

1. Roles Covered: SDRs, AEs/BDMs, Sales Managers, Sales Leadership, Sales Operations, and Finance.
2. Incentives Covered: Commissions, bonuses, spiffs, recognition rewards, and quarterly/annual incentive programs.
3. Activities Covered: Lead handling, opportunity management, deal closures, renewals, upselling, and cross-selling activities tied to incentives.

3. Definitions

1. Incentive Abuse: Any attempt to claim incentives or commissions through unethical or non-compliant actions.
2. Target Gaming: Manipulating activity, CRM data, or deal timing to artificially meet quotas or thresholds.
3. False Reporting: Recording inaccurate or misleading data in CRM to inflate performance metrics.
4. Shadow Pipeline: Deals withheld or staged artificially to meet incentive windows.
5. Spiff: A short-term bonus or incentive offered for specific behaviors (e.g., closing deals in a given month).

4. Policy Statements

1. Genuine Performance Only: Incentives will only be awarded for deals and activities that are legitimate, closed according to company processes, and verified in CRM.
2. No Shadow Deals: Deals must be entered into CRM as soon as they reach qualification. Withholding deals to manipulate reporting cycles is prohibited.
3. Accurate Reporting: All sales data, including lead status, opportunity stages, and deal values, must reflect real activity. False reporting or backdating is strictly prohibited.
4. Client-Centric Behavior: Incentives must not drive actions that harm client experience (e.g., rushing contracts, overpromising deliverables, or misrepresenting services).
5. CRM as Source of Truth: Incentive eligibility will be calculated solely based on CRM data, validated by Sales Operations and Finance.
6. Deal Validation: All incentive claims are subject to validation by Sales Managers and Finance. Deals found to be misrepresented will be excluded from incentive calculations.
7. Prohibited Practices:
   • Splitting deals artificially to maximize incentives.
   • Colluding with peers to swap leads or manipulate ownership.
   • Closing deals prematurely and reopening them post-incentive period.
   • Offering unauthorized discounts solely to secure incentives.
8. Transparency: Incentive structures and qualification rules will be communicated clearly to all sales staff.

5. Roles & Responsibilities

1. SDRs: Must qualify and hand off leads accurately; may not inflate lead counts or bypass qualification standards to earn incentives.
2. AEs/BDMs: Ensure all deals are logged, updated, and closed with accuracy; prohibited from manipulating values or closing stages for incentives.
3. Sales Managers: Validate team performance data, monitor for unusual patterns, and investigate potential abuse.
4. Sales Leadership: Define incentive structures, approve escalations, and ensure alignment with company strategy.
5. Sales Operations: Monitor CRM data integrity, flag anomalies, and provide reports for incentive validation.
6. Finance Team: Validate final incentive calculations before payouts; escalate discrepancies to Sales Leadership and HR.

6. Governance, Violations & Consequences

1. Governance Oversight: Jointly managed by Sales Leadership, Sales Operations, and Finance.
2. Monitoring: Incentive claims will be reviewed during monthly and quarterly cycles using CRM audit trails, deal validations, and Finance checks.
3. Examples of Violations:
   • Logging fake leads or activities in CRM.
   • Delaying or rushing deals to meet incentive periods.
   • Misreporting discounts, values, or deal sizes.
   • Collusion with other team members to inflate performance.
4. Consequences:
   • Minor Violations: Removal of incentive eligibility for the current cycle.
   • Moderate Violations: Formal warning, repayment of wrongly claimed incentives, and impact on performance evaluation.
   • Severe Violations: Escalation to HR with potential termination, legal recovery of funds, and disqualification from future incentive programs.

7. Review & Ownership

1. Policy Owner: Head of Sales, jointly with Finance.
2. Review Cycle: Reviewed annually, or sooner if incentive structures are revised.
3. Approval Authority: Sales Leadership, Finance, and HR.
4. Training & Awareness: Incentive rules must be explained to all sales staff during onboarding and before each program launch.
5. Version Control: All updates are logged in the Policy Register with version number, date, and approval signatures.

1. Purpose

The purpose of this policy is to define rules for the creation, handling, storage, and sharing of sales-related documents (e.g., proposals, contracts, decks, case studies, pricing sheets). These documents often contain sensitive business information, intellectual property, and client-specific data. Improper handling can lead to:

1. Breach of client confidentiality or data protection laws.
2. Unauthorized disclosure of company strategies, pricing models, or intellectual property.
3. Reputational and financial damage due to loss or leakage of sensitive materials.
4. Loss of competitive advantage if documents are shared externally without authorization.

This policy ensures that all sales documents are managed securely, used appropriately, and protected from unauthorized access or disclosure.

2. Scope

This policy applies to all employees, contractors, and third parties involved in preparing, reviewing, distributing, or storing sales documents.

1. Roles Covered: SDRs, AEs/BDMs, Pre-Sales Engineers, Sales Managers, Sales Operations, Marketing, Legal, and Leadership.
2. Documents Covered: Proposals, contracts, NDAs, presentations, pricing sheets, case studies, product/service one-pagers, and client deliverables shared during sales.
3. Channels Covered: CRM, company email, approved file-sharing systems, proposal software, and secure repositories.
4. Exclusions: Marketing collateral intended for public use (e.g., website content, brochures) is not covered by this policy.

3. Definitions

1. Confidential Sales Documents: Any document containing non-public company or client information (e.g., pricing, contracts, solutions).
2. Authorized Access: Permission granted by role or manager to view, edit, or distribute specific sales documents.
3. Repository: The official, access-controlled storage location (CRM, secure drive, or proposal management tool) where sales documents are stored.
4. Unauthorized Disclosure: Sharing or exposing documents to individuals not authorized to view them, internally or externally.
5. Document Classification: Labeling sales documents based on sensitivity (e.g., internal only, client-shared, restricted).

4. Policy Statements

1. Standard Repository Use: All sales documents must be stored only in the company’s approved repository or CRM. Personal devices or drives must not be used.
2. Access Control: Document access is role-based. Only authorized personnel may view, edit, or distribute specific documents.
3. Secure Sharing: Sales documents must only be shared via company email, CRM-integrated proposal tools, or secure file-sharing platforms. Personal email or consumer file-sharing services are prohibited.
4. Client Confidentiality: Client-provided materials must be treated with the same confidentiality as internal sales documents and never shared outside authorized teams.
5. Document Classification: All sales documents must be labeled with sensitivity levels (e.g., “Internal Only,” “Client Copy”) before distribution.
6. Version Control: Only the latest approved versions of proposals, decks, and pricing sheets may be shared with clients. Outdated versions must be archived.
7. No Unauthorized Modifications: Sales staff may not modify legal documents (NDAs, contracts) without Legal approval, or alter pricing sheets without Finance approval.
8. Record Keeping: Final signed documents (NDAs, proposals, contracts) must be uploaded to CRM or repository for audit and reference.
9. Prohibited Practices: Forwarding confidential sales documents to personal email, storing them on unapproved devices, or sharing them on social media is strictly prohibited.

5. Roles & Responsibilities

1. SDRs: May request and share only pre-approved sales collateral with prospects; cannot alter confidential documents.
2. AEs/BDMs: Ensure proposals, decks, and contracts are approved before sharing; maintain confidentiality of all client-facing materials.
3. Pre-Sales Engineers: Use only authorized demo decks and technical documents; log all shared content in CRM.
4. Sales Managers: Review team compliance, approve access exceptions, and monitor repository usage.
5. Sales Operations: Maintain repositories, templates, and version control; enforce document classification rules.
6. Legal Team: Own templates for NDAs and contracts; approve any client-requested changes before distribution.
7. IT/Security: Manage access controls, monitor unauthorized downloads/sharing, and investigate breaches.

6. Governance, Violations & Consequences

1. Governance Oversight: The Head of Sales and the IT/Security Team jointly govern this policy.
2. Monitoring: Access logs, CRM records, and repository activity will be monitored for compliance.
3. Examples of Violations:
   • Sharing proposals or pricing sheets via personal email.
   • Altering legal documents without approval.
   • Uploading confidential documents to unauthorized platforms.
   • Using outdated versions of documents with clients.
4. Consequences:
   • Minor Violations: Coaching, retraining, and documented warning.
   • Moderate Violations: Formal disciplinary warning and restricted access to repositories.
   • Severe Violations: Escalation to HR and Legal, potential termination, and legal action if confidentiality is breached.

7. Review & Ownership

1. Policy Owner: Head of Sales, with oversight from Legal and IT/Security.
2. Review Cycle: Reviewed annually or when significant changes occur in tools, repositories, or compliance regulations.
3. Approval Authority: Sales Leadership, Legal, and IT jointly approve updates.
4. Training & Awareness: All sales staff must undergo training on confidentiality practices during onboarding and annual refreshers.
5. Version Control: Updates must be logged in the Policy Register with version number, date, and approval authority.

1. Purpose

The purpose of this policy is to establish clear standards for the setup, usage, and maintenance of demo environments and sales tools. Demos are a critical part of the sales process, showcasing the company’s capabilities to prospects. Improper or inconsistent demo practices can lead to:

1. Misrepresentation of product/service capabilities.
2. Technical failures during live demos are damaging credibility.
3. Security risks from exposing client or internal data.
4. Operational inefficiency occurs when multiple versions or tools are used inconsistently.

This policy ensures that demo environments and tools are secure, consistent, and reliable, providing prospects with a professional experience while protecting the company’s assets and reputation.

2. Scope

This policy applies to all sales, pre-sales, and technical staff involved in preparing, delivering, or supporting product/service demos.

1. Roles Covered: SDRs, AEs/BDMs, Pre-Sales Engineers, Solution Consultants, Sales Managers, and Sales Operations.
2. Activities Covered: Demo setup, client walkthroughs, internal dry runs, and post-demo follow-ups.
3. Tools & Systems Covered: Demo platforms, sandbox environments, CRMs used for demo purposes, presentation tools, and integrations specifically provisioned for sales demonstrations.
4. Exclusions: Client-specific Proof of Concepts (POCs) are governed by a separate POC Execution Policy.

3. Definitions

1. Demo Environment: A secure, non-production system configured to simulate the company’s solution for demonstration purposes.
2. Sandbox: A test environment isolated from production data, used for experimentation and demos.
3. Sales Tools: Approved applications used for conducting demos (e.g., presentation decks, demo platforms, screen-sharing tools).
4. Live Demo: A real-time presentation of the company’s solution to a prospect.
5. Mock Data: Artificially generated data used in demos to prevent exposure of sensitive or client-specific information.

4. Policy Statements

1. Standardized Environment: All demos must be conducted using company-approved demo environments or sandbox systems. Production systems must never be used.
2. Data Security: Only mock or anonymized data may be used in demo environments. Client or live production data is strictly prohibited.
3. Tool Authorization: Only approved demo tools and presentation software may be used. Unauthorized third-party tools must not be introduced without Sales Operations approval.
4. Environment Readiness: Pre-sales staff must ensure demo systems are tested and functional before any client session. Dry runs are mandatory for high-stakes demos.
5. Consistency of Messaging: All demo scripts, decks, and walkthroughs must align with approved materials in the collateral repository.
6. Recording & Sharing: Demo recordings may only be shared with prospects if approved and hosted on secure company platforms.
7. Maintenance: Sales Operations is responsible for maintaining demo environments, updating scripts, and ensuring technical reliability.
8. Customization Rules: Custom configurations may only be added with manager approval and must not misrepresent product capabilities.
9. Escalation: Any demo failure or tool malfunction must be logged and reported immediately to Sales Operations for corrective action.

5. Roles & Responsibilities

1. SDRs: Use approved decks for prospecting conversations; not authorized to deliver live product demos.
2. AEs/BDMs: Conduct client demos using approved environments and ensure alignment with prospect needs.
3. Pre-Sales Engineers / Solution Consultants: Own demo setup, technical readiness, and customization within approved guidelines.
4. Sales Managers: Review demo performance, enforce policy adherence, and approve exceptions where needed.
5. Sales Operations: Maintain demo tools, environments, and a central repository of scripts.
6. IT / Security Team: Oversee environment access controls, monitor for unauthorized data usage, and ensure compliance with security standards.

6. Governance, Violations & Consequences

1. Governance Oversight: Shared between Sales Operations and the Head of Sales.
2. Monitoring: Demos and tool usage may be reviewed through CRM logs, feedback forms, and random audits.
3. Violations:
   • Using production data or systems for demos.
   • Conducting demos with unapproved tools.
   • Misrepresenting product capabilities during a demo.
   • Failing to log demo activity in CRM.
4. Consequences:
   • Minor Violations: Coaching and retraining.
   • Moderate Violations: Formal warning and exclusion from demo responsibilities until retrained.
   • Severe Violations: Escalation to HR, potential loss of role responsibilities, or termination in cases of repeated or intentional misuse.

7. Review & Ownership

1. Policy Owner: Sales Operations, with oversight from the Head of Sales.
2. Review Cycle: Annual, or sooner if demo tools, products, or compliance requirements change.
3. Approval Authority: Sales Leadership and IT/Security Team.
4. Training & Awareness: All AEs and Pre-Sales staff must undergo demo environment training during onboarding and refresher sessions yearly.
5. Version Control: All updates are logged in the Policy Register with revision date, version number, and approval record.

1. Purpose

The purpose of this policy is to establish clear guidelines for the ethical collection, use, and handling of competitor intelligence within the sales organization. Competitive insights are valuable for positioning, pricing, and client negotiations, but unethical or unlawful practices can expose the company to:

1. Legal risks such as violation of competition or data protection laws.
2. Reputational damage if the company is perceived as engaging in unethical spying or data theft.
3. Distrust among clients, partners, and employees.
4. Misaligned decision-making based on unreliable or improperly obtained data.

This policy ensures that all competitor intelligence activities are conducted lawfully, transparently, and in alignment with the company’s values and compliance obligations.

2. Scope

This policy applies to all sales, marketing, pre-sales, and leadership staff who may gather, share, or use competitor intelligence.

1. Roles Covered: SDRs, AEs/BDMs, Pre-Sales, Sales Managers, Marketing, Product, and Leadership.
2. Activities Covered: Research, client conversations, proposal benchmarking, market analysis, and deal strategy sessions.
3. Sources Covered: Publicly available information, authorized research subscriptions, analyst reports, and client-disclosed comparisons.
4. Exclusions: Any intelligence gathered through unlawful, deceptive, or unauthorized means is prohibited under this policy.

3. Definitions

1. Competitor Intelligence: Information about other companies operating in the same market, used for competitive positioning.
2. Ethical Sources: Public websites, press releases, regulatory filings, analyst reports, and information voluntarily provided by prospects/clients.
3. Unethical Sources: Hacking, misrepresentation, industrial espionage, bribery, or use of confidential client/partner data without authorization.
4. Benchmarking: The practice of comparing proposals, features, or pricing with competitors using only legally and ethically obtained data.
5. Misrepresentation: Pretending to be a client, partner, or third party to extract competitor information.

4. Policy Statements

1. Ethical Standards: All competitor intelligence must be gathered using publicly available or properly authorized sources.
2. Prohibition on Misrepresentation: Employees must not impersonate clients, partners, or third parties to obtain competitor information.
3. Client & Partner Confidentiality: Information shared by clients or partners about competitors must be treated as confidential and not circulated beyond internal strategy discussions.
4. Use of Approved Tools: Only company-approved research subscriptions, market reports, and tools may be used for competitor analysis.
5. Documentation & Attribution: All competitor insights must include source attribution to confirm legality and reliability.
6. Restricted Sharing: Competitor intelligence must not be shared externally (including on social media) or used in ways that could be seen as disparaging or defamatory.
7. Internal Use Only: Intelligence is to be used strictly for strategy, proposal development, and client positioning—not for personal or non-business purposes.
8. Compliance Alignment: All competitor intelligence activities must align with competition law, anti-bribery regulations, and the company’s Code of Conduct.

5. Roles & Responsibilities

1. SDRs / AEs / BDMs: May collect competitor information from client conversations or public sources but must log it appropriately in CRM notes or knowledge repositories.
2. Pre-Sales & Solution Consultants: Validate technical comparisons and ensure client discussions remain fact-based and ethical.
3. Sales Managers: Review competitor intelligence during deal reviews to confirm accuracy and adherence to ethical standards.
4. Marketing & Product Teams: Conduct structured competitor research using approved sources and share sanitized reports with Sales.
5. Sales Leadership: Approve major competitive benchmarking initiatives and ensure compliance with competition law.
6. Compliance & Legal Team: Provide guidance on acceptable practices and investigate reported breaches of this policy.

6. Governance, Violations & Consequences

1. Governance Oversight: The Head of Sales and Compliance Team jointly own governance of competitor intelligence practices.
2. Monitoring: Competitor-related notes and analysis will be reviewed periodically in CRM audits, proposal reviews, and strategy sessions.
3. Examples of Violations:
   • Pretending to be a client to solicit competitor pricing.
   • Using unauthorized tools to extract non-public data.
   • Sharing competitor intelligence outside the company.
   • Disparaging competitors in client-facing conversations.
4. Consequences:
   • Minor Violations: Coaching and written reminder.
   • Moderate Violations: Formal warning and impact on performance evaluation.
   • Severe Violations: Escalation to HR and Legal with potential termination and legal liability for the individual.

7. Review & Ownership

1. Policy Owner: Head of Sales with oversight from Compliance.
2. Review Cycle: Reviewed annually or sooner if legal or competitive landscape changes.
3. Approval Authority: Sales Leadership and Compliance jointly approve updates.
4. Training & Awareness: Annual training for sales staff to reinforce ethical competitor intelligence practices.
5. Version Control: All updates recorded in the Policy Register with version number, revision date, and approving authority.

1. Purpose

The purpose of this policy is to establish clear rules for offering discounts, handling pricing exceptions, and securing approvals during the sales process. Pricing integrity is critical for maintaining profitability, ensuring fairness, and protecting the company’s market positioning. Uncontrolled or ad-hoc discounting can lead to:

1. Erosion of margins and long-term profitability.
2. Inconsistent treatment of clients, leading to reputational risk.
3. Internal conflicts occur when different representatives offer varying discounts.
4. Poor forecasting and misalignment with Finance and Delivery teams.

This policy ensures that all discounting decisions are transparent, consistent, and approved through a defined governance framework.

2. Scope

This policy applies to all sales staff, managers, and leadership involved in pricing, discounting, and commercial negotiations.

1. Roles Covered: SDRs, AEs/BDMs, Sales Managers, Sales Leadership, Finance Team, Deal Desk (if applicable).
2. Transactions Covered: Service proposals, SaaS subscriptions, bundled offerings, renewals, and custom solutions.
3. Exclusions: Internal transfer pricing, employee discounts, or marketing-led promotions (governed by separate policies).

Section 3: Definitions

1. List Price: The standard price for services or products as defined in the company’s pricing catalog.
2. Discount: A reduction from the list price offered to a prospect or client.
3. Approval Threshold: The maximum discount a representative can offer without requiring higher-level approval.
4. Deal Desk: The centralized function responsible for reviewing, validating, and approving non-standard pricing or deal structures.
5. Pricing Integrity: Ensuring consistent and justified pricing across all clients, avoiding favoritism or arbitrary discounts.
6. Non-Standard Terms: Any terms involving discounts beyond thresholds, extended payment terms, or custom pricing models.

4: Policy Statements

1. Standard Pricing First: Representatives must present official list prices during initial negotiations; discounting is only considered in justified cases.
2. Discount Approval Thresholds:
   • SDRs: No authority to discuss or approve discounts.
   • AEs/BDMs: May approve discounts up to 5% of deal value.
   • Sales Managers: May approve discounts up to 10%.
   • Head of Sales / VP Sales: May approve discounts up to 20%.
   • Discounts beyond 20% require Deal Desk and Finance Leadership approval.
3. Documentation: All discounts must be documented in the CRM with reason codes (e.g., competitive match, strategic account, bundled deal).
4. Justification Required: Discounts must be tied to business justification such as deal size, long-term contract, or competitive landscape—not personal discretion.
5. Payment Terms: Any deviation from standard payment schedules must be approved by Finance in addition to Sales Leadership.
6. Prohibited Practices:
   • Offering unapproved discounts verbally or informally.
   • Splitting discounts across multiple line items to bypass approval thresholds.
   • Promising future discounts without documented approval.
7. Proposal Alignment: All discounted prices must be reflected in the official proposal and tracked in the pricing calculator.
8. Audit Trail: All discounting decisions must leave a traceable record in the CRM and deal approval system for audit and compliance.

5. Roles & Responsibilities

1. SDRs: Must only position standard list pricing when asked; not authorized to negotiate discounts.
2. AEs/BDMs: May apply approved discounts within thresholds, ensure CRM entries are accurate, and escalate larger requests to managers.
3. Sales Managers: Review and validate discounting requests from AEs, ensuring compliance with thresholds and justification requirements.
4. Head of Sales / VP Sales: Approve higher-level discounts, ensuring alignment with strategic goals.
5. Deal Desk / Finance: Validate high-value or non-standard deals, assess margin impact, and approve payment term changes.
6. Sales Operations: Maintain the pricing catalog, approval thresholds, and audit mechanisms within the CRM.

6. Governance, Violations & Consequences

1. Governance Oversight: The Head of Sales and Finance jointly own governance of discounting practices.
2. Monitoring: Discounts will be reviewed during pipeline reviews, quarterly audits, and Finance reconciliation.
3. Violations:
   • Offering unauthorized discounts.
   • Bypassing approval thresholds.
   • Misrepresenting discounts in CRM or proposals.
   • Collusion with clients to manipulate pricing.
4. Consequences:
   • Minor Violations (e.g., missing reason code): Corrective training and warning.
   • Moderate Violations (e.g., repeated failure to follow process): Formal warning and negative performance impact.
   • Severe Violations (e.g., unauthorized deep discounting, data manipulation): Escalation to HR with potential termination and financial recovery measures.

7. Review & Ownership

1. Policy Owner: Joint ownership by Head of Sales and Finance.
2. Review Cycle: Reviewed annually, or sooner if pricing strategy or market conditions change.
3. Approval Authority: Sales Leadership and Finance must jointly approve all updates.
4. Training & Awareness: All sales staff must receive training on discounting thresholds and approval workflows during onboarding and annual refreshers.
5. Version Control: All revisions logged in the Policy Register with version number, date, and approval record.

1. Purpose

The purpose of this policy is to establish clear standards for professional, respectful, and effective communication with prospects at every stage of the sales cycle. Communication is one of the most visible aspects of sales representation, and inconsistent or inappropriate interactions can lead to:

1. Reputational damage if prospects feel disrespected, pressured, or misled.
2. Loss of opportunities due to poorly timed or unprofessional communication.
3. Compliance risks arising from unsolicited or unauthorized outreach.
4. Fragmented client experience when multiple team members communicate inconsistently.

This policy ensures that all prospect-facing communication reflects the company’s values, maintains professionalism, complies with regulations, and creates a consistent, trustworthy experience.

2. Scope

This policy applies to all employees, contractors, and representatives engaged in prospect communication, regardless of role, geography, or channel.

1. Roles Covered: SDRs, AEs/BDMs, Pre-Sales, Sales Managers, Leadership, and any employee participating in prospect calls, emails, or meetings.
2. Channels Covered: Email, phone calls, video conferencing, LinkedIn and other professional social media, trade shows/events, and CRM-integrated messaging tools.
3. Activities Covered: Initial outreach, follow-ups, demos, negotiations, proposal discussions, and general prospect correspondence.
4. Applicability Period: Covers the entire prospect lifecycle from first touch through qualification, opportunity development, and handoff.

3. Definitions

1. Prospect: Any individual or organization that has shown potential interest in the company’s offerings but has not yet become a client.
2. Professional Communication: Clear, respectful, and business-appropriate communication that reflects company standards.
3. Follow-Up Cadence: The structured sequence and timing of outreach attempts, defined in the Outreach SOP.
4. Misrepresentation: Any communication that conveys false, incomplete, or exaggerated information about the company’s services, capabilities, or pricing.
5. Authorized Channels: Company-approved tools and platforms for outreach (e.g., CRM-integrated email, official LinkedIn accounts, approved dialers).

4. Policy Statements

1. Professionalism First: All communications must be courteous, respectful, and free from slang, informal language, or offensive remarks.
2. Clear Identification: Representatives must identify themselves, their role, and the company at the start of communications.
3. Accuracy: Information about services, pricing, or timelines must be factually correct and aligned with approved company materials.
4. No Harassment: Prospects must not be subjected to excessive calls, emails, or pressure tactics. Communication frequency must follow the approved cadence.
5. Respect for Boundaries: If a prospect declines further communication, requests removal from outreach, or opts out via unsubscribe links, the request must be honored immediately.
6. Timely Responses: Inquiries from prospects must be acknowledged within one business day, even if a complete response requires more time.
7. Consistent Messaging: All representatives must use approved templates, decks, and FAQs to ensure uniform messaging across the sales team.
8. Documentation: All communications (emails, calls, meetings) must be logged in the CRM for transparency and continuity.
9. Confidentiality: Sensitive information shared by prospects must not be disclosed outside authorized internal teams.
10. Compliance: All outreach must comply with regulations such as GDPR, CAN-SPAM, and Do Not Call lists.

5. Roles & Responsibilities

1. SDRs: Responsible for initiating respectful outreach, using approved scripts and cadences, and properly logging interactions.
2. AEs/BDMs: Ensure communication during discovery, demos, and negotiations remains professional, accurate, and client-centric.
3. Pre-Sales: Provide technical clarifications in a professional manner without overcommitting beyond delivery capabilities.
4. Sales Managers: Monitor communication tone and frequency during pipeline reviews; coach team members on etiquette lapses.
5. Sales Operations: Maintain updated outreach templates and ensure integration with CRM.
6. Compliance & Legal: Review communication processes for regulatory adherence and investigate reported violations.

6. Governance, Violations & Consequences

1. Governance Oversight: Sales Managers enforce communication standards daily; oversight rests with the Head of Sales.
2. Monitoring: Compliance is monitored through CRM audits, email reviews, call recordings, and client feedback.
3. Examples of Violations:
   • Using unapproved templates or personal email accounts.
   • Misrepresenting company services or pricing.
   • Ignoring opt-out requests or continuing communication against prospect wishes.
   • Using offensive, unprofessional, or coercive language.
4. Consequences:
   • Minor Violations: Coaching, retraining, and documented feedback.
   • Moderate Violations: Formal warning and impact on performance evaluation.
   • Severe Violations: Escalation to HR with potential disciplinary action, up to and including termination of employment.

7. Review & Ownership

1. Policy Owner: Head of Sales.
2. Review Cycle: Annually, or earlier if outreach regulations or company processes change.
3. Approval Authority: Sales Leadership and Compliance Team.
4. Training & Awareness: All sales staff must be trained on this policy during onboarding and receive refresher sessions twice yearly.
5. Version Control: Updates must be logged in the Policy Register with revision date, version, and approvals.

1. Purpose

The purpose of this policy is to define the standards and procedures for sharing Non-Disclosure Agreements (NDAs), proposals, and other sensitive sales documents with prospects, clients, and partners. These documents often contain confidential company information, pricing details, intellectual property, and client-specific solutions. Improper sharing or handling of such documents creates risks including:

1. Legal Exposure – Breach of confidentiality terms or regulatory requirements (e.g., data protection laws, IP rights).
2. Reputational Damage – Loss of trust if sensitive information is shared insecurely or falls into the wrong hands.
3. Commercial Risk – Unauthorized distribution of proposals or pricing models can undermine competitive advantage.
4. Operational Inefficiency – Lack of standardized processes results in inconsistent client experiences and internal confusion.

This policy ensures that all NDAs and proposals are created, approved, and shared securely, consistently, and in compliance with legal and organizational requirements, safeguarding both company and client interests.

2. Scope

This policy applies to all employees, contractors, and representatives involved in drafting, reviewing, approving, or sharing NDAs, proposals, or related sales documents.

1. Roles Covered:
   • Sales Development Representatives (SDRs): May request NDAs but cannot approve or sign them.
   • Account Executives (AEs) / Business Development Managers (BDMs): Responsible for proposal preparation and client-facing delivery.
   • Sales Managers: Review and approve proposals before external sharing.
   • Sales Operations / Legal Team: Own NDA templates and ensure legal compliance.
   • Senior Leadership: Authorized to sign NDAs or approve non-standard terms.
2. Documents Covered:
   • Non-Disclosure Agreements (NDAs).
   • Sales proposals (service, SaaS, or custom solution).
   • Pricing sheets and commercial terms.
   • Statement of Work (SOW) drafts prior to contract.
3. Channels Covered:
   • Official company email accounts.
   • Company-approved document sharing platforms (e.g., CRM, secure drive, proposal software).
   • E-signature platforms approved by Legal.
   • Any unauthorized use of personal email, WhatsApp, or file-sharing services is prohibited.

3. Definitions

1. NDA (Non-Disclosure Agreement): A legal contract ensuring confidentiality of information exchanged between the company and an external party.
2. Proposal: A formal sales document outlining scope, pricing, timelines, and value proposition for a prospect or client.
3. Confidential Information: Any non-public data related to the company, its clients, pricing, IP, or strategies, which must be safeguarded.
4. Authorized Sharing: The act of transmitting documents through approved company channels with necessary approvals.
5. Unauthorized Disclosure: Sharing or forwarding documents outside of approved processes, systems, or recipients.
6. Proposal Repository: The central, access-controlled storage location for company-approved proposal templates and NDA documents.

4. Policy Statements

1. Standard Templates: All NDAs and proposals must use company-approved templates maintained by Sales Operations and Legal. Modifications are not permitted without written approval.
2. Approval Workflow: Proposals must be reviewed by Sales Managers for accuracy and compliance before being sent to clients. NDAs must be reviewed and approved by the Legal Team if changes are requested by the client.
3. Authorized Channels Only: Documents may only be shared via official company email, CRM-integrated tools, or secure file-sharing platforms. Personal email or unapproved tools are prohibited.
4. E-Signature Compliance: NDAs and proposals requiring signatures must be executed using company-approved e-signature platforms. Handwritten or scanned signatures are only allowed if approved by Legal.
5. Confidentiality of Proposals: Proposals must not be forwarded or shared externally without approval. Internal circulation should be restricted to stakeholders directly involved in the opportunity.
6. Expiry and Version Control: Proposals must include validity dates (e.g., 30 days) and version numbers to avoid confusion or misuse of outdated proposals.
7. Record Keeping: All signed NDAs and sent proposals must be uploaded to the CRM or proposal repository with correct tagging to ensure visibility and auditability.
8. Client Communication: Any discussions around NDAs or proposals must remain professional, accurate, and aligned with the content of the documents. Over-promising beyond the approved proposal is prohibited.

5. Roles & Responsibilities

1. SDRs: Can request NDAs through the CRM or Sales Manager but cannot sign or modify them. Must log all NDA requests in CRM.
2. AEs/BDMs: Prepare proposals using approved templates, ensure accuracy of details, and seek Sales Manager approval before sending. Responsible for uploading final proposals and NDAs into CRM.
3. Sales Managers: Review proposals for accuracy, compliance, and pricing approval. Approve NDA requests before escalating to Legal if non-standard terms are included.
4. Sales Operations: Maintain master templates for proposals and NDAs. Ensure repository access is secure and up to date.
5. Legal Team: Approve NDA language, handle client-requested edits, and maintain compliance with confidentiality laws.
6. Senior Leadership: Authorized signatories for NDAs and high-value proposals. Escalation point for exceptions.

6. Governance, Violations & Consequences

1. Governance Oversight: The Head of Sales and the Legal Team share accountability for this policy. Sales Managers enforce it on a day-to-day basis.
2. Monitoring: Compliance will be monitored through CRM audits, repository checks, and random reviews of client correspondence.
3. Violations:
   • Using non-approved templates.
   • Sharing proposals via personal email or unauthorized platforms.
   • Sending proposals without manager approval.
   • Altering NDA terms without Legal involvement.
   • Failing to upload final signed documents into CRM.
4. Consequences:
   • Minor Violations (e.g., forgetting to upload a document): Corrective coaching and retraining.
   • Moderate Violations (e.g., repeated missed approvals, use of outdated proposals): Written warning and impact on performance review.
   • Severe Violations (e.g., unauthorized disclosure of confidential information, unapproved NDA alterations): Escalation to HR and Legal with possible termination and legal action.

7. Review & Ownership

1. Policy Owner: Jointly owned by the Head of Sales and Legal Team.
2. Review Cycle: Reviewed annually or sooner if legal, compliance, or sales process changes occur.
3. Approval Authority: Any updates must be approved by Sales Leadership and Legal.
4. Training & Awareness: All sales team members must be trained on this policy during onboarding and refresher sessions.
5. Version Control: All revisions will be logged in the Policy Register with date, version number, and approval signatures.

1. Purpose

The purpose of this policy is to establish clear standards for the entry, maintenance, and accuracy of data within the company’s CRM system. The CRM is the single source of truth for all client and prospect interactions. Inaccurate, incomplete, or inconsistent data leads to:

1. Pipeline Inaccuracy – Sales forecasts and revenue projections become unreliable when data is outdated or inconsistent.
2. Operational Inefficiency – Sales, marketing, and delivery teams waste time reconciling records or working with incomplete information.
3. Poor Client Experience – Duplicated outreach, misinformed conversations, and incorrect account details reduce trust and credibility with prospects.
4. Compliance Risks – Mishandling client data, or storing it outside authorized fields, can result in legal and regulatory violations (e.g., GDPR, privacy acts).

This policy ensures that all sales data is captured accurately, updated promptly, and maintained in compliance with both company standards and applicable laws. It defines what constitutes valid CRM data entry, how integrity will be safeguarded, and who is accountable at each stage.

2. Scope

This policy applies to all employees and contractors who interact with the company’s Customer Relationship Management (CRM) system. It governs the creation, update, transfer, and maintenance of all data related to leads, opportunities, accounts, and client interactions.

1. Roles Covered
   • Sales Development Representatives (SDRs): Responsible for accurate creation and enrichment of lead records.
   • Account Executives (AEs) / Business Development Managers (BDMs): Responsible for maintaining opportunity details, contact information, and progress updates.
   • Pre-Sales & Solution Consultants: Required to document demo outcomes, technical notes, and solution validation in linked CRM records.
   • Sales Managers: Accountable for reviewing pipeline accuracy, validating updates, and enforcing compliance.
   • Sales Operations / CRM Administrators: Maintain system configurations, field definitions, data standards, and conduct audits.
   • Marketing & Customer Success Teams: When interacting with CRM data (e.g., campaign tagging, client renewals), must adhere to the same accuracy and integrity standards.
2. Activities Covered
   • Lead Entry: Creation of new leads from inbound, outbound, or partner sources.
   • Data Enrichment: Adding missing details such as company size, industry, contact role, or intent signals.
   • Opportunity Updates: Recording discovery notes, proposal details, stage movements, and forecast amounts.
   • Account Management: Maintaining accurate organization-wide information including hierarchy, key contacts, and relationship history.
   • Interaction Logging: Documenting calls, emails, meetings, and notes within the CRM for visibility across teams.
   • Data Transfer: Ensuring clean handoff between SDR → AE → Customer Success with no gaps or duplication.
3. Systems Covered
   • The primary CRM platform used by the company (e.g., Salesforce, HubSpot, Zoho).
   • Any integrated tools that push or pull data into the CRM (e.g., Apollo, LinkedIn Sales Navigator, Outreach, marketing automation tools).
   • Data exports, reports, or trackers derived from the CRM for internal use.
4. Applicability Period
   • Applies at all stages of the sales lifecycle — from lead creation to client handoff.
   • Applies to all records created historically and going forward, ensuring continuous data integrity.

3. Definitions

1. Valid Lead Record: A CRM entry that contains complete, accurate, and non-duplicate information about a prospect, including at a minimum: full name, company name, role/title, email address, phone number (if available), and source of acquisition.
2. Mandatory Fields: CRM fields that must be completed before a record can be saved or progressed to the next stage (e.g., Lead Source, Contact Role, Account Name, Deal Value). These are defined and maintained by Sales Operations.
3. Data Integrity: The accuracy, consistency, and reliability of CRM records. A record maintains integrity when it is up to date, free of duplication, and aligned with established data entry standards.
4. Duplicate Record: A CRM entry that represents the same prospect, contact, or account already existing in the system. Duplicates create confusion, misaligned outreach, and inaccurate reporting.
5. Stale Data: Any CRM record that has not been updated with new activity (e.g., calls, emails, notes, stage movement) within a defined timeframe, typically 30–60 days depending on lifecycle stage.
6. Opportunity Record: A CRM entry that tracks a qualified sales pursuit, including details on stage, deal value, expected close date, and associated contacts.
7. Interaction Log: Documentation of any client-facing activity (emails, calls, meetings, demos) recorded in the CRM, providing visibility across the sales, marketing, and delivery teams.
8. Data Enrichment: The process of adding additional firmographic, technographic, or intent-based details to an existing lead or account record to improve qualification and targeting.
9. Ownership Field: The CRM attribute identifying the sales representative accountable for managing the record. This field ensures accountability and prevents conflict of ownership.

4. Policy Statements

1. Accurate Entry: All records must be created with complete and correct information. Placeholder text (e.g., “N/A,” “Test,” “Unknown”) is prohibited unless explicitly allowed in optional fields.
2. Mandatory Fields Completion: No lead, contact, account, or opportunity may be saved in the CRM without filling all mandatory fields defined by Sales Operations. Missing data must be enriched before advancing to the next stage.
3. Timeliness of Updates: All sales activities (calls, emails, meetings, demos) must be logged in the CRM within 24 hours of occurrence. Stage changes, proposal submissions, and deal updates must be reflected immediately.
4. No External Tracking: Sales representatives must not maintain shadow spreadsheets, personal trackers, or offline systems for leads and opportunities. The CRM is the single source of truth for all sales data.
5. Duplicate Prevention: Before creating a new record, representatives must search the CRM to confirm whether the lead, contact, or account already exists. Any duplicate entries discovered must be merged or flagged to Sales Operations.
6. Data Enrichment: Representatives are required to update incomplete lead/account records with additional details (e.g., industry, company size, tech stack, LinkedIn profile) using approved enrichment tools. Enrichment must occur before or at the qualification stage.
7. Ownership Accuracy: Every record must have an assigned owner. Ownership changes may only be executed through the defined transfer process and must include documented reason codes.
8. Activity Logging: All client-facing communications (emails, calls, demos, meetings) must be logged in the CRM using the designated activity fields or integrations. Failure to log activities will be treated as a compliance violation.
9. Opportunity Management: Opportunity records must include stage, expected close date, deal value, and primary decision-maker details. These fields must be updated consistently throughout the sales cycle.
10. Stale Record Handling: Leads or opportunities with no logged activity for more than 30 days must be reviewed by the owner. If inactive for 60 days, records must be closed, recycled, or reassigned following the Lead Management SOP.
11. Restricted Fields: Certain CRM fields (e.g., pricing approvals, discount levels, commission flags) are restricted and may only be modified by authorized roles (e.g., Sales Managers, Deal Desk, Finance). Unauthorized edits are prohibited.
12. Cross-Team Visibility: Notes and updates must be clear, professional, and usable by other departments (e.g., Marketing, Customer Success, Delivery). CRM entries are company property and not private working notes.

5. Roles & Responsibilities

1. Sales Development Representatives (SDRs):
   • Create accurate lead records from inbound and outbound sources.
   • Enrich leads with basic firmographic and contact details before handoff.
   • Ensure all mandatory fields are completed at the time of creation.
2. Account Executives (AEs) / Business Development Managers (BDMs):
   • Maintain and update opportunity records with accurate stage, deal value, and close dates.
   • Log all client-facing activities (emails, calls, demos, meetings) within 24 hours.
   • Ensure enrichment is complete before progressing leads into opportunities.
3. Pre-Sales & Solution Consultants:
   • Document demo notes, solution details, and technical validation outcomes in the CRM.
   • Attach all relevant files or links to the opportunity record for visibility.
4. Sales Managers:
   • Monitor CRM usage and ensure compliance within their teams.
   • Review pipeline accuracy during weekly or monthly sales reviews.
   • Approve ownership transfers and ensure inactive records are recycled or reassigned.
5. Sales Operations / CRM Administrators:
   • Define and maintain mandatory fields, data standards, and validation rules.
   • Manage duplicate detection, merging, and data cleansing.
   • Provide reporting dashboards and conduct periodic data integrity audits.
6. Marketing Team:
   • Ensure campaign-sourced leads are correctly tagged with source and campaign identifiers.
   • Validate that inbound forms are mapped to the correct CRM fields.
7. Customer Success Managers (CSMs):
   • Update CRM records with renewal, expansion, and health score details.
   • Maintain continuity of information during handoff from sales to delivery.
8. Compliance & Legal Team:
   • Oversee that CRM data handling complies with GDPR, CAN-SPAM, and other privacy laws.
   • Investigate reported misuse or unauthorized data entry practices.

6. Governance, Violations & Consequences

1. Governance Oversight: The Head of Sales is accountable for overall governance of CRM usage. Day-to-day enforcement is delegated to Sales Managers, supported by Sales Operations through dashboards, reports, and audits.
2. Monitoring & Audits: CRM records will be reviewed regularly through:
   • Weekly pipeline reviews led by Sales Managers.
   • Monthly data integrity checks by Sales Operations.
   • Quarterly audits to identify duplicates, stale data, and incomplete records.
3. Reporting Violations: Any misuse, inaccurate entry, or data manipulation must be reported to the Sales Manager or directly to Sales Operations. Anonymous reporting can be made through the company’s ethics channel.
4. Examples of Violations:
   • Creating incomplete or inaccurate lead records.
   • Maintaining duplicate records without correction.
   • Failing to log client-facing activities within the required timeframe.
   • Using unauthorized spreadsheets or offline trackers as a substitute for CRM.
   • Manipulating deal stages, values, or dates to influence forecasts.
   • Unauthorized editing of restricted fields (e.g., pricing, commission).
5. Consequences of Non-Compliance:
   • Minor Violations (e.g., delayed updates, incomplete activity logs): Corrective coaching and mandatory retraining.
   • Moderate Violations (e.g., repeated inaccurate entries, failure to enrich data, unreported duplicates): Written warning and negative impact on performance evaluation.
   • Severe Violations (e.g., intentional data manipulation, unauthorized access, falsification of records): Escalation to HR with potential disciplinary action, up to and including termination of employment.
6. Escalation Path:
   • First-level issues are handled by Sales Managers.
   • Repeated or unresolved issues escalate to the Head of Sales.
   • Cases involving regulatory or legal risks (e.g., GDPR violations, privacy breaches) are escalated further to the Compliance & Legal Team.

7. Review & Ownership

1. Policy Owner: The Head of Sales, in collaboration with Sales Operations, is the official owner of this policy. They are responsible for ensuring CRM standards remain aligned with business goals and compliance requirements.
2. Maintenance & Updates: This policy will be reviewed annually, or earlier if there are significant changes to CRM platforms, business processes, or regulatory obligations. Updates will reflect evolving best practices in data management and sales operations.
3. Approval Authority: Any amendments must be approved by Sales Leadership, Sales Operations, and the Compliance Team to ensure cross-functional alignment.
4. Training & Awareness: All sales staff must be trained on this policy during onboarding and attend refresher training after major updates. Managers are responsible for reinforcing best practices in weekly reviews and pipeline meetings.
5. Monitoring & Enforcement: Adherence will be measured through system reports, pipeline reviews, and audit findings. Non-compliance will trigger actions as defined in Section 6.
6. Version Control: Each revision will be logged in the Policy Register, capturing version number, revision date, and approving authority for audit and accountability purposes.

1. Purpose

The purpose of this policy is to establish clear rules for ownership, assignment, and management of leads and territories within the sales organization. Lead ownership disputes and unclear territory boundaries often result in duplicated effort, internal conflict, and poor client experience. This policy ensures that:

1. Accountability is Transparent – Every lead has a single, clearly defined owner responsible for nurturing and advancing it.
2. Territory Boundaries are Clear – Sales representatives know which regions, industries, or accounts they are responsible for, minimizing overlaps.
3. Fairness & Efficiency are Maintained – Leads are distributed using transparent criteria (geography, industry, deal size, account type) instead of favoritism or manual bias.
4. Client Experience is Protected – Prospects are not confused by multiple representatives contacting them, which can damage credibility.
5. Scalability is Enabled – As the company expands, territory and ownership rules remain consistent, measurable, and enforceable.

By defining ownership and territory management, the company enables its sales team to focus on building trust and driving conversions, rather than resolving internal disputes.

2. Scope

This policy applies to all sales employees and representatives involved in lead generation, qualification, and conversion. It governs the assignment, management, and transfer of leads across the sales organization, ensuring clarity and fairness in client engagement.

2.1 Roles Covered

• Sales Development Representatives (SDRs) – Responsible for prospecting and qualifying leads before handoff.
• Account Executives (AEs) / Business Development Managers (BDMs) – Responsible for pursuing owned leads, conducting discovery, and closing opportunities.
• Sales Managers – Oversee territory alignment, resolve ownership disputes, and approve lead transfers.
• Pre-Sales / Solution Consultants – Support lead-specific demos and discussions but do not assume ownership.
• Channel/Partner Representatives – Bound by the same ownership and territory assignment rules when working on company-assigned accounts.

2.2 Activities Covered

• Lead Assignment – Distribution of inbound and outbound leads via CRM or other authorized platforms.
• Territory Definition – Allocation of regions, industries, account segments, or product lines to specific sales representatives.
• Ownership Transfer – Guidelines for reassigning leads due to inactivity, role changes, or management decision.
• Conflict Resolution – Process for handling ownership disputes between representatives.
• Account Protection – Safeguards against duplication of effort when multiple representatives attempt to engage the same lead.

2.3 Geographies & Jurisdictions

• Applies globally across all regions where the company conducts business.
• Territory rules may vary depending on regional business strategies but must adhere to the principles defined in this policy.
• Regional Sales Leaders are accountable for ensuring alignment with this global standard while accommodating local market needs.

2.4 Applicability Period

• The policy applies from the moment a lead is created in the CRM until it is either converted into a client or marked as closed/lost.
• Ownership rules apply regardless of whether the engagement occurs during working hours, industry events, or through digital platforms.

3. Definitions

1. Lead: An individual or organization identified as a potential client, captured through inbound channels (website forms, referrals, events), outbound prospecting (calls, emails, LinkedIn), or partner networks, and entered into the CRM system.
2. Lead Ownership: The official assignment of responsibility for managing and progressing a lead. The “owner” is accountable for qualification, follow-up, opportunity creation, and communication until conversion or closure. Ownership is always visible in the CRM.
3. Territory: A defined segment of the market assigned to a sales representative, which may be based on geography (e.g., Australia, North America), industry vertical (e.g., SaaS, HealthTech), account size (SMB, mid-market, enterprise), or product line.
4. Lead Routing: The process of distributing new leads to representatives based on pre-defined rules such as territory, workload, availability, or specialization. Routing is automated in the CRM where possible.
5. Protected Account: An organization or lead assigned exclusively to a representative or team, protected from reassignment unless formally approved by Sales Management.
6. Ownership Transfer: The process of reassigning a lead from one representative to another, triggered by inactivity, role changes, or strategic reallocation. All transfers must be logged in the CRM with approval.
7. Conflict of Ownership: A situation where more than one representative claims responsibility for the same lead or account. Conflicts are escalated to Sales Managers for resolution under this policy.
8. Lead Lifecycle: The journey of a lead from creation → qualification → opportunity → client conversion, or closure. Ownership rules apply throughout this lifecycle.

4. Policy Statements

1. Lead Assignment: All new leads must be assigned through the CRM system using predefined routing rules (e.g., geography, industry, account size). Manual assignment is permitted only with Sales Manager approval. No lead may exist in the CRM without a clearly defined owner.
2. Territory Boundaries: Each sales representative is responsible for a defined territory (geographic, industry, or account-based). Representatives may only pursue leads within their assigned territory unless explicitly granted cross-territory access by Sales Leadership.
3. Ownership Exclusivity: A lead may have only one primary owner at any given time. Co-ownership is not permitted unless the Sales Manager approves a temporary joint assignment (e.g., for strategic accounts or cross-regional pursuits).
4. Protected Accounts: Once a lead progresses into an opportunity stage or becomes a strategic account, it is automatically classified as “protected.” No other representative may contact or claim the account unless formally reassigned by Sales Leadership.
5. Ownership Transfer: Leads may be reassigned in the following cases:
   • Inactivity by the current owner (e.g., no contact attempt within 10 business days).
   • Role or territory change (e.g., representative leaving the company or moving to a new market).
   • Strategic decision by Sales Leadership.
   • All transfers must be logged in the CRM with reason codes for transparency.
6. Conflict Resolution: If two or more representatives engage the same lead, the dispute must be escalated to the Sales Manager. Resolution will be based on CRM records, date of first contact, and territory alignment. The Sales Manager’s decision is final.
7. Account Re-engagement: Leads previously marked as “closed – lost” or “inactive” may be reassigned after a cooling-off period (default 90 days, unless overridden by Sales Leadership). Re-engaged accounts follow the same ownership rules as new leads.
8. Transparency & Reporting: All lead assignments, reassignments, and disputes must be documented in the CRM. Representatives are prohibited from pursuing leads outside of their official ownership records.
9. Client Experience Protection: At no time should a client or prospect receive outreach from multiple representatives of the company without coordination. Managers must ensure proper alignment before multiple stakeholders engage the same account.

5. Roles & Responsibilities

1. Sales Development Representatives (SDRs): Responsible for creating accurate lead records in the CRM, qualifying leads before handoff, and ensuring ownership is correctly tagged during assignment. SDRs may not bypass routing rules or directly assign leads without manager approval.
2. Account Executives (AEs) / Business Development Managers (BDMs): Responsible for managing leads within their assigned territory, progressing them through discovery and closure, and keeping CRM records updated. AEs/BDMs must respect protected accounts and refrain from pursuing leads outside their territory.
3. Pre-Sales & Solution Consultants: Provide technical and solution support for leads, but do not assume ownership. They must document all contributions in the CRM and work only on leads officially assigned to them by the owning AE/BDM or Sales Manager.
4. Sales Managers: Ensure fair distribution of leads within their teams, monitor CRM records for compliance with assignment rules, and resolve ownership disputes. They have the authority to approve ownership transfers and enforce inactivity-based reassignment.
5. Sales Leadership (Head of Sales, VP Sales, CRO): Define territory structures, lead routing rules, and ownership policies at the organizational level. They approve exceptions (e.g., cross-territory pursuits, strategic joint ownership) and oversee adherence through periodic audits.
6. CRM Administrator / Sales Operations: Maintain the technical setup of lead routing rules, protected account settings, and ownership fields in the CRM. Provide reporting dashboards to managers for transparency on ownership distribution and transfer history.
7. Compliance & Legal Team: Ensure that lead assignment, territory management, and data usage practices align with legal obligations (e.g., GDPR, competition laws). Support investigations if ownership disputes or mismanagement result in client complaints.

6. Governance, Violations & Consequences

1. Governance Oversight: The Head of Sales holds overall accountability for the governance of this policy. Day-to-day enforcement is delegated to Sales Managers, supported by Sales Operations through CRM reporting and audits.
2. Monitoring & Audits: Lead assignments, transfers, and territory compliance will be monitored via CRM dashboards and quarterly audits. Any irregularities (e.g., multiple owners, duplicate outreach) will be flagged for review by Sales Managers.
3. Reporting Violations: Suspected violations such as lead poaching, bypassing routing rules, or contacting protected accounts must be reported immediately to the Sales Manager. Anonymous reporting can be made through the company’s ethics channel.
4. Examples of Violations:
   • Claiming a lead outside of assigned territory without authorization.
   • Pursuing a lead already assigned to another representative.
   • Failing to update CRM records, causing ownership disputes.
   • Reassigning leads manually without manager approval.
   • Ignoring protected account rules.
5. Consequences of Non-Compliance:
   • Minor Violations (e.g., incorrect CRM tagging, delayed updates): Corrective coaching and mandatory retraining.
   • Moderate Violations (e.g., repeated mishandling of ownership, unauthorized contact with protected accounts): Formal warning and impact on performance evaluation.
   • Severe Violations (e.g., deliberate lead poaching, falsifying CRM data, bypassing approved routing to gain unfair advantage): Escalation to HR with potential disciplinary action, up to and including termination of employment.
6. Escalation Path:
   • Initial disputes are reviewed by the Sales Manager.
   • If unresolved, the matter escalates to the Head of Sales.
   • Issues involving regulatory or legal breaches (e.g., competition law, data misuse) are further escalated to the Compliance & Legal Team.

7. Review & Ownership

1. Policy Owner: The Head of Sales is the designated owner of this policy, responsible for ensuring that lead ownership and territory practices remain fair, transparent, and aligned with business goals.
2. Maintenance & Updates: This policy will be reviewed annually or earlier if significant changes occur in sales structure, CRM systems, or market coverage. Updates will reflect evolving best practices, compliance requirements, or organizational needs.
3. Approval Authority: Any amendments to this policy must be approved by Sales Leadership in consultation with Sales Operations and the Compliance Team.
4. Training & Awareness: All sales staff must be trained on this policy during onboarding and receive refresher training whenever updates are released. Sales Managers are responsible for reinforcing compliance during team meetings and 1:1 reviews.
5. Monitoring & Enforcement: Adherence will be tracked through CRM reporting, pipeline reviews, and quarterly territory audits. Consistent non-compliance will trigger disciplinary procedures as outlined in Section 6.
6. Version Control: Every revision of this policy will be logged in the company’s Policy Register, capturing version number, date of revision, and approving authority for full traceability.