ACTIDESK
Glowing cyan document outline standing out sharply from faded, overlapping older versions in the dark background

Marketing Updated the Pitch Deck. Half Your Reps Still Have the Old One.

Rodney Hall, COONovember 18, 2026

A prospect notices an outdated price, a discontinued feature, or a logo from two rebrands ago faster than you think, and it reads as carelessness, not a clerical slip. Sales materials go stale because nobody owns keeping them current, not because reps are careless. Fixing it takes a named owner, a refresh cadence, and one live version reps can't accidentally override with an old copy.

Why do reps keep sending outdated materials?

Reps send old decks because the version on their desktop feels more reliable than hunting through a shared drive for the current one. Once a rep downloads a brochure or pricing sheet, that file becomes their personal source of truth, regardless of what marketing changes afterward. One breakdown of the problem is blunt about how this plays out in practice: every sales team has had the moment where a rep sends a prospect a deck with last year's pricing, and nobody's happy about it because the rep didn't know there was a newer version.

This is not a motivation problem. It is a structural one. Research into why reps avoid marketing-provided content found that outdated product brochures, conflicting pricing sheets, and redundant one-pagers confuse both reps and buyers. When three versions of the same deck exist across a drive, a rep's own device, and a sales enablement tool, there is no way to guarantee which one lands in a prospect's inbox.

The gap between creating new collateral and retiring the old is where the damage happens. A detailed look at centralizing content put it plainly: when reps pull content from wherever they happen to find it, they're often pulling outdated versions, including the pitch deck from before the product rebrand. The refreshed version marketing shipped last quarter does nothing for the prospect if the rep working that deal never got the update, or got it and kept using the old file out of habit.

Who should own making sure prospect materials stay current?

Every asset a rep sends to a prospect needs one named person responsible for noticing when it goes out of date, not a department, a person. Teams that solve this well assign ownership at the asset level rather than the team level. One guide to organizing collateral recommends you assign an owner to every asset whose job includes flagging it when something changes, like pricing, features, or a case study client that's churned, and keep only one live version per asset.

That single detail, one live version instead of several archived copies floating around, is what actually prevents the problem rather than just cleaning it up after the fact. A separate analysis of collateral mistakes names the failure mode directly: no version control means reps find an old case study, share it with a prospect, and the pricing on page three is two years out of date. Nobody decided to send stale information. The system simply had no mechanism to stop them.

Manufacturing teams, where specifications and pricing change on an engineering schedule rather than a marketing calendar, have had to solve this more deliberately than most. One guide to enablement in that industry recommends you connect every product change to collateral directly, noting that teams should connect engineering changes to a review of sales content, then publish approved materials and retire older versions. If you sell into manufacturing or run a technical sales process yourself, the same discipline of tying content updates to the moment the underlying facts change, not to whenever someone remembers, applies directly. You can see how that looks in practice on ActiDesk's manufacturing page.

What a stale deck costs you that a spreadsheet won't show

The cost of an outdated deck rarely shows up as a single lost deal you can point to. It shows up as a prospect who quietly trusts you a little less without saying why. One frank account of this dynamic calls the result a "Frankendeck," and describes how a sales team can end up with over forty versions of a standard company overview, with prospects receiving conflicting pricing tiers and outdated product features because reps didn't trust the official repository.

That distrust runs in both directions. Reps stop trusting the official library because it is slow to update, so they build personal copies to feel safe, and those personal copies are exactly what reaches prospects with last year's numbers on them. The fix is not telling reps to check the drive more carefully. It is removing their ability to have a wrong copy at all.

This is part of why a static file is the wrong format for anything a prospect will actually open. A PDF downloaded in January does not know your prices changed in March. A page that lives in one place and updates in place does. Centralized platforms built around this idea are explicit about the mechanism: centralized version controls help publishers retire outdated materials with ease and distribute accurate messaging as product offerings change. That is the structural difference between a file a rep can hoard and a link a rep can only ever point to the current version of.

This is the same reasoning behind building every prospect-facing page through a single, trackable template rather than a library of files reps keep on their laptops. When pricing, case studies, or product details live in a prospect page every rep builds from the same current source, an update to that source reaches every open deal at once. Nobody is sending last quarter's numbers because there is no copy of last quarter's numbers sitting anywhere to send.

Building a refresh habit that doesn't quietly stop

Most collateral cleanups fail not because nobody tries, but because the effort doesn't survive past the first fire drill. One account of this cycle is uncomfortably familiar: a rep gets caught using an outdated case study in front of a prospect, someone notices, and there's a scramble to clean up the library that lasts a week and then quietly stops until the next embarrassing moment. A cadence only works if it is scheduled, not triggered by embarrassment.

A simple structure holds up better than a heroic one-time audit. Three habits cover most of what matters:

  • Assign a named owner to every prospect-facing asset, someone whose job includes noticing when a price, feature, or client reference changes.
  • Set a fixed review date, monthly for anything touching pricing or competitors, quarterly for everything else, and put it on a calendar rather than hoping someone remembers.
  • Keep exactly one live version of each asset so there is nothing outdated sitting in a folder for a rep to grab by accident.

None of this requires new software to start. It requires a decision about who owns what and a date on a calendar that actually gets kept. Where it helps to have a tool is in making the "one live version" rule automatic rather than a matter of discipline, which is where a centralized, editable prospect page earns its place over a shared drive full of PDFs.

If your team is still sending decks as attachments, the fastest way to see the difference is to watch what happens when a prospect opens something built to update in place rather than something somebody downloaded weeks ago. You can see that in action by trying a live prospect page you can set up ahead of your next meeting and updating once, instead of chasing down every rep who still has the old file.

The underlying point is not about tools. It is about trust. A prospect who spots an error forgives it once. A prospect who spots the same kind of error from a second rep starts to wonder what else in your pitch they shouldn't take at face value. Keeping materials current is less about polish and more about not giving them a reason to ask that question.

Further Reading

Get Started →