How to Choose a FileMaker Consultancy (2026)

In short: choose a UK FileMaker consultancy on five things that actually predict outcomes - whether they'll tell you when FileMaker is the wrong tool, how quickly they put working software in your hands, whether the people building your system are employed developers or a contractor network, how many people could maintain it if one left, and whether the solution is shaped around you or around their product. Verify the claris.com Partner listing and named references, and be wary of vanity claims like "number one partner" or "largest team". The rest of this guide explains each criterion and the questions to ask.

We are a FileMaker consultancy and a Claris Partner, so read this with the scepticism it deserves. But the criteria below are the ones we would use if we were the buyer - the things that genuinely predict whether a FileMaker engagement lands on time, survives staff changes, and keeps paying back for years. None of them are about logos or awards. They are about how a firm is built and how it works.

Most teams who switch consultancy do it for one of two reasons. Either their current setup - often a one- or two-person operation - has started to struggle with the workload or simply gone quiet when they're needed. Or they've realised the advice they keep getting is the same as it was five years ago: another list view, another small tweak, when what they actually want is a fresh, modern perspective on what their system could be. The criteria below are written with both of those moments in mind.

The five things that actually matter

1. Platform breadth - will they tell you when FileMaker is the wrong tool?
2. Delivery cadence - how soon do you hold working software, not diagrams?
3. Who does the work - employed senior developers, or a contractor network?
4. Team depth & bus factor - how many people can maintain your system?
5. Bespoke fit - are they shaping the solution to you, or you to their product?

1. Platform breadth, not platform tunnel vision

Deep Claris FileMaker expertise is essential - but a consultancy that only sells FileMaker has a commercial incentive to recommend FileMaker for everything, even when the problem is screaming for a web stack, a native iOS app, or an off-the-shelf tool. That single-platform framing quietly limits the thinking applied to your problem.

The stronger position is deep FileMaker expertise plus the honesty and capability to integrate with - or recommend - other tools when they fit better. Ask a prospective partner: "When would you tell a client not to use FileMaker?" A good answer is specific and immediate. A bad answer is a long pause.

2. Delivery-led, not planning-heavy

Planning matters. But planning is not delivery, and some firms - especially those used to large, slow-moving organisations - spend months on workflow mapping and discovery before you ever see working software. That burns budget and, worse, defers the moment you can actually validate decisions against reality.

You learn more from a real prototype in week three than from another workshop. Look for a consultancy that ships a working slice early and iterates with you, rather than one that treats a thick requirements document as the deliverable. Ask: "When in the engagement do I get working software in my hands?"

3. Who actually does the work

Some consultancies are essentially brokers - a thin front office over a network of "associate" contractors who do the real building. That can work, but it adds a layer of middle men between you and the people writing your code, dilutes accountability, and makes continuity fragile: when a contractor moves on, knowledge of your system can walk out with them.

Directly employed senior developers mean you talk to the people actually building your software, the consultancy owns quality and continuity, and your system survives staff changes. Ask plainly: "Who specifically will write my code, and are they your employees?"

Watch out for headcount as a marketing number. A firm may advertise the "largest" team of FileMaker developers, but if that number is a pool of associate contractors rather than employees, it tells you very little about accountability or continuity - it just means there are more middle men. A smaller team of employed developers you can actually speak to is usually the stronger position. Ask whether that developer count is staff or contractors.

4. Team depth and bus factor

A small team can be brilliant - but a two- or three-person shop carries the same structural risk as a freelancer: a bus factor (the number of people who can pick up your system if someone becomes unavailable) of one or two. If a key person is ill, leaves, or simply gets over-stretched, your business-critical system becomes a ticking clock. This is the single most common reason teams come to us - a one- or two-person setup that has gone quiet or can no longer keep pace with the workload.

Depth also buys peer review, a separate architecture/QA function, and the ability to add developers when the project grows. Ask: "How many of your developers could maintain my system if one of them left tomorrow?"

5. Bespoke fit, not product fit

Be clear on whether a firm is a consultancy or a product company. A team built around its own online platform will, understandably, try to fit your needs into that product - which is great if the product fits and frustrating if it doesn't. A consultancy shapes the solution around your processes instead of asking you to change your processes to suit the software.

Neither is wrong - but you should know which you are buying. Ask: "Is this your product, or is it built for us?"

What good looks like vs watch-outs

The questions to ask any consultancy

• When would you tell a client not to use FileMaker?
• When in the engagement do I get working software in my hands?
• Who specifically will write my code, and are they your employees?
• Is your developer count staff or contractors?
• How many developers could maintain my system if one left tomorrow?
• Is this your product, or is it built bespoke for us?
• If any ranking is claimed - ranked number one by whom, measured on what?
• What would you do differently with my system if you were starting today?
• Can you give me a named, reachable UK client reference?

Red flags

• Cannot link you to their claris.com Claris Partner listing.
• Recommends FileMaker for everything without asking about your problem first.
• Cannot name who will actually do the work, or relies entirely on contractors.
• Leans on vanity metrics - a "number one" ranking or "largest team" claim it can't substantiate.
• Long discovery phases with no working software in sight.
• A bus factor of one or two on a business-critical system.
• Only ever proposes small tweaks - never a fresh, modern direction.
• No named, reachable client references.

What rankings and badges actually tell you

Be careful with "number one Claris Partner" or "top-ranked" claims. Some partner rankings are driven by visible marketing activity - LinkedIn posts, event presence, content volume - rather than by how Claris itself rates a partner's delivery, certification or client outcomes. A firm can be genuinely the most active on social media without being the best at building and supporting systems.

The same applies to the Platinum Partner designation. Platinum is not a sign of size, quality or value - it was granted at a point in time (in some cases more than a decade ago) and has never been re-evaluated. Platinum Partners need only one certified developer, and some have historically been sole traders.

The signals that actually mean something are verifiable: a current listing on claris.com, named and reachable UK client references, employed (not contracted) certified developers, Claris Excellence Awards, and Partner Council involvement. When you see a superlative claim, ask the simple follow-up: "Ranked number one by whom, and measured on what?"

Are you getting fresh thinking, or the same old advice?

The world has moved on, and so have the options for what a business system can do - integrations, automation, AI-assisted workflows, modern web and mobile front ends on top of your FileMaker data. If every conversation with your current developer ends in another list view or a small tweak, you may be getting maintenance dressed up as advice.

A modern consultancy should be able to look at your system and tell you what it could be, not just keep it ticking over. Ask a prospective partner what they'd do differently with your system if they were starting today - the answer tells you whether you're buying fresh thinking or the status quo. (For a sense of how we think about this, see our essay on the future of FileMaker.)

The short answer

Pick the consultancy that tells you the truth about the tool, puts working software in your hands quickly, employs the people who build it, has enough depth to survive a resignation, shapes the solution around you, and brings a genuinely modern perspective rather than the same old advice. The logos, rankings and headcount claims are noise; these are the things that actually determine whether you're glad you chose them in three years.

See also the pillar - Best FileMaker Developers in the UK (2026) - and Claris Partner vs FileMaker Freelancer.