Genipy and Google Slides

Teams build tools that fill a QBR deck for each account, create a pitch deck from the team template, build the weekly pipeline review deck with commit and best case, and prepare renewal decks for customer success with the contract end date and talking points.

In Slides alone, someone updates charts and figures by hand before every meeting, and each rep tweaks a copy of the template. A Genipy tool builds the deck from the numbers you enter or connect, using one team template, so every rep presents the same layout and message.

Yes. A tool your team builds creates a deck from your template and fills it with an account’s name, figures and next steps. The rep reviews the deck in Google Slides before it reaches a customer or a manager. The tool can also keep its own data, such as past QBR notes, in its own database.

From what your team enters or connects. A rep can type the figures into the tool, or the tool can read them from Google Sheets. Google Slides is where the deck is built and presented.

An admin of your workspace does it once: they sign in with Google on Genipy’s Integrations page, and Genipy checks the access before saving the connection. The admin decides which tools may use the Slides connection. Genipy gives your AI the setup link.

The tool is private by default and open only to teammates you invite by email, as Viewer, Editor or Owner, with roles enforced by the server. Viewers can open the tool and read its data, while generating a deck takes an Editor or an Owner. In Google Slides, owners decide who can edit, comment on or view each deck.

Yes, in two ways. For a deck that already exists, anyone with edit access can open its version history in Google Slides and restore an earlier version. If a new version of the tool starts building decks the wrong way, you roll back to the previous version of the tool in one click.