Does FieldHub use AI?

Yes, but not in the way most software does. FieldHub does not bolt a chatbot onto the application or let a model guess at your numbers. Instead, FieldHub ships an MCP server that connects the AI assistant you already use, such as Anthropic Claude or ChatGPT, to your live FieldHub account.

What that means in practice

• You ask in plain language. Which customers are more than 90 days overdue and when did we last contact them? What is our total RMR? What is sitting uninvoiced right now? Who is scheduled tomorrow and where?
• The answers are computed, not generated. Every figure comes from live FieldHub records and the native general ledger, the same one your controller uses. Anything the assistant cannot compute from your data comes back as unavailable, never as an estimate.
• It can act, with your confirmation. Apply a deposit across open invoices, generate a statement, log a collection note, advance a workflow, or email a contact. Every write stops and shows you what it is about to do first. Everything else is read-only.
• It only sees what you see. The assistant runs under your own roles, business units, and record access. Every request is logged and changes appear in the normal activity log.

Why we built it this way

Nine business domains and forty object types are already in FieldHub, on one ledger, with nothing to reconcile. An assistant reading that data directly is more useful and more trustworthy than a built-in AI feature working from a copy. It also means you choose the assistant and control the connection, and you can revoke it at any time.

This is what we mean when we call FieldHub an agentic system of record: the assistant brings the reasoning, and FieldHub keeps authority over permissions, business rules, approvals, and the audit trail.

The MCP server is available to Enterprise customers on request. See the MCP Server page for the full capability list, or request a demo.