Software: how the industry works
Software companies turn reusable code into licensed products and ongoing services. Retention, distribution, reliability and the cost of serving usage determine the business model.
Scope and segments
Software product vendors and hosted software services. Custom implementation and advisory work are related but labor-intensive services, and cloud infrastructure ownership has a different capital profile. Public-company disclosure is illustrative rather than representative of every vendor.
- Licensed products
- Customers acquire rights to use a version or product, with maintenance and support sometimes sold separately.
- Hosted subscriptions
- Customers pay for continuing access, often by seat, organization, feature tier or usage.
- Infrastructure and developer tools
- Platforms sell capabilities such as computation, storage or APIs; serving cost may rise directly with usage.
Sources: [1]. See source scope below.
10 companies to know
Illustrative examples cover creative tools, business applications, technical design, collaboration and commerce software. This alphabetical selection is not a revenue, market-share or product-quality ranking.
Listed alphabetically. Names link to official sources. Checked . How we select examples.
-
Adobe
Creative and document applications
Develops applications for photography, design, video, digital documents and customer experiences. Its portfolio illustrates specialist software used to create, edit and distribute digital work.
-
Atlassian
Team collaboration software
Develops tools including Jira and Confluence for software, IT and business teams. Its products illustrate software that coordinates work and preserves shared organizational knowledge.
-
Autodesk
Design and engineering software
Provides design and production software for construction, manufacturing and media industries. Its model illustrates tools embedded in technical workflows where files and expertise accumulate over time.
-
Intuit
Financial management applications
Provides products including QuickBooks, TurboTax and Mailchimp for businesses and consumers. Its portfolio illustrates software supporting recurring financial, administrative and customer-management tasks for different user groups.
-
Microsoft
Productivity and cloud platforms
Provides productivity applications, operating systems, business software and cloud services. Its range illustrates how software products can connect individual work, organizational systems and underlying computing infrastructure.
-
Oracle
Enterprise applications and databases
Provides enterprise software, database technology and cloud services. Its product range illustrates systems used to store business information and support interconnected organizational processes at scale.
-
Salesforce
Customer relationship management
Provides cloud applications for managing customer relationships and related business workflows. Its platform illustrates subscription software built around shared customer information and connected organizational activities.
-
SAP
Enterprise resource planning
Develops enterprise applications and data technology for business operations. Its software illustrates how finance and other operational processes can be organized around integrated systems and records.
-
ServiceNow
Enterprise workflow software
Provides a platform combining data and workflows, including customer service and IT management tools. It illustrates software that coordinates requests and actions across organizational functions.
-
Shopify
Commerce platform
Provides software for selling online and in person, with storefront and back-office capabilities. Its platform illustrates how merchants use a shared software foundation to run commerce.
How it works
Follow the main sequence. Actual operating models may combine or outsource individual stages.
- 1
Identify a recurring problem
Understand the workflow, buyer and alternatives. The user, budget owner and security approver may be different people.
- 2
Build and verify
Develop features, review dependencies, test behavior and prepare release artifacts. Security is a continuing engineering responsibility.
- 3
Distribute and onboard
Sell through self-service, partners or enterprise teams, then connect customer data and train users.
- 4
Operate and support
Keep the service available, respond to incidents, maintain compatibility and handle customer requests.
- 5
Renew and improve
Measure whether the product remains useful, fix friction and earn renewals; expansion should follow actual customer value.
How money moves
- Revenue or funding unit
- A license, subscription period, seat or measured unit of consumption.
- Who pays
- Consumers, business departments and public organizations buy access; enterprise contracts may bundle multiple products and services.
Main costs
- Product development
- Engineering, design, testing and security require investment before and after the first sale.
- Distribution
- Sales compensation, marketing, partner margins and onboarding can dominate early customer economics.
- Service delivery
- Cloud resources, support, third-party APIs and inference costs vary with architecture and usage.
Assets and investment
Many vendors rent infrastructure rather than build data centers. Intangible product investment can be economically significant even when physical assets are modest.
The cash cycle
Annual prepayment can fund operations before revenue is recognized over the service period. Receivables, renewal timing and committed infrastructure spending still affect cash.
The economic mechanism
Reusable code can create scale economies, but retention determines how long acquisition spending is recovered. High gross margin does not establish profitability if sales and product investment exceed the resulting contribution.
Sources: [1]. See source scope below.
Inside the operation
Measures that matter
| Measure | What it measures | Why it matters |
|---|---|---|
| Gross revenue retention | Recurring revenue retained from an opening customer cohort, excluding expansion. | Separates the durability of existing revenue from upselling. |
| Net revenue retention | Recurring revenue retained plus expansion from the opening cohort, divided by its opening revenue. | Can exceed 100%, but expansion can mask customer losses. |
| Contribution per customer | Revenue less explicitly defined variable serving costs. | Prevents compute-heavy or support-heavy usage from hiding behind total revenue growth. |
What shapes the industry
Distribution can be as consequential as code quality. A product embedded in daily workflows accumulates integrations and training that make replacement costly, but switching friction also creates an obligation to make data export and migration workable.
Horizontal products serve many sectors; vertical products encode a narrower industry’s workflow. A niche vendor can compete through depth even when a larger platform has lower infrastructure cost. Open-source alternatives and internal development constrain pricing.
Sources: [1]. See source scope below.
Who it connects to
These relationships describe typical flows. They are not a list of every supplier or customer.
Buys from / depends on
- Telecommunications
Hosted services depend on networks connecting users and infrastructure.
- Semiconductors
Computing hardware ultimately depends on chips, even when vendors rent cloud capacity.
Supplies / serves
- Commercial banking
Banks buy ledger, analytics and workflow software.
- Healthcare providers
Providers use software for clinical records and administration.
Substitutes and alternatives
- Manual workflows and internal development
Organizations may choose spreadsheets, custom code or existing bundled tools instead of another product.
Retention changes acquisition payback
Illustrative calculation
The inputs below are hypothetical. They explain a mechanism and are not industry benchmarks or a forecast.
Assumptions
- Illustrative service charges $100 per customer per month.
- Variable serving and support cost is $25 per customer per month.
- Acquiring one customer costs $600; fixed engineering costs and financing are excluded.
Calculation
- Monthly contribution = $100 − $25 = $75.
- Simple contribution payback = $600 ÷ $75 = 8 months.
- A customer leaving after 5 paid months contributes $375, leaving $225 of acquisition spending unrecovered.
Payback assumes the customer stays and serving costs remain stable; it is not a complete lifetime-value forecast.
What changes when…
A new feature doubles compute use without changing price.
- Customers may use the product more, but infrastructure expense rises with those requests.
- Contribution can fall even while engagement and subscription revenue look healthy.
- Caching, product limits, architecture or consumption pricing may be needed; changes must preserve the value customers expected.
What to watch
- Serving cost per active account
- Feature-level usage
- Retention after pricing changes
A qualitative scenario based on the operating model, not a quantitative prediction.
Risks and misconceptions
- Security failure
- A vulnerable dependency or access-control error exposes customers and creates remediation costs.
- Usage-cost mismatch
- A flat subscription attracts unusually heavy usage whose serving cost exceeds revenue.
- Retention deterioration
- A product loses relevance or reliability, weakening renewals before the effect is obvious in total sales.
Sources: [2] [1]. See source scope below.
Common misconceptions
- Software has zero marginal cost.
- Code replication can be cheap; compute, support, storage, security and third-party services are not necessarily cheap.
Sources and scope
Primary references anchor the factual mechanisms below. Operating models, relationship choices, and worked examples are editorial synthesis. Linked sources do not constitute endorsement.
- Microsoft 2025 Annual ReportMicrosoft
First-party examples of licenses, subscriptions, cloud revenue and operational risks; not industry-average economics.
- Secure Software Development FrameworkNational Institute of Standards and Technology
Secure development, release provenance and ongoing vulnerability practices.
- Software Developers, Quality Assurance Analysts, and TestersU.S. Bureau of Labor Statistics
Development, testing and maintenance roles and activities.
The operating model and causal analysis are editorial synthesis. All worked-example figures are invented assumptions for explanation, not industry benchmarks. Regulations and payment conventions vary by jurisdiction.
From understanding to operating
Try this workflow with ERP.AI
Turn software backlogs into sprint plans, track bugs and task progress, and connect pull requests with release planning and approvals throughout the development workflow.
2 Run it with Proto
Get the desktop agent, then return to the app page to continue setup.