Can Trial Pricing work in Logistics & Supply Chain Technology with operational risk?
Logistics software gets purchased after a costly failure, so a trial should resolve an actual shipment, inventory or hiring workflow rather than show a feature list. Veeqo gives sellers free core shipping functionality and sells additional inventory capability; Tenstreet uses tailored enterprise pricing based on fleet and recruiting scope. Neither proves a fixed-duration Trial Pricing offer here. A warehouse that connects one channel may still suffer overselling elsewhere; a carrier cannot assess driver compliance from a fabricated application.
See how top industrial technology companies like Hexagon scaled past $50M ARR, in Business Core.
✓ Skip the success story. Get the decisions behind it ✓ Not a case study. A teardown you can copy from.
Business Core shows how top industrial technology companies grew beyond $50M ARR, so you can see what each one did to defend and widen its lead.
40 Foundational Decisions
34 Model Frameworks
80 Strategy Patterns
4 Pillars of any Business
Backed by evidence
On which a company is built on
Of proven growth & expansion
Model · Market · Money · Motion
✓ Find relevant precedents in under 2 minutes ✓ Updated every 6 months ✓ 6 ARR stages, from pre-$1M to $100M+
Pick a decision or a strategy.
Go deep on companies that made it
Your exact comparables, one filter away.
The companies you study didn't build by instinct alone.
Neither should you.
Stop studying companies that never faced your call.
Famous case studies won’t fit your decision. These will.
With a Situation or Strategy you need insight on
Open results to see exactly how they did it - and how you can do the same.
The framework walks you through every layer of how the company was built, grown & sustained big
Plottr
Koyeb
ElevenLabs
Bitwarden
N26
Hippocratic AI
BigCommerce
OpenAI
PlannerHub
Revolution Brewing
Smartsheet
My PT Hub
MailerLite
✓ Get the Full list of companies under each ✓ Unlock in-depth intel on each company
From “what should we do?” to a written plan in one sitting
DISTRIBUTION MODEL
What does €204.4M in a quarter imply about how large Hexagon's asset software business is?
A simple multiple gives a sense of scale. Four quarters at €204.4 million would be roughly €800 million a year, but that is an annualised division figure and not a reported ARR, because it includes hardware-linked and services revenue as well as subscriptions.
The useful lesson is how to read it. A division quarter shows that the business is large, while the share that recurs, and how fast it grows, needs separate figures, which is why double-digit SaaS growth in asset management is the more telling number.
How do you read a division's quarterly revenue when ARR isn't reported?
• Multiply the quarter by four for a rough scale, and then state clearly that it is an annualised estimate and not ARR.
• Look for the recurring share, because subscription revenue and hardware or services revenue behave differently.
• Check growth rates for the software line alone, since that shows how fast recurring revenue is building.
• Compare with the group figure, to see how large the division is within the wider business.
Which moves widened Hexagon's asset business beyond a single product?
These moves spread asset intelligence across the lifecycle and across customers.
• Asset Lifecycle Intelligence as a focused division, with enterprise asset management at its centre.
• Double-digit software-as-a-service growth in EAM, which shows a growing recurring base.
• Octave as a spin-out that concentrated the asset and software portfolio on a clearer offer.
• Manufacturing intelligence and autonomous-production positioning that widened the problems the platform addressed.
Which risks matter most for Hexagon at this scale?
Hardware cyclicality and integration debt remain the structural ones. Industrial capital spending and project delays affect device and services revenue, and multiple acquisitions can leave disconnected products and a complex support burden.
Incumbent bundling and data resistance follow. SAP, IBM Maximo and IFS can include asset management in broader enterprise agreements, and customers may restrict access to operational or safety-sensitive data, so each large renewal has to defend its separate value.
How can an industrial software division protect revenue at large scale?
• Shipments completed with correct inventory deduction.
• Verification time for a qualified driver application.
• Use a contained operational lane: one channel-to-shipment flow or one verified driver application, with a rollback path and signed success criteria.
Which exposures come with Hexagon's size and history of acquisitions?
These exposures come from a large group built through acquisitions and hardware.
• Hardware cyclicality, where capital spending and project delays affect device and services revenue.
• Integration debt, since multiple acquisitions can leave products that do not share a data model.
• ERP and EAM incumbency, as SAP, IBM Maximo and IFS can bundle asset management into wider agreements.
• Data-ownership resistance, where customers limit access to safety-sensitive operational data.
What should an industrial company avoid when it scales a software division inside a hardware group?
Treating hardware revenue as proof of software scalability. Hexagon's own caution is that recurring-revenue quality requires separate product and sales economics, because a strong device quarter says nothing about renewals.
It should also avoid adding software without a plan to integrate it around one data model. Acquisitions that do not share the asset record create more silos, and customers see little reason to hold more than one product.
Why should a software division report and manage itself apart from the hardware around it?
• Software renewals, growth and margins follow different drivers from hardware, so blending them hides problems in each.
• Sales teams paid on hardware projects have little reason to sell subscriptions unless their incentives change.
• Investors and customers judge the software business on recurring measures, which need to be visible on their own.
• A separate view lets the division make decisions, such as the Octave spin-out, with clear evidence.
Where did Hexagon separate asset software from the rest of the group?
These choices made the software business easier to see and manage.
• Asset Lifecycle Intelligence reported as a division with its own quarterly revenue of €204.4 million in Q1 2025.
• Software-as-a-service growth in EAM tracked separately from hardware and services.
• The Octave spin-out, which focused the asset and software portfolio on a smaller and clearer set of products.
• Enterprise subscriptions priced by users, assets, sites and modules, separate from hardware project pricing.
What Hexagon's $50M+ stage shows about turning physical data into software
The principle is to convert proprietary physical data into an operational decision system, and then expand across the asset lifecycle. Hexagon's Asset Lifecycle Intelligence division reached €204.4 million in the first quarter of 2025, with double-digit SaaS growth in EAM.
The sequence was to own differentiated data, connect it to maintenance and inspection workflows, and add adjacent software only when it shared the same asset record.
The caution is that hardware revenue is not proof of software scalability, so recurring revenue quality needs separate economics.
Business Core shows how top industrial technology companies grew beyond $50M ARR and which risks followed, so you can plan your own next stage.
Read the cautions in each company's how-to-copy steps in Business Core before you copy the acquisition route.
Which signals would show that Hexagon's asset software is a durable business and not a hardware extension?
Growth in the software line itself. Double-digit SaaS growth in enterprise asset management, reported separately from group revenue, shows subscriptions are building on their own, and not simply riding on device sales.
Renewals across the whole lifecycle are the second signal. When customers keep maintenance, safety and design products together, the platform has become the system of record for their assets, and its revenue is more likely to last through a hardware downturn.
How do you separate durable software growth from hardware-driven growth in a group?
• Look at the growth rate of the software line alone, and compare it with the hardware cycle over several years.
• Check whether renewal rates hold when capital spending slows, since that shows whether customers rely on the software.
• Count customers who use more than one module, because breadth is a sign of embedded use.
• Review margins for each line, as a durable software business should show stable and growing margins.
Which companies grew through a cycle without relying on it?
These examples show growth that continued through unusual conditions.
• Hexagon's asset software kept double-digit SaaS growth in EAM while the wider group depended on a cyclical hardware business.
• Doctolib's telemedicine growth deepened clinician workflow beyond the pandemic surge.
• Clari's forecasting stayed central to revenue operations through changing conditions.
• A system of record outlasts any single cycle or moment.
What rule explains Hexagon's path from measurement to lifecycle intelligence?
Move from owning a differentiated data source, to connecting it to an action workflow, to widening across the asset lifecycle only with products that share the same record. Each stage in Hexagon's story follows that order, and the last step carries the largest figures.
For your own plan, the rule asks which step you have actually completed. Acquisitions can speed the path, but they do not replace proof that customers act on your data.
How do you check which stage of the data-to-workflow path you have really reached?
• Ask whether customers make a decision from your data, and not only look at it on a screen.
• Check whether acquired products use the same asset or customer record as the original.
• Treat revenue added by acquisition as a tool for the next step, and not as evidence that the previous step is complete.
• Write down the evidence for each stage, and be honest about which parts are still assumptions.
Where is the evidence strongest about how these companies built larger businesses?
These examples show how published stages give better lessons than guesses about later ones.
• Hexagon has a documented strategy at each stage, with the clearest figures at the $50M+ stage.
• Confluent has detailed stages through its public reporting, which makes later figures easier to read.
• Zuora has detailed stages through public reporting, which shows how a subscription company scales.
• Confirmed stages give you evidence, while unconfirmed ones give you questions.
What mistakes do people make when they read a division's quarterly revenue as annual recurring revenue?
They multiply the quarter by four and call it ARR. A division's revenue includes services, hardware and one-time items, so the annualised number overstates what recurs, and it can mislead anyone using it to plan.
They also forget the group around it. Hexagon's approximately €5.4 billion in group revenue is far larger than the asset division, and reading one as a sign of the other makes the software business look larger or smaller than it is.
Why do quarterly division figures mislead people comparing software companies?
• Division revenue often mixes subscription, services and hardware, which makes it a poor proxy for ARR.
• Annualising one quarter ignores seasonality and one-off deals that can distort a single period.
• Different companies define their divisions differently, so figures are hard to compare directly.
• Comparing a division with a pure software company's ARR creates a false picture of the gap between them.
Which firms are easiest to misread from quarterly or group-level revenue?
These examples show where a headline number gives only part of the picture.
• Hexagon's €204.4 million is a division quarter and not a reported ARR figure.
• Confluent's quarterly revenue includes subscription and services, so it is not a pure recurring number.
• ANSYS's revenue now appears inside Synopsys, so a subsidiary figure and a parent figure are easily confused.
• A quarterly figure is a reason to ask what recurs, not an answer to it.
Enter business core
Does Business Core show how companies grew beyond $50M ARR?
Yes. Each company's ARR journey continues through its larger stages, with the focus, the main move and what to watch at each one.
Can Business Core tell division figures apart from ARR?
Reliable recruiting or verification under the carrier’s real operating requirements.
Does Business Core cover the risks that grow with a company's size?
Yes. Each breakdown lists revenue risks and cautions, including those that appear at larger scale, where they are public.
Can I read how companies separated software from other businesses?
Yes. Where a company reports a software division or a spin-out separately, its ARR journey notes that decision.
Business Core
Everything You Need To Build a Winning Business
Own the
playbook of companies
that won
One-time payment · No subscription · No seat fees
Lifetime Access
Business Core
180
Valid until canceled
SSL Secure Checkout. Instant access.
Companies broken down on the same 56 fields
Filter by 40 decisions carried out by SAAS Cos.
114 model & strategy labels executed by Top Cos.
See what worked, failed and why
Leave with an ARR-stage replication blueprint
Turn proven patterns into your own strategy
Your Business Core access is automatically added to your account on purchase.
The strategic intelligence gap closes the moment you open it.
Walk in with the decision; Walk out with companies that already made it - Here's what's INCLUDED :
MODEL
• Business Models • Distribution Model • Model Insights • How to Apply it • Opportunities & Risks
MARKET
• Market Type • Market Entry & Foothold Strategy • Growth Model • Market Intelligence • Playbook
MONETIZATION
• Revenue & Pricing Model • Target Audience • Customer Buying Behaviour • Patterns • Pricing Intel
MOTION
• Competitive Strategy • Growth & Expansion Strategy • GTM Summary • Growth Engine • Sustaining Moats
