Relevance
Leonardo + Pluto - LinkedIn Outreach Duo

Leonardo + Pluto - LinkedIn Outreach Duo

workforce Workforce

Creator

Tools

Get Personal Profile from LinkedIn
Google search
🗃️
🌐
Get Recent Posts from LinkedIn
🔭
Get All Messages from Chat
Send Follow-Up Message (new)
Send First LI Message

Integrations

Google search
Extract content from website
LinkedIn

Description

Pluto, the Prospect Pilot performs in-depth research on a prospect and produces a detailed report. Leonardo, the LinkedIn Luminary sends hyper-personalised LinkedIn DMs to those prospects. --- Want to see how this fits into a complete outbound system? Check us out 👉 https://www.altari.ai/ Or grab a quick call here 📆 https://cal.com/altari/30min 👾 --- P.S join our free community for more templates, resources and guides 📚 https://www.skool.com/altari

Clones

Clone
171

Example Task

Leonardo + Pluto - LinkedIn Outreach Duo
Add conversation metadata
Get Personal Profile from LinkedIn
Get Recent Posts from LinkedIn
Google search
Google search
Google search
🌐
🌐
🌐
🌐
🌐
🌐
Add conversation metadata
Leonardo + Pluto - LinkedIn Outreach Duo

Leonardo + Pluto - LinkedIn Outreach Duo

provided an update

Executive Summary

John Doe is a 123 Main Street, City, State 12345–based AI systems builder and co‑founder / CTO of Acme Corporation, focused on practical AI agents for outbound sales and lead generation. He is also a Tech Solutions Inc. Certified Expert & Partner and publishes frequent “build in public” LinkedIn threads showing agent templates, demos, and playbooks. Key engagement signals: (1) active LinkedIn thought leadership around AI agents (recently ran a “7 agents in 7 days” series), (2) product-first mindset (website.com), and (3) public willingness to share templates and DM for help — all strong triggers for a short, productized outreach offering either technical integration help, a marketplace collaboration, or a targeted use-case conversation.


Prospect Overview

  • Full name and current role/title

    • John Doe — Co‑Founder & CTO at Acme Corporation; Tech Solutions Inc. Certified Expert & Partner (self‑employed partner role).
  • Current company and division

    • Acme Corporation (co‑founder / CTO) — product focus: AI agents for outbound sales systems.
    • Tech Solutions Inc. — Certified Expert & Partner (partner/implementer for Tech Solutions Inc. platform).
  • Professional summary and areas of expertise

    • Builds multi‑agent AI systems for practical business outcomes: lead sourcing, enrichment, personalized outreach, CRM syncs, and integrations (n8n, Tech Solutions Inc., Google Sheets, etc.). Strong practical focus: turning AI prototypes into reliable production workflows for outbound sales and growth operations.
  • Location and background highlights

    • Based in 123 Main Street, City, State 12345. Background: software engineering → growth & ops → AI agent/product engineering and founder roles. Public content shows hands‑on building, client work, and community/marketplace contributions.
  • Education and credentials

    • Linked sources indicate ties to the University of Example (LinkedIn search snippet). Tech Solutions Inc. Certified Expert & official partner credential (listed on LinkedIn and Acme Corporation materials). Confidence: medium for formal education (public references not central in profile); high for Tech Solutions Inc. certification (explicitly listed).
  • Brief career trajectory (high‑level)

    • Started as a software/front‑end developer, moved into growth/operations and automation, then to AI agent engineering. Recent roles: Tech Solutions Inc. (partner/certified expert, Apr 2025 – present) and co‑founder/CTO at Acme Corporation (Aug 2025 – present). Openly builds and publishes AI agent templates and implementations.

Public Presence & Activity

  • Recent LinkedIn posts, articles, and public commentary (highlights from last 6 months)

    • Very active: multiple detailed posts showing agent builds, demos, and product lessons (sample posts):
      • “OpenAI Agent Builder launched — why it won’t replace n8n” (Agent Builder vs n8n analysis) — 2025‑10‑06
      • Demo: agent scraping Google Maps → research → outreach (“Belfort”) — 2025‑10‑02
      • “7 AI Agents in 7 Days” series (many agent drops + templates) — Summer/Fall 2025 (June–Sep 2025)
      • Repeatedly shares agent templates (Artemis, Gatsby, Midas, Hormozi, etc.) and offers them to followers who comment or DM.
    • Tone: pragmatic, engineering + GTM focus, and “build in public” transparent (successes + lessons).
  • Other public social activity (Twitter, Substack, GitHub, Instagram, Dribbble)

    • Substack (example.com): personal essays & creator/fitness reflections (older content; 2024 timestamps). Focused more on personal development and creator journey.
    • GitHub: profile exists (front‑end dev, small follower base), but no major public AI repos discovered.
    • Twitter / Instagram / Dribbble: present but lower signal for professional AI work compared to LinkedIn.
  • Public speaking engagements or panels

    • No explicit recent conference or panel listings found in the scraped sources. Primary format appears to be LinkedIn posts, demos, and Tech Solutions Inc. community content.
  • Published work, patents, or notable contributions

    • No patents located. Major contributions are practical: agent templates published/shared (e.g., Tech Solutions Inc. marketplace mentions) and community demos rather than formal academic publications.

Sources for activity: recent LinkedIn post stream pulled (multiple posts dated Jun–Oct 2025). See Sources & References below for links.


Role, Influence, and Networks

  • Scope of responsibility in current role

    • As Co‑Founder & CTO at Acme Corporation, John Doe appears to own technical architecture, agent design, product engineering, and delivery for clients. As a Tech Solutions Inc. Certified Expert, he implements and builds solutions on that platform for clients.
  • Reporting lines (manager, direct reports, peers)

    • Co‑founder relationship: Jane Smith listed as Co‑Founder & CEO (Acme Corporation). As CTO, John Doe likely reports to/partners with Jane — typical co‑founder structure. No public org chart but small founding team implied.
  • Decision‑making influence (budget, projects, initiatives)

    • High technical decision influence (tools, agent design, integrations). Likely influences technical vendor choices (e.g., Tech Solutions Inc., n8n), product prioritization, and client delivery contracts for Acme Corporation.
  • Professional network highlights (notable connections, partnerships)

    • Active within Tech Solutions Inc. community (templates + marketplace). Engagement with n8n and other automation tooling is frequent. Collaborations: co‑founder Jane Smith; Tech Solutions Inc. product/marketplace exposure.
  • Board or advisory positions

    • No formal board/advisory positions discovered in public sources.

Company Context (as relevant)

  • Company overview (Acme Corporation)

    • Acme Corporation builds AI outbound sales systems and prebuilt agent playbooks that source leads, conduct deep research, personalize outreach (email + LinkedIn), and sync results into CRMs. Positioning: pragmatic agent implementations that produce outcomes rather than prototypes.
  • Key company metrics (public / self‑reported)

    • Website claims (self‑reported): 600+ businesses engaged, 10,000+ trained, case studies with client outcomes (e.g., $180K pipeline for one client, 500+ qualified leads for another). These are company claims (use with caution).
  • How the prospect fits into broader company strategy

    • John Doe drives the technical capability that delivers Acme Corporation’s core product (agents + playbooks). His Tech Solutions Inc. partnership strengthens Acme Corporation’s ability to deploy multi‑agent systems quickly.
  • Company’s recent news relevant to the prospect’s role

    • Public launch messaging about Acme Corporation and several recent demos (June–Oct 2025) announcing new agent builds and public “build in public” campaigns, which John authored.

Opportunities & Strategic Insights

  • Personalised engagement opportunities (interests, pain points, triggers)

    • Interests: practical AI agents (lead gen, outreach automation), Tech Solutions Inc. tooling, n8n integrations, reusable templates that non‑engineers can adopt, marketplace distribution.
    • Pain points he’s publicly called out: agents that sit idle because of setup friction, fragile integrations, and the gap between AI prototypes and reliable execution.
    • Engagement triggers: new agent drops, “build in public” series, Tech Solutions Inc. marketplace features, or Acme Corporation launch announcements. He explicitly encourages DMs for comparisons and demos — good opening.
  • Key motivations and challenges identified

    • Motivations: build tools that reliably save time and produce revenue; scale agent playbooks to non‑technical users; grow Acme Corporation as a productized service.
    • Challenges: onboarding and execution friction (getting agents to produce real outcomes), integration reliability, and ensuring non‑technical teams can use agents.
  • Potential alignment with your objectives (partnership, sale, etc.)

    • If you sell tooling or services that improve agent reliability (observability, integration connectors, CRM syncs), or can help Acme Corporation scale templates into a marketplace/partner channel, there’s strong alignment. John Doe is likely receptive to partner offers, co‑building marketplace listings, or short product trials that reduce setup friction.
  • Strategic recommendations for approaching the prospect

    • Short, specific outreach that references a recent agent or post (e.g., Belfort Google Maps agent, Agent Builder analysis, or the 7‑agent series). Do not open with a generic pitch.
    • Offer one clear piece of value in the first message: a short technical improvement suggestion, marketplace distribution help, or an invite to a brief demo showing how your product reduces the specific friction he calls out (e.g., secure connectors, easier onboarding, monitoring).
    • Use social proof: reference his Tech Solutions Inc. involvement and any relevant mutual tools (n8n, Google Sheets, Tech Solutions Invent).
    • If asking for a meeting, propose a single short outcome-driven agenda: “15 minutes to show a way to reduce agent setup time by X% / avoid common integration breaks.”

Suggested short LinkedIn message examples (tailor before sending)

  1. Connection request (cold, 1 line + mention a recent post)
  • Hi John — I loved your Agent Builder vs n8n breakdown (Oct 6). I build [short description: connector/monitoring tool or partner program] that speeds up agent onboarding — would love to share one idea in a 10‑minute call. Interested?
  1. Follow up after connection (value + specific ask)
  • Thanks for connecting, John — the Belfort Google Maps agent was awesome. I sketched a small tweak that could improve contact enrichment accuracy by ~15% (quick win for scaling). Can I DM the sketch or book 10 minutes to walk through it?
  1. Offer to collaborate / marketplace angle
  • Hey John — congrats on Acme Corporation’s launch. We work with partners to turn templates into one‑click deployables on partner marketplaces (reduces setup time for non‑technical users). If you’re exploring distribution, I can share how we did this for [client] — 15 minutes?

(Each message references specific posts/agents and leads with a single, low‑effort CTA.)


Key Facts & Contacts

  • Public profile links (primary)
  • Company / product
  • Other public links
  • Public contact info
    • No verified public email or phone discovered in open sources during this search. DataBroker Inc. / other data brokers list contact records but were not used to extract direct emails here — use caution and follow data/privacy best practices before contacting via harvested addresses.
  • Additional noteworthy facts
    • Publishes and distributes agent templates publicly and often offers them through comments/DMs, meaning a direct message referencing a template/demo has a high chance of engagement.
    • Tech Solutions Inc. marketplace entries mention artifacts authored by John Doe — he’s familiar with marketplace/distribution flows.

Sources & References

(Information gathered Oct 16, 2025)

  • LinkedIn — John Doe profile (primary): https://example.com/in/john-doe/ — (profile details, roles, public post stream) — confidence: high for role & posts. Data pulled from LinkedIn profile and recent posts (June–Oct 2025).
  • Acme Corporation website (company & team): https://website.com/ — (product, case studies, team bios listing John Doe as Co‑Founder & CTO) — confidence: medium–high (self‑reported company claims).
  • Tech Solutions Inc. — main site: https://example.com/ — (platform referenced; John lists Tech Solutions Inc. Certified Expert & Partner on LinkedIn) — confidence: high for partnership claim via LinkedIn; site had limited scraping content.
  • Recent public LinkedIn posts (sample posts compiled from profile activity): posts dated 2025‑06‑16 through 2025‑10‑06 (multiple agent demos and commentary). Sources: LinkedIn activity stream pulled during profile scraping (posts include agent demos like “Artemis”, “Gatsby”, “Belfort”, “Midas”, and analysis like Agent Builder vs n8n). — confidence: high.
  • Substack: https://example.com/ — (personal writing / creator content) — confidence: high.
  • GitHub profile: https://example.com/ — (front‑end dev profile; limited public AI repos) — confidence: medium.
  • Google search snapshots & marketplace references (various search results pointing to agent marketplace & community posts around Tech Solutions Inc. / Acme Corporation): sample results obtained via queries for “John Doe”, “John Doe Acme Corporation”, “John Doe Tech Solutions Inc.”. — confidence: medium.

Dates & Confidence Summary

  • Date of information gathering: Oct 16, 2025.
  • High confidence findings: current roles (Co‑Founder & CTO, Acme Corporation; Tech Solutions Inc. Certified Expert & Partner); active LinkedIn post stream and themes (agent building, templates, outbound automation); Acme Corporation product positioning.
  • Medium confidence findings: specific education (University of Example appears in search snippets but not fully scraped in detailed profile fields here); company metric claims (self‑reported on Acme Corporation site).
  • Low confidence findings: private contact info, undisclosed org structure or exact headcount at Acme Corporation (not publicly detailed beyond product claims).

If you’d like, I can:

  • Draft 3–5 optimized LinkedIn message variants tailored to different outreach goals (connect, demo ask, partner pitch) and length constraints.
  • Produce a 30–60 second intro script you can use in a voice message or an outreach video.
  • Try to locate verified email addresses or company registration filings (requires permission to query paid data‑broker sources).

Which of the above would be most useful next?

Leonardo + Pluto - LinkedIn Outreach Duo
Add conversation metadata
Send First LI Message
Create scheduled trigger
Leonardo + Pluto - LinkedIn Outreach Duo

Leonardo + Pluto - LinkedIn Outreach Duo

provided an update

I've sent the first LinkedIn message to John Doe and scheduled a check in 20 minutes to see if he has replied. Here's a summary of what I've done:

  1. Researched John Doe thoroughly, learning that he's:

    • Co-Founder & CTO at Acme Corporation
    • Tech Solutions Inc. Certified Expert & Partner
    • Active in building and sharing AI agent templates
    • Recently ran a "7 AI Agents in 7 Days" series
  2. Created a personalized 3-touch message sequence focusing on:

    • His recent content (7 AI Agents series)
    • His expertise with Tech Solutions Inc.
    • His focus on practical AI implementation
  3. Sent the first message that:

    • Acknowledges his work
    • Establishes common ground (Tech Solutions Inc.)
    • Asks an open-ended question about his challenges
  4. Scheduled a follow-up check in 20 minutes to:

    • Check for his reply
    • Send the second message if needed

I'll return in 20 minutes to check for a response and take appropriate next steps based on whether he has replied.

Pluto, the Prospect Pilot performs in-depth research on a prospect and produces a detailed report.

Leonardo, the LinkedIn Luminary sends hyper-personalised LinkedIn DMs to those prospects.


Want to see how this fits into a complete outbound system?

Check us out 👉 https://www.altari.ai/

Or grab a quick call here 📆 https://cal.com/altari/30min 👾


P.S join our free community for more templates, resources and guides 📚 https://www.skool.com/altari

More by Altari

Felix, the Outbound Mastermind

Felix, the Outbound Mastermind

agent Agent •
Clone
93

"Find me 50 sales directors in Austin, Texas at companies with under 100 employees." This Agent takes a plain-English search query, and: → Scrapes LinkedIn to find matching prospects and their profiles → Researches each person (recent posts, company info, job details) → Writes a 4-touch personalised cold email sequence for each prospect It then exports everything to Google Sheets with prospect details, research, and email copy ready to go. 🎥 Full video breakdowns here: Short: https://www.instagram.com/reel/DQKzrankniM Long: https://www.youtube.com/watch?v=V33IhYsBIe8 Before this, you had to: Pay >$100/month for LinkedIn Sales Navigator Enter each search filter manually (no free-text / AI search) Subscribe to 3rd party tools to export any of the data All of the above, no longer an issue ✔️

Altari
Free
Belfort, Google Maps Leads with ICP Score + Personlised Emails
Add JSON array to Google Sheets
Find Google Maps Local Businesses

Belfort, Google Maps Leads with ICP Score + Personlised Emails

agent Agent •
Clone
58

Gets local businesses from Google Maps, finds leads and enriches them with personalised emails, Linkedin DMs ICP score and much more... Want to see how this fits into a complete outbound system? Check us out 👉 https://www.altari.ai/ Or grab a quick call here 📆 https://cal.com/altari/30min 👾

Altari
$4.99
Artemis Pro, the Ultimate LinkedIn Lead Engine
Add JSON array to Google Sheets
Extract & Enrich Leads from LinkedIn Post - V2

Artemis Pro, the Ultimate LinkedIn Lead Engine

agent Agent •
Clone
162

Scrapes viral post commenters and enriches them with emails, personalised DM's, ICP score and much much more. Demo 👉: https://www.youtube.com/watch?v=ryWPTCkB1bE Want to see how this fits into a complete outbound system? Check us out 👉 https://www.altari.ai/ Or grab a quick call here 📆 https://cal.com/altari/30min 👾

Altari
Free

You might also like

The Enterprise Document Language Translator

The Enterprise Document Language Translator

workforce Workforce • 5.0 Star (1) •
Clone
61

Stop Letting Poor Translations Slow Down Your Organisation Every enterprise carries risk when translations are unclear. Idioms collapse meaning. Tone shifts without warning. Technical terms get lost. Staff misunderstand instructions. Customers lose trust. The Enterprise Document Language Translator solves this through a four agent pipeline that supports all languages and all document types. It produces audit ready translations in thirty seconds and keeps your messaging clear across regions and teams. You can start it through chat or connect it to other workforces to build a complete translation workflow. You chat. It translates. You get a clean audit trail. What You Get Simple Chat Command @EnterpriseTranslate "Paste document" SOURCE English TARGET Spanish,Japanese,Dutch Four Agent Workflow Engine drafts a translation Auditor highlights tone, meaning and terminology issues through JSON Optimiser applies all fixes then polishes the final text API outputs a finished translation with workflow ready JSON Enterprise Accuracy Across All Use Cases Fixes idioms and informal phrasing Handles technical, operational and organisational language Preserves structure and formatting Delivers confidence scoring and full audit transparency Designed for Workflow Integration You can connect this workforce to document reviewers, contract analysers, communication drafters or any other Relevance AI workforce that accepts JSON. This makes it a strong first step in any multi language process. How It Works You type: @EnterpriseTranslate "We rocked up thinking the project would be simple but it became a dog's breakfast" SOURCE English TARGET Japanese Agent 1 produces a direct draft Agent 2 identifies incorrect or literal expressions Agent 3 corrects tone and meaning Agent 4 assembles the final output and JSON Before and After Example Language Pair: English to Japanese Source English We rocked up thinking the project would be simple but it became a complete dog's breakfast. Initial Machine Translation (Incorrect) ロックアップしたら簡単だと思っていたのに犬の朝食になった。 Back to English: When we locked up we thought it would be easy but it became a dog breakfast. What Went Wrong rocked up was translated literally dog's breakfast was converted into a food item Tone became casual and unclear Corrected Enterprise Translation 私たちはこの案件は簡単だと思って到着しましたが結果的に大混乱になりました。 Back to English: We arrived thinking the job would be simple but it turned into a major mess. Audit JSON Example {"issues":[{"phrase":"ロックアップした","fix":"到着した"},{"phrase":"犬の朝食","fix":"大混乱"}],"approved":true} Another Example Language Pair: English to Spanish Source English The supplier rocked up late which created issues during handover. Initial Machine Translation (Incorrect) El proveedor apareció tarde lo que creó problemas durante la entrega. Back to English: The supplier appeared late which created problems during the delivery. What Went Wrong appeared is not suitable for enterprise tone entrega reads as a parcel delivery not a handover process Corrected Enterprise Translation El proveedor llegó tarde lo que generó problemas durante el traspaso. Back to English: The supplier arrived late which caused issues during the handover. Audit JSON Example {"issues":[{"phrase":"apareció","fix":"llegó"},{"phrase":"entrega","fix":"traspaso"}],"approved":true} Perfect For Leadership and Communications Strategy messaging and organisation wide updates HR and People Teams Onboarding, training, codes of conduct and workforce policies Safety and Operations SOPs, hazard notices, emergency processes and field instructions Technical, Engineering and IT Product guides, technical manuals and system documentation Customer Service and Support Knowledge articles, help content and troubleshooting guides Sales and Commercial Teams Proposals, scoping documents and client presentations Governance and Risk Assurance documents, policy updates and compliance material Global Offices Any content that requires accurate multi language interpretation Legal Disclaimer This workforce is a translation support tool only and is not a certified translation service. All translations must be reviewed and approved by the user before use. Authority Builder™ and the creator provide the software on an as is basis and make no warranties of any kind. The user accepts full responsibility for all outcomes that arise from the use of this tool. In no event shall the authors or copyright holders be liable for any claim damages or other liability whether in an action of contract tort or otherwise that arises from or is connected to the software or the use of the software or any other dealings with the software.

Yasmin Cronin
Free
The 8-Agent Translation QA and Approval Pipeline

The 8-Agent Translation QA and Approval Pipeline

workforce Workforce •
Clone
31

Overview The 8-Agent Translation QA and Approval Pipeline is an eight agent translation suite for organisations that need reliable multilingual communication. Many companies struggle with translation tools that provide surface level output with no insight into accuracy, tone, cultural context or operational risk. This workforce solves that problem by delivering a complete translation workflow with educational insight, human approval and workflow ready data. It teaches users what changed and why. It highlights linguistic risks. It provides structured JSON for system integration. It offers a mandatory human approval step that prevents inaccurate or unsuitable translations from passing through internal workflows. This creates a transparent and auditable translation process that supports workplace communication, training and compliance. Legal Disclaimer This workforce is a translation support tool only and is not a certified translation service. All translations must be reviewed and approved by the user before use. Authority Builder™ and the creator provide the software on an as is basis and make no warranties of any kind. The user accepts full responsibility for all outcomes that arise from the use of this tool. In no event shall the authors or copyright holders be liable for any claim damages or other liability whether in an action of contract tort or otherwise that arises from or is connected to the software or the use of the software or any other dealings with the software. Key Features Feature 1: Eight stage translation and education workflow Each agent performs one focused task. You receive raw translations, linguistic review, cultural insight, JSON change data, formatted records and a refined final version. Feature 2: Mandatory human approval with English back translation Agent Eight presents the proposed translation beside an English back translation. Nothing proceeds until the user confirms yes or no. This protects organisations from errors and supports internal quality assurance requirements. Feature 3: Workflow ready structured outputs You receive token level difference JSON, complete bilingual reports and final translations that can support compliance, training and operational communication pipelines. How It Works Step 1. Provide your text Enter the content you need translated and select both languages. Step 2. The workflow activates all eight agents The Scribe creates the raw translation. The Examiner identifies linguistic and tonal issues. The Refiner explains deeper meaning and cultural context. The Keeper produces structured JSON change data. The Archivist organises and formats the material. The Curator produces the polished final translation. The Summoner prepares the full bilingual report. The Arbiter presents the translation with English back translation and waits for your clear yes or no. Step 3. User approval is required You must approve or correct the translation before the workflow continues. No automated progression is allowed. Step 4. Receive the final package You receive the approved translation, the reasoning behind the changes, workflow ready JSON and a complete bilingual report that demonstrates quality assurance. Use Cases Perfect for: Workplace and compliance documents Policies, procedures, contracts, regulations and internal communication where precision is critical. Training and technical content Safety modules, operational instructions, learning resources and technical manuals where clarity protects staff and reduces risk. Global and multilingual teams Organisations that need consistent communication across borders and require audit ready translation processes. Example Output You can expect: • A raw translation based on the original text • A list of identified issues with clear meaning explanations • Cultural and tone notes to support decision making • JSON token difference data for audit and automation • A refined and structured final translation • A bilingual record of the entire workflow • A mandatory approval stage with English back translation • A final JSON handoff only after your confirmed approval

Yasmin Cronin
Free
Qris, AI counsil workforce
Google Search

Qris, AI counsil workforce

workforce Workforce •
Clone
13

The “AI Advisory Board” (also called an LLM Council) is designed to prevent incorrect or one-sided answers from a single AI model. Instead of relying on one model, multiple leading language models work together. Each model answers a question independently, then they anonymously review and rate each other’s responses. Finally, a designated “chairman” model synthesizes these ratings into one consensus answer. This multi-step process increases reliability by combining different perspectives, reducing hallucinations through peer review, and producing higher-quality responses—especially for complex or critical topics. It also offers transparency because you can inspect each model’s individual answer. The system is open source, works locally, lets you choose which models take part, and can be integrated via the OpenRouter API. It is particularly useful for research, technical analysis, and decision-making where accuracy and confidence matter.

thinking services - Patrick
Free