The short version.

Five buckets: Claris licensing, hosting, a stewardship retainer, project work, and backups. Licensing and stewardship scale with users and complexity. Project work sits on top, and backups are the line that gets skipped. What it all adds up to varies widely, because system complexity varies more than user count does.

What follows is what goes into each bucket, so you can see where your own system sits.

The five cost buckets.

1. Claris licensing. FileMaker user licenses are sold as annual subscriptions, priced per user. Buying more licenses, signing for several years, and current Claris deals can lower this; ask your reseller for the actual current quote before budgeting. Server licensing is separate if the server sits in your office, and usually included with Claris Cloud.

2. Hosting. Three common models. Self-hosted on a Mac or PC in the office costs nothing ongoing beyond new hardware every 5–7 years. Claris Cloud is bundled with the subscription for basic tiers and extra for higher tiers. A FileMaker hosting company charges a monthly fee that depends on system size, security setup, how often it backs up, and how much support you get.

3. Stewardship retainer. This is a developer whose job is knowing your system, being reachable, and doing routine work — small fixes, moving hosting and macOS or Windows versions, keeping plug-ins working, checking that backups work. It scales with the system: users, complexity, integrations, how many parts it has. This is the bucket most small businesses underspend on until something breaks and they wish they hadn't.

4. Ad-hoc project work. On top of the retainer. A small change or bug fix; a new piece, web screens, a Stripe integration, a customer portal; or a larger project like a significant integration, a modernization effort, or a staged migration. These are priced from a scope, not billed against the retainer.

5. Backup and disaster recovery. Often forgotten in budgeting. If hosting is self-managed, a real backup strategy (offsite copies, verification, restore testing) needs a little tooling and 2-3 hours of the steward's time monthly to verify. Third-party hosts usually include this. Businesses that skip this line item eventually pay for it as an emergency, at ten times the price.

The bucket most owners underspend on is stewardship. It is also the one that separates a bill from a crisis.

A worked example: five-user small business.

Realistic scenario. A small services business runs FileMaker for CRM, quoting, and invoicing. Five active users. System has been in place for eight years. Runs on a Mac Mini in the office. Original developer is semi-retired but still available occasionally. Owner is starting to worry about that fact.

  • Claris licensing: five user licenses, renewed each year
  • Hosting: self-hosted on the office Mac Mini, with power and new hardware every few years
  • Stewardship: a light retainer with a check-in each month, for a small, low-complexity system
  • Backups: an external drive plus a cloud snapshot, verified quarterly

On top of this, a budget for project work and enhancements — the amount depends on how much the business is changing, not on the system.

What drives the cost up.

  • More licenses than people using them. Every unused license is on the renewal quote. An audit before the annual renewal typically finds 15-30% overspend on licensing at businesses that have grown, shrunk, or reorganized in the last three years.
  • System complexity. Heavy customization, many connections to other software, hosted services, data flowing to other systems as it happens. Each of these adds to the steward's hours and to the frequency of things needing attention.
  • Rapid growth. Fifty percent user growth means fifty percent more licensing and, often, meaningful changes to the system's shape. Growth is usually good for the business and expensive for the software line item.
  • Deferred maintenance. Systems that have not been touched in years pile up things that may stop working with newer versions — old FileMaker versions, old macOS or Windows versions, plugins that stopped shipping updates. Catching up costs a project or a short catch-up retainer.

What brings the cost down.

  • Paying only for the licenses you use. The cheapest saving there is. See above.
  • Extensions instead of expansions. Web screens on top of FileMaker, or a connection to your other software, let new people use the system without each needing a FileMaker license. For a business adding a customer portal, field crew access or online payments, that often costs less than buying the extra licenses.
  • Choosing the right hosting model. Third-party hosting is worth the cost when the business has nobody to look after its computers. Self-hosted is meaningfully cheaper when it does.
  • Stewardship sized to the system. Not every system needs weekly attention. A simple, stable one can run on a lighter retainer, with a clear plan for when something goes wrong.

Common cost mistakes.

  • Paying for licenses nobody uses. Universal, often unnoticed until the annual quote.
  • Skipping the retainer to save money. Then paying emergency rates when something breaks, which is usually more than the retainer would have cost.
  • Not budgeting for the annual FileMaker or macOS/Windows upgrade cycle. Every year there is at least one thing that needs testing. Businesses that plan for it are fine. Businesses that don't get surprises.
  • Paying premium hosting when self-hosting would work. Or the reverse — trying to self-host without someone to look after it well.
  • Not doing an audit at renewal time. The renewal quote is the one moment each year when the licensing conversation is naturally open. Skipping the audit is skipping the savings.

What to do next.

If you are trying to figure out what your specific system needs, the free triage call is where we start. Tell me the system — users, complexity, integrations, what's been going on — and I'll tell you what a sane plan looks like. The System Assessment turns it into a quote you can actually budget against.