Automatically generate a decision-ready ICP from your website content and publish it to Google Docs.
The AI agent crawls your website to extract up to 20 pages of content, then structures that data into a complete ICP document. It builds an executive summary, a one-page ICP, tiering and lead scoring, and ABM plays, all with an evidence log and confidence scores. Finally, it converts the ICP into a Google Doc and applies formatting in your Drive folder for easy sharing.
Concisely explains the core function.
Crawl up to 20 pages of site content to gather messaging, buyer signals, and context.
Extract and normalize data into a formal ICP structure.
Assemble a Markdown ICP with sections: Executive Summary, One-Pager ICP, Tiering & Lead Scoring, Demand Gen & ABM Plays, Evidence Log, and Section Confidence.
Convert Markdown ICP to Google Docs via batchUpdate and apply final formatting.
Create a document named “ICP for <Business Name>” in your Drive folder and apply formatting.
Log facts vs. inferences with confidence scores for auditability.
This AI agent turns scattered site content into a shareable, decision-ready ICP and removes manual drafting friction. It delivers a formatted Google Doc that teams can act on without reflowing data. The workflow is auditable, with confidence scores and an evidence log guiding decisions.
A simple 3-step flow that non-technical users can follow.
User submits Website URL and Business Name; the system redirects to the target Google Drive folder.
Crawl up to 20 pages, extract messaging, and assemble a Markdown ICP with sections and confidence data.
Convert Markdown ICP to Google Docs via batchUpdate and apply final formatting in Drive.
A realistic, end-to-end scenario.
A Growth team submits the Acme Widgets site URL and the business name “Acme Widgets LLC.” In about 8 minutes, the AI agent creates an ICP titled “ICP for Acme Widgets LLC” in their Drive folder, including an Executive Summary, One-Pager, Tiering & Lead Scoring, Demand Gen & ABM Plays, and a detailed Evidence Log.
One-sentence focus on practical adoption.
to accelerate ICP creation from site content into a shareable document.
to align ICP with on-site messaging for campaigns.
to enable targeted outreach with a clear ICP and lead scoring.
to inform GTM decisions with a decision-ready ICP.
to align product strategy with ICP insights.
to deliver client ICPs quickly with standardized output.
One supporting sentence about the tools in use.
Crawls up to 20 pages from the website and fetches content for ICP generation.
Generates the ICP content, sections, and confidence data from crawled content.
Creates and formats the ICP document in Drive.
Stores the final ICP document in the target folder.
Initiates the workflow when Website URL and Business Name are submitted.
Six practical scenarios that map to real workflows.
Practical concerns answered in detail.
The ICP output includes an Executive Summary, a One-Pager ICP, Tiering and Lead Scoring details, Demand Gen and ABM Plays, an Evidence Log, and a Section Confidence report. It is delivered as a shareable Google Doc named after your business. The structure mirrors the Markdown ICP that was generated from your site content, with clear sections and formatting. You can review and edit the final document in Drive as needed. The approach ensures you have a decision-ready artifact for GTM planning and outreach.
Up to 20 pages are crawled to extract messaging, buyer signals, pain points, and product claims. The crawler focuses on content that informs ICP attributes, such as ICP audience, buying roles, and decision criteria. Data is parsed into a structured ICP template with explicit sections. Sensitive data is not collected unless provided by the user, and the process emphasizes publicly available content. The result is a data-grounded ICP aligned with the site’s public messaging.
The workflow targets a defined ICP framework consisting of Executive Summary, One-Pager ICP, Tiering & Lead Scoring, Demand Gen & ABM Plays, Evidence Log, and Section Confidence. You can modify the content within each section after generation by editing the Google Doc. Advanced customization requires adjusting the prompt template or adding extra sections through the integration configuration. The core structure remains intact to ensure consistency and auditable outputs.
All actions use authenticated connections to your Google Drive and Google Docs. Data is processed within your account and stored only in your Drive folders. Credentials (OpenAI, Firecrawl, Google OAuth) are used to perform the necessary tasks and are not exposed beyond the automation flow. The system does not share your ICP content with third parties without your explicit consent. You maintain control over access to the final document.
From form submission to a ready Google Doc, the workflow typically completes within several minutes, depending on website size and Google API response times. Crawling up to 20 pages is designed to be efficient, so you can receive a complete ICP quickly for immediate GTM planning. You can trigger repeats or updates whenever the website content changes. The result is a near real-time reflection of your site messaging in the ICP.
If crawling is blocked by the site’s robots.txt or other protections, the agent gracefully degrades by using available cached or alternate sources and focusing on the most accessible pages. The ICP will reflect what could be gathered, with a noted limitation in the Evidence Log. You can supply additional inputs or allow manual adjustments to fill gaps. The workflow will still output a usable ICP document with clearly labeled limitations.
Yes. The final ICP is delivered as a Google Doc named after your business, which you can export or copy to other tools. The structure is designed to be interoperable with common ABM, marketing, and sales workflows. You can reference the Executive Summary and Lead Scoring in downstream campaigns, enablement decks, or CRM notes. The document acts as a single source of truth for ICP-driven activities.
Automatically generate a decision-ready ICP from your website content and publish it to Google Docs.
