{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreid77nt3kkwfov32nnginrezrlbevogvmubfztwsmmhgc3t5k3x3sy",
    "uri": "at://did:plc:kgbf2s4rqirwwntvajrwzlj7/app.bsky.feed.post/3mfcern2zu4t2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreicyeyu6ulboj2pli3ozjq2j4b2kc4we52l3d4xrlr5xbuaryjw7ga"
    },
    "mimeType": "image/png",
    "size": 511236
  },
  "description": "Your tech stack shouldn’t feel like a burden. Learn how to move from overwhelm to intentional design by focusing on workflows, strategy, and measurable outcomes.",
  "path": "/less-tool-more-impact-a-guide-to-the-sales-enablement-tech-stack/",
  "publishedAt": "2026-02-20T15:00:36.000Z",
  "site": "https://www.salesenablementcollective.com",
  "tags": [
    "Pentaho,",
    "the average tenure of a CRO",
    "Sales enablement professionals",
    "a sales methodology",
    "forecasting",
    "the stack meets these criteria",
    "Subscribe now"
  ],
  "textContent": "I'm Nada, and I look after sales enablement, partner enablement, and customer enablement for Pentaho, part of Hitachi Vantara. Over the past 25 years working with major organizations, I've implemented over 15 pieces of tech stack and retired over 20.\n\nThis experience has taught me something crucial: managing the ever-growing, ever-changing world of sales tech stacks requires a fundamentally different approach than most enablement leaders take.\n\n### The VUCA environment\n\nWe're operating in what's known as a VUCA world—one characterized by volatility, uncertainty, complexity, and ambiguity.\n\nVUCA World\n\nIn this environment, agility isn't optional. The statistics bear this out: the average tenure of a CRO in organizations turning below $5 billion annually is just 18 months.\n\nFor those who've been in an organization for five years or more, this likely means working under two or three different CROs, each bringing their own strategy, direction, and preferences. This constant change inevitably influences decisions around tech stack adoption and retirement.\n\nSales enablement professionals often find themselves responsible for the tech stack whether they've formally accepted that responsibility or not. The landscape typically looks chaotic: multiple overlapping tools, some actively used, some abandoned, and some that nobody remembers purchasing or why.\n\nThe expectation is that sellers will work smoothly across 10, 15, or sometimes even 20 different platforms. Yet the reality rarely matches this expectation. Many organizations maintain extensive tech stacks that their sales teams don't consistently use.\n\n### Understanding your tech landscape\n\nThe fundamental question becomes, what am I actually trying to get my sellers to do? This isn't straightforward. Beyond the basics; perhaps Salesforce as a CRM and a sales methodology like Command of the Message, Sandler, or Challenger, the layers multiply quickly.\n\nConsider the question: What handles forecasting? What about call listening and coaching? Where does content live, and how do we measure its effectiveness? Is this internal content for sellers or customer-facing materials? Who creates it? Who ensures compliance?\n\nWorking in data at Hitachi Vantara, where data storage, protection, and integrity are paramount, has reinforced an important truth about AI and GenAI: they're only as intelligent as the data they're fed.\n\nAn enablement tech stack needs optimization, quality data, proper categorization, and alignment with the sales cycle and stages.\n\nThere's always an opportunity to reassess how well the stack meets these criteria.\n\n### This post is for subscribers only\n\nBecome a member to get access to all content\n\nSubscribe now",
  "title": "Less tool, more impact:  A guide to the sales enablement tech stack",
  "updatedAt": "2026-02-20T15:00:36.000Z"
}