Live predictions

What will these companies do next?

Five live predictions about Tesla, Microsoft, Amazon, AMD and NVIDIA, researched by Paldo and updated as new evidence comes in.

How a Paldo prediction works
  1. A callA dated statement that can turn out wrong
  2. SignsWhat we'd expect to see if it's coming, and if it isn't
  3. EvidenceHiring, filings, public records, news and the web, read against those signs
  4. LikelihoodWeighed for and against, strongest and newest first
  5. UpdatesResearched again as new evidence appears

Microsoft will introduce a single enterprise subscription SKU that includes both GitHub Copilot and Microsoft 365 Copilot, by May 18, 2028.

59%likely

Deadline 18 May 2028 · 1 research run, last 17 Nov 2026

Bottom line

Microsoft has built meaningful commercial and technical bridges between the two Copilots, but the evidence still stops short of a single enterprise subscription SKU including both.

The evidence and what would settle it

Where it stands

On September 11, 2025, Microsoft announced plans to absorb three role-based Copilots into its $30-per-user-per-month Microsoft 365 Copilot package. Microsoft 365 E7 became generally available on May 1, 2026; its listed suite components combine E5, Microsoft Copilot, Entra Suite and Agent 365, without GitHub Copilot. On June 16, Microsoft announced Agent Factory’s single consumption model spanning Microsoft 365 Copilot and GitHub Copilot, with user subscription licenses as the foundation.

On September 25, Microsoft announced Home, Code and Autopilot, with Code using GitHub Copilot’s underlying technology and pricing combining subscriptions with consumption. On October 28, Microsoft announced its company-wide adoption of the harness built by GitHub’s engineering team. That day, GitHub also included Copilot access for every licensed GitHub Enterprise user at enterprises served by a GitHub or Microsoft account team, with AI usage metered against the enterprise budget rather than included monthly credits.

The case against

The case is weaker than the unified-app language suggests: a September LinkedIn post claimed both products were bundled, whereas Microsoft’s official announcement described shared technology, previews and subscription-plus-consumption pricing—not a GitHub Copilot entitlement. Microsoft’s October 16 Azure guide still requires a separate GitHub-managed subscription, and November 9 licensing coverage reports separate licenses and bills. Microsoft’s November 12 documentation explicitly says harness-agent consumption is excluded from the Microsoft 365 Copilot license.

August reporting described expanded FTC bundling scrutiny, a potential obstacle rather than a prohibition. The European Commission’s June 2024 preliminary objections to Teams tying provide an older regulatory precedent, not a decision on this proposed bundle.

Evidence for

  • 16 Jun 2026 Microsoft's June 16, 2026 strategy announcement describes Agent Factory as offering a single consumption model spanning Microsoft 365 Copilot and GitHub Copilot, with user subscription licenses as the foundation. This is a specific commercial bridge between the products, although it does not announce one subscription SKU including both. blogs.microsoft.com
  • 28 Oct 2026 On October 28, 2026, Microsoft announced that GitHub's engineering-built harness had been adopted company-wide and powers Copilot Code, Copilot Studio, the GitHub Copilot app, CLI and VS Code, with availability through Foundry. Sharing this core platform makes joint subscription packaging more practical, but technical integration does not establish joint licensing. linkedin.com
  • 25 Sept 2026 Microsoft's September 25, 2026 announcement brings Home, Code and Autopilot into one Copilot experience, with Office integration and Code powered by the same underlying technology as GitHub Copilot. This moves the user experience toward convergence, but the official announcement describes preview rollouts and subscription-plus-consumption pricing, not a GitHub Copilot subscription entitlement; item 472's stronger bundling interpretation is not corroborated by those terms. blogs.microsoft.com
  • 28 Oct 2026 On October 28, 2026, GitHub announced Copilot access for every licensed GitHub Enterprise user served by a GitHub or Microsoft account team, replacing separate seat management with enterprise-budget usage metering. This demonstrates willingness to bundle Copilot into an existing enterprise subscription, although it bundles with GitHub Enterprise rather than Microsoft 365 Copilot. github.blog

Evidence against

  • 17 Nov 2026 Microsoft's October 16, 2026 Azure setup guide explicitly requires a separate GitHub-managed Copilot subscription; November licensing coverage likewise reports separate licenses, admin centers and bills, with GitHub Copilot seats not bundled with Microsoft 365 Copilot. This is the strongest evidence that commercial convergence has not yet reached the predicted SKU, though it does not rule out a launch by May 2028. aipricing.guru
  • 1 Jun 2026 June 2026 reporting describes FTC scrutiny of Microsoft's licensing, interoperability and bundling, and August reporting says the investigation expanded to cloud, AI and software bundling, including Copilot. This creates a directly relevant regulatory obstacle to adding another AI service to a Microsoft enterprise suite. cio.com
  • 12 Nov 2026 Microsoft's November 12, 2026 documentation states that agents powered by the Microsoft Copilot harness use consumption-based billing not included with a Microsoft 365 Copilot license. Copilot Studio documentation and a September billing discussion also distinguish harness use from users' Microsoft 365 Copilot entitlements, limiting how far shared technology can be treated as a subscription bundle. learn.microsoft.com
  • 26 Jun 2024 The European Commission's June 2024 preliminary findings objected to Microsoft's tying of Teams to Office 365 and Microsoft 365 and considered Microsoft's initial unbundling changes insufficient. This provides a concrete regulatory precedent against using the productivity suite to distribute another product, though an optional Copilot bundle could be structured differently. courthousenews.com

What would settle it

Microsoft would make the prediction true by introducing, by May 18, 2028, one enterprise subscription SKU whose terms grant both GitHub Copilot and Microsoft 365 Copilot entitlements. A binding decision prohibiting that packaging through the deadline would rule it out; otherwise, the deadline passing without introduction would settle it negatively.

What to watch

A shared-entitlement purchasing pilot would show commercial integration beyond a common interface. Product terms or ordering documentation assigning both paid entitlements through one SKU would signal an approaching launch. A regulatory proceeding specifically targeting developer-AI tying to productivity subscriptions would create a more direct obstacle than today’s broader scrutiny.

Amazon will acquire a controlling interest in an electricity-generation business specifically to supply its data centres by 15 May 2028.

Researching

Deadline 15 May 2028 · first research run in progress

The evidence and what would settle it

NVIDIA Corporation will acquire a company whose principal business is optical interconnect hardware for data centres by 31 December 2027.

Researching

Deadline 31 Dec 2027 · first research run in progress

The evidence and what would settle it

Tesla Inc will announce a licensing agreement allowing another car manufacturer to install its self-driving software in vehicles sold under that manufacturer's brand by 15 May 2028.

Researching

Deadline 15 May 2028 · first research run in progress

The evidence and what would settle it

Microsoft Corporation will introduce an enterprise AI-agent plan priced solely by completed workflows rather than user seats or computing consumption by 30 September 2027.

Researching

Deadline 30 Sept 2027 · first research run in progress

The evidence and what would settle it

AMD will acquire a software company whose principal product automatically routes AI workloads across competing chip architectures by 30 November 2027.

77%likely

Deadline 30 Nov 2027 · 1 research run, last 17 Nov 2026

Bottom line

AMD’s acquisition record makes this a credible possibility, but no documented purchase yet establishes the required principal product: automatic AI-workload routing across competing chip architectures.

The evidence and what would settle it

Where it stands

AMD signed its Nod.ai acquisition agreement on October 10, 2023, and completed the purchase on October 19; SHARK automated deployment across AMD architectures. On June 4, 2025, AMD announced the Brium acquisition, aimed at reducing dependence on particular hardware configurations. That is the closest precedent, but AMD’s description establishes compiler optimization and portability, not automatic cross-vendor placement.

AMD completed the MK1 acquisition on November 10, 2025; its AMD-optimized Flywheel technology served over one trillion tokens daily. On July 23, 2026, AMD partnered with Cerebras to combine GPU throughput with wafer-scale low-latency token generation, making coordination across different architectures strategically relevant. AMD’s September 28 World Labs agreement valued the spatial-intelligence developer at approximately $8.2 billion in stock; a November 17 report says the acquisition closed November 13.

The case against

The case is weaker than the acquisition tally suggests: buying compilers, inference optimization or spatial-intelligence research does not establish ownership of the specified routing product. The collected material identifies no acquisition talks with a qualifying target. FlexAI’s reported work with AMD dates to April 2024 and establishes collaboration, not purchase interest.

AMD already documents routing and NVIDIA-cluster support, although those undated release notes do not establish automatic architecture-based placement. Meanwhile, llm-d v1.0 supports multiple accelerators, following its October 20, 2026 release, offering another route to cross-hardware inference without buying a specialist.

Evidence for

  • 4 Jun 2025 AMD announced its acquisition of Brium on June 4, 2025 to improve inference portability and reduce dependence on particular hardware configurations. This is a close acquisition precedent, but the factual descriptions establish compiler optimization and portability—not a principal product that automatically routes workloads between competing architectures. amd.com
  • 23 Jul 2026 On July 23, 2026 AMD and Cerebras announced a solution combining Helios GPU throughput with Cerebras wafer-scale low-latency token generation, initially expected through Cerebras Cloud in the second half of 2026. This makes coordinating workloads across fundamentally different accelerator architectures strategically relevant to AMD. ir.amd.com
  • 28 Sept 2026 AMD's September 28, 2026 definitive agreement valued spatial-intelligence developer World Labs at approximately $8.2 billion in stock; a November 17 report says completion occurred November 13. This demonstrates substantial, recent appetite for AI software and research acquisitions, but World Labs' products generate and simulate 3D environments rather than route workloads. linkedin.com
  • 19 Oct 2023 AMD announced the Nod.ai agreement on October 10, 2023 and completion on October 19; its SHARK compiler automates optimization and deployment across AMD architectures. This demonstrates willingness to buy AI deployment software, although the stated capability concerns AMD hardware rather than routing between competitors. amd.com

Evidence against

  • AMD Enterprise AI 2.4.1 release notes describe a Semantic Router for on-premises and cloud API requests, plus NVIDIA-cluster support and a fallback image for switching between AMD and NVIDIA clusters. These existing capabilities provide a plausible build-and-integrate alternative to buying a specialist, though the notes do not establish automatic architecture-based routing. enterprise-ai.docs.amd.com
  • 4 Aug 2026 AMD launched ROCm.ai in 2026, while ROCm supplies compilers, runtimes, framework integrations and tools for porting CUDA code to AMD GPUs. Expanding this internal software foundation offers another route to improving portability without acquiring a workload-routing company. amd.com
  • 9 Nov 2026 A November 9, 2026 report puts AMD's quarterly free cash flow at $554 million against $13.38 billion in revenue, while describing World Labs and Taalas transactions totaling $11.1 billion. This creates some financial and execution friction for another deal, although the stock-funded transactions do not establish a cash constraint or an M&A pause. kavout.com

What would settle it

An acquisition-completion announcement or filing by November 30, 2027 would establish the outcome if accompanying product documentation confirms that the acquired company’s principal product automatically routes AI workloads across competing architectures. An agreement alone would leave completion unresolved. No qualifying completed acquisition by the deadline would rule it out; cancellation of one proposed deal would not.

What to watch

Credible reporting of AMD conducting acquisition due diligence on a qualifying routing company would turn strategic plausibility into transaction evidence. A demonstration of automatic placement between AMD and competing chips would establish the technical capability, but not an acquisition. A long-term partnership leaving an independent vendor in control of routing would strengthen the alternative to ownership.

These are Paldo's own forecasts from public sources, not investment advice. Customers get the same, for the companies in their market.

See it live

Want to see what Paldo can track in your market?