This weeks newsletter included the news that Microsoft has released Scout the first always on Desktop agent to Frontier firms. This follows on the news about surprise billing where GitHub Copilot users found out just how much their musings, tools, and inefficient coding really cost when billing flipped from monthly fee to usage based token billing. The badly burned made the news.
I’m a long term Perplexity Pro subscriber and I think that the $20 a month is worth it. That same fee also buys me a certain amount of Computer credits, which I also occasionally use when I want Perplexity to build up a polished project. there are numerous other benefits that I enjoy like paywall free access to most news sources. That feature alone take a lot of the annoyance out of the Internet.
Then along comes Microsoft Scout which promises to learn my work patterns and do work on my behalf automatically in the background. I immediately wondered how much this was going to cost me given that Scout requires both a Copilot license AND a GitHub Copilot license.
So I launched M365 Copilot and asked. Then I asked it to compare Perplexity and Scout and finally I asked whether the price would be worth it given my pattern of work.
You’re now a fly on the wall, reading that conversation
How much is the GitHub license going to cost me to use this agent?
Copilot said:
Here’s the real cost picture for what you’ll need to run Scout—this is one of those “looks cheap, can surprise you later” setups.
💰 Base license cost (what you’ll see on the invoice)
For Scout, you need GitHub Copilot Business or Enterprise:
Copilot Business → about $19/user/month
Copilot Enterprise → about $39/user/month
👉 Most orgs testing Scout will start with Business ($19/user/month)
⚠️ The part most people miss (new as of mid‑2026)
Pricing is no longer just the flat fee.
GitHub Copilot now includes:
A monthly pool of AI credits
Usage-based billing beyond that pool
So:
Light usage → stays near $19/user/month
Heavy agent usage (like Scout) → can exceed included credits
📊 What that means specifically for Scout
Scout is important because it’s:
an always-on agent capable of multi-step, autonomous tasks
Those behaviors:
consume AI credits continuously not just occasional chat usage
👉 Translation:
Scout will burn credits faster than normal Copilot coding/chat use
Your real cost depends heavily on how much you let it run
💡 Realistic budgeting guidance (what people are seeing)
Based on how pricing is structured:
Baseline
→ ~$19/user/month (Business plan)
Moderate usage (typical testing / light automation)
→ likely still close to base price
Heavy usage (lots of automation / always-on workflows)
→ can exceed included credits
→ additional usage billed based on tokens/credits
👉 Microsoft/GitHub explicitly warn that usage can vary widely because pricing now depends on AI consumption.
github
🧠 One big licensing nuance for MSP-type environments
Two often-overlooked costs:
Enterprise plan adds more credits
$39 may actually be cheaper for heavy users
Enterprise Cloud requirement
Enterprise tier may require GitHub Enterprise Cloud (~$21/user/month)
which can push real cost closer to ~$60/user/month total
✔️ Bottom line (practical answer)
Expect $19/user/month to get started (Business)
Expect variable overage costs depending on usage
For serious Scout usage, budget higher than the base price
🔎 If you want a quick sanity check
Given your MSP/consulting context, a useful way to think about it:
Testing Scout personally → ~$20/month
Enabling for a small internal team → ~$100–$300/month baseline
Letting it run real workflows → budget becomes usage-driven, not license-driven
If you want, I can map this to a real-world MSP use case (like automating ticket triage or inbox management) and estimate what the credit burn would look like—that’s where this gets very interesting (and where most people get surprised).
I use my Perplexity Pro license quite a bit. It comes with Computer credits which I also use. How does Scout compare? $20 for Perplexity and $20 for Scout adds a lot to my monthly spend.
Copilot said:
You’re asking exactly the right question—because Scout vs Perplexity is not apples-to-apples even though the pricing looks similar at first glance.
Let me break this down in a way that maps to how you actually work.
🧠 The core difference (this is the big one)
Perplexity Pro ($20/month)
Interactive research tool
You drive it (prompt → response)
“Computer” usage = on-demand automation
You control when costs/usage happen
Microsoft Scout (+ GitHub Copilot)
Always-on autonomous agent
It runs in the background
Can take action across M365 + local system
You’re paying for ongoing activity, not just requests
👉 Think:
Perplexity = you working faster
Scout = a junior employee that never sleeps
💰 Cost comparison in practical terms
Tool Base cost How usage works Predictability
Perplexity Pro ~$20/mo Mostly fixed ✅ predictable
Scout (Copilot Business) ~$19/mo + usage Credit-based, ongoing ⚠️ variable
Key difference:
Perplexity “Computer” use is intentional
Scout activity is continuous unless constrained
And GitHub explicitly states: usage now consumes credits based on token consumption
additional usage is billed beyond included credits
⚠️ Where Scout gets expensive (fast)
This is what most people underestimate:
1) Autonomous behavior
Scout:
monitors inbox, files, meetings
runs multi-step workflows
can act without prompting
That means: constant credit consumption, not burst usage
2) Model switching
Higher-end models cost more per action.
GitHub notes: usage cost depends on model choice and tokens
So: “smarter Scout” = more expensive Scout
3) “Always-on” = always consuming
Perplexity: idle = free
Scout: idle ≠ truly idle (monitoring + context building)
🔍 Real-world usage comparison (how it feels)
Your Perplexity workflow
Research a topic
Run a few “Computer” actions
Done
✅ Cost stays bounded
Equivalent Scout workflow
Watches your email
Prepares meeting briefs
Tracks tasks
Automates flows
✅ Way more powerful
❌ Way more usage exposure
🧮 What you’re realistically comparing
If you’re deciding where to spend:
Perplexity ($20)
Best for:
research
synthesis
interactive exploration
ROI = your thinking acceleration
Scout (~$20–??)
Best for:
workflow automation
reducing coordination work
proactive task execution
ROI = reducing manual work
💡 Blunt reality (based on your usage pattern)
Given how you described using Perplexity:
👉 You are using Perplexity heavily as a thinking partner
Scout will NOT replace that.
Instead it adds:
automation
background execution
orchestration
🎯 My recommendation (practical, MSP-minded)
If you’re optimizing spend:
✅ Keep Perplexity if:
You’re doing research, writing, content, analysis
You value predictable cost
⚠️ Add Scout only if:
You have specific automation use cases, like:
inbox triage
meeting prep automation
recurring workflow execution
cross-M365 orchestration
Otherwise: 👉 Scout becomes an expensive curiosity
🔥 Simple way to decide
Ask yourself:
“What tasks do I want done without me asking?”
If you can’t list 3–5 concrete automations, Scout will feel overpriced.
🧭 Bottom line
Perplexity = thinking multiplier
Scout = execution multiplier
They stack—but they don’t overlap much.
If you want, I can map your actual daily workflows (email, MSP work, content creation, mastermind groups) to specific Scout automations so you can see if it’s worth adding—or just a shiny distraction.
Sources
You said:
Sure go ahead and map my work flows
Copilot said:
This is where Scout can either be game‑changing for you… or just rack up costs without much payoff. I mapped this specifically to how you work (MSP consulting, content creation, mastermind groups, speaking, etc.), not generic “email automation” fluff.
🧭 Your real workflows (what you actually do)
From everything I know about how you operate, your day breaks roughly into:
1) 🧠 Content + Thought Leadership
Writing (Petri articles, book, newsletters)
Podcast prep / run sheets
Research (AI, MSP trends, tools)
Speaking prep
👉 You already use Perplexity heavily here
2) 🧑💼 Client & MSP Consulting Work
Reviewing MSP financials
Advising owners
Structuring deals / M&A discussions
Building presentations
3) 📬 Communication Coordination
Email triage (clients, communities, partners)
Scheduling (podcasts, mastermind groups)
Follow-ups and loose tasks
4) 👥 Community / Mastermind Leadership
Preparing sessions
Tracking member progress
Pulling insights from discussions
Keeping engagement moving
5) ⚙️ Operational Overhead
Reminders, deadlines, recurring tasks
Admin work
Coordination across tools
🔍 Where Scout actually fits (and where it doesn’t)
✅ HIGH-value Scout use cases (worth the cost)
These are the ones that match Scout’s strengths:
1) Inbox → Action Engine (🔥 biggest win)
What Scout can do:
Watch your inbox continuously
Identify:
follow-ups
scheduling needs
“this needs a reply” vs “ignore”
Draft responses + propose actions
Why this matters for you: You have:
a lot of context-heavy conversations
loose threads (clients, podcast guests, MSP owners)
👉 This is where Scout feels like a junior assistant
2) Meeting & Podcast Prep Automation
What Scout can do:
Pre-assemble:
background on guests
recent conversations
related files/emails
Generate:
talking points
prep briefs
Reality check: You can do this with Perplexity/Copilot already… …but Scout can do it without you asking
👉 Value = removes cognitive overhead, not capability gap
3) “Things Falling Through the Cracks” Monitor
This is very “you”:
Scout can:
Notice:
unanswered emails
stalled threads
pending commitments
Nudge you or act
Why this matters: You run:
multiple streams (clients, content, community)
👉 This is one of the only tools that tries to solve coordination fatigue
4) Light Workflow Automation (carefully controlled)
Examples:
“If client sends financials → flag + summarize”
“If mastermind member posts update → track themes”
“If meeting scheduled → auto-prep brief”
⚠️ MEDIUM-value use cases (nice, but not essential)
Content prep / research
Scout can help
But Perplexity is better at:
deep research
synthesis
exploration
👉 Stick with Perplexity here
Document generation (presentations, writing)
Scout can draft things
But you’re already strong here
👉 Low incremental ROI
❌ LOW-value (don’t use Scout for this)
Writing articles/blog posts (Perplexity wins)
Financial analysis (Excel + your brain wins)
Deep research (Perplexity wins)
One-off tasks (Scout overhead too high)
🧮 ROI reality for YOU
Let’s be blunt and practical:
If you enable Scout but don’t configure it deeply:
It feels like a novelty
Generates “interesting but unnecessary” activity
Costs creep up
If you configure 3–4 real workflows:
You start getting:
✅ Less inbox stress
✅ Fewer dropped threads
✅ Faster meeting prep
✅ Reduced mental context switching
👉 That’s where it earns its keep
💰 Should you stack both tools?
Here’s the honest answer:
✅ YES — if you separate roles
Use:
Perplexity → thinking
Scout → execution
❌ NO — if you expect overlap
Scout will NOT replace:
research
writing workflow
idea development
🎯 My recommendation (tailored to you)
Given how you work:
Try Scout ONLY if you commit to:
Start with these 3 automations:
Inbox triage + follow-up detection
Meeting/podcast prep brief generation
“stalled thread” monitoring
👉 If you don’t set those up: Skip Scout for now
🔥 The easiest way to test without over-spending
Try 1 license
Limit scope:
email + calendar only
Watch:
does it reduce friction or add complexity?
🧠 Bottom line
Perplexity = makes you smarter and faster
Scout = reduces coordination and mental load
For someone like you: 👉 Scout is a manager/assistant amplifier, not a thinking tool
