At a program and construction management firm, project teams stopped waiting on the ticket queue and started asking the portal. We went through the chat logs to see what really changed, and where the assistant still falls short.
In project delivery, a lost hour is rarely just an hour. A scheduler waiting on a laptop, a project engineer locked out of a shared folder, a new hire without an account on the day a job kicks off: each one slows a team that is already working against a milestone.
One evening, an employee on a project team opened the company IT portal and typed that automatic email signatures had stopped working in Outlook. The portal's AI assistant confirmed which signature tool the company uses, walked her through the first fixes, and passed the case to the IT team with the details already filled in. A little later, she wrote back: it was working.
Nobody puts moments like that in a quarterly report. That is exactly why we went looking for them.
Why we counted stories, not chats
The firm is an architecture, engineering and construction (AEC) program management company, with schedulers, project controls staff, project managers and a corporate team supporting them. It runs IQ-IT, the InstinctIQ platform for IT operations and CMMC compliance management, and an AI assistant is built into the same portal employees already use to request help.
Over about three months we went through the assistant's chat logs, with a simple rule: a conversation only counted if the assistant answered or acted on a real request in a way that plausibly saved someone time. Greetings, thank-you messages, refusals and conversations where the assistant did not help were left out. Repeat requests were merged.
What was left was 119 stories, adding up to about 29 hours of time saved.
That figure is an estimate, and we want to be plain about it. Nobody was timed with a stopwatch. Each kind of win, such as a how-to answered without a human, a ticket written up from a short request, or a data lookup, gets a fixed, deliberately conservative time value, and we added them up. Waiting time is not counted, so the real number is probably higher. It is a floor we can defend.
New hires, interns and project staffing
AEC firms staff up and down with the work. A new scheduler starts on Monday, an intern joins a project team, a temporary account is needed for someone helping with interviews. Each of those is a small pile of requests: an email account, access to the right project folders, the right licenses for design and project accounting tools.
The assistant turned those piles into complete tickets. A manager typed who was starting and when, the assistant asked for the missing details, such as title, device needs and which folders the person would need, and logged one clear request. When the same person later could not get into the project accounting tool or a creative app, the assistant noticed the missing license and updated the original ticket instead of starting a new one.
The tickets nobody had to write
Across the quarter, the single most common thing the assistant did was turn a vague sentence into a complete helpdesk ticket.
That sounds small. Anyone who has worked a helpdesk knows the cost of "my computer is slow" arriving with no device, no screenshot and no availability. The assistant asks the follow-up questions a good technician would, attaches the screenshot, notes whether the person holds the needed license, and links related tickets. For a team that lives in large design files and project schedules, that detail is often the difference between a fix on the first try and a week of back and forth.
Technicians used it too, asking it in a short sentence to create a ticket on behalf of a colleague and getting a complete ticket back to confirm instead of clicking through a form.
A full offboarding from a single sentence
One story stands out: an offboarding.
When a project winds down or someone leaves, access has to be cut cleanly, especially at a firm that handles sensitive project data. A staff member who handles personnel changes typed a single line into the portal: she could go ahead and terminate a departing employee's access. That was it.
The assistant built the full offboarding request, with the departing employee's details and the mailbox handling it asked for, showed it back to her for confirmation, and submitted it when she said yes. No form, no email thread, no checklist left half done. For a compliance-minded firm, it also meant offboarding was recorded the same way every time.
Fixed without waiting for a technician
Several of the best stories ended with the employee confirming the fix themselves.
One employee's Teams camera stopped working. The assistant reopened his previous ticket to keep the history together, walked him through troubleshooting, and he confirmed the camera worked, without waiting for a technician.
Another employee whose cloud file sync kept failing got step-by-step help in the chat, tried it, and confirmed it was fixed. An employee setting up meetings for a new compliance project asked how to record them in Teams. The assistant explained where the option appears and suggested a quick solo test. No ticket needed.
Doing the work, with judgment
The assistant does more than answer questions. With approval, it carries out IT actions.
Project work runs on outside partners: owners, subconsultants, engineering and design partners. When the firm needed a Teams workspace for an outside partner, the IT team asked in plain language for the team, a project lead as owner, the external guests and read access to a project folder. The assistant did all of it in a single conversation. Just as important, it refused to grant folder access until the guests actually existed in the company directory, then finished the job once they did. That is the behavior you want from anything allowed to touch permissions.
The IT team also stopped pulling device enrollment reports. They asked who was still pending and got the list in one sentence. When the numbers looked stale, they asked the assistant to sync with Microsoft, and the corrected status showed up on the spot.
Compliance without the scavenger hunt
Clients in this industry increasingly expect their contractors to prove their security posture, and CMMC is where that conversation lands. For the firm's security lead, the assistant became the fastest way to answer recurring compliance questions: how many licenses are assigned and free, which employees have a managed laptop and which are enrolled, and where the CMMC program stands today.
It also took on the small chores that make audits painful when they slip. A suspicious email became a security ticket with the screenshot attached. Employees justified their use of a file-sharing tool through the assistant, which recorded each answer so nobody had to chase them. A social media post was logged for a controlled information review.
Where it fell short
We looked at the failures as carefully as the wins, and there were some.
The assistant can grant SharePoint access and take it away again, both for a single site or folder while someone stays with the company, and across the board during an offboarding, where disabling the account and clearing every group membership closes all the doors at once. The edge cases are the ones SharePoint itself makes tricky: standalone sites that keep their own internal permission groups, access inherited from a broad security group, and tenant-wide sharing links. Those still call for an admin in the SharePoint admin center. Removing an external guest completely is also still a manual step, and it declines to answer headcount questions about Teams membership. A plain "confirmed" reply was sometimes treated as a brand new request instead of approval, which created duplicate tickets someone had to tidy up.
Some problems simply need hands on a keyboard. A stubborn cloud storage problem stayed open until a person stepped in. The assistant logged it well, but it could not fix it. By design, it also does not buy licenses or grant mailbox access. It writes the ticket and flags what is missing.
These are the gaps we are working to close, starting with smarter confirmations and cleaner handling of external guests.
What the numbers mean
About 29 hours across 119 stories is not a headline about replacing an IT team. It is a picture of where small amounts of friction add up: the ticket nobody had to retype, the answer that arrived without a wait, the new hire request that arrived complete, the offboarding that got done properly because it was easy.
The bigger change is harder to put in a spreadsheet. Project teams started treating IT as a conversation instead of a queue. The IT team spent less time collecting information and more time fixing things. The security lead answered compliance questions in one conversation instead of opening admin consoles.
See it in your own portal
If your IT team spends its mornings decoding vague tickets, or your compliance work depends on data scattered across admin tools, we would like to show you what this looks like with your own requests. Learn more about IQ-IT and book a walkthrough at instinctiq.ai.
Ready to simplify IT and CMMC?
Join hundreds of AEC teams already saving hours every week.