Hiring an in-house FileMaker developer vs outsourcing

Bias disclosure: we are a UK Claris Partner. Our commercial interest is obviously in outsourcing. But we also advise several clients who run their FileMaker systems with an in-house developer and a Partner safety net - it's a pattern we actively recommend when it fits. This guide walks through the numbers, the risks, and when each option is the right call in 2026.

The honest cost comparison (UK, 2026)

Translation: one in-house FileMaker developer = roughly 70–110 days of a UK Claris Partner's time per year. If your actual development demand is less than that, you are over-buying by hiring. See our UK FileMaker Cost Guide for the underlying day-rate and project-band numbers.

Non-cost factors that matter at least as much

1. Hiring timeline

The UK FileMaker talent pool is small. A realistic search for a Claris Certified developer runs 3–6 months; add 2–3 months notice period and you're often 6+ months from signing to first line of code. A Partner engagement starts in 2–4 weeks. If your business case needs movement this quarter, outsourcing is the only credible option.

2. Bus-factor risk

This is the biggest structural difference. One in-house developer = bus factor of 1. Two = bus factor of 2. A Claris Partner gives you a bus factor of 5–15 developers who share a codebase standard, a QA process, and documented handover. FileMaker systems often live for 10–15 years; betting that on a single hire is a serious governance risk, especially in regulated sectors.

3. Breadth of skill

A FileMaker system touches layouts, scripting, data model, integrations, iOS (FileMaker Go), hosting, backup, auth, security, and reporting. No single developer is excellent at all of those. A Partner gives you specialists behind the lead developer - iOS, security, integrations, DBAs. One in-house developer is unavoidably going to be "good at most, great at some, weak at the rest".

4. Proximity and context

In-house wins this one, comfortably. A good in-house developer sits in stand-ups, drinks tea with operations, overhears the problem before it becomes a ticket, and has years of institutional context baked in. For businesses where FileMaker is genuinely core and needs constant small iteration, that is hard to replicate via a Partner's weekly call.

When to hire in-house

• Sustained FileMaker demand of 1.5+ FTE - essentially a pipeline that never empties.
• FileMaker is a core strategic capability, not a back-office tool you happen to use.
• You can afford the 6-month hiring runway and the 20–30% chance the first hire doesn't stick.
• You have existing engineering leadership (CTO or Head of Engineering) who can line-manage effectively.
• You're prepared to keep a Partner retainer alongside for specialist cover and safety net.

When to outsource to a Claris Partner

• Demand is under ~1.5 FTE (which it is for the vast majority of SME FileMaker systems).
• You need momentum this quarter, not next year.
• You need breadth of skill - iOS, integrations, security, hosting - without building a team.
• You want a bus-factor 5–15 safety net by default.
• You're in a regulated sector and need evidenced compliance, audit trails and documentation.
• You'd rather pay per day used than carry a fixed £90k+ fixed cost year-round.

The hybrid: in-house developer + Partner retainer

For medium businesses where FileMaker is important but not the only thing engineering does, the hybrid is usually the highest-leverage answer:

• One in-house FileMaker developer (occasionally two) for day-to-day iteration, embedded context, fast turnaround.
• A Claris Partner on a £1,500–£4,000/month retainer for code review, architecture sign-off, holiday / illness cover, specialist work (security, iOS, integrations), and out-of-hours cover.
• Shared codebase standards - the Partner often sets the baseline at the start of the engagement.
• Quarterly pulse reviews - the Partner audits the codebase for drift and raises technical debt items into the backlog.

This is what several of our larger clients run. The in-house developer gets a real team rather than being a department of one; the business gets bus-factor protection; the Partner gets a long-term relationship with a client who understands the platform.

What about offshoring?

On paper, offshoring looks cheap. In practice, for FileMaker, it rarely works. The FileMaker / Claris community is predominantly English-speaking and clustered in North America, the UK and parts of Europe - the offshore talent pool is thin, the rate gap is smaller than on mainstream stacks, and time-zone overlap with UK operations is often the killer. Every offshored FileMaker system we have taken over for a UK client had three common problems: undocumented codebase, inconsistent naming, and no real understanding of UK GDPR. For regulated, public-sector or healthcare clients, offshore is usually a non-starter.

How to hire if you decide to go in-house

1. Ask for Claris Certified status, verify with Claris if in doubt.
2. Test relational modelling and scripting (not just "can they make a layout").
3. Test integrations / REST / Data API - a weak area for many FileMaker CVs.
4. Reference-check with at least one former client or manager.
5. Agree up front that a Claris Partner will pair with them for the first 3–6 months.
6. Pay market rate. Trying to save £10k on salary costs you 12 months of pain later.

See also - Claris Partner vs FileMaker Freelancer, UK FileMaker Cost Guide, and Best FileMaker Developers in the UK.