Account context in your brief
See what your data team's tables say about a customer next to the deal you are working, without asking for a report.
Go Fig reads the account data your team keeps in Databricks so your brief can show it next to each deal and renewal.
This one is for your data team. They connect it once with a solutions engineer, and your brief can use it. A solutions engineer connects Databricks with you during setup. Access is read only, so nothing in Databricks changes. The tables your data team already maintains can then add context to the accounts you are working.
See what your data team's tables say about a customer next to the deal you are working, without asking for a report.
Check a customer's history from Databricks before you reach out about a renewal.
Work from the tables your data team already trusts, so what you tell a customer matches internal reporting.
Let your solutions engineer know you use Databricks and which catalogs and schemas (groups of tables) hold the account data that matters.
Your data team works with the solutions engineer to give Go Fig read-only access (it can look but never change anything) to those tables.
Together, choose the tables and views Go Fig should use, and leave out anything it doesn't need.
Confirm the tables you picked show up in Go Fig and look right before your brief starts using them.
No. A solutions engineer connects Databricks with your data team during setup. You get the result in your brief.
No. Access is read only. Go Fig can look at the tables you share but never change them.
Yes. Your data team and your solutions engineer pick the tables and views Go Fig reads during setup.
Schedule a demo. A solutions engineer walks through your Databricks setup and plans the connection with your data team.
Someone on your data team who can grant read-only access in Databricks. The rest of the sales team doesn't need to do anything.
A solutions engineer connects it with you on the call. Then you see Go Fig work on your own data.