🥇 Proud providers of TeamGB and ParalympicsGB for Milan26 🥇 - Watch the video 👀

    THE FUTURE OF FILEMAKER

    Bringing FileMaker into Outlook

    A follow-up to The Future of FileMaker, with a concrete example of what that future actually looks like on a Monday morning.

    By Jordan Watson, Director at Neptune Digital · Published 2026-05-20

    The thesis, in one line

    The future of FileMaker isn't a better FileMaker window. It's no FileMaker window at all.

    FileMaker becomes the engine - the trusted, structured, permissioned source of business data - and the interface moves to wherever your team already spends their day. Outlook. Teams. The browser. Slack. An AI assistant. A handheld in a warehouse.

    In our original article, we made the case for why this matters. In this follow-up, we want to make it concrete with the first of a series of real examples we'll be publishing over the coming weeks.

    This one is about email.

    The problem we kept seeing

    Most knowledge workers live in Outlook. It's where briefs arrive, quotes get approved, problems escalate, and decisions get made.

    Their CRM - whether it's FileMaker, Salesforce, HubSpot or anything else - lives somewhere else. A different window. A different login. A different mental model.

    So what happens in practice?

    A client emails to ask about a quote. To answer them properly, the account manager needs to know:

    • What's the current quote value?
    • What stage is it at?
    • When did we last speak to them?
    • Are there other open opportunities with this account?
    • Are there any unpaid invoices that might be the real reason they're emailing?

    To get those answers the old way, they have to open FileMaker, search the company, click into the record, click into related tables, and stitch the picture together themselves. That's a minute or two. Multiply by 60 emails a day. Multiply by every account manager in the business.

    And here's the kicker: even when they do all that work, the act of replying to the email rarely makes it back into FileMaker. The CRM goes stale. Nobody knows the latest. Reports lie.

    We've seen this pattern on every FileMaker project we've worked on for years. The fix isn't "train people to use the CRM more." The fix is to put the CRM where the work already happens.

    What we built

    For over a year now we've been quietly building custom add-ons for our FileMaker clients - inside Outlook, Microsoft Teams, WhatsApp and the browser. Same pattern every time: the tool the team already lives in becomes a window into their FileMaker system, with the data live and the actions writing straight back.

    The example below is one of those Outlook add-ons, built on top of a FileMaker CRM we delivered. It looks like an extension of Outlook itself, but every piece of data in it is live FileMaker data.

    Here's the flow from the user's perspective:

    1. An email arrives. Sarah from a client company sends a question about project quote CLX-2024-089.

    2. One click - the Neptune panel opens. A button sits in the Outlook toolbar (and on the email itself). Click it, and a panel slides in on the right.

    3. The right record is already loaded. The add-on has read the sender's email address, matched it to a contact in FileMaker, and pulled the right account. The user sees:

    • Client info - company, contact, account ID, current status badge
    • Related project - project ID, quote value (£24,500), stage (Proposal), due date
    • Recent activity - a timeline of the last touches: quote sent, discovery call completed, lead qualified, with timestamps and who did them
    • Related records - a quick counter showing 2 open quotes, 1 active project, 0 unpaid invoices, 0 support tickets

    In about a second, the user has the same context they would've spent two minutes hunting for. They can reply intelligently now.

    4. They can action it without leaving the email. Four quick-action buttons sit in the panel:

    • Create Task - opens an inline form, pre-filled with sensible defaults. Task title pulls from the email subject. Description carries the gist of the email. Suggested assignee is the account owner from FileMaker. Priority and due date are easy to set. One click writes the task back into FileMaker.
    • Log Call - captures a call note against the contact.
    • Update Status - change the project stage, lead status, or any other workflow field.
    • Add Note - drop a free-text note against the account.

    5. There's still a "back door" to FileMaker. Sometimes the user genuinely needs the full FileMaker layout - to make a complex edit, to look at an attachment, to run a multi-step script. An Open in FileMaker button deep-links them straight to the right record. No searching.

    What it looks like

    Below is a working demo of the Outlook interface with the Neptune add-on panel open on the right. Click Open Neptune Panel in the email toolbar (or the Neptune button), then try Create Task in the quick actions - the form pre-fills from the email, exactly as it does in the live add-on.

    Interactive prototype - the data shown is illustrative. In a live deployment, every field is live FileMaker data.

    Crucially, the design language of the add-on is Neptune-branded and FileMaker-flavoured, not a generic Microsoft control panel. It feels like an extension of the client's own system, because it is one.

    Under the hood (in plain English)

    For the technically curious, here's the short version of how it's built. We won't bore the rest of you.

    • Microsoft Office.js Add-in framework. This is the modern, cross-platform way to extend Outlook. The same add-on runs in Outlook on Mac, Windows and the web - no client install, no group policy gymnastics.
    • The add-on talks to FileMaker Server over HTTPS using the FileMaker Data API (with OData as an option where it makes sense for richer queries). Authentication uses the same identity the user already has - so permissions, audit trails and field-level security all carry through cleanly.
    • A thin web layer in between handles the email-to-record matching logic and any business rules - for example, deciding which project to surface when a contact has more than one open.
    • It's hosted on the same infrastructure as the FileMaker system itself in our managed FileMaker hosting environment, so there's one place to patch, monitor and back up.

    No new database. No data sync. No "single source of truth" PowerPoint that quietly becomes two sources of truth. FileMaker is still the system of record. We've just given it more doors.

    No new database. No data sync. FileMaker is still the system of record. We've just given it more doors.

    Why this matters more than it might sound

    A small add-on with a few buttons doesn't sound revolutionary. The impact is.

    1. CRM adoption goes from a battle to a side effect. If logging a call takes five seconds and happens in the same window as the email, people log calls. Data quality goes up without a change-management programme.

    2. Response times collapse. The two-minute "let me check the system" delay disappears. Customers feel the difference.

    3. New starters get productive faster. They don't need to learn the FileMaker UI to do 80% of their day. The 20% that needs the full system, they grow into.

    4. FileMaker stops being "that legacy thing." When the CFO emails a client back from Outlook with live FileMaker data in front of her, FileMaker stops being a system the business merely tolerates and starts being infrastructure the business actively uses. That changes investment conversations.

    5. It future-proofs the platform. Every system in your business is going to be expected to plug into AI assistants, Teams, browsers and mobile within the next few years. Building these "doors" into FileMaker is exactly the muscle you need.

    Where we're taking this next

    The Outlook add-on is the first of a small family of integrations we're rolling out for FileMaker clients. The same architecture lets us push FileMaker data into:

    • Microsoft Teams - surface a client record as a tab, action it from chat, get notifications when a key field changes.
    • The browser - a Chrome extension that recognises a customer on any third-party portal (Stripe, Xero, a supplier site) and brings up the FileMaker context.
    • AI assistants - letting a copilot read from and write to FileMaker safely, with full permissioning, so "draft a reply to Sarah and log the call" becomes a single instruction.
    • WhatsApp and SMS - for field teams who never open Outlook in the first place.

    Same FileMaker. Same data. Same Neptune-built engine. New doors.

    The takeaway

    If your FileMaker system today is a window people open, you're using maybe 30% of what the platform can be in 2026.

    If your FileMaker system is an engine that quietly powers Outlook, Teams, the browser and the tools your team already lives in - that's the future of FileMaker.

    We'd love to show you what that looks like for your business.

    Read the original Future of FileMaker essay, or explore related guides - AI & LLMs Inside FileMaker and WebDirect vs Modern Web Stack.

    Want this for your FileMaker system?

    If your team lives in Outlook (or Teams, or the browser) and your FileMaker CRM lives somewhere else, this is the gap we're closing for clients right now. Book a free 30-minute call to see it in action.

    Book a call