/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

SAP's Business Intelligence Leap

To expand in one of business software's hottest sectors, the German giant detours from its organic growth plan and agrees to buy Business Objects for $6.8 billion  —  In the rapidly consolidating business software market, SAP (SAP) has taken a conservative tack …

Business Week Aaron Ricadela

Context & Ripple Effects

SAP had spent 2007 insisting it would grow the old-fashioned way: the September launch of Business ByDesign for the 100–500 employee mid-market was pitched as organic expansion into a $15 billion segment, and the company's doctrine under Henning Kagermann had long been build-don't-buy. The €4.8 billion ($6.8 billion) agreement for France's Business Objects, confirmed on October 7–8, breaks that doctrine outright — SAP's largest move yet into business intelligence, one of the hottest sectors in business software.

The timing is pointed. In July, SAP admitted its TomorrowNow subsidiary had inappropriately downloaded Oracle's proprietary software, leaving the third-party maintenance unit's future uncertain and handing its arch-rival a public grievance. Buying rather than building now signals that SAP judged the BI race too fast to win organically, and that rapid consolidation across the business software market left no patient alternative.

First-order effects

  • Business Objects' shareholders receive a €4.8 billion cash exit while SAP instantly acquires an independent BI product line it would otherwise have spent years building — at the cost of abandoning its stated organic-growth strategy.
  • Business Objects' large installed base of reporting customers now faces integration into SAP's roadmap, with the vendor relationship shifting from independent specialist to SAP subsidiary.

Second-order effects

  • Oracle, already SAP's antagonist in the TomorrowNow dispute, is pushed to defend its own BI position as suite vendors absorb the remaining independents — consolidation pressure transfers directly down the vendor list.
  • Standalone BI vendors lose their most plausible acquirer-independent future: once SAP bundles analytics with ERP, pricing pressure moves toward suite discounts, squeezing specialists' standalone license economics.

Third-order effects

  • If the pattern holds, business intelligence stops being a separate market and becomes a feature attached to transactional suites, with the big ERP platforms — not BI specialists — setting the pace and price of analytics.
  • A repeatable template emerges for SAP: when a capability gap threatens suite completeness, buy the leader rather than build — a doctrine shift that reshapes how the whole applications layer consolidates.

The trend: Enterprise applications are consolidating through acquisition-led expansion, as ERP giants absorb standalone business intelligence vendors to keep their suites complete.