Salesforce announced its acquisition of SteelBrick for approximately $360 million in cash and stock this month, a transaction that will barely register in the technology press beyond the standard acquisition coverage. The target company — a configure-price-quote (CPQ) solution built natively on the Force.com platform — generated perhaps $20 million in ARR at acquisition. The multiple appears rich but not extraordinary by current standards. Yet this deal deserves far more attention than it will receive. It represents a fundamental inflection point in how value accrues within mature SaaS ecosystems.

The conventional narrative around platforms emphasizes their winner-take-all economics. Build the dominant platform, the thinking goes, and you capture the majority of value creation in your category. Salesforce has executed this playbook brilliantly over sixteen years, building a $50 billion market capitalization atop its CRM platform. But SteelBrick's emergence and acquisition suggests something more nuanced: as platforms mature, the highest-margin, most defensible businesses may not be the platforms themselves, but rather the specialized vertical applications built on top of them.

The CPQ Category and Why It Matters

Configure-price-quote software solves a deceptively complex problem. For companies selling configurable products — think Dell configuring a server, or Oracle pricing a complex enterprise license — the sales process involves navigating thousands of potential product combinations, pricing rules, discount approvals, and contract terms. Get it wrong and you've either left money on the table or promised something you can't deliver. Traditional CPQ solutions from vendors like Apttus and BigMachines (acquired by Oracle in 2013 for $400 million) attacked this problem as standalone applications, integrating with CRM systems through APIs.

SteelBrick took a different approach. Founded in 2006 by former Salesforce employees Max Rudman and Chris Sung, the company built its entire product natively on Force.com. This wasn't simply an integration strategy — the application shares the same data model, security architecture, and user interface paradigm as Salesforce itself. For users, SteelBrick doesn't feel like a separate application; it feels like a natural extension of their existing CRM workflows.

The results speak clearly. Despite entering a crowded market years after established competitors, SteelBrick grew rapidly, reportedly reaching $20 million in ARR with exceptional retention metrics. Customers including Hewlett-Packard, Cloudera, and Marketo adopted the platform. More tellingly, SteelBrick achieved this growth while maintaining gross margins in the 80-85% range — materially higher than Salesforce's own 75% gross margin.

The Platform Paradox

This creates a paradox that should concern any platform investor. Salesforce spent fifteen years and billions of dollars building Force.com infrastructure, acquiring customers, training administrators, and establishing ecosystem lock-in. Yet a company founded by former employees, using Salesforce's own platform, built a business with better unit economics in a fraction of the time.

The explanation lies in the economics of vertical specialization. Salesforce must maintain broad horizontal functionality across sales, service, marketing, and custom applications. Its R&D investment gets distributed across hundreds of features serving millions of users across every industry. SteelBrick, by contrast, could focus exclusively on solving the CPQ problem for companies with complex pricing needs. Every dollar of R&D spending went toward deepening one vertical capability.

This focus created multiple advantages. SteelBrick could develop domain expertise that Salesforce, spread across multiple priorities, could not match. The product could incorporate industry-specific best practices, advanced pricing algorithms, and sophisticated approval workflows that would be too niche for the platform to justify. Customers received a purpose-built solution rather than a general-purpose tool they had to customize heavily.

More importantly, SteelBrick captured value at the application layer where willingness-to-pay is highest. Companies don't pay for CRM because they want a database of contacts — they pay for solutions to business problems. A sales manager might grudgingly accept Salesforce's standard pricing, but a VP of Sales facing quote-to-cash cycle times measured in weeks will pay substantial premiums for software that compresses that to days.

The AppExchange Economy

This dynamic isn't unique to SteelBrick. The Salesforce AppExchange now hosts more than 3,000 applications, many built by independent software vendors who have identified vertical problems that the platform doesn't address directly. Companies like FinancialForce (ERP), Veeva (pharma CRM), and Rootstock (manufacturing) have built substantial businesses — some approaching or exceeding $100 million in revenue — entirely on Force.com infrastructure.

The economics merit examination. Salesforce collects platform fees from these ISVs, typically 15-25% of license revenue transacted through the AppExchange. The platform benefits from increased customer lock-in — the more applications a customer runs on Force.com, the harder it becomes to migrate. Yet Salesforce also watches substantial value creation occur one layer above its own infrastructure.

Consider the math from an investor perspective. Salesforce trades at roughly 8x revenue. SteelBrick commanded an 18x revenue multiple at acquisition (assuming $20 million ARR). The vertical application, despite its complete dependence on the underlying platform, achieved a valuation multiple more than twice as high as the platform itself.

This creates a strategic dilemma. Should platforms allow ISV ecosystems to flourish, accepting that others will capture premium value? Or should they acquire or compete with successful verticals, risking ecosystem trust? Salesforce has historically taken a partnership approach, but the SteelBrick acquisition suggests a shift. When vertical applications reach sufficient scale and strategic importance, the platform will bring them in-house.

Lessons From Other Platform Ecosystems

The pattern extends beyond Salesforce. Consider Shopify, which has built a $10 billion market capitalization providing e-commerce infrastructure. The highest-value applications in the Shopify ecosystem — tools for email marketing, inventory management, customer service — are often built by third parties. Companies like Klaviyo (email marketing) and ShipStation (fulfillment) have achieved valuations that rival or exceed Shopify's on a revenue-multiple basis.

Amazon Web Services presents another lens. AWS provides raw infrastructure — compute, storage, networking. The highest-margin businesses built on AWS are often vertical SaaS companies that solve specific problems: MongoDB for databases, Twilio for communications, Slack for team collaboration. AWS captures usage fees, but these vertical players capture the premium pricing that comes from solving complete business problems.

Even Apple's iOS ecosystem follows this pattern. Apple earns 30% of application revenue through its App Store, but companies like Uber, Airbnb, and Tinder built multi-billion dollar businesses on top of iOS infrastructure. The platform enables, but applications capture disproportionate value by solving specific use cases.

What This Means for Enterprise Software Investment

For investors, the SteelBrick acquisition illuminates several critical lessons about where value accrues in mature software markets.

First, platform dominance doesn't guarantee value capture at every layer. As platforms mature and become infrastructure, the highest-return opportunities often emerge one layer up, at the application layer where solutions meet specific business problems. This suggests a barbell investment strategy: own the dominant platforms for their defensive characteristics and predictable growth, but seek venture-scale returns in vertical applications built on those platforms.

Second, native platform development creates genuine competitive advantages. SteelBrick's decision to build exclusively on Force.com appeared to create dependency risk — what if Salesforce competed directly or changed platform terms? In practice, this native approach created a product so tightly integrated with customer workflows that it became virtually unassailable by competitors taking integration-based approaches. The lesson: platform risk can transform into platform advantage when execution is excellent.

Third, the acquirer's identity matters enormously. Salesforce paid $360 million for SteelBrick despite Apttus — a competitor with substantially higher revenue — recently raising money at a $500 million valuation. Why the discount? Because SteelBrick's value to Salesforce differs from its value to other buyers. Salesforce can integrate the product seamlessly into its core offering, cross-sell to its existing base, and eliminate platform fees. For strategic acquirers, vertical applications on their own platforms represent the highest-confidence M&A opportunities.

The Future of Platform Economics

Looking forward, we should expect platform companies to face increasing pressure to acquire successful verticals. The logic is compelling: why allow an independent company to capture 80%+ gross margins on top of your infrastructure while paying only 15-25% platform fees? Acquisitions let platforms recapture that value while strengthening competitive moats.

But aggressive acquisition strategies risk ecosystem health. ISVs invest in platform-native development because they believe they can build independent, valuable businesses. If platforms routinely acquire or clone successful applications, developers will rationally shift investment to more neutral infrastructure like AWS. Salesforce must navigate this tension carefully — acquire too aggressively and the AppExchange ecosystem stagnates; acquire too passively and competitors capture value that should accrue to the platform.

We expect to see platforms develop acquisition frameworks that address this tension. Likely approaches include: focusing acquisitions on strategic categories (like CPQ) while leaving others to partners; establishing clear rules about when the platform competes versus partners; and providing economic incentives (like reduced platform fees) for ISVs that achieve scale without acquisition.

For venture investors, this dynamic creates clear opportunity. Vertical SaaS businesses built natively on dominant platforms represent an unusual combination: the focused economics of vertical software plus the strategic acquisition value of platform extensions. The key is selecting platforms with durable advantages and identifying verticals where the platform is unlikely to build directly but will pay to acquire.

Identifying the Next SteelBricks

What characteristics should investors seek in platform-native vertical businesses?

First, pick the right platform. The infrastructure must be dominant enough to create lock-in but open enough to allow third-party innovation. Salesforce's Force.com clearly qualifies. Shopify's app ecosystem shows promise. Microsoft Dynamics presents opportunities but with platform risk given Microsoft's history of competing with partners. NetSuite's ecosystem existed until Oracle's acquisition introduced uncertainty.

Second, target verticals where the platform won't invest directly. SteelBrick succeeded because CPQ is too specialized for Salesforce's core roadmap but too important for customers to ignore. Look for similar gaps: capabilities that serve specific industries, complex workflows that require deep domain expertise, or features that matter intensely to a subset of customers but not the broader base.

Third, insist on native development, not integration. The company must be built on the platform's core infrastructure, not sitting beside it. This creates switching costs that generic integration-based competitors cannot match. It also signals to the platform vendor that acquisition is more valuable than building — the institutional knowledge and customer relationships are harder to replicate than feature parity.

Fourth, seek vertical applications with inherent pricing power. The best opportunities solve painful, expensive problems where customers have high willingness-to-pay. SteelBrick addressed quote-to-cash inefficiencies that cost enterprise customers millions in delayed revenue and pricing errors. The more quantifiable and severe the business problem, the better the pricing leverage.

Finally, consider the acquirer universe early. A vertical application's value depends heavily on who might buy it and why. SteelBrick had clear strategic value to Salesforce but would be worth far less to most financial buyers. Map potential acquirers and their strategic priorities during initial diligence, not when seeking exits.

Implications for Portfolio Construction

The SteelBrick acquisition should influence how we think about enterprise software portfolio construction. The traditional approach separates platform investments (lower risk, steady growth, moderate returns) from application investments (higher risk, variable growth, seeking venture-scale returns). This framing misses the opportunity in platform-native verticals, which combine platform-like retention economics with application-like margin expansion and strategic acquisition value.

We recommend a three-tier framework for enterprise software allocation:

Tier one comprises dominant horizontal platforms: Salesforce, Workday, ServiceNow. These provide portfolio stability, predictable growth, and strategic exposure to cloud transition macro trends. Expected returns are moderate but reliable — think 15-20% annually over five-year periods.

Tier two focuses on platform-native vertical applications built on tier-one infrastructure. These represent our highest-conviction opportunities for venture-scale returns in enterprise software. Companies like SteelBrick, FinancialForce, and Veeva demonstrate that proper execution can generate 25-30x+ return multiples in 5-7 years. The key is identifying them early, before metrics support traditional late-stage valuations.

Tier three includes emerging platforms and standalone vertical applications. These carry higher risk — new platforms face adoption challenges and competitive threats, while standalone verticals compete on features rather than integration. But successful companies in this tier can migrate to tier one (like Slack's rapid emergence) or be acquired into tier-one ecosystems.

This framework recognizes that different software categories offer different risk-return profiles and different paths to value creation. Platform-native verticals occupy a sweet spot: more defensible than standalone applications, more scalable than consulting-intensive solutions, more acquisition-worthy than horizontal tools.

Conclusion: The Verticalization Thesis

Salesforce's acquisition of SteelBrick for $360 million marks a turning point in how we should think about value creation in mature software platforms. The deal validates a thesis that has been building quietly for years: as platforms achieve dominance and become infrastructure, the most attractive investment opportunities often emerge one layer above, in vertical applications that solve specific problems with platform-native approaches.

This verticalization trend will accelerate. Every major platform will face the same pressure Salesforce faces with CPQ — watching third parties capture premium economics on top of platform infrastructure. Some will acquire aggressively, some will compete directly, some will find creative partnership models. But the dynamic itself is structural, driven by the fundamental economics of platform versus application businesses.

For investors, this creates both opportunity and obligation. The opportunity lies in backing platform-native vertical businesses early, before their strategic acquisition value becomes obvious. Companies that combine SteelBrick's playbook — native platform development, vertical focus, clear strategic acquirer — offer unusual combinations of growth, retention, and exit certainty.

The obligation is to think more carefully about where value accrues in software ecosystems. Platform dominance matters, but it doesn't capture all value creation. Sometimes the best investment isn't the platform itself, but the specialized businesses built on top of it. As Salesforce discovered with SteelBrick, the applications layer may be where the highest margins and most defensible positions ultimately emerge.

We expect to see hundreds of millions in venture capital flow toward platform-native vertical software over the next several years. The playbook is proven, the infrastructure is mature, and the acquirer demand is clear. The question isn't whether this trend continues — it's which platforms and verticals represent the best opportunities for capital deployment. Based on SteelBrick's outcome, investors who identify the next generation of platform-native verticals early will generate exceptional returns.