logo image

An Intense Weekend Day in the Life of the UBX Cloud Team – When the Client’s Need Is Beyond the Ordinary

The intensity of the challenges we tackle are part of who we are.

UBX Cloud

We love what we do here at UBX Cloud, because we know it delivers great value to our clients – and they tell us constantly how much they appreciate that.

Now anyone can love a day at work when it’s easy. On the rare occasions when we get a day like that, we suppose we soak up the leisure just like anyone else. Then again, it’s hard to remember the last time we had a day like that.

And we don’t really care, even if it happens on a weekend. The intensity of the challenges we tackle are part of who we are, which is why we get into it when a client has an extraordinary need that really demands the best in us.

Here’s how it might go:

8:30 a.m. Company X is concerned about its ERP database given the capacity of its current on-premise environment, and wonders if we can offer more. Of course we can, but there’s more. This company is about to head into a busy production period – literally tomorrow – and is afraid its existing system could be pushed to the limit if something isn’t done.

9:15 a.m. We loop in our team on the ground in India to coordinate with our account pros here in Michigan, and they begin developing a migration strategy. Within two hours, they’ve mapped out a way to fully integrate the new client by first thing Monday morning.

Noon. Our India managing director Mohamed Ali checks in with the project team and asks if they need any help coordinating with our partners to make sure the plan goes forward as designed. The team had every intention of getting to that while multitasking, but gladly accepts the help. The partners are fully brought in to ensure the data capacity is made available.

3 p.m. Our CEO Steven Panovski gets on the phone with the team at Company X and updates them on the progress. They’re worried that if anything goes wrong, they might face disruptions on Monday morning, when they’re going to be under some serious deadline pressure. Although the project is already ahead of schedule, Steven checks in with the team to see if they can relay anything to calm the new client’s concerns.

3:30 p.m. After checking in with the team, Steven gets back to his contacts at Company X and gives them encouraging news: While the team had initially anticipated a 7 p.m. completion time, the current pace of the project now has things on track for 5:30 or 6 p.m.

5:30 p.m. Top executives at Company X remember a detail they had overlooked in their earlier, frantic call. It’s something we can handle but it will take several more hours than we had initially anticipated.

11 p.m. The team in India reports back to Steven. The additional issue is under control and it’s time for final testing of the migration.

3:15 a.m. The client calls Steven again, concerned that the last-minute change from one system to another might cause unforeseen glitches, and wonders if we shouldn’t just put the whole thing off so they can get past their production deadlines.

3:16 a.m. Before Steven can even answer the question, he receives a text from the team in India: Final testing is complete and successful, and Company X is now fully migrated to the UBX Cloud servers, with all storage capacity available and confirmed by UBX’s strategic partners.

Steven assures leaders at Company X that their team can simply proceed as normal, and that he has created a dashboard for them – so they can constantly, in real time, see the state of the server health without having to call and ask about it. The team further customized the dashboard to make it as relevant to their needs as possible.

5 a.m. Steven decides to get some sleep.

5:03 a.m. Steven’s kids have other ideas.

MONDAY: 8 a.m. The team at Company X convenes and gets rolling on one of their most challenging projects to date – without any concern for the stability or security of their ERP database.