Skip to content

Zapier Discovery-Form-to-Outline Automation: A Draft Assessment Outline Before Your Coffee Finishes

For IT Consultants ·

Tools:Zapier, Google Workspace
Time to build:1-2 hours
Difficulty:Advanced
Prerequisites:Comfortable asking ChatGPT or Claude to turn a list of notes into a structured document, since this automation asks an AI step to do that same job on its own.
ZapierGoogle Workspace

What This Builds

A new prospect's intake form sits in your inbox for a day or two right now before you find the hour to start a first assessment outline. This automation drafts that outline the moment the form comes in, landing as a Google Doc clearly marked for your review, so your first follow-up call starts from a half-built document instead of a blank one.

Prerequisites

  • A Professional plan with the AI by Zapier step available ($29.99/month)
  • A form tool that connects to Zapier, such as Google Forms
  • A Google account for Google Docs, free for personal use or your paid Business Standard account if that's what you already run client work through
  • An existing discovery intake form you're willing to redesign around the wording below

Your ongoing cost is whatever Zapier tier your task volume needs beyond its free allowance, since Google Docs itself is free to use for this.

The Concept

This automation is three linked steps instead of one manual one. A form submission triggers it, an AI step drafts an outline from the answers, and a Google Doc gets created holding that draft. No step in the chain waits for you to click anything, which is exactly why the form's wording matters so much: whatever a prospect types gets sent straight to the AI step with no screening in between.


Build It Step by Step

Part 1: Design the form around what it's safe to automate

This automation sends whatever a prospect types into the form to the AI step automatically, on every single submission, with no chance for you to review it first. That means the form itself must never ask for admin credentials, IP addresses, or a full employee list. Word the questions around business problems and rough counts instead of identifying technical detail:

  • "About how many employees use computers day to day" instead of "List employee names and logins"
  • "What's not working right now, in your own words" instead of "What's your current admin password"
  • "What systems do you currently rely on" (email platform, accounting software, in general terms) instead of a request for specific account numbers or network diagrams

Keep the form to five or six short-answer fields: company name, industry, employee count range, primary pain point, systems currently in use, and general timeline or urgency.

Part 2: Build the Zap

  1. Trigger: New form response on your chosen form tool.
  2. Action 1, AI by Zapier: Give it a prompt like:
Copy and paste this
Here are a prospect's answers from a technology assessment intake form:
{{form responses}}

Draft a first-pass assessment outline with these sections: Current State
Summary, Likely Assessment Areas, Open Questions for the Consultant. Write
the Current State Summary directly from what the prospect said, without
adding claims they didn't make. List Open Questions for anything the form
didn't cover that a full assessment would need. Do not recommend specific
products or pricing.
  1. Action 2, Google Docs, Create Document from Text: Use the AI step's output as the document body, and set the document title to include the prospect's company name and the words "DRAFT: Review Before Use." Save it into a folder reserved for new prospect assessments.
  2. Action 3, optional notification: Send yourself an email or Slack message with a link to the new document, so you know it's ready without checking the folder manually.

Part 3: Test before turning it on live

Submit a sample form response yourself and walk through the entire Zap end to end. Confirm the AI step's output reads sensibly, the Google Doc lands in the right folder with the right title, and your notification actually arrives. Only turn the Zap on for real submissions once one full test run has worked cleanly.


Real Example: A Dental Practice's Intake Form

Setup: The Zap above, connected to a Google Form embedded on the consultant's website.

Input: A 12-employee dental practice submits the form, describing slow office computers and no backup system in place.

Output: Within a minute, a Google Doc titled "Riverside Dental - DRAFT: Review Before Use" appears in the New Prospect Assessments folder, with a Current State Summary restating the slow-computer and no-backup issues in the prospect's own terms, a short Likely Assessment Areas list, and Open Questions noting that the form didn't specify how many workstations or what backup solution, if any, is currently in place.

Time saved: Cuts the time between a form submission and a first outline from days to minutes.


Before This Touches a Prospect

Every outline this Zap produces carries "DRAFT: Review Before Use" in its own title, and nothing in the Zap emails or shares that document with the prospect. You are still the one who opens it, checks it against what the prospect actually wrote, and decides what belongs in a real assessment. Treat the automation's output as a rough draft from a junior assistant working from limited information, not a finished document.

What to Do When It Breaks

  • The Zap silently stops running because a connected account's authorization expired → This is the failure you won't notice on your own, since prospects simply stop getting a fast follow-up and nothing tells you why. Turn on Zapier's built-in failure email alerts for this Zap, and periodically submit a test form entry yourself to confirm the whole chain still runs end to end.
  • The AI step produces a thin or garbled outline when a form field is left blank → Add a default fallback value for each field in the Zap, so a blank answer reads as "not specified" instead of confusing the AI step.
  • The Google Doc lands with sharing permissions that make it visible to more people than intended → Lock down the destination folder's sharing settings once, before the Zap runs for real, rather than checking permissions after each document is created.
  • The same prospect submits the form twice and you get two documents → Add a filter step that checks for a matching company name or email within a short time window, and skip creating a second document when one already exists.

Variations

  • Simpler version: Skip the Google Doc step entirely and have the AI step's output emailed to you directly as plain text, if you'd rather review outlines in your inbox than in a folder.
  • Extended version: If your PSA or CRM has its own Zapier integration, add a step that creates a new prospect record there automatically, so the lead shows up in your pipeline the moment the outline does.

What to Do Next

  • This week: Let it run on your next real form submission and compare the draft outline to what you'd have written by hand.
  • This month: Adjust the AI step's prompt once you've seen a handful of real outputs and know where it tends to guess too much or too little.
  • Advanced: Once an outline has been reviewed and edited, carry it forward into your discovery call as the starting point for the pain-point ranking and scope work that follows.

Advanced guide for IT consultant professionals. These techniques use more sophisticated AI features that may require paid subscriptions.