Ask from wherever your team already works.

That's the point of Kipper. Most people who need a number from NetSuite, QuickBooks, or Xero don't have a seat in it — and often shouldn't, either because per-seat licensing is expensive or because broad access to the finance system isn't appropriate.

Kipper sits in front of the finance system. A workspace admin connects it once and decides who can ask what. Everyone else just asks in Slack, Teams, SMS, or their AI assistant. Only the admin needs finance-system credentials.

Kipper is read-only by architecture — it can never create, edit, or delete a record in your accounting system, in any interface. Access is permissioned by the workspace admin and enforced on every query, no matter how the question is phrased or which interface it arrives through.

Every question and answer is written to an audit log that admins can review. The security posture doesn't change between interfaces: connecting through ChatGPT gives that assistant exactly the same scoped, read-only access a Slack user has.

In Slack, Teams, and SMS, Kipper is the assistant you're talking to. With ChatGPT, Gemini, and Claude, your assistant is talking to Kipper — Kipper acts as a tool it can call through the Model Context Protocol.

The data access is identical either way. The difference is where the conversation lives and who administers it: native apps are set up once for the workspace, while MCP connections are configured per user in their own assistant.

No. Every interface reads from the same connection to the same finance system, so the answer to a given question is the same wherever it's asked. Most teams end up using several — Slack for day-to-day questions in channel, SMS for people who are away from a desk, and MCP for individuals who live in an AI assistant.

Kipper doesn't predict your figures. It translates the question into a SQL query, runs it against a synced copy of your finance records, and returns what the query returned. There's no document retrieval and no RAG step in between.

If the data can't answer the question, Kipper says so rather than estimating.

Kipper answers direct questions about transaction-level records and the supported financial statements, plus bank balances on a QuickBooks connection. It is not a general-ledger, journal-entry workflow, or bank-feed tool, and it does not read bank feed transactions or reconciliation status.

It also isn't an analytics tool: it won't build budgets, calculate financial ratios, or produce board narratives. Those stay with your finance team and their finance system.