Organizing AI Work Across Your Org

Summary
AI lets sales make its own decks, but someone still has to check the claims and keep the slides current. Start with one thing people already make, and spell out what they can change, which sources to trust, and what needs a review.
By Jenn Steele, President & COO at Heinz Marketing
Tom Swanson and I got together with a few CMOs recently to talk about how they’re organizing AI work. Tom is a senior engagement manager at Heinz Marketing and was my engagement manager back when I was a client. I wanted him in the conversation because he’s good at spotting the parts of a process everybody assumes somebody else takes care of.
The discussion started with a practical problem. When people can make decks and other materials with AI, how does everyone else know what’s current, what’s ready to share with a customer, and where to find it? We talked through shared folders, naming conventions, and how much of the review process you could automate.
The question we kept coming back to was what happens when people can do things they used to come to marketing for. If sales can make its own deck, great. We can all spend less time moving boxes around in PowerPoint. But making the deck was also how marketing found out what sales needed, caught product claims that needed checking, and shared the updated version with the rest of the team. Who does that work when the request stops coming in?
What changes when the request goes away
Say a rep needs slides for a prospect who’s asking about a new product. Before, the request to marketing gave someone a chance to ask what the prospect was trying to do, check what the product could actually support, and notice that three other reps had asked for the same thing. Now the rep can make the slides and send them before marketing knows there was a question.
We want that rep to be able to move quickly. We also want the next rep to benefit from whatever the first one figured out. If they both start from scratch, we get two decks, two versions of the answer, and no reason for anyone to fix the original material. That’s how a faster task turns into more work for everybody.
This is where Tom brought up governance. Get sales and marketing in a room and decide what sales can change on its own, what needs a review, and who keeps the source material current. Swapping in a prospect’s name? Go for it. Making a new product claim? Give the rep someone who can check it.
That person needs to know what they’re checking and how to get the answer back to sales. Otherwise you’ve recreated the original bottleneck, except now the rep has a finished-looking deck and a very good reason to hit send. This is the sort of handoff we look at in our marketing orchestration work.
Tom suggested two shared folders, one for review and one for approved material. Here’s how that could work for a sales deck.
- Send it for review. The rep puts the draft in the review folder. A scheduled task can flag new files.
- Check the draft. The reviewer checks new product claims, links, and branding.
- Share the approved version. The reviewer moves the deck to the approved folder and tells the rep where it is.
An approved folder helps until it’s full of files called “Final,” so you should probably have another system to help with that. Name files the way people search for them. If you use a skill to make decks, build the naming convention into it. If you need an index, start with the link, the owner, and the last review date. If you need folder structures, make them.
The review folder gives sales a place to go when a claim needs checking. When AI is doing some of the work, you also have to tell it which decisions to make before anyone sees a draft. I ran into the AI decision-making process with the proposal generator I built here.
What I had to teach our proposal plugin
I built a Claude plugin to help us make proposals at Heinz Marketing. I tell everyone to type “proposal for [client name]” to get it started. What do I do personally? I babble at Claude and attach a transcript (luckily, it usually figures out what I need and fires the plugin).
When we attached a transcript, Claude made a proposal. The trouble was that the proposal generator was the only tool we’d built for working from a sales call transcript. We’d use Claude when we wanted help brainstorming or putting together recommendations from a call, too. And out came a proposal. Not great all the time, and we had a lot of weird and random proposals.
So I made a change. Now the plugin reads the transcript before it decides what to make. Sometimes that’s a proposal. Sometimes it’s a brainstorming doc or a set of recommendations. The call gives Claude the guidance, and the multiple skills in the plugin handle it from there.
When the transcript does call for a proposal, Claude has more decisions to make. It might find one price in an old proposal and another in the current guide (conveniently included in the plugin). I tell it which source wins. “Use the current pricing guide. If you can’t find it in the guide, ask me.” That gives Claude a way to handle both situations without guessing.
The pricing guide tells Claude which numbers to use. The plugin runs discount calculations with a script and also uses a skill and process to check the claims against their sources (because sometimes LLMs are going to LLM). Then one of us reads the whole proposal before it goes out. We’re the ones making the promises, so we get the last word.
Start with one thing people already make
Tom’s advice on how to get started is this: Pick something people used to ask marketing for and now make themselves. Pull up a real example with the person who made it and ask what marketing used to handle.
- Where did the facts come from? Put the current messaging in the same place as the template people already use (or put it into a plugin, skill, agent, or whatever today’s trendy word is for where folks are working with AI).
- What did they change or have to guess? If reps keep making their own version of the same slide, give them one they can use.
- What happened to the draft? Make clear when someone needs a review and where to send the draft. Show the workflow at a meeting sales already attends and have them pin the link.
If you’re setting this up in Claude, pick the tool based on what people need.
- Project Keeps reference material together, like the current messaging and approved claims.
- Skill Handles a repeatable task, like formatting a document.
- Plugin Brings several skills and reference files together, as we do for proposals.
Then watch what happens the next time somebody needs a deck. If they Slack marketing to ask which version to send, find out what they couldn’t tell on their own. If they just… send stuff without marketing, check whether they had the resources they needed once you calm down a bit.
We want people to be able to do work they used to have to wait for, yes. But we still want to maintain brand consistency and whatever sanity we have left. For that to work, marketing has to spell out the decisions we used to make inside the department along the way, so other people (or LLMs) can make them, too. Then we can spend less time making the fifth version of a deck and more time figuring out what the brand should be saying in the first place.
If you want to talk through where this is getting messy on your team, let us know; Tom says he’s always game: Acceleration@heinzmarketing.com



