Mark opened the email at 7 a.m. on a morning in late February 2025. Skype was shutting down in early May. Sixty-seven days, and the tool he had never paid for had just sent its first and final bill.
Every client call link in his active proposals pointed to Skype. Five years of saved project conversations, booking integrations, and client-facing URLs were running toward a wall with no contract behind them. He had used the platform for 14 years without paying a dollar. Not once in those 14 years had he asked what it would cost to leave.
"Keep overhead low. Use free tools." Most operators who have run a lean business for ten or more years have heard this advice repeated like scripture. It sounds right. It is not.
The Pattern
The documented history here is worth knowing. Microsoft bought Skype in 2011 for $8.5 billion. For 14 years the tool ran free for the vast bulk of its users. No enterprise contract. No SLA that promised the lights would stay on past next month. No formal migration path when the end came. Then the parent company shifted strategy. The free tier got 67 days to move or lose everything.
What did "everything" mean in practice? Client-facing links broke. Proposals already in a prospect's hands pointed to dead endpoints. Recorded call history did not transfer. Third-party integrations wired into booking systems and CRMs went dark. Operators had to contact active clients, explain the change, retrain them on a new tool, and rebuild workflows. All on a clock they did not set.
This was not a one-off. Microsoft ran the same play with Wunderlist. Bought it in 2015. Let solo operators and small teams build whole project systems around it. Shut it down in 2020. Pointed everyone to a replacement app with a different structure. The people who had stored years of task history lost access to their own records.
Google has run this cycle over 290 times. Google Reader, Google Hangouts, Google Domains. The graveyard is public, tracked at killedbygoogle․com, and it grows every quarter. The sequence is always the same. A free tool gains adoption. The parent company shifts direction. The tool gets killed. Users absorb the full switching cost with no recourse and no warning beyond a short countdown.
I have made this mistake. Most people in this position make this mistake. The advice to keep overhead low does not fail people. It fails the system they are trying to run.
The Structural Flaw
The problem is not that the tool costs nothing. The problem is that zero price removes the one trigger that would force a review. No invoice arrives, so no quarterly look at the tool ever happens. No look means no backup plan gets built. Switching cost grows every month the tool stays in the stack. A new client gets routed through it. A new file gets stored in it. A new integration gets wired to it. The dependency compounds in the background, and the operator never sees it, because nothing ever arrives in the mail.
Most people treat this as a planning flaw. It is a system flaw. The system has no trigger. Without a trigger, the review never fires.
The Replacement Principle
Every tool in the stack gets scored once a quarter, whether it sends a bill or not. Fifteen minutes prevents a forced scramble. Once that is clear, three moves follow from it.
Move 1: The Dependency Count. Open your client workflow. Count how many steps run through a tool you do not pay for. Include call links, file storage, booking pages, client-facing URLs, and any integration that would break if the tool went dark this week. Write the number down.
That count is the real price of the tool. It just never showed up on a statement.
Move 2: The Exit Window. For each free tool on the list, answer one question: if the shutdown notice came this week, how many days would you need to move? Count the client-facing materials you would need to update. Count the data you would need to export. If the answer is more than a weekend, the tool has earned a quarterly review slot. Mark it. Put it on the calendar. Treat it like a bill that arrives four times a year.
Move 3: The Paid Floor. Pick the one free tool with the highest dependency count. Find a paid version, same tool or a close rival, that comes with a contract, a data export path, and a stated SLA. The cost is almost never more than a few dollars a month. What you are buying is not the feature. You are buying the right to plan your own exit on your own schedule, not theirs.
What the Audit Shows
Running this for one quarter does something the advice never did:
You see which tools carry real weight in client-facing work and which are just habit.
You find the one integration that would take days to replace, not hours.
You spot the tools where your data sits in a format you cannot export.
You catch the dependency that grew since last quarter without a conscious choice behind it.
The Three Questions
At the end of one quarter, ask three things.
→ Which tool carried the most client-facing weight without a contract behind it?
→ Which review felt like a waste of time because the exit path was already clean?
→ Which dependency grew without you choosing to grow it?
That is the difference between advice that sounds right and a system that proves itself.
Where You Stand
Sixty-seven days is what Skype gave. Some will give less. The most expensive tool in any stack is the one that never sends a bill. Not because it costs nothing. Because you never ask what it would cost to leave.
