Alphabet, Microsoft and Amazon lead 10 major earnings reports next week, according to Opening Bell Daily’s week-ahead preview. Alphabet and Microsoft report on Wednesday, October 28, 2026, and Amazon follows on Thursday, October 29. For software engineers, the dates matter for a practical reason: each company sells a flagship AI coding product, and each will face questions about what those products earn.
Microsoft owns GitHub Copilot. Amazon runs Kiro, which CEO Andy Jassy has called its agentic coding service. Alphabet sells Gemini Code Assist through Google Cloud. The three cloud divisions also buy the chips, build the data centers and set the prices that every AI editor, agent and code-review bot ultimately runs on.
This analysis covers the calendar, the developer-tool numbers each company has already put on record, and the questions worth listening for. We covered the product side recently, including how GitHub Copilot now controls desktop apps on two operating systems. Preview sources publish conflicting consensus estimates, so this piece sticks to confirmed dates and figures the companies stated themselves.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
Earnings Week at a Glance: Oct. 27 to Oct. 30
The week opens Tuesday, October 27, with Visa and The Coca-Cola Company, according to TheStreet Pro’s earnings calendar for the week of October 26. Wednesday brings the two cloud-and-developer heavyweights, Alphabet and Microsoft. Thursday adds Amazon, Eli Lilly and Company, and Mastercard Incorporated. Friday closes with Exxon Mobil Corporation, AbbVie Inc. and Chevron Corporation.
Alphabet’s third-quarter 2026 call is listed for 1:30 p.m. Pacific Time, which is 4:30 p.m. ET, on October 28. Sources disagree on the exact timing for Microsoft and Amazon, with some placing the releases after the close and others listing different windows. Check each company’s investor relations page on the day before you plan around a call.
Only three of the week’s reports touch the developer-tools market directly. The rest give useful context on consumer spending, energy and health care, but they will not tell you whether engineering teams are paying for AI assistants. That is why this site treats Wednesday and Thursday as the two days that count.
The Calendar: Who Reports and When
The table below lists the names confirmed in our fact sheet. Apple appears on one calendar for Thursday, October 29, but it is not part of the headline’s confirmed list, so treat that date as provisional.
| Company | Report date | Developer-tool relevance |
|---|---|---|
| Visa | Tue, Oct. 27, 2026 | Low (payments) |
| The Coca-Cola Company | Tue, Oct. 27, 2026 | Low (consumer goods) |
| Alphabet | Wed, Oct. 28, 2026 (call 1:30 p.m. PT / 4:30 p.m. ET) | High (Google Cloud, Gemini Code Assist) |
| Microsoft | Wed, Oct. 28, 2026 | High (Azure, GitHub Copilot) |
| Amazon | Thu, Oct. 29, 2026 | High (AWS, Kiro) |
| Eli Lilly and Company | Thu, Oct. 29, 2026 | Low (pharma) |
| Mastercard Incorporated | Thu, Oct. 29, 2026 | Low (payments) |
| Apple (one calendar only) | Thu, Oct. 29, 2026 | Medium (platform and Xcode ecosystem) |
| Exxon Mobil Corporation | Fri, Oct. 30, 2026 | Low (energy) |
| AbbVie Inc. | Fri, Oct. 30, 2026 | Low (pharma) |
| Chevron Corporation | Fri, Oct. 30, 2026 | Low (energy) |
The relevance column is our own editorial rating, not a figure from any calendar. Calendars such as MarketBeat’s next-week earnings page list the same dates and add estimates you can compare against the actual results.
Why a Coding-Tools Site Is Watching Cloud Earnings
Not long ago, an editor plugin counted as a side project. Today the biggest AI coding assistants sit inside companies that spend heavily on AI infrastructure. When those companies report, they reveal how many developers pay, how usage is billed and how much compute the agents consume.
Those answers shape your tooling decisions. Pricing models change after earnings calls, free tiers shrink or grow, and model access moves between products. A team choosing between Copilot, Kiro, Gemini Code Assist or an independent editor such as Cursor is partly betting on which parent company will keep funding the product.
Independent tools face the same forces from the other side. Our guide to running Cursor and VS Code on one repository with shared AI rules exists because teams increasingly hedge across editors. Earnings season is when the hedge either looks smart or looks unnecessary.
Microsoft on Oct. 28: GitHub Copilot Is the Number to Watch
Microsoft has given the clearest trail of developer-tool data of the three. On its fiscal 2026 second-quarter call, chairman and CEO Satya Nadella said, “In coding, we are seeing strong growth across all paid GitHub Copilot. Copilot Pro+ subs for individual devs increased 77% quarter-over-quarter. And, all up now we have over 4.7 million paid Copilot subscribers, up 75% year-over-year.” The remarks appear on Microsoft’s fiscal 2026 Q2 investor page.
By the third quarter, the framing had moved from seats to infrastructure strain. Nadella said, “When it comes to developers, GitHub itself is seeing unprecedented growth driven by the proliferation of agentic coding, and we are hard at work to scale and meet this demand.” The statement is on the fiscal 2026 Q3 page. Agentic coding means longer sessions, more tool calls and far more tokens per developer than autocomplete ever required.
The most recent datapoint came from the fiscal fourth quarter, when Nadella told investors, “When it comes to developers, GitHub Copilot now has 50 million users. This quarter, we introduced usage-based billing, and have continued to see Business and Enterprise seat growth, and also significant consumption revenue after the new model went into effect.” Read the full remarks on the fiscal 2026 Q4 page.
Subscribers Versus Users: Read the Metric Shift Carefully
Do not divide 50 million by 4.7 million and call it growth. The first figure counts paid Copilot subscribers, and the second counts users, a broader group that can include free-tier accounts. Microsoft changed the unit it reports, so the two numbers describe different populations.
The useful question for October 28 is which unit Microsoft chooses next. If it returns to paid subscribers, you can measure conversion. If it keeps reporting users and adds consumption revenue, the usage-based billing change is carrying more of the story. Either answer tells you how Microsoft wants investors to judge the product.
Alphabet on Oct. 28: Gemini Code Assist Inside Google Cloud
Alphabet gives developers the thinnest paper trail of the three. Our verified sources contain no on-record Alphabet executive quote about coding tools tied to this report, and the research we ran did not surface a dated Gemini Code Assist adoption figure. Reviews describe Gemini Code Assist as an enterprise and plugin-style product, which places it inside the broader Google Cloud pitch.
That makes Alphabet’s call a test of disclosure as much as performance. Analysts will press on Google Cloud demand, backlog and margins. Developers should listen for any number attached to Gemini inside coding workflows, even a passing mention of usage or enterprise seats. Silence would itself be informative, because it would suggest Google still treats coding assistance as a feature rather than a product line.
Google’s model ecosystem is also getting more crowded. Outside models now run on its platform, as we reported when OpenAI models reached Google Cloud, completing the big three clouds. For a developer, that means Google Cloud earnings are partly about whether customers pick Google’s own coding tools or simply rent Google’s servers for someone else’s.
Amazon on Oct. 29: Kiro, AWS and a $200 Billion Capex Line
Amazon’s developer story runs through AWS. On the company’s second-quarter 2026 call, Jassy said, “On your first question, Colin, we see a very substantial opportunity both for our customers and for AWS in building some of these agentic applications. Some of this is born out of what customers tell us they wish they had and they want to be using. Some of it is born out of just needing to provide those capabilities to ourselves inside Amazon. Kiro, which is our agentic coding service, is an example of that.” The transcript is on Yahoo Finance.
The same call carried the spending number. Jassy said, “Earlier this year, we said we plan to invest approximately $200 billion in cash CapEx in 2026, the majority of which to support AI and AWS.” The line comes from the Q2 call listing on Yahoo Finance.
Two things stand out. Jassy described Kiro as something Amazon built partly for itself, which suggests the company dogfoods its agents on internal engineering. And a capex plan of that size means AWS must fill new capacity with paying workloads, including the token-hungry agent sessions that coding tools generate.
Capex Is the Real Developer-Tools Story
Coding assistants look cheap per seat, yet they sit on some of the most expensive hardware ever deployed. Every autocomplete, test generation and multi-file refactor consumes accelerator time. When Amazon commits roughly $200 billion in 2026 cash capex, mostly for AI and AWS, the implicit bet is that demand like agentic coding will fill those racks.
Investors have started asking whether that bet pays back. CNBC’s October 23 market preview, whose headline warns that next week brings major risks for the stock market just as the AI trade keeps faltering, captures the mood. Cloud earnings are the moment companies must show revenue to match the build-out.
Other hyperscalers are moving in the same direction. We tracked how Meta raised AI capex to $145 billion while Tesla cut spending, and the contrast shows how different the pressure looks for companies without a cloud business to rent capacity out. Alphabet, Microsoft and Amazon can resell their compute to developers, which is exactly why coding products matter to their pitch.
Developer-Tool Scorecard: What Each Company Has Said
The table below compresses the on-record material from the previous sections. It marks gaps honestly, because a missing datapoint is information too.
| Company | Coding product | Latest on-record datapoint | Open question for earnings |
|---|---|---|---|
| Microsoft | GitHub Copilot | 50 million users and usage-based billing (fiscal Q4 call) | Does it return to reporting paid subscribers? |
| Microsoft | GitHub Copilot (earlier) | 4.7 million paid subscribers, up 75% year over year (fiscal Q2 call) | How much consumption revenue sits on top of seats? |
| Microsoft | GitHub platform | Unprecedented growth from agentic coding (fiscal Q3 call) | Is capacity keeping up with agent traffic? |
| Amazon | Kiro | Called an agentic coding service by Jassy (Q2 2026 call) | Will Amazon give a user or revenue figure? |
| Amazon | AWS capex | About $200 billion planned cash capex for 2026, mostly AI and AWS | Does the plan change? |
| Alphabet | Gemini Code Assist | No verified executive quote in our sources | Will Alphabet quantify coding usage at all? |
The scorecard shows an asymmetry. Microsoft gives developers the most data, Amazon gives direction and money, and Alphabet gives the least. If that pattern holds on October 28 and 29, buyers should lean on independent benchmarks rather than vendor statements when they compare tools.
Competitive Comparison: Three Clouds, Three Coding Bets
Microsoft’s bet is distribution. GitHub already holds the repositories, pull requests and issue trackers, so Copilot can slot into the place where developers already work. The usage-based billing change shows Microsoft wants revenue to scale with agent activity, not only with seat counts.
Amazon’s bet is the platform. Kiro sits next to the compute and infrastructure services AWS customers already buy. Jassy’s remark about building capabilities for Amazon itself points to an internal feedback loop that rivals cannot copy easily.
Alphabet’s bet is the model. Google builds its own frontier models and sells them through Google Cloud, so Gemini Code Assist doubles as a showcase for that stack. Because the company discloses less about coding products, outsiders have to judge it on model quality and enterprise adoption stories.
Independent vendors complicate the picture. GitLab, for one, now offers many models inside its agent platform, which we covered in GitLab Duo’s addition of Gemini 4 Argon. A neutral multi-model layer is attractive when the big three keep changing prices and packaging.
Historical Context: From Plugin to Line Item
The progression in Microsoft’s own remarks tells the story. First came a subscriber count with quarter-over-quarter growth for an individual plan. Next came a statement about platform-level strain from agentic coding. Most recently, the company cited a user total and a new billing model. Three consecutive calls moved the discussion from adoption to monetization.
Software features often get their own reported metrics once the revenue grows large enough to matter. AI coding appears to be following that path, and each earnings week asks whether it has reached the point where a separate disclosure is warranted.
Productivity claims have shaped that arc too. Our reporting on how AI cuts coding time 52% while flooding open source with low-quality submissions shows both sides, since faster output also creates review burdens that the earnings calls rarely mention.
Market Impact: What Moves Stocks and What Moves Roadmaps
Stock reactions will hinge on cloud growth and spending guidance, not on a Copilot milestone. That is the uncomfortable truth for developer-tool coverage. A coding-assistant metric might fill thirty seconds of a ninety-minute call.
Roadmaps move for different reasons. A raised capex plan can mean more regions, more GPU inventory and lower prices for inference. A trimmed one can mean tighter rate limits and fewer free tiers. Watch the guidance language rather than the headline revenue beat.
The Broader Market Backdrop
The earnings arrive alongside a Federal Reserve meeting and a crowded reporting schedule, as we explained in our look at how one-third of the major US index reports while the Fed tests the AI rally. Calendars such as MetaCap’s weekly earnings list show how packed Tuesday through Friday will be, which raises the odds that a developer-tool comment gets lost in the noise.
Why the Company Count Keeps Changing
Readers who search for the week’s schedule will find wildly different totals. Sources give 10, 9, 163, 542 and 1,052 companies reporting between October 26 and 30, 2026. None of those figures is a confirmed single count, because each outlet applies different criteria, such as market capitalization, index membership or exchange.
The headline number of 10 describes major reports from U.S. companies worth more than $400 billion, but the source does not name all ten. That is why this article lists only the companies with a confirmed date. If you need a full list, pull it from an exchange or investor relations pages instead of trusting a headline count.
Five Predictions for the Week
These are our expectations, not company guidance or consensus. Treat them as hypotheses to check against the transcripts.
- Microsoft keeps the Copilot spotlight. We expect Nadella to cite a Copilot or GitHub metric again, most likely tied to usage-based billing.
- Amazon names Kiro but gives no hard number. Jassy has framed it strategically, and a revenue or user figure would be a departure.
- Alphabet talks Gemini broadly, not Code Assist specifically. Coding will likely appear inside a general enterprise AI narrative.
- Capex language stays aggressive. With about $200 billion planned at Amazon, a sharp pullback from any of the three looks unlikely.
- Pricing changes follow within weeks. Usage-based models tend to spread, so expect rivals to adjust packaging after Microsoft’s results.
What Developers and Engineering Leaders Should Do Now
First, read transcripts, not recaps. The three quotes from Nadella and two from Jassy above are short, specific and checkable. Summaries tend to flatten the difference between users and subscribers, which is exactly the distinction that matters.
Second, review your own spend. If your team pays per seat today, ask your vendor how usage-based billing would change the bill. Agentic workflows can multiply token use, and a flat fee that looks generous now may not survive a pricing shift.
Third, keep your options open. Standardize on shared rules files and portable configuration so a move between editors costs hours, not weeks. More guides for this kind of work live in our software category.
FAQ: Big Tech Earnings and Developer Tools
When do Alphabet, Microsoft and Amazon report earnings? Alphabet and Microsoft are scheduled for Wednesday, October 28, 2026, and Amazon for Thursday, October 29, 2026. Alphabet’s call is listed for 1:30 p.m. PT, or 4:30 p.m. ET.
Which 10 companies make up the headline list? The source does not publish a verified list of all ten. Confirmed dates exist for Visa, Coca-Cola, Alphabet, Microsoft, Amazon, Eli Lilly, Mastercard, Exxon Mobil, AbbVie and Chevron, and one calendar also lists Apple.
How many paid GitHub Copilot subscribers does Microsoft have? On its fiscal 2026 second-quarter call, Microsoft reported over 4.7 million paid Copilot subscribers, up 75% year over year. A later call cited 50 million Copilot users, which is a different metric.
What is Kiro? Andy Jassy described Kiro as Amazon’s agentic coding service on the company’s second-quarter 2026 call. Amazon has not given a verified user count in the sources we reviewed.
Will earnings change Copilot, Kiro or Gemini Code Assist pricing? Not directly, and none of the companies has announced a change tied to this week. Microsoft has already introduced usage-based billing for Copilot, so watch for follow-on moves from rivals.
Why do sources report different numbers of companies reporting? Outlets count differently. Totals of 10, 9, 163, 542 and 1,052 for October 26 to 30 reflect varying coverage rules, not one confirmed figure.
Do these earnings give any official guidance on AI coding revenue? We have no verified executive statement from Alphabet, Microsoft or Amazon about this specific report yet. Check transcripts after each call for any new coding metrics.
