The short version.

A five-user small business running on FileMaker typically costs $21,000 to $30,000 per year to keep healthy. A ten-user mid-size business is closer to $30,000 to $45,000. A twenty-user operation is $50,000 to $75,000. These are all-in numbers that include licensing, hosting, stewardship, and routine maintenance — but not ad-hoc projects or new capability builds, which sit on top.

The ranges are wide because system complexity varies more than owner count does. What follows is how the number gets built, so you can put your own system somewhere realistic within it.

The five cost buckets.

1. Claris licensing. As of 2026, FileMaker user licensing sits near $600 per user per year at list prices, sold as annual subscriptions. Five users is roughly $3,000/year. Ten is $6,000. Twenty is $12,000. Volume tiers, multi-year commits, and the current Claris promotional pricing can reduce this; ask your reseller for the actual current quote before budgeting. Server licensing is separate for on-premise deployments and is typically bundled when using Claris Cloud.

2. Hosting. Three common models. Self-hosted on a Mac or PC in the office costs nothing ongoing beyond hardware refresh every 5-7 years. Claris Cloud is bundled with the subscription for basic tiers and extra for higher tiers. Third-party FileMaker hosting (dedicated FMS providers) runs $50-300 per month depending on system size, SSL, backup frequency, and support level. Most SMBs pay $0-1,500 per year here, depending on which model they picked.

3. Stewardship retainer. This is a developer whose job is knowing your system, being reachable, and doing routine work — small fixes, hosting and OS upgrades, plugin compatibility, backups verification. Retainers for small systems start at $1,500 per month ($18,000/year) and scale up from there. A ten-user system with more complexity typically runs $2,000-2,500 per month. A larger operation with integrations and multiple modules can run $3,000+ per month. This is the bucket most SMBs 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 runs $500-3,000. A new module, a web front end, a Stripe integration, a customer portal — each of these runs $5,000-25,000 depending on scope. A larger project like a significant integration, a modernization effort, or a staged migration runs $25,000-100,000 or more. These are project-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) costs $0-500/year in 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: 5 users × $600 = $3,000/year
  • Hosting (self-hosted, includes power and periodic hardware refresh amortized): $300/year
  • Stewardship retainer (small system, low complexity, monthly touch): $1,500/mo = $18,000/year
  • Backup strategy (external drive + cloud snapshot, verified quarterly): $200/year

All-in baseline: $21,500/year. On top of this, budget $5,000-15,000 per year for project work and enhancements — the amount depends on how much the business is changing, not on the system.

What drives the number up.

  • More seats than active users. Every unused seat 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 integrations, hosted infrastructure, real-time data flow to other systems. 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 accumulate compatibility risks — old FileMaker versions, old macOS or Windows versions, plugins that stopped shipping updates. Catching up costs a project or a small remediation retainer.

What brings the number down.

  • Right-sizing the license count. The cheapest optimization available. See above.
  • Extensions instead of expansions. A web front end on the FileMaker backend — or an integration with your other software — serves new users and new capability without consuming per-seat licenses. For a business adding a customer portal, field crew access, or a payment integration, this is often a net cost reduction against adding equivalent FileMaker seats.
  • Choosing the right hosting model. Third-party hosting is worth the cost when the business does not have IT capacity. Self-hosted is meaningfully cheaper when it does.
  • Right-sized stewardship. Not every system needs weekly touch. Simple, stable systems can run on a lighter retainer with clear escalation.

Common cost mistakes.

  • Paying for seats 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 the IT capacity to actually do 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.

Publishing prices in the open is the same discipline as owning the software. It removes uncertainty from the wrong side of the table.

What to do next.

If you are trying to figure out what your specific system should cost, the free triage call is where that gets estimated honestly. You describe the system — how many users, how complex, what integrations, what has been going on with it — and I tell you what an appropriate annual budget looks like for your situation. Thirty minutes, no pitch, and you leave with numbers you can put in a budget document.