Use Cases

Common Use Cases for Sheets

Problem	Setup (Columns + Skills)	Workflow	Impact
Lead scoring takes too long	Columns: name, email, company, domain. Skills: job title, company description, lead score.	Enrich leads with job titles and company context → AI scores each lead → Review scores and notes → Push qualified leads to Salesforce.	Save hours of manual research per week; prioritize best-fit leads faster.
Cold outreach is inconsistent	Columns: contact info, firmographics. Skills: job title, company description, cold email generation.	Generate 3 personalized email variants per lead → Approve best option → Send or export to cadence tool → Track outcomes in status column.	Improve outreach quality and volume; maintain on-brand messaging at scale.
CRM data is incomplete or outdated	Columns: contact/account records. Skills: job title, company description, enrichment prompts.	Update missing fields (titles, company info) → Approve changes → Sync updates back to Salesforce/HubSpot.	Keep CRM clean with less manual data entry; improve downstream reporting.
Operational data is messy	Columns: expense details, categories. Skills: auto-categorization by rules or AI.	AI tags expenses or tickets by category → Team reviews edge cases → Export categorized data to Finance or Support systems.	Reduce errors; save time categorizing repetitive data.
Support tickets pile up without triage	Columns: ticket ID, subject, description. Skills: sentiment analysis, priority tagging, auto-routing.	AI reviews tickets → assigns urgency levels and routes to the right team → Support team reviews high-priority cases first.	Shortens response times; ensures urgent issues are surfaced immediately.

Summary: Sheets flex across functions wherever structured data meets repetitive work — from Sales and Marketing to Ops and Support — turning raw records into enriched, prioritized, and actionable outputs.

How Sheets Connect to Other Features

Sheets aren’t meant to stand alone — they connect with the rest of Motion to make data useful across your workflows.

• vs. Docs → Docs are for long form narratives like briefs, plans, or updates. Sheets are for structured data. Use them together: enrich lead data in a Sheet, then generate a campaign brief in Docs.

• vs. Knowledge → Knowledge holds atomic facts (like “Company founded in 2015”). Sheets apply enrichment logic across multiple rows of data. Think of Knowledge as your fact base, and Sheets as your processing engine.

• vs. AI Chat → AI Chat can query or update rows directly, making Sheets interactive. Example: “Show me all leads with a score above 7” → AI pulls from your Sheet.

• vs. AI Employees → Employees can run skills across rows automatically. Example: a “Sales Research Employee” enriches contacts in a Sheet daily, so the team always has fresh data.

Together, Sheets, Docs, Knowledge, Chat, and Employees form a closed loop:

• Data is captured and enriched in Sheets.

• Facts are stored in Knowledge.

• Insights are shared in Docs.

• Requests flow through Chat.

• Execution scales through Employees.