Playbooks & Help

Use Cases & Playbooks

These playbooks show how teams use Jarvis to automate sales prospecting, operations, customer success, marketing, and research. Every workflow is a sequence of plain-language prompts you can replicate today, no coding, just natural language. Because Jarvis covers every role, you run all of these from one place, and it spins up specialist sub-agents behind the scenes when a step needs heavy lifting.

Tip: Any of these is a great candidate for a Mission (so you can re-run it) or a Skill (so Jarvis runs it your way every time).

For Sales Teams

Playbook: Outbound Prospecting Pipeline

The problem: researching leads, personalizing outreach, and tracking follow-ups eats hours you could spend closing.

1. Research "Research 20 fintech companies with 50–200 employees. For each, find the CTO or VP of Engineering, their LinkedIn, what the company does, recent news, and any pain points we can address."

2. Outreach "Using that research, draft a personalized 3-email sequence for each prospect in our brand voice and value prop from the Brain. Send the first email in each sequence via Gmail."

3. Pipeline tracking "Create a sales pipeline board in Spaces with columns: Researched, First Email Sent, Replied, Meeting Booked, Proposal Sent, Closed. Add each prospect as a task."

4. Follow-up "Check the pipeline board for prospects in 'First Email Sent' for more than 3 days, and draft follow-ups for each."

Playbook: Pre-Meeting Research

"I have a meeting with Sarah Chen from Acme Corp tomorrow at 2pm. Research her background and Acme's recent news, prepare 5 talking points based on how we address their likely needs, and check the Brain for any previous interactions."

You walk in informed, web research plus your own history, in one brief.

For Founders & Operations

Playbook: Monday Operations Review

1. "Look at my calendar this week. Summarize my meetings, flag conflicts, and find blocks of free time for deep work." 2. "Check my Gmail for urgent emails from the weekend. Summarize the key ones and draft responses to the top 5." 3. "What tasks are overdue or due this week across all my Spaces? Organize by priority." 4. "Draft a Monday standup update summarizing last week's wins and this week's plan, reference our Q2 goals in the Brain."

Fifteen minutes and your week is triaged. Even better: schedule it as a recurring Mission so it's waiting for you every Monday.

Playbook: Project Planning

"We're launching a product on March 15th. Create a project board in Spaces with phases Planning, Design, Development, QA, Marketing Prep, Launch. Under each, create the key tasks, and set deadlines working backwards from March 15th."

For Customer Success

Playbook: Customer Health Monitoring

1. "Summarize all support tickets this week. Categorize by issue type and flag any customer with more than 2 tickets." 2. "For customers who seem at risk based on ticket patterns, draft a personal check-in email referencing their specific issues and offering a call." 3. "From the most common issues this week, create Brain snippets with our recommended solutions so we can answer faster next time."

Playbook: Customer Onboarding

"Create a 5-email onboarding sequence over 2 weeks: (1) welcome + first steps, (2) account setup with a link to our setup guide in the Brain, (3) key features for week one, (4) power-user tips, (5) a check-in. Use our brand voice and make new customers feel supported, not overwhelmed."

For Marketing

Playbook: Weekly Content Machine

1. "Suggest 5 blog topics for this week based on trending themes in our industry, check the Brain for our content strategy and what we've already published." 2. "Write the post on [topic] as a Page. Target 1,200 words, our brand voice, and a clear CTA." 3. "Create a LinkedIn post and 3 tweets promoting it, engaging and conversational." 4. "Add these pieces to the Content Calendar board in Spaces with publish dates."

Playbook: Product Launch Campaign

"We launch [feature] next Tuesday. Plan the campaign: (1) a launch blog post as a Page, (2) an email announcement, (3) a week of social posts (LinkedIn + X), (4) a landing page draft as a gated Page to capture leads, (5) a campaign tracking board in Spaces. Check the Brain for product details and brand guidelines."

For Strategy & Research

Playbook: Competitive Intelligence

"Do a competitive analysis of our top 5 competitors: [list]. For each, current offerings and recent launches, pricing and positioning, strengths and weaknesses vs. us, recent press, key differentiators. Create a detailed Page with a summary comparison table, and reference our product info from the Brain, with sources."

A report that would take an analyst days, grounded and cited.

Playbook: Market Entry Analysis

"We're considering expanding into the European market. Research market size and growth for our category, established competitors, regulatory considerations, and localization factors, then recommend an entry strategy. Be thorough, and create the report as a Page."

End-to-End Workflows

The real power is chaining steps into one flow. Hand Jarvis the whole thing in a single briefing, or run each stage as a Mission, outputs land in your shared workspace either way.

End-to-end deal flow: research the target market and ideal customer profile → find specific prospects and run outreach → book and prep meetings → onboard new customers → turn wins into case studies. Jarvis delegates each heavy stage to a specialist sub-agent and keeps the thread together.

Content-led growth: research trending topics → produce blog and social content → publish gated Pages to capture leads → follow up with everyone who downloads → onboard those who convert.

Tips

  1. Start with one workflow, pick your highest-value one and nail it before automating everything.
  2. Build the Brain first, these playbooks work dramatically better with rich context.
  3. Iterate, first outputs won't be perfect; give feedback and Jarvis improves.
  4. Track in Spaces, every workflow deserves a board for visibility.
  5. Save what repeats, turn a proven playbook into a recurring Mission or a Skill.
← IntegrationsFAQ & Troubleshooting →