How ITERO88 gets client contracts signed without asking clients for a Google login

Introduction

Mark Jones is a User Experience Designer and Consultant at ITERO88. The documents ITERO88 sends for signature are contracts, and its clients sign them on SignWith. We asked Mark how SignWith is working out. Everything in quotes below is his own words.

His first words on how it is going: "Yeah, good." Asked whether he would recommend SignWith, he answered: "Yes."

Who ITERO88 are

ITERO88 gives organisations specialist digital support, and Mark runs it with a business partner. In his words:

“I have my own company, which I run with a business partner. We partner with organisations who need specialist digital support. Our expertise is UX and UI design, and front and back-end development. However, we do work more strategically with organisations to help teams within an organisation understand the real problems they're trying to solve and deliver solutions that we then continue to track, monitor and improve.”

The challenge

ITERO88 writes its documents in Google Docs, and its clients need to sign contracts. Google Workspace has its own signature feature, but Mark found it did not fit how his clients work:

“We needed to find a platform that would allow us and clients to be able to sign contracts. The documents we create are in Google Docs but the native signature functionality within Google Workspace requires the client to have a Google login, which they often don't.”

What changed after SignWith

ITERO88 kept writing in Google Docs and moved the signing step to SignWith:

“Therefore, SignWith allows us to export a Doc as a PDF, upload to SignWith and then the client can easily sign it there.”

“It's made it possible for clients to do this and for us to manage it at a sensible cost.”

1. 1Write the contract in Google Docs.
2. 2Export the Doc as a PDF.
3. 3Upload the PDF to SignWith.
4. 4The client signs it there.