November is when next year’s budget gets closed. In IT the habit is well known: take what was spent this year, add inflation and leave a “projects” line that gets fought over in the meeting against everything else.
In 2027 that habit fails for a concrete reason. The year brings dates you did not choose, that will not move and that cost money even though nobody asked for them. If they go into the budget as one more project, they compete with what leadership wants to see, and they lose, because nobody can see them.
The calendar that already decided for you
These are the 2027 dates that land on a plant on the border. None of them is optional and none of them waits:
| Date | What happens |
|---|---|
| January 1 | Work-hour records must be electronic, and the maximum work week drops to 46 hours |
| January 12 | The last patch for Windows Server 2016 ships; extended updates are billed from the 13th |
| February 10 | Let’s Encrypt starts issuing 64-day certificates |
| March 14 | Juárez springs forward and 2 a.m. does not exist |
| March 15 | Public certificates are capped at 100 days |
| October | Year two of Windows 10 extended updates ends; year three costs double |
We have already covered almost all of them in detail: the work-hour record, Windows Server 2016, certificates and the clock change. We will not repeat what each one means here. What matters now is how they go into the budget.
Three buckets, not one
An IT budget makes more sense split in three:
Required, with a date. The table above. Whether it gets done is not up for debate; only how and for how much. If it does not get done, the cost arrives anyway, as a fine, an unpatched server or a portal that is down.
Keeping what already runs alive. Licenses, subscriptions, extended updates, support, backups, renewals. It is the spending nobody sees until it is missing.
Improving. The new system, the dashboard, the pilot. It is the only bucket that truly competes in the meeting, and the way to rank it is the criteria for deciding what goes first.
The most expensive mistake is mixing the first bucket with the third. When the server migration is presented next to the production dashboard, the meeting picks the dashboard, because it is understood in ten seconds. The server is pushed to “next quarter”, and by February it has no patches.
What is required is rarely a purchase
The second trap is budgeting the required work as if it were buying something. Almost always it is labor.
The fingerprint reader on the time clock is cheap. What costs money is getting the record into payroll without re-keying, with your plant’s shift and overtime rules, and having someone test it against real payroll before the first January cutoff.
The Windows Server 2022 or 2025 license is the small part of a migration. The big part is the application running on top, which nobody knows will start on the new version. That means hours from the vendor, hours from the person who knows the system and a window when it can be stopped.
And certificates barely cost money; Let’s Encrypt gives them away. With 100-day certificates, each one is renewed about four times a year instead of once. Renewed by hand, that is someone’s time four times a year, per certificate. Automated, it is a one-time job, but it has to be budgeted.
If the required line only lists purchases, half of it is missing. Write down how many hours each date takes and whose hours they are, because they come out of the same people who have to run the plant.
The window that is already reserved
If your plant shuts down between Christmas and New Year’s, that week is the best window of the year to touch a server: there is no production to interrupt and nobody needs the system.
Look at where the first two dates in the table fall: January 1 and January 12, right after. If the work needs that window, the decision is made in November, not in the first January meeting. And if it needs Microsoft’s extended updates, the licensing paperwork will not get sorted out the week of Christmas either.
Keeping things running costs more on its own
This bucket is usually calculated from what was paid last year. In 2027 that falls short on at least two lines.
Windows 10 extended updates. If you have Windows 10 machines on Microsoft’s paid extended updates, you are already in year two, at 122 dollars per device. The third and last year costs 244, because the price doubles every year, and it starts in October 2027. These are the PCs that come attached to a test machine or a station on the floor, the ones you cannot replace without the equipment maker. Thirty of them are 7,320 dollars in year three, and after that there is no year four.
Windows Server 2016 extended updates. Billed from January 13, mostly purchased through Azure Arc, and they require Software Assurance. The price depends on your licensing, so ask your reseller before you close the number, not after.
And review the software contracts that renew in 2027: which month, for how many users and with what increase. Almost nobody has that list in one place, and it is the difference between a budget and a guess.
What can wait
Not everything with a date is urgent. 47-day certificates arrive in 2029, and whatever you do in 2027 to automate renewals already covers that step.
The work week is the opposite case. It drops to 46 hours in 2027, but it keeps dropping every January until it reaches 40 in 2030. If the attendance system treats the work week as a number you can change, you pay once. If every January you have to ask the vendor to adjust it, you pay four times. Budget it once, for the whole staircase.
Four questions for the budget meeting
- For each date in the table, who owns it and which line pays for it? If one has no name and no line, you already know which one will not get done.
- How many machines still run Windows 10, and how many servers run Windows Server 2016? If nobody can answer in an afternoon, the first expense is finding out.
- How much of the required work is people’s time, and whose? If it is all purchases, half the cost is missing.
- Which contracts renew in 2027, in which month and with what increase? Without that list, the keep-running bucket is a made-up number.
Where we come in
We do this exercise with the company before the budget closes: an inventory of what runs, the 2027 calendar with amounts and hours, and the split between what is not up for debate, what has to be kept running and what can be improved. It is part of our technology consulting and it ends in a document you can take to the meeting.
If you would rather start on your own, Chira asks how your company operates and tells you in writing what to fix first. And if you already have the list and want to go over it with someone, book a call.
References
The dates and prices in this article come from these sources. Microsoft’s extended-update prices change from time to time; confirm them with your licensing reseller before you budget.
- Decree amending the Federal Labor Law, DOF, May 1, 2026 — electronic work-hour records from January 1, 2027, and the staircase from 48 to 40 hours. In Spanish.
- Windows Server 2016 lifecycle, Microsoft — end of extended support on January 12, 2027.
- Prepare to deliver Extended Security Updates through Azure Arc, Microsoft — Windows Server 2016 extended updates, their requirements and billing from January 13, 2027.
- Extended Security Updates (ESU) program for Windows 10, Microsoft — 61 dollars per device in year one, a price that doubles every year for up to three years, and years that are paid cumulatively.
- Ballot SC-081v3, CA/Browser Forum — the schedule that cuts certificate lifetimes to 100 days on March 15, 2027 and to 47 in 2029.
- Decreasing Certificate Lifetimes to 45 Days, Let’s Encrypt — 64 days from February 10, 2027.
- Law on Time Zones in Mexico, Chamber of Deputies — seasonal time on the border, which starts on the second Sunday of March at 2 a.m. In Spanish.