Most of the time, sending a contract means leaving whatever you were doing, opening the e-signature app, finding the right template, typing the signer's details, and clicking through three screens. If you already talk to Claude during the day, you can skip all of that. Here's a 50-second demo of what it looks like.
What happens in the video
The whole exchange is four messages.
- You ask in plain words. "Send my Roofing Service Agreement to Alex Stewart at alex.stewart@example.com for signature. I'm the provider." No form, no template picker.
- Claude reads the template. Through the GSD connector it sees the agreement has two signer roles, Customer and Provider, puts Alex in the first, and asks for the one thing it doesn't know: your name and email for the Provider role.
- You get a preview before anything is sent. Template name, both signers, both addresses, and the question "Should I send it?" This step is deliberate. The connector is built so that an assistant cannot send a document without a second confirmation, so a mistyped address or a wrong template gets caught here.
- You say yes. GSD sends the signing invitations. Alex signs on a phone with no account. Your own invitation lands in your inbox, and you can ask Claude "has Alex signed yet?" any time afterwards.
What the connector can and can't do
It can list your templates, prepare a document from one, send it, and report signing status. That's the full set on purpose. It cannot change a template's payment amount, add signers the template doesn't have, or send without the preview step. Every request is recorded in the document's audit trail as coming from a connected app, and nothing about the assistant appears on the signed document or the Certificate of Completion.
Setting it up
It takes about two minutes and works on every GSD plan, including the free one.
- In Claude, open the connectors menu and add GSD (or add it from the connector directory).
- Sign in to your GSD account when it asks. That's the only credential involved; there are no API keys to copy.
- Ask it to send something.
It works the same way in ChatGPT and in any other app that supports MCP, the open standard for connecting assistants to tools. The step-by-step guide, with screenshots, is at gsdhere.com/developers/mcp.
Why we built it this way
We didn't want a chatbot inside GSD. We wanted GSD available inside the tools people already have open. A property manager who drafts a lease renewal with Claude shouldn't have to switch apps to send it. A contractor who asks their assistant to "get the roofing job signed" should be able to do exactly that. The connector is small, and that's the point.
If you'd rather see it on your own documents, start free. Five documents a month, no credit card, and the connector is included.
Ready to get signing done? Start free with 5 documents a month and no credit card, or browse the e-signature guides.