Ask a mid-size PM/CM firm how many software seats it pays for, and you will usually get a pause. Then a guess. Then someone offers to "pull the invoices."
That pause is the problem. Not because anyone is careless, but because seats pile up the same way project files do: one reasonable decision at a time, with nobody assigned to go back and clean up.
This post is about how that happens, why it is harder to fix in AEC than in most industries, and a practical way to keep it under control without turning your IT lead into a full-time license auditor.
How seats pile up in a project-based firm
AEC firms do not buy software once. They buy it project by project, person by person, and owner by owner.
A few common patterns:
- A project needs a tool. The owner requires a specific PMIS, document control platform, or scheduling tool. The team gets seats. The project closes. The seats stay.
- Someone leaves. Their email gets shut off, but the design, PDF markup, or scheduling license tied to their name keeps renewing.
- Someone changes roles. A project engineer becomes a PM and picks up new tools, but nobody removes the ones they no longer open.
- A pilot never ended. A team tried a new collaboration or AI tool, a few people kept using it, and the subscription quietly moved from a trial to an annual plan.
- Two tools do the same job. One office standardized on one platform, another office on a different one, and both renew.
None of these are bad decisions on their own. Together they become a line item that grows every year and that nobody can fully explain.
Why this is harder in AEC than it looks
In a typical office business, software is a fairly stable list. In a PM/CM or AEC firm, it changes with the project mix.
Owners dictate tools. A public agency may require one PMIS, a private developer another. Your team adapts, and so does your license count.
Staffing flexes. Field staff, inspectors, and project engineers move between jobs, and some are seasonal or contract. Access needs change faster than anyone updates a spreadsheet.
Purchasing is spread out. Some seats are on the IT budget. Some are on a project budget. Some are on a corporate card from a PM who needed it that week. Finance sees the spend, IT sees part of the access, and the project team sees what they use. Nobody sees all three at once.
Renewals arrive at random. Annual plans renew on whatever date they were first bought. Without a calendar, the renewal shows up as a charge, not a decision.
That is why "pull the invoices" never quite answers the question. Invoices tell you what you paid. They do not tell you who is using it.
What the work looks like today
At most firms, a license review happens when something forces it: a budget cycle, a big renewal notice, or a CFO asking why the software line went up again.
The usual process goes something like this:
- Someone in IT or finance exports invoices and vendor admin lists.
- They build a spreadsheet of tools, seat counts, and costs.
- They compare named users against the HR roster to find people who left.
- They email PMs and department leads to ask who still needs what.
- They wait. They follow up. They wait again.
- They cancel a handful of obvious seats and promise to do a deeper review next quarter.
It is slow, it is manual, and it depends on one person carrying the context in their head. By the time the review is done, a few new seats have already been added.
What changes with a regular, lightweight review
The goal is not a one-time cleanup. It is a clear picture of what the firm pays for and what it uses, kept current and reviewed on a schedule.
Here is what that looks like in practice.
One list, not four
Bring together what you pay for, who has access, and when each plan renews. That means the vendor admin consoles, your identity and directory system, and the invoices or card statements finance already has. The point is a single view where every tool has an owner, a seat count, a cost, and a renewal date.
Usage, not just assignment
A seat assigned to someone is not the same as a seat used by someone. Many platforms report last sign-in or activity. Where they do, the review can flag seats with no recent activity so a person can decide whether to keep them.
Tie access to people events
Most of the leak starts with a change: a hire, a departure, a role change, a project closing. When license cleanup is part of offboarding and project closeout, it stops being a quarterly scramble. The person leaving or the project ending becomes the trigger, not the invoice.
Renewals as decisions
Put every renewal on a calendar with enough lead time to ask, "Do we still need this, and at this size?" A renewal that gets a decision is very different from a renewal that just gets paid.
A human makes the call
This is where AI helps and where it should stop. Pulling lists together, matching names to the roster, flagging inactive seats, and drafting the "do you still need this?" note to a PM is grunt work that software handles well. Deciding to cancel a seat is a judgment call. A PM may need a tool twice a year for a specific owner. A principal may want a license kept for a pursuit next month. The review should surface the facts and leave the decision with the people who know the work.
Where AI does and does not help here
It is worth being honest about the limits.
What works well:
- Combining exports from different systems into one view.
- Matching named users to current staff and spotting departures.
- Flagging seats with no recent activity, where the vendor provides that data.
- Drafting reminders and summaries so the review takes an hour, not a week.
What still needs people and care:
- Data quality. Some vendors do not expose usage data, or only expose it on certain plans. Some seats are shared or tied to generic accounts. Those need a human look.
- Integrations. Not every tool connects cleanly. Some lists will still come from a manual export, at least at first.
- Security. License and user data is sensitive. Access to admin consoles should stay tight, and any automation should use the least access it needs.
- Context. Only your team knows which tools are required by a specific owner contract, or which "unused" seat belongs to someone on leave.
A good review process respects all of that. It removes the hunting and the spreadsheet building, and it keeps the decisions with your people.
Why this fits an embedded IT model
Most mid-size firms do not have someone whose job is to watch software spend. The IT lead is handling tickets, onboarding, security, and whatever broke this morning. A license review is always important and never urgent, so it slides.
This is the kind of work an embedded IT partner can own as a running program instead of a yearly project. At InstinctIQ, IT oversight is part of how we work with PM/CM firms through IQ-IT, alongside an AI-first help desk that takes repetitive Level 1 and 2 requests off your team. Because we embed with your operations first, we learn which tools your owners require, how your projects staff up and wind down, and where purchasing actually happens. Then we build the review around that, rather than handing you a generic dashboard and asking you to change how you work.
We will not promise you a savings number before we have seen your list. Every firm's mix is different, and the honest answer is that you do not know what you are leaking until you look.
A useful next step
You do not need a big program to start. Try this:
- Pick your five most expensive software subscriptions.
- For each one, write down the seat count, the renewal date, and who owns the decision.
- Compare the named users against your current staff list.
If that takes more than an afternoon, or if you cannot find the renewal dates, that is a good sign the rest of the list deserves a closer look.
If you would like a second set of eyes, talk to us about one time-consuming IT workflow at your firm. License reviews are a good place to start: small, concrete, and easy to measure.
Ready to simplify IT and CMMC?
Join hundreds of AEC teams already saving hours every week.