What follows is a composite tale stitched from episodes that web teams meet constantly. The people are fictional, and so is the studio, but the pattern will look familiar to anyone who has managed a content management system for more than a year. It follows a small agency, a mid-sized client site and a request that began with the words “we need a plugin.”
The request
The client ran a regional services business with a site of about sixty pages and a blog. Their marketing lead sent the agency a short message: visitors kept abandoning the quote request page, and they wanted a multi-step form with progress indication, plus the ability to save a partial entry. A colleague had recommended a premium add-on for exactly that job. The lead asked the agency to buy and install it.
The project manager, a practical person who disliked surprise invoices, opened the ticket and wrote a single line before assigning it: “Inventory first.” The developer assigned to the task grumbled mildly, because the add-on was only a few clicks away. But she agreed that a short audit would not hurt.
The audit
The developer set aside one afternoon and worked through the CMS in a fixed order. She wrote findings into a shared sheet with four columns: component, purpose, status and notes.
Installed plugins
The plugin list held twenty-three entries. Seven were active and clearly in use. Nine were active with an unclear purpose. Five were switched off. Two were flagged as out of date. Three of the unclear ones looked like leftovers from a campaign two years earlier. She noted each one and traced its purpose through settings screens and the site’s change history.
Theme options and built-in blocks
Next she opened the theme settings and the page editor’s block library. The theme included a form builder panel that nobody had touched. It supported conditional fields and multi-step layouts, but the option was hidden behind a toggle in a section titled advanced layouts. She switched it on in a staging copy and saw the step progress bar appear.
The form tool already in use
The agency had installed a general form plugin for the contact page. Its settings panel had an add-on section, and one of the bundled modules handled multi-page forms with progress. It had simply never been enabled. It also had a draft-saving option. The very feature the marketing lead wanted was sitting there, free of charge, waiting for a checkbox.
Analytics and tracking
She also checked what analytics the site already collected. An old events setup recorded when a form field was focused and when the submit button was pressed. That meant the team could see exactly where visitors left the quote form, instead of guessing. No new tracking tool was needed.
The decision
On Monday the developer presented the sheet in a fifteen-minute call. The project manager asked three questions: which item covered the multi-step form, who maintained it, and what would be left over that still needed buying. The answers were: the bundled module in the existing plugin, the agency itself, and nothing. The premium add-on was dropped from the plan. The agency built the multi-step flow with the tools already on the site, tested it on staging and moved it live the following week.
The marketing lead was understandably curious about the audit itself, so the agency sent a copy of the sheet. It went into the client’s own handover folder, and the lead added it to the page that listed every vendor and subscription behind the site.
What the audit also found
- Two plugins performing near-identical jobs, which the team parked for a later clean-up discussion.
- A licence that renewed in six weeks for a feature nobody used, which was noted for the client’s decision.
- An unused social sharing block that had been loading on every page.
- A forgotten admin account belonging to a contractor who had left, which was raised for the client to review.
None of these were emergencies. Together, though, they turned a vague sense of an untidy site into a short, clear to-do list that the client could prioritise.
Lessons the team wrote down afterwards
- Ask what exists before asking what to add. The inventory took an afternoon; the purchase would have taken longer to evaluate, install and maintain.
- Look in the settings, not just the plugin list. Features hide in tabs titled advanced, add-ons and modules.
- Record the owner of every item. If nobody owns a plugin, nobody updates it.
- Keep the sheet. The next person to touch the site will thank you.
- Review before renewal. A licence is easiest to question before the charge appears.
How this fits with planning a site properly
Stock-taking sits comfortably alongside good planning. If you are about to commission something from scratch, it pays to skim a walkthrough that covers mapping out a company website ahead of the build and the checklist of pages a business site is expected to include. A decent audit then tells you which of those pages and features exist already and which are genuine gaps.
A note on keeping a wider view
The habit travels well beyond web work. Anyone who maintains something that grows by accretion benefits from a list of what is in it. Even outside our field, a blog-style website about robotics operations such as RobotsOps demonstrates how specialist communities keep their own running notes. The lesson for a CMS team is the same: write down what you have, and share it.
A short audit routine you can copy
One more point from the retrospective: the afternoon was only possible because the CMS allowed an export of plugin data and because a staging copy existed. Teams without either should set them up first, since testing a toggle on a live site is how small experiments become outages.
For teams that want to try this on their own site, here is a stripped-down version of what the developer did:
- Export or copy the full plugin and theme list with version numbers and status.
- Open each settings page and note features switched on and off.
- List every integration and third-party script, including analytics and forms.
- List every user account with role and last activity.
- Write the request, then match it against the list before approving any purchase.
The agency in this story did not become cleverer overnight. It simply made visible what it already had, and that was enough to turn a purchase into a checkbox. The next time a request starts with “we need a plugin,” try the audit first. It might save a licence fee, and it will certainly save a few surprises.