The whole account before a call
See product usage or contract details from Snowflake next to the deal in your CRM, without asking the data team for a report.
Go Fig reads the account and usage data your team keeps in Snowflake, right where it sits, so your brief sees the whole account.
This one is for your data team. They connect it once with a solutions engineer, and your brief can use it. Your data stays in your Snowflake. Go Fig reads it there and doesn't copy it into its own storage. That means the product usage, contracts, or billing history your company already keeps in Snowflake can sit next to your CRM when you prep for a call. Go Fig only reads. It never changes or deletes anything in Snowflake.
See product usage or contract details from Snowflake next to the deal in your CRM, without asking the data team for a report.
Spot accounts whose usage dropped before the renewal conversation, not after it.
Ask Celeste, Go Fig's AI analyst, a question about an account and see which Snowflake table each number came from.
Your data team creates a dedicated Snowflake user and a role for it. The role gets USAGE on the warehouse, database, and schema, and SELECT (read access) on the tables and views you want Go Fig to see. Don't grant ACCOUNTADMIN or SYSADMIN. A read-only role is all Go Fig needs.
Choose the warehouse (the Snowflake compute that runs queries) Go Fig should use. A dedicated small warehouse keeps Go Fig's usage easy to see on your Snowflake bill.
With a solutions engineer, enter the account, username, password, warehouse, database, schema, and role. Once it connects, they walk through what Go Fig can see.
Your tables show up in Go Fig and are read straight from Snowflake each time they are used, so there is no copy to keep in sync.
Your data stays in your Snowflake. Go Fig reads it there and doesn't copy your tables into its own storage. So it can find the right table, it keeps field names, descriptions, and a few sample rows in its search index, as our security page explains.
No. Go Fig only reads from Snowflake, and the role you give it should be read only, so it can look but never change or delete anything.
As current as your Snowflake. Go Fig reads the data where it sits each time it's used, so there is no separate update schedule.
Someone on your data team who can create a Snowflake user and role, and a solutions engineer from Go Fig. After that, reps don't need to do anything.
Point Go Fig at its own small warehouse. Every query Go Fig runs then shows up under that warehouse on your Snowflake bill, apart from your data team's work.
A solutions engineer connects it with you on the call. Then you see Go Fig work on your own data.