The FileMaker Tax: A Love Story in Monthly Invoices

Let me tell you about Raymond.

Raymond was a contractor. He was brilliant with FileMaker. He built your inventory system in 2014, back when your operation processed 3,000 devices a year and the biggest challenge was tracking which shelf they were on. Raymond's system worked beautifully. It had a nice interface. It tracked serial numbers. It even printed labels, which at the time felt like sorcery.

Raymond left in 2016. He took another contract. You still have his phone number. You've called it four times this year. He charges €150 per hour now, and every change request takes three weeks and costs €30,000 because Raymond is the only person on earth who understands the relationship between Table 14 and Layout 7, and Raymond has other clients.

This is the FileMaker tax. And you've been paying it for a decade.

The True Cost of "It Works"

Your system works. Nobody disputes that. Devices go in, serial numbers get tracked, labels get printed. It does what it was built to do. The problem is that what it was built to do was solve the problems of 2014, and it is now 2026, and your problems have evolved in ways that Raymond did not anticipate because Raymond was solving 2014 problems and Raymond is not a fortune teller.

You now process 25,000 devices a year. You have three warehouses. You handle lease returns with chargeback calculations. You need multi-dimensional grading. You need erasure certificate integration. You need your inventory to talk to your sales tools. None of these requirements existed when Raymond was building layouts in your office while eating sandwiches from the shop downstairs.

Each new requirement costs approximately €30,000 and three weeks. A new grading field? €30K. Integration with Blancco? €30K and a conversation with Raymond about APIs that makes both of you uncomfortable. Multi-warehouse support? Raymond will call you back. Raymond always calls back. Eventually.

The most expensive software in the world is the software that was cheap to build and impossible to change.

The Documentation Problem

When someone asks "is the system documented?" the answer is a Post-it note on the server rack that says "Raymond's system — DO NOT UPDATE FILEMAKER." This is not documentation. This is a warning label.

The actual logic of your system exists in three places: Raymond's memory, the FileMaker file, and the accumulated institutional knowledge of the three employees who have been using it long enough to know that you have to click "Refresh" twice after adding a new record or it doesn't save. Nobody wrote this down. Nobody needs to write it down, because the people who know it are still here. But one of them is thinking about retirement, and another just updated their LinkedIn profile, which in your industry is the equivalent of a tornado warning.

The Replacement Fear

You've thought about replacing it. Of course you have. You've looked at ERPs. You've attended demos. You've received proposals that make your eyes water — not from the price (though that too), but from the implementation timeline. Twelve months. Eighteen months. "It depends on your requirements." Everything depends on your requirements, and your requirements depend on Raymond's layouts, and Raymond's layouts depend on decisions made in 2014 that nobody remembers the reason for.

The fear of replacement is rational. Migration is painful. Data mapping is tedious. The transition period — where you run both systems in parallel and everyone hates everything — can last months. But the fear of replacement needs to be weighed against the cost of staying: €30K per change, three-week lead times, single-person dependency, no integration capability, and a system that will one day need to be replaced regardless. The question is whether you replace it on your timeline or on an emergency timeline when Raymond finally stops answering the phone.

---

Raymond built you a good system. It served you well. But the gap between what it can do and what you need it to do grows wider every year, and every year that gap costs you more to bridge. The FileMaker tax isn't the license fee. It's the opportunity cost of operating at 2014 speed in a 2026 market.

Somewhere, Raymond is building someone else a FileMaker database. He wishes you well. He just can't help you anymore. Not at a price that makes sense. Not at a speed that matters.