What Happened to SMAR Stock?
Smartsheet makes cloud-based work management and collaboration software used by businesses to plan projects and automate workflows. It traded on the NYSE under the ticker SMAR until it was acquired by investment firms Blackstone and Vista Equity Partners in a take-private deal completed in early 2025. SMAR shares no longer trade publicly.
Smartsheet was founded in 2005 in Bellevue, Washington, and listed on the NYSE in 2018.
In 2024 it agreed to be acquired by Blackstone and Vista Equity Partners, and the deal closed in early 2025.
How Smartsheet's Business Works
In a take-private deal, investors buy all outstanding shares, and shareholders receive cash for their shares when the deal closes.
Smartsheet's software competes in work management with tools such as Asana, Monday.com, Microsoft and Atlassian.
As a private company, Smartsheet no longer publishes quarterly results the way public companies do.
Smartsheet's Competitors
Smartsheet competes with Asana, Monday.com, Microsoft Project, Atlassian and Wrike.
Publicly traded competitors include Asana, Monday.com, Microsoft and Atlassian.
What Mattered for Smartsheet's Business
These measures were central to Smartsheet's results:
- Subscription revenue
- Enterprise customer growth
- Net revenue retention
- Product integrations
- Competitive position in work management
Considerations After Going Private
Going private changes what investors can see and do:
- No public market for shares after the acquisition
- Competition in collaboration software
- Execution under private ownership
- Limited public financial disclosure
From Sheets To Managed Workflows
A work management platform organizes work around shared records rather than a single person's file. A team might use rows to represent requests, projects or tasks, with columns for owners, deadlines, status and supporting information. The same underlying records can then appear in different views suited to the people using them. A manager may need a portfolio view, while an individual contributor needs a list of assigned tasks. The value of the structure depends on whether the data is current and whether people interpret its fields consistently.
Standardized intake is one practical use of this structure. A form can collect a request using defined fields, after which rules can route it to an owner or flag missing information. This reduces the need to reconstruct a decision from separate messages. It also makes the design of the process important: an unclear field or an incorrect routing rule can spread confusion across many requests. Teams therefore need to decide who maintains the workflow, who can change it and how exceptions reach a person able to resolve them.
The distinction between a template and an operating process matters. A template supplies an initial arrangement of fields and views, but a functioning process also requires ownership, update habits and agreed definitions. For example, a status labeled complete has limited meaning unless participants agree on what must happen before it is selected. As an organization adds teams, governance can balance local flexibility with common reporting. Too little consistency makes aggregation difficult; excessive standardization can make a workflow awkward for the people doing the work.
Reporting from shared work records introduces another design choice: what should be measured and at what level of detail. A dashboard can combine information from several projects, but totals become misleading when teams use different definitions or leave fields blank. A consistent owner and review cadence for the underlying records can make the report more useful. Historical snapshots can also help distinguish a task that has stayed on schedule from one whose deadline was repeatedly revised, provided the organization retains and interprets the relevant history.
Subscription Economics And Customer Adoption
Subscription software generally separates the timing of a customer agreement, billing and revenue recognition. A provider may invoice a customer before all of the contracted service has been delivered. The cash received is not automatically revenue for the entire contract; the undelivered portion is ordinarily recorded as deferred revenue and recognized as the service is provided. Changes in deferred revenue can therefore reflect billing schedules and contract timing as well as changes in demand. Reading it alongside recognized revenue gives a more complete picture than treating either measure alone as orders.
The economics of a customer relationship also depend on implementation and use. Winning an account can involve sales effort, security review, procurement and training before a broad rollout. Once a platform is established in a department, additional teams may adopt it through new use cases. Expansion can arise from more paid users, different product capabilities or wider organizational deployment, depending on contract terms. Adoption is not the same as a signed agreement: unused licenses and workflows that remain outside daily routines may tell a different story from the headline contract.
Retention measures summarize the combined effect of customer departures, reductions and expansion, but definitions matter. A revenue-based retention figure follows spending from an existing customer group, while customer-count retention treats accounts as units regardless of their size. The chosen period, inclusion of add-on products and treatment of acquisitions can affect comparisons. A revenue measure above its starting level can coexist with the loss of some customers if expansion elsewhere offsets that loss. Neither measure alone explains whether a change came from price, usage, product mix or customer departures.
Reading Software Financial Statements
Gross profit starts with revenue and subtracts the direct costs of delivering the service. For a cloud software provider, those costs can include hosting, customer support and personnel associated with service delivery. Gross margin expresses gross profit as a share of revenue. Its movement can reflect infrastructure efficiency, customer support needs or a change in the mix of subscriptions and services. Professional services such as implementation may have different cost characteristics from recurring software access, so the mix of those activities helps explain changes in the combined margin.
Operating expenses show the resources devoted to developing, selling and administering the business. Research and development supports product work, sales and marketing supports customer acquisition and account growth, and general and administrative costs support company operations. These categories should be read together with gross profit to understand operating income or loss. A lower expense share can result from revenue growing faster than spending, but the underlying cause may also involve reduced hiring, changes in sales activity or other operating choices. The notes and management discussion provide context for those movements.
Cash flow adds a different perspective because accounting expenses and cash payments do not always occur in the same period. Operating cash flow adjusts net income for noncash items and changes in operating assets and liabilities. Capital spending can then be considered when assessing cash left after investment in long-lived assets. Stock-based compensation is an example of an expense that affects accounting results without an equivalent cash payment at the time it is recognized; its effects on share ownership require a separate look at the share count and award disclosures.
Platform Design And Enterprise Decisions
Work management products sit between several established software categories. A spreadsheet is flexible for individual analysis, a dedicated project tool can impose stronger project controls, and a broader enterprise system may maintain authoritative records for finance or customer relationships. A work management platform can coordinate steps across those systems without necessarily replacing them. The relevant comparison is often how each approach handles permissions, reporting, customization and the movement of information, rather than whether every product has a superficially similar task list.
Integrations connect workflows to other applications, but a connection does not settle which system owns a piece of data. Teams need rules for the source of truth, the direction of updates and what happens when information conflicts. An automated update can save manual work while also propagating an error if a source field is wrong. Reliability depends on permission settings, monitoring and a process for correcting failed or unexpected updates. These operating details influence how readily a company can use a platform across departments.
Enterprise adoption also brings security and administrative requirements. Organizations may review access controls, identity management, audit records and policies for retaining or removing information. The ability to grant appropriate access to outside collaborators can matter alongside controls over sensitive internal data. These requirements vary by customer and use case, so a feature list alone does not show how difficult deployment will be. Buyers must also consider migration, training and the work of maintaining existing automations when processes or connected systems change.
A platform's flexibility can create switching costs without making a change impossible. A customer may need to map fields, move attachments, rebuild permissions and test automations in a replacement system. The difficulty depends on how deeply the workflows are embedded and how easily information can be exported in a usable form. Conversely, reliance on a single platform can concentrate operational knowledge in a small group of administrators. Documentation and clear responsibility for workflows help an organization understand that dependency and manage changes to its processes.
Conclusion: Smartsheet After the Buyout
Smartsheet remains a work management software company, but SMAR stock no longer trades after its acquisition by Blackstone and Vista Equity Partners. Publicly traded competitors offer similar business exposure.
