How Small IT Decisions Create Big Business Profit

Before I moved to Saudi Arabia, I was already working as a DevOps engineer in India. I thought the transition would be simple. Same skills, new country.

Instead, I joined Code7 and my first task was aligned with IT administration, not DevOps.

I will be honest, it stung a little.

The Month I Did Not Plan

I had already proven myself in DevOps. Pipelines, environments, deployments, the work I had spent years getting good at. Now I was starting with IT admin work for my first month, and every instinct told me I had taken a step sideways at exactly the wrong moment.

That one month taught me something no certification or course ever could. Small IT decisions can create surprisingly big business value.

Why I Cannot Show Real Numbers

I cannot share the actual numbers or the systems I worked with, because they belong to the company. That is not a dodge, it is the terms of the job.

So here is a simplified hypothetical example that reflects the kind of calculation I learned to think about. It is not a real invoice. It is the shape of the reasoning.

A Hypothetical Seat Comparison

Imagine a company with 1,000 employees choosing between two plans.

	Google Workspace Business Starter	Microsoft 365 Business Basic
Storage per user	30 GB	1 TB OneDrive
Storage across 1,000 seats	30,000 GB	1,000,000 GB, which is 1 PB
Bundled services	Not part of this comparison	Teams, Exchange, SharePoint, and other integrated Microsoft 365 services

Now imagine Microsoft 365 costs about $1 less per user per month under a particular licensing setup. The cheaper option is also the one carrying more storage and more bundled services.

What One Dollar Does

At 1,000 seats, one dollar a month per user is:

• $1,000 saved every month. One line on one renewal, repeating on its own.
• $12,000 saved every year. From just one licensing decision, before anyone writes a line of code.

Pricing and plan details here are illustrative. Actual costs vary by region, licensing agreement, plan, and time. Always verify current pricing before using these figures.

The point is not the dollar. The point is the multiplier sitting next to it. A decision that looks trivial per user stops looking trivial once you write the seat count beside it.

The Part That Compounds

Now imagine adding, on top of that same renewal:

• Small automations that eliminate repetitive work. The task nobody enjoys, done once in code instead of every week by hand.
• Standardised processes. One documented way of doing a thing, so the outcome does not depend on who picked it up.
• Better collaboration through integrated tools. Fewer handoffs lost between platforms that were never meant to talk to each other.
• A few minutes saved per employee, every day. Individually invisible. Multiply it by headcount and by working days.

None of these decisions look extraordinary on their own. Nobody gets applause for a licensing comparison or a naming convention. But at scale they compound into real business value, and they keep compounding after the person who made them has moved on.

Back Into DevOps

After that first month of IT admin work, I moved into DevOps at Code7. The title caught up with the skills, the way I had expected it to.

But that month changed how I approach technology, and it did not change back. I no longer start with the engineering question by default.

I used to ask: can I build this?

Now I ask first: is this worth building?

The Question I Ask Now

Those are two different jobs. The first one makes you useful. The second one makes you worth listening to when the budget is on the table.

Sometimes what looks like a step backward is actually the experience that changes how you move forward.

Small IT decisions never look extraordinary one at a time, and at scale they are exactly where the profit is.

What is a step back that ended up moving you forward?