The short version.

Your FileMaker system has real value in three specific places: the data, the business logic, and the workflow. The value of the platform itself — Claris's continued shipping of FileMaker — is a separate and smaller consideration than most owners assume in this conversation. A mature operational system does not become worthless because the vendor's ecosystem thins. It becomes something you value differently.

The logic and data are the asset. The platform is the wrapper.

What you actually own.

The data. Every customer record, every transaction, every quote, every invoice, every history entry, every touch and every note. Ten or fifteen years of your business's operational memory, in a structured queryable form. This data does not lose value regardless of what happens to FileMaker as a platform. If you ever move to a different system, the data comes with you.

The business logic. The calculations that price your products correctly. The scripts that route work through your shop or your office. The automations that catch exceptions before they become problems. The reports that show the owner what actually matters. This is a codified version of how your business works, developed and refined over years, usually through many small conversations between owners and developers. It is arguably the most valuable piece of the system, and the least visible from the outside.

The workflow. How staff interact with the system every day. The muscle memory of running the business through it. The patterns for handling the weird cases nobody documented. This part is not in the file at all — it is in the people using it. But it is inseparable from the value the system delivers, and it is expensive to replace.

What you don't own.

The future of the platform itself. FileMaker is proprietary; Claris controls its trajectory. This is the specific concern that usually sparks the question this page answers. It is a real concern, but it is a narrower one than "the whole system is worthless" — it is a concern about the wrapper, not the contents.

How to put a real number on it.

Two lenses that give different but useful answers.

Replacement cost. What would it take to rebuild what you have from scratch, on any modern platform? For a mature operational system — dozens of scripts, hundreds of fields, years of accumulated business rules, integrations with other systems — the honest range is $80,000 to $250,000. Some go higher, some come in lower; complexity varies more than owner count does. That number is a floor on what your existing system is worth to your business, because rebuilding is what you would be doing if you didn't have it.

Ongoing operational value. Different question. What would you pay this month for a system that already knows your business, holds your customer history, produces your reports, and runs without needing to be built? You would pay a meaningful number. In fact, you are paying it right now — in Claris licensing, hosting, and stewardship costs. That's the ongoing rent on an asset that is already delivering value every day.

Both numbers are informative. The replacement cost tells you what the asset is worth in an absolute sense. The ongoing value tells you what it's worth relative to what you're spending to keep it running. When those two numbers are healthy against each other, the system is a good asset for the business — regardless of the platform's headlines.

Why sunk cost feels wasted, and mostly isn't.

The sunk-cost frame is the wrong one for valuing a working operational system. Sunk cost applies when you are deciding whether to keep spending on an unfinished project. It does not apply when you are valuing something that is currently producing value every day.

The $200,000 spent over fifteen years did not become $0 because Claris's growth story slowed down. It became the price of what you have — a system your business runs on. The strategic question is not "was this money well spent?" (retrospective; the answer no longer matters). The strategic question is "given what we have now, what should we do with it going forward?" (prospective; where all the real decisions live).

Fifteen years of business logic does not lose value because the vendor's market thins.

Three ways to realize the value going forward.

Stewardship. Someone whose job is keeping the system safe, current, and documented. Compatibility work before OS or FileMaker upgrades. Small fixes as they come up. Reachable when something breaks. This protects the asset — the everyday equivalent of maintaining a well-built building.

Extension. Add modern web front ends on top of the existing FileMaker backend — customer portals, mobile field access, dashboards, integrations. The business logic and data stay where they are. The new capability lives alongside. This grows the value of the asset without discarding what already works.

Staged migration. When the platform math tips — because of licensing pressure, hiring difficulty, or a specific capability the platform can't deliver — move the business logic and data to a new platform in stages. The data comes with you. The logic gets translated, module by module. The workflow gets rebuilt on the new side. The value survives the platform change because the value was never really about the platform.

Each of these is a way of realizing the value of what you already have. The option that doesn't realize anything is sitting still and worrying about what might happen to FileMaker.

What to do next.

The free triage call is where "is our system worth anything" becomes "here's what our system is worth, and here's what to do about it." You describe the system, roughly what it does, roughly what you've spent on it. I tell you where the real value sits and which of the three paths above is the right shape for your situation. Thirty minutes, no pitch, and you leave with a much clearer read on an asset you probably haven't valued honestly before.