Why does business news feel like it’s written for people who already get it?

Morning Brew changes that.

It’s a free newsletter that breaks down what’s going on in business, finance, and tech — clearly, quickly, and with enough personality to keep things interesting. The result? You don’t just skim headlines. You actually understand what’s going on.

Try it yourself and join over 4 million professionals reading daily.

Check it out

By Jonathan Peslar, Founder of LeadPanther

Word Count: 4,800+ words | Reading Time: ~20 minutes

Your tech stack is a mess.

Most businesses run ten to fifteen tools for lead generation.
None of them talk to each other.

You copy data between endless browser tabs.
You forget to follow up with warm prospects.
Deals die in the dark gaps between your tools.

This guide fixes that exact problem.

Claude Cowork sits dead center in your business.
It connects fourteen tools through MCPs.

One AI brain. Fourteen tools. Ten workflows.
Zero manual data entry for your sales team.

What is an MCP?

It stands for Model Context Protocol.
Think of it as giving Claude a set of hands.

Without MCPs, Claude just thinks and chats.
With MCPs, Claude acts and executes.
It reads your databases and writes your emails.

Your new revenue stack:

Apollo, Clay, LeadPanther, G2.
Gmail, Beehiiv, Slack, Calendly.
Fireflies, Granola, Figma, Gamma.
Notion, Airtable, Stripe.

How to use this guide:

Scan the ten workflows below.
Find the ones that patch your funnel gaps.
Copy the skill files.
Connect your MCP integrations.
Watch your pipeline fill on autopilot.

I run this exact stack across four products — GetDeals.ai, LeadPanther.ai, GetInterviews.ai, and my LaunchpadFast parent company.
Every workflow in this guide is battle-tested on real revenue.

Forget the complex technical documentation.
We will talk about MCPs in plain business English.

The mental model is simple.
Claude is the brain of your operation.
MCPs are the hands that do the heavy lifting.

Without them, you run queries and copy the text.
With them, you delegate entire business processes.

Claude reads your Airtable base.
Claude drafts your outbound emails.
Claude audits your prospect lists.

Here is your reference map for the new stack.

Find (Top of Funnel)

→ Apollo — Prospect lists, company intel, intent data
→ Clay — Data enrichment across fifty sources
→ LeadPanther — Lead magnet delivery and capture
→ G2 — Buyer intent from review and comparison activity

Engage (Mid Funnel)

→ Gmail — Outreach, follow-ups, sequences
→ Beehiiv — Newsletter subscribers, engagement data
→ Slack — Lead alerts, internal handoffs

Meet

→ Calendly — Booking trigger, meeting prep kick-off
→ Fireflies — Meeting transcript and action items
→ Granola — Meeting notes

Close

→ Figma — Visual mockups, solution diagrams
→ Gamma — Proposal decks, one-pagers

Manage

→ Notion — CRM, client notes, pipeline tracking
→ Airtable — Campaign tracking, lead scoring tables

Collect

→ Stripe — Invoicing, payments, subscription tracking

Installing an MCP takes less than five minutes.
Open your Claude Cowork workspace.
Navigate to the integration directory.
Paste the connection credentials for your tool.
Hit connect and start delegating tasks.

No code required. No complex server setups.
Just plug the tools in and turn the machine on.

Quick note.

We have had multiple instances of bots scraping this content and people republishing it without authorization.

This guide took 60+ hours to build. It is free. But it is not public domain.

To keep the full playbook available for real humans (and out of the hands of content thieves), we require a valid email address to unlock the remaining sections.

It takes 3 seconds. No spam. No upsells. Just proof you are a real person.

Enter your email below to unlock the full guide.

Workflow 1: The Inbound Lead Machine

Trigger: A prospect books a call via Calendly.

Chain: Calendly → Apollo → Clay → LeadPanther → G2 → Notion

Most sales reps show up blind to their calls.
They spend ten minutes skimming a company website.
That wastes time and kills your conversion rates.

You need bespoke intelligence before you say hello.

This workflow triggers the moment a meeting hits your calendar.
It grabs the prospect email from the booking.

Apollo pulls their company size and tech stack.
Clay hunts for recent news and hiring signals.
LeadPanther checks their past lead magnet downloads.
G2 audits their recent competitor software searches.

Claude packages this data into a one-page brief.
It drops that brief straight into your Notion CRM.

You walk into every meeting holding all the cards.
You know their pain points before they speak.

Here is the exact skill file to copy.

Here is a sample of the Notion brief output.

This automates forty-five minutes of manual prep work.
Zero human intervention required.

Workflow 3: The Outbound Prospecting Engine

Trigger: You define your ideal customer profile once.

Chain: Apollo → Clay → Gmail → Airtable → Slack

Cold outbound is broken.
Generic spam gets ignored by default.

Personalized emails take twenty minutes to write by hand.
You cannot scale that math to hit quota.

This engine crushes the manual research bottleneck.

It triggers when you feed Claude an ideal profile.
It pulls fifty matching targets from Apollo.
It enriches every single prospect via Clay.

Claude writes a custom first line for each person.
It bases the hook on real business signals.

It drafts fifty emails in your Gmail outbox.
It logs every prospect in your Airtable base.
It sends a Slack alert when the batch is ready.

You do fifty deep-researched emails in two minutes.

Here is the difference this workflow makes.

Generic template approach:

The MCP enriched output:

You get five times the response rate.
You spend a fraction of the time.

Workflow 4: The Newsletter-to-Pipeline Converter

Trigger: Every week on a set schedule.

Chain: Beehiiv → Apollo → Clay → LeadPanther → Gmail → Airtable

Your newsletter subscribers are your warmest audience.
They read your content week after week.

Most founders never do anything with this engagement data.
They leave massive revenue sitting on the table.

This workflow turns passive readers into active pipeline.
It cross-references engagement data with prospect intelligence.

It audits Beehiiv for your top clicking subscribers.
It runs them through Apollo for company fit.
It checks LeadPanther for specific asset downloads.
It ranks the top ten hottest leads.
It drafts a direct pitch in Gmail.

Here is the exact skill logic.

You stop guessing who wants to buy.
You let the data dictate your outreach schedule.

Workflow 6: The Lead Magnet Delivery Engine

Trigger: Someone comments your keyword on a social post.

Chain: LeadPanther → Apollo → Clay → Gmail → Airtable → Slack

This is where LeadPanther shines the brightest.
I built LeadPanther to solve this exact problem for my own lead magnets.

A prospect comments on your post.
LeadPanther catches the comment and delivers the asset.
It captures their verified email in the process.

But a simple download is just step one.
Most businesses stop there and lose the deal.

This workflow enriches every single captured lead.
It turns a random email into a full profile.
It scores their buying potential in real time.
It alerts your team if a whale downloads your asset.

Here is how you build the engine.

You strike while the iron is piping hot.
You never let a high intent prospect cool down.

Workflow 7: The Content Repurposing Machine

Trigger: You publish a long form text asset.

Chain: Figma → Gamma → Beehiiv → Notion

Creating core content takes hours of deep work.
Posting it once is a massive waste of effort.
You need volume to dominate your niche.

This workflow multiplies your output by ten.
One core essay becomes endless top of funnel assets.

It builds visual frameworks in Figma.
It generates presentation slide decks in Gamma.
It drafts newsletter snippets for Beehiiv.
It logs all the variations in Notion.

This is inbound lead generation at true scale.

You feed the machine one piece of text.
The machine feeds your entire distribution funnel.

Workflow 2: The Post-Meeting Closer

Trigger: Meeting ends. Fireflies or Granola captures the transcript.

Chain: Fireflies/Granola → Figma → Gamma → Gmail → Calendly → Notion/Airtable

Meetings are a massive time sink.
You spend an hour on the phone.
Then you spend two hours on admin tasks.

This is amateur behavior.
Professionals delegate admin work to machines.

Workflow 2 fixes the post-call slump.
It triggers the second you hang up.

Granola or Fireflies captures every word.
That transcript is pure gold.
But raw text is useless.
You need structured data.

Claude reads the transcript and extracts the core pain points.
It hunts for budget signals.
It defines the decision timeline.
It outlines exact next steps.

Then the real magic happens.

Figma takes those extracted needs.
It draws a custom solution diagram.

Gamma takes that diagram.
It builds a stunning proposal deck.
Scope. Timeline. Pricing. Deliverables.

All pulled straight from the call.
All formatted in your brand style.

Gmail drafts the final email.
It attaches the Gamma deck.
It drops in your Calendly link.

Notion updates the deal stage.
All of this happens in the background.
You do not lift a finger.

Here is the exact chain of events:

→ Fireflies/Granola captures the full transcript
→ Claude extracts: pain points, budget signals, decision timeline, specific needs, next steps
→ Figma generates a solution diagram or mockup based on what the prospect described
→ Gamma builds a proposal deck: scope, timeline, pricing, deliverables — all pulled from the transcript
→ Gmail drafts a follow-up email with the deck attached and a Calendly link for the next call
→ Notion/Airtable updates the deal stage and logs all extracted intel

Meeting ends at 2:00 PM. Proposal in their inbox by 2:05.

Here is your skill file.

Workflow 8: The Event-to-Pipeline Converter

Trigger: You host a webinar, workshop, or live session.

Chain: Fireflies/Granola → Apollo → Gmail → Gamma → Airtable

Webinars are great for top of funnel.
But most founders ruin the follow-up.

They send a generic mass email.
They ignore the specific questions asked.
They treat every attendee the same.

This is a massive mistake.

Workflow 8 audits your event data.
It finds the hidden buying signals.

Fireflies captures the event Q&A.
Claude maps questions to pain points.

If someone asks about pricing, they are hot.
If someone asks about integration, they have intent.

Apollo steps in next.
It enriches every single attendee.
You get company size and revenue data.

Now you can score the list.
Claude ranks the attendees.

Gmail drafts custom follow-ups.
It references the exact question they asked.

Gamma builds a one-page event recap.
Airtable logs the entire dataset.

You wake up the next day.
Your pipeline is full of warm conversations.

Here is the process:

→ Ingest the event transcript from Fireflies/Granola
→ Extract attendee questions and map them to pain points
→ Cross-reference attendees against Apollo for company intel
→ Score attendees by engagement level (asked questions = hot, just watched = warm)
→ Draft follow-up emails for the top 10 hottest attendees via Gmail
→ Create a recap one-pager in Gamma
→ Log everything in Airtable with engagement scores

Here is the skill file.

Workflow 9: The Proposal Autopilot

Trigger: You decide to send a proposal to a prospect.

Chain: Notion → Fireflies → Apollo → Gamma → Figma → Gmail → Stripe → Calendly

Closing deals requires precision.
You cannot drop the ball here.

Generic proposals kill deals.
You need context from every interaction.

But gathering that context takes hours.
You dig through old Notion pages.
You re-read Fireflies transcripts.
You check Apollo for recent company news.

Workflow 9 handles this entire hunt.
It acts as your chief of staff.

First, it pulls your Notion history.
Second, it reads the Fireflies transcripts.
Third, it checks Apollo data.

It hands this context to Gamma.
Gamma drafts a master proposal.
Figma builds custom visual mockups.
Stripe generates a live payment link.
Gmail wraps it all in a drafted email.
Calendly secures the review call.

This is the apex of the MCP stack.
It uses 8 different MCP tools.

A human needs 3 to 4 hours to build this.
Claude crushes it in minutes.

Here is the exact action chain:

→ Pull client notes and past conversation history from Notion
→ Pull meeting transcripts from Fireflies
→ Pull company intel from Apollo
→ Generate a proposal deck in Gamma (scope, timeline, pricing, deliverables)
→ Create visual mockups or architecture diagrams in Figma
→ Draft the send email in Gmail with the deck attached
→ Create an invoice draft in Stripe
→ Include a Calendly link for a follow-up call

Here is the skill file to run it.

Workflow 5: The Revenue Radar

Trigger: Weekly or monthly.

Chain: Stripe → Notion/Airtable → Gmail → Slack

Protecting revenue is your prime directive.
New leads mean nothing if old clients churn.

Most businesses obsess over new leads.
They ignore the money sitting in their accounts.
They react to churn after it happens.

Workflow 5 gives you a radar.
It watches your existing revenue.
It spots trouble before the client leaves.

Stripe holds your payment truth.
Notion holds your project status.
This workflow forces them to talk.

It looks for failed payments.
It flags upcoming annual renewals.
It audits recent client communication.

No contact in 30 days? Red flag.
Project complete and happy? Upsell flag.

Gmail drafts the perfect intervention message.
Slack sends you a digest.

You review the digest over coffee.
You approve the emails with one click.

Here is how the radar works:

→ Pull subscription data and payment history from Stripe
→ Cross-reference with client project status from Notion/Airtable
→ Flag: renewals approaching, at-risk clients (failed payments, no recent contact), upsell candidates
→ Draft retention or upsell messages via Gmail
→ Send a weekly Slack digest: "3 renewals this week, 1 at risk, 2 ready for upsell"

Use this skill file to trigger the radar.

Workflow 10: The Win-Back Campaign

Trigger: Monthly review.

Chain: Stripe → Notion/Airtable → Beehiiv → Gmail → Slack

Lost customers are a goldmine.
You already paid to acquire them.
They already trust your brand.
Sometimes timing was just wrong.

Churned customers are not dead.
Some just need a nudge to return.

Workflow 10 runs your win-back efforts.

It digs through Stripe for lapsed accounts.
It checks Notion for past friction.
It calls Beehiiv to check engagement.

Are they still reading your newsletter?
If yes, they are warm.
If they unsubscribed, they are cold.

Claude segments the list.
It defines who needs re-education.
It defines who gets a hard offer.

Gmail drafts the customized campaigns.
Slack notifies you of the drafts.

You reclaim lost revenue with zero manual work.

Here is the exact chain:

→ Pull churned/lapsed customers from Stripe
→ Pull their history from Notion/Airtable
→ Check Beehiiv engagement (still opening emails = warm, unsubscribed = cold)
→ Segment into: win-back, re-education, lost
→ Draft tailored messages per segment via Gmail
→ Slack weekly digest

Run this skill file to reclaim lost revenue.

This is your action plan for Monday morning.
Practical execution. Blunt truth. No theory.

I installed these workflows one at a time across my LaunchpadFast portfolio.
Here is the order that delivered the fastest ROI.

Reading this guide changes nothing.
Execution is the single metric that matters.

You must build the stack.
But you must build it in order.

Do not rush this process.
If you rush, you will break things.

Priority Order (install these first):

→ Week 1: Workflow 1 (Inbound Lead Machine) — instant ROI on every sales call
→ Week 2: Workflow 3 (Outbound Prospecting Engine) — fills top of funnel
→ Week 3: Workflow 2 (Post-Meeting Closer) — converts meetings into proposals
→ Week 4: Pick based on your biggest funnel gap

Common Mistakes:

→ Trying to install all 10 at once (pick 1, master it, add the next)
→ Not configuring context files (the skill is only as good as the data you give it)
→ Skipping the Airtable/Notion tracking step (if you don't track it, you can't improve it)

The Stack It Approach:

Do not install all 10 workflows on Monday.
Pick one single workflow.

Master the prompt structure.
Configure your context files.
Feed Claude good data.
Trash data creates trash output.

Start with one workflow.
Run it for a week straight.
Measure the time saved.
Feel the friction disappear.

Then add the next tool to the chain.

In 4 weeks you have a full pipeline.
It runs on raw machine speed.

Your pipeline is only as fast as the slowest manual step. Remove every one of them.

Option 1: Do It Yourself

You have the skill files. You have the workflow maps. You have the implementation playbook.

Install Workflow 1 this week. Measure the time saved. Add Workflow 3 next week.

If you get stuck, join Agent J — our free AI community with 500+ builders who are doing the same thing.

→ Join Agent J (Free)

Option 2: Get It Done For You

If you want these workflows installed, configured, and running inside your business — I do this for clients.

I audit your pipeline, pick the workflows that move the needle, connect the MCPs, build the skill files, and hand you a working system.

→ Book a Build Strategy Session

Option 3: Go Deeper

Agent J Plus ($87/mo) is the hands-on version. Weekly live builds, 4-module curriculum, and direct access to the team building this stuff every day.

→ Join Agent J Plus

Connect with me:
→ LeadPanther.ai — Lead magnet delivery and capture
→ GetDeals.ai — AI-powered sales outbound
→ Newsletter — The Pulse (weekly AI ecosystem briefing)