Your team is leaving money on the table.

A unit of AI spend, not a question. A credit tracks what an answer actually costs to produce, so a quick lookup on a small model costs a fraction of one while a deep multi-step analysis on our most capable model costs several. Work that is cheap for us to run is cheap for you, and you are never charged for a retry or for our own infrastructure calls. Every plan includes credits for the users it includes, and every additional user adds their own allowance at that plan's rate, so adding people never means paying twice for the work those people do. The allowance per user rises with the plan, so a seat on Growth brings more credits than a seat on Starter.

Nothing breaks and nothing throttles. Unused credits roll over first, up to a second month's worth, so a quiet month funds a busy one and you are not buying for your peak and wasting it the rest of the year. Beyond that, usage is metered at $0.10 per credit ($50 per 500), the same rate on every self-serve plan, and at a negotiated rate on Enterprise. Billing is per credit, so going slightly over costs slightly more, never a whole block. Additional users also bring their own credit allowance, so growing the team does not mean paying twice for the work that team does.

On the Go Fig platform, yes, and one rule covers every plan: an additional user costs that plan's own per-user rate. Starter is $30 per month, Pro is $40 and Growth is $50, each 20% less on annual billing, and each is the same rate already built into the plan price. So a seat costs the same whether it came with the plan or you added it later, and nothing about your bill changes shape as the team grows. Moving up a plan is not a volume discount and is not meant to be: you upgrade because the seats do more, connecting warehouses, holding more history, carrying access controls. Enterprise is quoted with graduated volume pricing that improves as your team grows. Separate custom build engagements are scoped to the work rather than priced per seat.

Yes, and it is what the plans above show by default. Annual saves 20% on every self-serve plan; flip the toggle to see the monthly rate. Enterprise agreements run on a 12-month minimum term with terms set in your Order Form.

Yes. You can start and connect your first system without talking to sales. Enterprise involves a negotiated agreement, so that one starts with a conversation.

Two things you cannot get on Growth at any headcount: deployment inside your own infrastructure, and the contractual layer. A negotiated agreement with redlines accepted, a counter-signed DPA with Standard Contractual Clauses, an uptime SLA, security incident notification within 72 hours as a contractual commitment, a negotiated liability cap set in your Order Form above the standard contractual cap, named support and dedicated implementation. On the product side: graduated volume per-user pricing that improves as your team grows, instead of Growth's flat $50 per additional user, a permission audit log, and unlimited exports. Enterprise customers can also have AI disabled entirely at the organization level, which is a hard technical block rather than a setting. If your legal and security review has to pass before you can buy, or your data cannot leave your environment, that is what Enterprise is for.

Four things, and none of them is a surprise at renewal. First, the systems we capture: how many sources we pull in and reconcile, since a CRM and an accounting system is a smaller build than a dozen systems across sales, finance and operations, each with its own quirks. Second, how many people use it: the per-user rate is graduated, so it improves as the team grows and a wide rollout costs less per head than a narrow one. Third, the domains and entities in scope: adding finance, operations, or multiple legal entities to consolidate brings more modelling and reconciliation into the build. Fourth, deployment and governance: running in our infrastructure is one thing, running inside your own perimeter, on your servers, against your review process and your compliance requirements, is another. Enterprise is quoted rather than published because those four move independently. Tell us what your rollout looks like and we will price it.

Yes, on Enterprise. We deploy inside your perimeter, on your servers and your network, against your codebase and your review process. This is the same deployment model we already run for customers whose data cannot leave their environment. Talk to us about what your infrastructure looks like and we will scope it.

Yes, on every plan. It is an organization-level master switch an admin controls in your settings, not a preference and not an upgrade. With it off, no data from your organization reaches any AI provider under any code path: no assistant, no summaries, no enrichment, no semantic training. A privacy control that only the largest customers can afford is not a privacy control, so it is not gated. On Enterprise we will additionally commit to that configuration in your agreement, so it becomes a contractual term your team can hold us to rather than a setting someone could flip back.

Yes, though it is a separate engagement from a platform subscription. Data capture, internal tools, integrations and the modelling underneath them, built on your stack and owned by you. See services, or book a discovery session and we will scope it against your actual situation.

For custom builds and FigClaw deployments, yes. The data layer and the infrastructure we build are yours, not rented back to you. The Go Fig platform is our product, which you subscribe to, and your data in it is always yours to export.

Yes. SOC 2 Type II, Security trust services category, with zero exceptions. The examination covered Security only, not Availability, Processing Integrity, Confidentiality, or Privacy. The report is available under NDA to Enterprise customers through our Trust Center; on other plans we provide a security summary and written answers to specific questions. Our subprocessor list is published at the Trust Center and our DPA is published in full.