Case Study: The IT Person Quit in October. The Holiday Rush Was Weeks Away.
A multi-brand online retailer lost the only person who knew how their technology worked. No documentation, no diagrams, and a network that was down more than it was up.
A multi-brand online retailer lost the only person who knew how their technology worked. No documentation, no diagrams, and a network that was down more than it was up.
No network designs, no server designs, no vendor list. We rebuilt the picture by working backwards from the invoices.
Cut from communications and data center hosting bills, plus licensing nobody was using.
That is what their tickets look like now. Standard help desk requests, not outages.
An online retailer with multiple brands and substantial transaction volume, running distribution warehouses in two Midwest states. We do not publish client names. That is how we protect the people we work for.
Their internal IT person quit abruptly. It was October, right before the holiday rush. The call we got was simple: we need help, we do not know what he did, and we do not know what to do.
There were no network designs and no server designs. Nobody could tell us what the company owned or who it was paying. What we found was an over-engineered, multi-state infrastructure, custom applications written by the person who had just left, and a network that was down more than it was up.
Every team went in at once.
The invoices told the story: numerous vendors, duplicated products and significant overspending.
We met with the client weekly and sent status updates daily. From the start of the Thanksgiving shopping rush through New Year’s Eve, our teams worked around the clock keeping a hosting environment we did not control stable enough to carry their season.
The goal was to get them off a patchwork of non-commercial systems and into Azure, stabilize the environment, and stop the spending nobody could explain. Products and vendors were sitting on autopay on a company card. Accounts payable did not know what they were for. Leadership did not either. They had trusted one person, and he was gone.
They were spending $2K a month on Microsoft 365, and nobody was managing the licensing. Licenses nobody was using just sat there, billed every month.
We are now their Microsoft Cloud Solution Provider and manage the licensing for them, and the bill is down to $1,200 a month. The rule is simple: only pay for what you use. Do not over-order. Do not buy things and let them sit. When someone leaves, the license comes off, so they are not paying for it.
We are now migrating their home-grown applications into cloud applications, so their leadership team and investors can analyze sales data and customer engagement.
As our dev team says: what is the challenge? Let us talk about how other clients use their data, and maybe that gets your team thinking about what you want to see. What one client does is not what the next one will do. That is why it starts with a conversation.
We have been at this since 2007. We have seen a lot that worked, a lot that failed, and a lot that went through ten versions before the client got the result they wanted. On this one we did not falter, we did not walk, and we did not get scared. We pushed through until their technology worked for them, not against them.