Every managed IT client should get more from their provider than fast ticket responses. The review meeting is where that happens, and it is also the easiest thing for a busy provider to let slide. We built software to make sure we do not.
What is a technology business review, and what does our app do?
A technology business review is a recurring meeting where we walk a client through the state of their technology and what should happen next, and our app is the system that schedules, prepares, and records those meetings. Instead of rehashing tickets, the review covers things an owner or office manager needs to plan around: who still lacks multifactor authentication, whether backups are succeeding, which computers are aging out, what licenses are going unused, and what the next few years of replacements will cost.
The platform handles the work around that meeting. It keeps a review rhythm for every client and shows which ones are due or overdue. It gives each client a health score from 0 to 100. It builds the client report, a multi-year technology roadmap with budget projections, and the supporting Excel workbook. It also keeps a log of calls, emails, and visits, so we can see which accounts have gone quiet.
Why did we build a review platform instead of buying one?
We built it because preparing each review was taking us hours, and the data needed to fix that already sat in a database we own. We previously used AuditForIT for our reviews. The tool itself was fine. The problem was everything that had to happen before we opened it: someone had to go into each of our systems, collect the numbers for that client, and compile them into the report. Multiply a few hours of gathering by every client on a review schedule and the preparation crowds out the conversation the review exists for.
Meanwhile, W!FE, the workflow platform we built, was already pulling information from our monitoring, Microsoft 365, security, backup, and licensing tools into one central place every night. A review tool that reads that data directly did not need a new set of integrations. It needed a good application on top.
We did look at the other commercial options. In July 2026 we compared our platform against ScalePad Lifecycle Manager, vCIOToolbox, and myITprocess, which are well regarded tools sold to IT providers for exactly this job. They cover scorecards, review scheduling, and roadmaps well. What we wanted on top of that was specific to us: a health score weighted the way our leadership ranks risk, relationship history sitting next to technical data, and a roadmap we control. This is the same buy or build question we walked through in what it takes to replace a SaaS subscription with custom software, and here it came out in favor of building.
What does the review platform do that the alternatives did not?
It puts the technical picture and the relationship picture on one screen, using our numbers and our rules. Four things stand out in daily use.
- Our own scoring model. Multifactor authentication coverage and backup success carry the most weight, followed by aging hardware, the security stack, and supported operating systems. Scores sort clients into Healthy, Watch, and At Risk, so attention goes where the data points instead of to whoever called most recently.
- Honest gaps. When we do not have verified data for a metric, the app shows it as not available. It never shows a zero, and missing data never drags a score down.
- History that came with us. We imported more than 220 past reviews from our archive, so the date a client was last reviewed reflects the real relationship, not just activity since launch.
- Guardrails on the data. If a nightly refresh shows an implausible swing across the whole client base, the app rejects it and keeps the last good numbers.
The platform also drafts with AI. It can write an executive summary or an email to a client from that client’s actual review data. Every draft goes to the account manager to edit, and nothing reaches a client without a person approving it.
How was the review platform built?
It was built in phases by the person who runs our reviews, working with Claude as the coding partner. That matters more than the technology. The person who knew the process best described what the software should do, phase by phase, and reviewed what came back. The first phase, covering review rhythm and the review lifecycle, was finished in early July 2026, and the platform went live in Azure that same month. It has grown steadily since.
The stack is deliberately ordinary. It is an ASP.NET Core application with a Bootstrap interface, an Azure SQL database, and Azure App Service hosting. Our team signs in with the Microsoft 365 accounts they already have, the same approach we describe in internal apps with Microsoft 365 single sign on. The app connects to its database without a stored password, updates deploy through GitHub Actions, and the repository carries several hundred automated tests covering scoring, scheduling, and report generation. If you want to see the general pattern of putting an application on top of data you already have, we cover it in turning a database into a dashboard with AI.
When does a custom build like this make sense for another company?
It makes sense when the process is specific to how you operate, the data already exists in systems you control, and someone will own the software after launch. All three were true for us. Our review process is part of what we sell, our data was already centralized, and we maintain software for a living.
The same test applies to a manufacturer in Houston tracking job quotes in a shared workbook, or a professional services firm in DFW managing client renewals from a calendar and a folder of documents. If the process is yours alone, the information is already yours, and the gap is an application that ties it together, custom software development is now a realistic option for a company that could not have justified it a few years ago.
When should you buy instead?
Buy when a product already matches how you work, when your data is scattered across systems with no central home, or when nobody will maintain the software after it ships. The commercial review tools we compared against are good products, and a provider without a central data store would be better served by one of them than by a build.
Software is never finished. Ours has changed almost every week since launch because the people using it keep finding better ways to run a review. That is a benefit when you have an owner for it and a liability when you do not. If you are not sure which side of the line your process falls on, book a discovery call and we will walk through it with you.