MyCarrier: DevOps & Cloud Transformation for Scalable Logistics SaaS

Preview description: We helped MyCarrier move toward cloud-ready DevOps: adapted the system for microservices, implemented CI/CD and test automation, moved workloads to Azure, achieved 99.9% availability, decreased update delivery time to minutes.

Full description:

Problem MyCarrier was growing fast, and the monolithic codebase became harder and more expensive to maintain. It was heavy, resource-consuming, and less suitable for the client’s long-term scaling plans. The team also needed faster delivery processes, but changes in the codebase and cloud migration had to stay unnoticed by users. Their logistics workflows could not be interrupted.

Solution IT Craft aligned the project infrastructure with a microservices architecture and prepared the system for cloud operation. The team started with a technical audit and developed the migration strategy consisting of 20-28 items. The process was divided into pre-migration, migration, and post-migration phases, thus the product could keep running while infrastructure changed step by step.

The team moved non-critical standalone jobs to the cloud, connected virtual machines to Azure Storage Account, moved logging to MongoDB Atlas, and transferred user data and related processes to the cloud. New app functionality was released as microservices. IT Craft also designed and fine-tuned a CI/CD pipeline, automated infrastructure deployments, and reduced update delivery time through regression test automation.

Results · Achieved 99.9% system availability. · Maintained high fault tolerance using three shared clusters. · Reduced update delivery time from hours to minutes. · Enabled Sprint focus changes every two weeks based on client priorities.

Tech Stack: · Azure Cloud · MongoDB Atlas · Azure SQL · Azure App Service · Azure Functions · Azure Storage Account

My recent client is an Australian printing firm.

They already had clients coming in.

The problem was what happened after the agreement.

When a client agrees to payment terms, every delay matters.

A payment process that sits waiting for someone to follow up can slow down the entire client journey. And when clients experience unnecessary delays, it can affect more than cash flow. It can affect their confidence in the business.

So I built an Agreed Payment System in Make.com designed around the client journey.

The goal wasn’t simply to automate emails.

It was to create a process that keeps agreed payments moving, keeps communication consistent, and reduces the amount of manual follow-up required from the team.

The workflow takes the agreed payment process and routes it through the appropriate steps, conditions, and Gmail communications.

The system helps keep the process moving.

And this is where my background in sales development and client retention comes into the automation work.

I don’t look at automation as:

Trigger → Action → Done.

I look at it as:

Lead → Sale → Client → Experience → Retention → Repeat business.

Because getting a client is only part of the job.

You also need systems that make it easy for that client to keep doing business with you.

Sales development + client retention + workflow automation.

That’s the intersection I build around.

The handoff after a client agrees to terms is where many service businesses leak cash flow. Automating follow-up there is a practical B2B wedge because it ties the workflow directly to revenue.