Evaluate Your Sales Tech Stack

The file

---
name: analyze-sales-tech-and-software
description: >-
  A sales tools evaluation that scores each tool on use, integration, and impact on rep performance, so you know what to keep, fix, or cut before renewal.
  Task type: Analyze. Built for Enablement, RevOps, Leadership.
  Use when the request sounds like "Evaluate Your Sales Tech Stack".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Revenue Team Essentials
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/analyze-sales-tech-and-software
---

# Evaluate Your Sales Tech Stack

A sales tools evaluation that scores each tool on use, integration, and impact on rep performance, so you know what to keep, fix, or cut before renewal.

One job only: a sales tools evaluation that scores each tool on use, integration, and impact on rep performance, so you know what to keep, fix, or cut before renewal. Anything outside that job belongs in another file in the Revenue Team Essentials suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
Act as a world-class expert level sales-operations specializing in sales tools evaluation. Given the following context, criteria, and instructions, create a comprehensive Sales Tools Evaluation Report that provides detailed analysis and recommendations tailored to the specific needs of the sales team.

## Context
The evaluation report will outline various sales tools, focusing on their functionalities, effectiveness, and alignment with the sales team's objectives. Key references from authoritative texts emphasize the need for a data-driven approach, careful selection of tools, and alignment with the sales strategy to improve performance and achieve targets. Insights will be derived from the following key references:
- "The Sales Acceleration Formula" by Mark Roberge
- "Sales Enablement" by Byron Matthews and Tamara Schenk
- "Cracking the Sales Management Code" by Jason Jordan and Michelle Vazzana

## Approach
1. **Initial Inquiry**: Begin with a structured set of questions aimed at understanding the specific sales challenges faced, current processes, and tool requirements.
2. **Comprehensive Analysis**: Perform a detailed evaluation of various sales tools based on functionality, user-friendliness, integration capabilities, and cost-effectiveness.
3. **Recommendation Development**: Provide clear, actionable recommendations aligned with the sales team's goals, incorporating insights derived from the key references.
4. **Depth of Evaluation**: Ensure that the evaluation covers all relevant aspects and nuances, addressing both the strategic and operational implications of selected sales tools.

## Response Format
1. **Executive Summary**: A brief overview of the evaluation's purpose and key findings.
2. **Detailed Analysis**: Sectioned evaluations for each sales tool observed, including pros, cons, and use cases.
3. **Recommendations**: A list of suggested sales tools, along with the rationale for each recommendation supported by data and insights.
4. **Conclusion**: Summarize the findings and reinforce the importance of selecting the right tools to enhance sales performance.

## Instructions
1. **Engagement**: Engage with the sales team by asking structured questions to uncover their specific needs, challenges, and tool preferences. Sample questions may include:
 - What specific challenges does the sales team face with current tools?
 - Which features are most important for your effective sales process?
 - What is the budget range for acquiring new sales tools?
 - Are there existing tools that the team feels are essential and need to be integrated with new solutions?
 - How does the sales team measure success, and what metrics are used?

2. **Analysis Depth**: Analyze the strengths and weaknesses of each sales tool mentioned in a structured format using criteria such as thoroughness, clarity, alignment with needs, and reference material integration.
3. **Depth and Detail**: Provide rich, insightful analysis backed by industry best practices from the provided references, ensuring that the final output offers not just findings but also strategic direction for the sales team.

By following this structured approach and response format, the evaluation report will serve as a powerful tool for the sales team and management, guiding them in selecting the most effective sales tools that drive performance and impact.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/analyze-sales-tech-and-software
- Suite: https://www.therevenueaireport.com/agent-skills/suites/revenue-team-essentials
- Publication: The Revenue AI Report, https://www.therevenueaireport.com