Champion the tools you already have
It is more likely than not that AI is already inside your company in one way or another. It often shows up as a lightweight Copilot subscription, or inside software the company already uses that has since built in its own AI tools (HubSpot AI, Apollo AI, Figma Make and so on). This is rarely the best way to bring AI into your processes, but it is a real opportunity for people who feel their company is falling behind to take ownership and “champion” the technology.
What it looks like
At Accord, we are currently working with the sales team of a UK events company. Leadership there has asked everyone to spend an hour a week finding ways to use AI and to report back. The tools to act on it were already in the building: a Copilot subscription, likely bundled into a wider Microsoft plan and so not a real extra expense, and an Apollo account with a large balance of credits. Apollo even had its own AI built in, but it was running on defaults: the AI-written content was auto-filled and generic, and the personas feature had never been set up.
The sales lead we are working with saw the chance to combine the two. We took a copy of one of the team’s sequences and ten contacts from its list, and added an enrichment column in Apollo, with its prompt worked out in a Copilot chat that knew the company’s context. The line in the email saying that leaders from X, Y and Z are coming now names the three or four attending companies that best fit each contact’s industry and website, rather than the same names for everyone. None of it has been sent yet. This first version exists to be shown internally, and that is the point. Tools like these, floating around a business with no real owner, give the employees who are forward-thinking and proactive the chance to champion the technology with something tangible to show for it.
What changes
When someone in the team takes the lead and presents a real proof of concept, leadership is forced to make a decision about AI. It has to become more intentional about what the company invests in and who is put in charge of the technology, rather than leaving it as a floating entity that no one really owns. A proof of concept built in tools the company already pays for is hard to argue with: it cost nothing extra, and it is good enough to show what a proper version could do. That is usually what gets budget and attention moving, not a slide about AI strategy.
Being the champion is not the same as doing free work for a company that is falling behind. When the decision does come, it tends to land with whoever showed the thing working first, and that person ends up owning the work, the budget conversation and the relationship with whoever is brought in to help. The skill also travels. Knowing how to take a tool someone else bought, give it the context it was missing and put a working result in front of leadership is worth more in the next role than in the current one. The people who wait for a plan from above usually end up working inside someone else’s.