By the end of this you will have Docusign connected to Gemini Enterprise as a data store, three queries a B2B legal team can run every Monday morning, and a straight answer on what the Deloitte and KPMG names on the launch list actually give you. Google put Gemini Enterprise for Legal into preview on 25 August 2026. The connector catalogue underneath it has been live longer, and that is the part you can set up this week.
This one is written for legal and contract teams on the B2B side: aggregators, platform providers, game studios, payment firms, data suppliers. The volume problem there looks different from an operator’s. It is 20 to 40 agreements and addendums a week, most of them variations on the same master services agreement, each carrying terms that change depending on whether the counterparty is licensed in Malta, New Jersey or Brazil.
The setup
Four things before you start.
A Gemini Enterprise licence, and you need to know which edition. Business edition ships with roughly 20 third-party connectors, and Docusign is one of them. Standard and Plus add around 70 more, including the Google Cloud databases and the larger enterprise applications. The legal-specific connectors announced on 25 August, iManage, NetDocuments, Everlaw, RelativityOne, Harvey, Legora, Solve Intelligence and Thomson Reuters HighQ, arrived with the Legal edition and sit in preview. Check your edition before you plan a workflow around any of them.
A Google Cloud project where you have rights to create data stores and attach them to an app.
A Docusign administrator who can authorise the connection. This is the step that stalls most often, because in a lot of B2B companies the Docusign account is owned by sales operations rather than legal.
About 45 minutes, of which the sync is most of the waiting.
Step 1: open the connector catalogue before you commit to anything
The public list is at cloud.google.com/gemini-enterprise/connectors. Read it with your own stack open next to it, and mark three columns: what you already pay for, what edition the connector needs, and whether it is generally available or in preview.
For a B2B legal function the list that matters is short. Docusign for signed agreements. Microsoft 365 or Google Workspace for the negotiation trail sitting in SharePoint, Outlook, Drive or Gmail. Box or Dropbox if that is where the executed PDFs land. Jira or Asana if contract requests come in as tickets. Everything else on the legal launch list is US litigation tooling. Everlaw, RelativityOne, CourtListener and Courtroom5 are built for discovery, dockets and court opinions, and a supplier legal team in Malta or Gibraltar will open them close to never.
Step 2: connect Docusign as a data store
In the Google Cloud console, go to Gemini Enterprise, then to the data stores section, and create a new data store with Docusign as the source. You authenticate against a Docusign account, choose which entities to bring in, set a sync schedule, and then attach the finished data store to the Gemini Enterprise app your team uses.
The field-level detail changes as the product moves, so read Google’s own page, “Set up a Docusign data store”, while you have the console open. Two things to get right at this stage rather than later.
The account you authenticate with decides what the model can see
Gemini Enterprise inherits the permissions of the connected system. Authenticate with a Docusign account that can only see the legal folders and that is the boundary. Authenticate with a company-wide administrator and every envelope in the account becomes searchable by anyone with access to the app, including the commercial terms of your competitors’ contracts if you happen to hold both sides of a white-label arrangement.
The sync schedule decides how stale the answers are
Pick the interval against how fast your contract flow moves. A supplier signing 30 documents a week does not need continuous sync, and a daily run is enough. Whatever you set, write it down, because in three months somebody will ask why an envelope signed this morning is not in the results.
Step 3: know what the connector actually reads
The Docusign connector brings in agreement metadata, envelope status, templates and the documents themselves, subject to the permissions above. That gives you counterparty names, dates, signing status and the contract text in one searchable place.
The gain is the ability to ask questions across a signed archive that previously answered only through a folder search and somebody’s memory. The gap is everything a contract lifecycle management system does: there is no obligation register, no automated renewal alert, no workflow that chases a signature on its own.
For a B2B team running weekly addendums, that difference is the whole point. The archive is where the answers already live.
Step 4: the three queries to run on Monday
These are the ones that earned their place when we mapped the workflow against a supplier’s contract week. Paste them as written, then adjust the jurisdiction names to your own portfolio.
Query 1: addendum triage
List every agreement in the connected Docusign account with an
executed addendum in the last 90 days. For each one give me:
counterparty, master agreement date, addendum date, and a
one-line description of what the addendum changed.
Group them by what changed: commercial terms, territory,
technical scope, compliance obligations, other.
Cite the envelope for every line. If you cannot identify what
an addendum changed, list it under "unread" rather than guessing.
Query 2: renewal and termination windows
Find every agreement with a renewal date, auto-renewal clause
or termination notice period falling in the next 120 days.
Return: counterparty, agreement type, the exact date, the
notice period in days, and the clause number the date comes from.
Sort by date ascending.
Flag separately any agreement where you found a renewal date
but no notice period, or a notice period but no clause reference.
Query 3: signature bottleneck
List every envelope sent for signature more than 14 days ago
that is not complete. For each: counterparty, date sent, which
party has not signed, and how many reminders were sent.
Query 3 is the one that pays for itself in the first week. In most B2B legal functions nobody owns the question of which envelopes are sitting unsigned, and the answer usually includes at least one agreement that everyone assumed had closed a month ago.
Step 5: licence terms review across US, Europe and LatAm
This is the workflow with the most value for a supplier and the most ways to go wrong.
A B2B contract changes shape by jurisdiction. A game studio selling into New Jersey needs different representations from the same studio selling into Malta, and the Brazilian market has moved fast enough that a template written 18 months ago is already behind. The review job is to check each agreement against the terms that jurisdiction requires, and it is exactly the kind of repetitive comparison work that eats a Tuesday.
The rules go into the prompt as a file you wrote. Build that file before you run a single comparison.
Build the jurisdiction file first
Write one document, per market, that states what a supplier agreement in that market must contain. Keep it factual and keep the citations in it. Something like this per entry:
MARKET: Brazil
Regulator: SPA (Secretaria de Premios e Apostas)
Supplier position: certification and authorisation requirements
under the fixed-odds regime
Contract must contain:
- [clause requirement, with the source article]
- [data localisation position, with source]
- [player fund handling, with source]
Terms that must NOT appear:
- [list]
Last verified: [date] by [name]
Source documents: [titles and links]
Repeat for the markets you actually sell into. For most European suppliers that is the MGA, the UKGC, ADM in Italy, DGOJ in Spain and ONJN in Romania. For the US it is state by state, so New Jersey, Michigan and Pennsylvania each get their own entry rather than one line saying “USA”. For LatAm, Brazil under the SPA, Colombia under Coljuegos and Peru under MINCETUR.
This file is the same idea as the context file we built for chat models, written for contracts instead of copy. It takes an afternoon and it is the difference between a review you can rely on and a confident guess.
Then run the comparison
Compare the attached supplier agreement against the jurisdiction
file for [MARKET].
For each requirement in the jurisdiction file, tell me:
PRESENT - quote the clause and give its number
ABSENT - state which requirement is missing
UNCLEAR - quote the clause and say what is ambiguous
Then list any clause in the agreement that conflicts with a
term the jurisdiction file says must not appear.
Do not assess anything that is not in the jurisdiction file.
If the agreement covers a market not in the file, say so and stop.
The last two lines matter more than the rest. Without them the model will start assessing the agreement against general contract principles, produce a page of reasonable-sounding commentary, and bury the three findings you needed.
Keep the jurisdiction file current. Brazil alone has moved twice this year, and a review run against a stale file returns clean results for terms that no longer apply. If you are entering a market rather than reviewing an existing one, the market entry brief workflow is the step before this one.
Step 6: what Deloitte and KPMG each give you
The launch listed ten partner names in one paragraph, and they are not the same kind of thing. Sorting them is a 5-minute job that saves a procurement conversation.
Deloitte: two agents you can deploy
Deloitte has two agents on Google Cloud Marketplace that work inside Gemini Enterprise.
Contract Summarize Pro reads a contract and produces a structured summary. For a B2B team this is the intake step: a new counterparty sends their paper instead of accepting yours, and you want the commercial and risk positions on one page before a lawyer reads all 40 pages.
Clause Guard is a redlining agent. It compares an inbound draft against your positions and marks the clauses that fall outside them. The value depends entirely on how well you have written down your fallback positions, so if your playbook lives in a partner’s head this agent will not help you yet.
Both deploy from Marketplace into your own Google Cloud project, which means your procurement process is a Marketplace purchase rather than a services engagement. That is a materially different signature path and a much shorter one.
KPMG: what an integrator engagement covers
KPMG appears on the list as a global systems integrator, alongside Accenture, Devoteam, Factor Law, Tribe.ai, Valtech, Zazmic, Zencore and 66degrees. There is no KPMG agent to install and no KPMG connector to switch on. What you are buying is people who configure the platform against your processes.
For a B2B supplier that is worth considering in one specific case: you hold licences or certifications in more than 8 markets, your contract templates have drifted apart across regions, and nobody internally owns the job of reconciling them. That is a consulting problem before it is a software problem, and an integrator engagement is a reasonable answer to it.
If you have 3 markets and one template, you do not need an integrator. Connect Docusign, write the jurisdiction file, and spend the budget elsewhere.
Step 7: check the permissions before anyone else gets access
Run this before you open the app to the wider team. Sign in as a user with limited Docusign access, ask a question whose answer sits in a folder that user cannot open, and confirm the answer comes back empty.
Permission inheritance is the feature the whole platform is sold on, and it is also the one that fails quietly. A wrong answer is visible. A user seeing a contract they should not see produces no error message at all.
What to test before you trust it
Five checks, each about 10 minutes, run before this workflow touches a live negotiation.
Test the citations by hand. Take one output from query 2 and open every envelope it cites. You are checking that the clause number exists and says what the model claims. Do this on 10 results. If all 10 hold, move to spot checks. If one fails, the workflow is not ready.
Test with a document you already know cold. Pick the agreement your team argued about most this year, run the jurisdiction comparison against it, and see whether the findings match what you concluded at the time. Disagreement is informative either way.
Test the empty case. Ask for renewal dates in a 30-day window where you know there are none. A model that returns a confident empty result is behaving. A model that produces something to fill the space is a model you check every time.
Test the sync lag. Sign a test envelope, then query for it at 1 hour, 6 hours and 24 hours. Now you know what “current” means in your setup, and you can tell the team.
Test the permission boundary twice. Once at setup and once after your next Docusign user change. Access reviews drift, and the connector reflects whatever the source system says on the day.
The limits
This workflow cuts the first-pass reading a person has to do. It does not produce legal advice and it does not sign anything off. Every finding that changes a negotiating position gets read by a qualified person before it leaves the building.
Gemini Enterprise for Legal is in preview. Preview features change, get renamed and occasionally get withdrawn, so do not build a process that only works if a specific preview connector survives. The Docusign and Microsoft 365 connectors are the stable base. The legal-specific ones are worth testing and not yet worth depending on.
The jurisdiction file is your responsibility, not the platform’s. Nothing in Gemini Enterprise knows whether your Brazil entry is current. If the file is 8 months old, the review is 8 months old, and it will read as authoritative either way.
Counterparty confidentiality applies to the connector the same way it applies to a shared drive. Before you connect Docusign, check whether any of your agreements restrict processing of that document by third-party systems, because a handful of platform and payment contracts do.
AI for iGaming is a recurring series from The iGaming Europe. Bartosz, our Head of Content, shares the prompts, setups and workflows he has tested on real iGaming work. One workflow per issue, including what went wrong. No tools to buy, no affiliate links.
Source: Google Cloud
