AI Stack Audit Template
A structured worksheet for auditing your current tool stack. Use it to identify what you already have that's AI-ready, what needs replacing, and what's missing before you start building.
How to use this template
Work through each category below. For each one, answer the questions honestly - then compare your answers to the "Ready signal" and "Not ready signal." Your goal is to identify any gaps that need to be addressed before you build the corresponding workflows. Most firms find 1 - 2 categories that need work before they can start.
CRM & Pipeline Management
Tracks contacts, deals, and client relationships - the primary data source for Plays 1, 2, and 3.
Audit questions
- What CRM are you currently using?
- Does it have API access? (Check Settings → API or Integrations)
- Are contact and deal fields consistently filled in, or are there gaps?
- Does it support outgoing webhooks?
- Does n8n have a native node for it? (Check n8n.io/integrations)
Ready signal
HubSpot, Salesforce, Pipedrive, or Close - with consistent data and webhook support enabled.
Not ready signal
Spreadsheet, shared inbox, or a CRM with no API. Address this before building anything.
Automation Platform
The workflow engine that connects everything. Every play runs through this.
Audit questions
- Do you currently use any automation tools (Zapier, Make, n8n)?
- If yes: are they actively used, or set up and forgotten?
- Do you have an n8n Cloud account or a self-hosted instance?
- Who on your team understands how existing automations work?
Ready signal
n8n Cloud or self-hosted, actively used, with at least one person who can maintain workflows.
Not ready signal
No automation platform, or Zapier/Make only. Plan for migration or parallel build.
AI / LLM Access
The intelligence layer. Every play that involves scoring, drafting, or summarizing uses this.
Audit questions
- Do you have an OpenAI account with API access? (Not just ChatGPT)
- Have you set spending limits in the OpenAI dashboard?
- Do you have an Anthropic account for Claude? (Optional but useful for long documents)
- Are API keys stored securely - not in shared docs or Slack?
Ready signal
OpenAI API access with spending limits set and credentials stored in n8n.
Not ready signal
Using ChatGPT manually but no API access. Set up the API before building any workflow.
Email Infrastructure
Required for any outreach or notification workflows. Plays 1, 6, and 9 all touch email.
Audit questions
- What email service/client does your team use? (Gmail, Outlook, etc.)
- Do you have a separate sending domain for automated emails?
- Does your email provider support API/SMTP access for n8n?
- Are your email authentication records set up? (SPF, DKIM, DMARC)
Ready signal
Google Workspace or Microsoft 365 with API access enabled, sending from a separate subdomain.
Not ready signal
Sending automated emails from your main domain without authentication records. This will hurt deliverability.
Document Generation
Needed for Play 3 (Proposal Draft) and any workflow that produces formatted output.
Audit questions
- Where do you currently create proposals and client documents?
- Do you have document templates that follow a consistent structure?
- Can your document tool output to PDF automatically? (Google Docs, Notion, Docusign, etc.)
- Does n8n have an integration for your document tool?
Ready signal
Google Docs or a tool with n8n integration, templated proposals, PDF export capability.
Not ready signal
Each proposal built from scratch in Word. Standardize your template before automating.
Project / Task Management
Needed for Play 6 (Onboarding Sequence) - automatically creating tasks and assigning them.
Audit questions
- What do you use for project and task management? (Asana, ClickUp, Linear, Monday, etc.)
- Does it have an API or n8n integration?
- Do you have standardized onboarding task templates?
- Who on your team owns onboarding tasks and delivery setup?
Ready signal
Asana, ClickUp, or Linear with n8n integration and a standardized onboarding checklist.
Not ready signal
Onboarding managed informally via email or Slack. Document the process before automating it.
Interpreting your results
You're ready to start building. Follow the 30-60-90 Day Roadmap and start with Play 1.
Address the gaps first. Most take 1 - 2 weeks to resolve (choosing a CRM, getting API access, standardizing a template). Don't build automations around broken infrastructure.
You have infrastructure work to do before automation makes sense. That's not a problem - it's clarity. Fix the foundation, then build.
Revenue Institute
Revenue Institute conducts a comprehensive AI readiness audit as part of every engagement - covering infrastructure, data, process, and team readiness before any workflow is built.