
Sign up to save your podcasts
Or


GitHub Copilot's billing model changed on June 1 — and most enterprise teams are about to see their first full bill under the new system. For many organizations, it'll be the first real look at what AI adoption actually costs at scale.
The shift from flat-rate to usage-based billing sounds straightforward. Pay for what you use. But what your team is "using" turns out to be a lot more complicated than anyone expected — and the habits that felt like strong AI adoption six months ago are the same ones quietly running up the tab today.
Sumner Ohye works with GitHub partners and enterprise customers across the Americas and APAC. And since June 1, he's been fielding a lot of calls about billing. Parker Johnston is Insight's Agentic Field CTO — he's in the field with engineering teams every week. Together they get into what's happening on the ground, the common — and costly — mistakes people are making with token usage, and how teams are changing habits to keep token costs in check.
There's a reason Parker opens with "you can no longer YOLO mode it" — and it's not just about prompting.
Get GitHub Copilot solutions, available from Insight, because having the right partner means your billing controls, usage dashboards, and workflow guidance are in place before the charges hit — not after: https://www.insight.com/en_US/shop/partner/microsoft/github-copilot.html
Want to go deeper on GitHub? Check out these resources from Insight:
Burning Questions: Hot Takes on Developer Tools, AI, & What's Next: https://www.insight.com/en_US/content-and-resources/webinars/burning-questions-hot-takes-on-developer-tools-ai-whats-next.html
What's New in GitHub Advanced Security: https://www.insight.com/en_US/content-and-resources/webinars/whats-new-in-github-advanced-security-key-updates-explained.html
Maximizing Developer Efficiency With GitHub Enterprise: https://www.insight.com/en_US/content-and-resources/webinars/maximizing-developer-efficiency-a-guide-to-github-enterprise.html
Strategies for GitHub Actions Optimization: https://www.insight.com/en_US/content-and-resources/webinars/strategies-for-github-actions-optimization.html
Maximizing Team Productivity With GitHub Copilot: https://www.insight.com/en_US/content-and-resources/webinars/maximizing-team-productivity-with-github-copilot.html
Subscribe for more episodes of Insight On: new conversations every week on AI, technology strategy, and what's actually working in enterprise tech.
#GitHubCopilot #UsageBasedBilling #AgenticCoding
Chapters:
03:25 — Is a 24x bill increase normal? What actually changed June 1st
05:38 — The transition period and what enterprises need to do now
07:14 — Agentic coding: when to use AI vs. doing it yourself
09:27 — Governing AI agents inside your codebase
11:24 — How to set up billing thresholds and avoid access shutdowns
13:28 — Why a third-party partner beats going direct to GitHub
17:11 — What the GitHub billing shift means for software development's future
18:20 — Running AI models locally vs. cloud: the real cost comparison
20:25 — How GitHub Copilot adoption has shifted since June 1st
21:43 — GitHub's evolution from source control to full agentic platform
25:34 — Building trust in agentic workflows: cost, security, and code quality
28:07 — The biggest mistakes teams are making with model selection and context
31:53 — Best practices for developers new to the GitHub Copilot environment
35:58 — How to measure ROI on agentic AI: DORA metrics, retention, and churn
37:54 — Real-world agentic use cases where the ROI still holds
40:57 — Code review automation: understanding the double billing reality
By Insight EnterprisesGitHub Copilot's billing model changed on June 1 — and most enterprise teams are about to see their first full bill under the new system. For many organizations, it'll be the first real look at what AI adoption actually costs at scale.
The shift from flat-rate to usage-based billing sounds straightforward. Pay for what you use. But what your team is "using" turns out to be a lot more complicated than anyone expected — and the habits that felt like strong AI adoption six months ago are the same ones quietly running up the tab today.
Sumner Ohye works with GitHub partners and enterprise customers across the Americas and APAC. And since June 1, he's been fielding a lot of calls about billing. Parker Johnston is Insight's Agentic Field CTO — he's in the field with engineering teams every week. Together they get into what's happening on the ground, the common — and costly — mistakes people are making with token usage, and how teams are changing habits to keep token costs in check.
There's a reason Parker opens with "you can no longer YOLO mode it" — and it's not just about prompting.
Get GitHub Copilot solutions, available from Insight, because having the right partner means your billing controls, usage dashboards, and workflow guidance are in place before the charges hit — not after: https://www.insight.com/en_US/shop/partner/microsoft/github-copilot.html
Want to go deeper on GitHub? Check out these resources from Insight:
Burning Questions: Hot Takes on Developer Tools, AI, & What's Next: https://www.insight.com/en_US/content-and-resources/webinars/burning-questions-hot-takes-on-developer-tools-ai-whats-next.html
What's New in GitHub Advanced Security: https://www.insight.com/en_US/content-and-resources/webinars/whats-new-in-github-advanced-security-key-updates-explained.html
Maximizing Developer Efficiency With GitHub Enterprise: https://www.insight.com/en_US/content-and-resources/webinars/maximizing-developer-efficiency-a-guide-to-github-enterprise.html
Strategies for GitHub Actions Optimization: https://www.insight.com/en_US/content-and-resources/webinars/strategies-for-github-actions-optimization.html
Maximizing Team Productivity With GitHub Copilot: https://www.insight.com/en_US/content-and-resources/webinars/maximizing-team-productivity-with-github-copilot.html
Subscribe for more episodes of Insight On: new conversations every week on AI, technology strategy, and what's actually working in enterprise tech.
#GitHubCopilot #UsageBasedBilling #AgenticCoding
Chapters:
03:25 — Is a 24x bill increase normal? What actually changed June 1st
05:38 — The transition period and what enterprises need to do now
07:14 — Agentic coding: when to use AI vs. doing it yourself
09:27 — Governing AI agents inside your codebase
11:24 — How to set up billing thresholds and avoid access shutdowns
13:28 — Why a third-party partner beats going direct to GitHub
17:11 — What the GitHub billing shift means for software development's future
18:20 — Running AI models locally vs. cloud: the real cost comparison
20:25 — How GitHub Copilot adoption has shifted since June 1st
21:43 — GitHub's evolution from source control to full agentic platform
25:34 — Building trust in agentic workflows: cost, security, and code quality
28:07 — The biggest mistakes teams are making with model selection and context
31:53 — Best practices for developers new to the GitHub Copilot environment
35:58 — How to measure ROI on agentic AI: DORA metrics, retention, and churn
37:54 — Real-world agentic use cases where the ROI still holds
40:57 — Code review automation: understanding the double billing reality