top of page
Won by betting SolidWorks' own co-founders would rather cannibalize their old desktop-CAD legacy than let a browser-native competitor do it for them, then sold the company to PTC for the exact SaaS transition PTC couldn't build itself.
1
MODEL
BUSINESS MODEL
SaaS
model bm
HOW THEY BUILT IT
Founded 2012 in Cambridge, MA by SolidWorks alumni Jon Hirschtick and John McEleney; built the first fully cloud-native, browser-based 3D CAD platform on AWS with real-time multi-tenant collaboration; raised $150M+ before being acquired by PTC in November 2019 for approximately $470 million, roughly 3x Hirschtick's earlier SolidWorks sale.
HOW TO ARCHITECT IT
1) Build cloud-native from a blank slate rather than porting an existing desktop application to the cloud. 2) Recruit founders with a proven exit in the exact same category to accelerate trust. 3) Sell to the legacy incumbent once you've proven the SaaS model works, rather than trying to out-scale it independently.
DISTRIBUTION MODEL
Direct Sales
dm
HOW THEY OPERATIONALIZED
Subscription direct sales (~$1,500-$3,000/user/year) targeting mechanical engineers; post-acquisition, cross-sold alongside PTC's existing Creo and Windchill customer base.
HOW TO REPLICATE WHAT WORKED
Win engineers on the tangible cost-savings pitch (cheaper hardware since rendering happens in the cloud) before PTC's acquisition layers the product into its existing enterprise sales relationships.
| PATTERNS OF THIS MODEL
PATTERNS IN CLOUD-NATIVE REBUILDS OF DESKTOP PROFESSIONAL SOFTWARE:
1. REBUILD FROM ZERO; DO NOT PORT. The entire thesis is that the incumbent's architecture cannot become multi-tenant and real-time without a rewrite it will never fund. If your pitch is "same thing, in a browser," you have a feature.
2. FOUNDER PROVENANCE IS THE FASTEST TRUST SHORTCUT IN CONSERVATIVE PROFESSIONS. The SolidWorks founders re-entering CAD removed years of credibility-building; engineers took the meeting on the name alone.
3. THE INCUMBENT IS THE MOST LIKELY BUYER, AND THAT CAPS THE OUTCOME. PTC acquired Onshape for roughly $470M after $150M+ raised — a good outcome, not a category takeover. Cloud rebuilds usually prove the model and then sell it to whoever owns the installed base.
4. YOU WILL BE VALUED ON PROOF, NOT PENETRATION. Onshape sold with modest revenue relative to Autodesk or PTC; what it sold was a working cloud architecture the acquirer could not build in time.
5. INTEROPERABILITY WITH THE INCUMBENT FILE FORMAT IS NON-NEGOTIABLE. Anything that cannot round-trip is unusable regardless of quality — the same constraint that shaped Modumate and Snaptrude.
CAUTION: capital intensity is high and adoption is governed by the customer's project cycle. Size the raise to years, not months.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — BUILD CLOUD-NATIVE FROM A BLANK SLATE, NOT BY PORTING.
Standard: in categories dominated by decades-old desktop architecture, a genuine rewrite gives you capabilities (real-time multi-user editing, no installs, no version conflicts) the incumbent cannot retrofit without rebuilding its core. Onshape's founders — SolidWorks alumni Jon Hirschtick and John McEleney — built on AWS from scratch in 2012.
GOLDMINE 2 — FOUNDER PEDIGREE AS COMPRESSED TRUST IN CONSERVATIVE CATEGORIES.
Standard: where buyers are professionally liable for their output (engineers, architects, lawyers, clinicians), a founding team with a prior exit in the exact category shortens the evaluation more than any feature. Sell the résumé early, deliberately.
GOLDMINE 3 — SELL TO THE INCUMBENT ONCE THE MODEL IS PROVEN.
Standard: in an entrenched professional category, proving that the SaaS model works is often worth more to the incumbent than to you. PTC acquired Onshape in November 2019 for approximately $470 million after roughly $150M+ raised.
THE PIT — A ~3x RETURN ON CAPITAL IS THE HONEST READ.
Roughly $470M out against $150M+ in is a good outcome and not a venture-scale one, in a category where the incumbent had thirty years of ecosystem — trained staff, file formats, university curricula, regulatory expectations. Beating the product does not beat the ecosystem. Size your raise to that reality.
THE SECOND PIT — PROFESSIONAL LIABILITY SLOWS ADOPTION STRUCTURALLY.
Stamped, signed deliverables make practitioners rationally conservative. Expect adoption cycles measured in project cadence, not renewal dates.
MOVE WITH CAUTION — INTEROPERABILITY IS THE PRICE OF ENTRY.
If your file cannot round-trip with the incumbent's, quality is irrelevant. Budget for that engineering before you budget for differentiation.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
MARKET TYPE
Mature Market
WHY THEY WON
Professional CAD is mature and dominated by Autodesk Inventor and Dassault SOLIDWORKS. Onshape won differentiated share by being the only fully cloud-native, browser-accessible option.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
Onshape entered directly building an entirely new cloud-native platform from scratch, a deliberate bet that porting legacy software to the cloud couldn't match a purpose-built system.
FOOTHOLD STRATEGY
fs
Beachhead Strategy
The beachhead was engineers frustrated with license-server management and hardware costs, validated through a beta with 1,000+ CAD professionals across 52 countries before the March 2015 launch.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
The public beta and 2015 launch, covered extensively by outlets like TechCrunch given founder Hirschtick's SolidWorks pedigree, functioned as a major credibility-building moment.
KEY LEARNING
If re-entering a mature market you've already succeeded in once, your prior exit's credibility is itself a growth asset that press and customer trust follow faster than product marketing alone.
gc
Market Context
| MARKET INTELLIGENCE
THE STANDARD: In a mature market, a DELIVERY-MODEL SHIFT is the only re-entry that incumbents cannot simply copy — because copying it means devaluing the installed base and the channel that funds them.
RULE 1 — THE INNOVATOR'S DILEMMA IN MATURE ENGINEERING SOFTWARE IS ARCHITECTURAL, NOT ATTITUDINAL.
Autodesk Inventor and Dassault SOLIDWORKS are file-based, desktop-installed and sold through a reseller network trained on perpetual and desktop licences. Rebuilding browser-native breaks the file model, the reseller economics and the upgrade cycle at once. That is why the retrofit is slow, and it is the only reason a challenger gets a window.
RULE 2 — STATE THE RETROFIT BARRIER IN ONE SENTENCE OR YOU DO NOT HAVE A MATURE-MARKET ENTRY.
"There are no files" is a structural claim: no check-in/check-out, no version conflicts, no PDM bolt-on, real-time multi-user editing and full edit history as a native property. "Ours is better" is a feature. Only the first survives a procurement comparison against a forty-year incumbent.
RULE 3 — RELEASE CADENCE IS THE VISIBLE PROOF OF THE ARCHITECTURE, AND IT IS THE BEST MARKETING ASSET YOU HAVE.
Onshape publishes that it shipped 17 updates in 2025 against desktop CAD's single annual release, and points to a 2026 SOLIDWORKS release with a reduced feature count while Dassault invests in its next-generation cloud platform. In mature markets, shipping frequency is the evidence buyers can verify themselves.
RULE 4 — LICENSED-KERNEL DEPENDENCE MEANS YOUR DIFFERENTIATION MUST BE ABOVE THE GEOMETRY LAYER.
Onshape is built on the licensed Parasolid kernel — the same lineage available to others. Capability parity from a licensed component is real leverage and zero defensibility. The defensible layer is the data model, the collaboration semantics and the accumulated design history.
RULE 5 — THE MATURE-MARKET ENDGAME IS USUALLY ACQUISITION BY AN INCUMBENT WHO NEEDS YOUR ARCHITECTURE.
PTC acquired Onshape in 2019 for approximately $470M, and has since used it as the cloud-native front of its portfolio — extending it in March 2026 with fully cloud-native Model-Based Definition tied to Arena PLM. Buying the architecture is cheaper and faster than rebuilding it. If you are the cloud-native challenger in a mature category with three entrenched vendors, that is your base case.
MARKET TYPE: Mature Market (professional mechanical CAD), re-entered via a cloud-native delivery-model shift.
| MARKET ENTRY PLAYBOOK
THE STANDARD: A GROUND-UP REBUILD BEATS A PORT ONLY WHEN THE INCUMBENT'S ARCHITECTURE — NOT ITS FEATURE SET — IS THE CUSTOMER'S PROBLEM. State the architectural impossibility in one sentence or you do not have this entry.
RULE 1 — THE THESIS MUST BE THAT THE INCUMBENT CANNOT RETROFIT, NOT THAT IT HAS NOT.
File-based desktop CAD cannot be made simultaneously multi-user, versioned and browser-native by hosting it. That is a structural claim, testable and defensible. "Ours is on the cloud" is not.
RULE 2 — TEAM PROVENANCE IS THE PROOF THE MARKET WILL ACCEPT.
When the founders previously built the incumbent's category-defining product, the architectural claim carries evidence a newcomer cannot manufacture. In deep-technology entries, credibility substitutes for reference customers during the years before you have any.
RULE 3 — EXPECT THE PROFESSION TO ADOPT SLOWLY AND FOR GOOD REASONS.
Engineering work carries liability, archival requirements and file-format obligations. Interoperability with the incumbent chain is the price of entry regardless of product quality.
RULE 4 — ENTER THROUGH EDUCATION AND SMALL TEAMS, WHERE THE SWITCHING EVENT IS A NEW PROJECT.
Nobody migrates a live programme. The addressable moment is a new project, a new team or a new graduate — which makes free education tiers a distribution channel rather than charity.
RULE 5 — A DEEP-ARCHITECTURE BET IS EXPENSIVE ENOUGH THAT STRATEGIC ACQUISITION IS THE LIKELY RESOLUTION.
Onshape raised over $150M and was acquired by PTC in 2019 for approximately $470M. That is a strong outcome and it is not independence — capitalise accordingly.
EVIDENCE: founded 2012 by former SolidWorks leadership including Jon Hirschtick; built a browser-native, multi-user CAD platform from scratch rather than hosting existing software; acquired by PTC in 2019 in a deal reported at about $470M, and now sold alongside PTC's Atlas platform and Arena PLM.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: WHEN YOU ATTACK AN ENTRENCHED PROFESSIONAL TOOL, THE BEACHHEAD IS NOT THE FEATURE — IT IS THE OPERATIONAL BURDEN THE INCUMBENT'S ARCHITECTURE FORCES ON ITS USERS. Licences, servers, file copies, version conflicts and hardware refreshes are costs the incumbent cannot remove without dismantling itself.
RULE 1 — Target the pain that comes from HOW the incumbent is built, not from WHAT it does.
Feature complaints get fixed in a release. Architectural complaints — install this, license that, manage the server, reconcile the file — cannot be fixed without a rewrite the incumbent will not undertake while its revenue depends on the current model. That asymmetry is the only durable wedge against a dominant professional tool.
RULE 2 — FOUNDER PROVENANCE IS THE FASTEST CREDIBILITY IN A CONSERVATIVE PROFESSION.
In categories where an incorrect tool choice has professional consequences, buyers discount unknown vendors heavily. A founding team that built the incumbent generation's defining product converts the first meeting from qualification to curiosity.
RULE 3 — RUN A LARGE PRE-PRODUCTION BETA, AND KNOW WHAT IT DOES AND DOES NOT PROVE.
Recruiting professionals across many countries into pre-release testing produces real product hardening, real edge cases and real launch demand. It validates INTEREST and CAPABILITY. It does not validate willingness to pay, willingness to migrate live work, or willingness to change the file formats their clients and suppliers expect.
RULE 4 — IN PROFESSIONAL TOOLS THE SWITCHING EVENT IS A NEW PROJECT, NOT A RENEWAL DATE.
Nobody migrates work in progress. Your sales cycle is governed by the customer's project cadence, and your pipeline must be planned against their calendar rather than your quarter.
RULE 5 — CATEGORY-DEFINING ARCHITECTURE STILL LOSES TO ECOSYSTEM.
Trained staff, university curricula, consultants, file-format expectations, plug-ins and client requirements are the incumbent's real moat. Beating the product does not beat the ecosystem, and the gap between the two is measured in years of adoption — years your capital has to survive.
RULE 6 — A CORRECT ARCHITECTURAL THESIS CAN STILL END IN A MODEST EXIT, AND THAT IS THE RESULT TO PLAN FOR.
Being right early in a slow-moving professional category means the incumbent's transition, not your growth, sets the pace. The realistic outcome is a strategic sale to a larger vendor that needs your architecture to make its own transition.
EVIDENCE (Onshape):
- Founded 2012 (initially as Belmont Technology) by SolidWorks veterans including Jon Hirschtick, John McEleney and Dave Corcoran; spent roughly three years building with no revenue.
- Public beta opened 10 March 2015 after pre-production testing with more than a thousand CAD professionals across 52 countries; demand overwhelmed servers at launch. Full commercial release followed in December 2015 / January 2016.
- IMPORTANT DATA CORRECTION: the "1,000+ CAD professionals across 52 countries" statistic belongs to Onshape and is well documented in the public record. The same phrasing appears attached to Modumate in the source research supplied; that attribution does not match any Onshape-independent source and should be treated as a copy-paste error rather than two identical betas.
- Raised more than $150 million in venture funding.
- Acquired by PTC in a deal announced 23 October 2019 and closed November 2019 for approximately $470 million net of cash — PTC's largest acquisition at the time, made explicitly to accelerate its own SaaS transition. Onshape had over 5,000 customers at the time.
- READ THE EXIT HONESTLY: roughly $470M against more than $150M raised is a real but modest multiple for a technically superior, category-first product with an exceptional founding team — the direct consequence of Rule 5. Post-acquisition, PTC has continued extending Onshape by acquisition (Arena, Migenius, CloudMilling and others).
APPLICATION CHECKLIST: (a) Attack the architecture, not the feature list. (b) Put the incumbent's own veterans on your founding team if you can. (c) Design the beta to test payment and migration, not enthusiasm. (d) Plan pipeline against the customer's project cadence. (e) Size your capital against the ecosystem's adoption speed, not your product's readiness. (f) Decide early whether a strategic sale is the outcome you are building for.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
REVENUE MODEL
Subscription
PRICING MODEL
Tiered Pricing
WHY THEY WON
Annual per-user subscription across Standard (~$1,500/year), Professional (~$2,100/year), and Enterprise (~$3,000/year) tiers.
Tiers gate advanced simulation, PDM depth, and enterprise administration, while core modeling and collaboration are available at Standard.
TARGET AUDIENCE
CUSTOMER BUYING BEHAVIOUR
tg cb
Mechanical engineers and product-development teams from small manufacturers to large enterprises.
Considered, evaluation-driven purchase, often triggered by frustration with legacy license-server management.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
THE STANDARD: Gate on PRIVACY, not on capability. When professional work is confidential by nature, giving away the full product with everything public is the highest-converting free tier that exists — because the free version is unusable commercially for reasons the user cannot argue with.
RULE 1 — MAKE THE FREE TIER FULLY CAPABLE AND FULLY EXPOSED.
Onshape's free plan gives real CAD tooling with unlimited public documents; all work is publicly visible and non-commercial. Hobbyists, students and evaluators get a complete product. No professional can use it for client work. The conversion trigger requires no feature-envy and no upsell campaign.
RULE 2 — A CONFIDENTIALITY GATE CONVERTS BETTER THAN A FEATURE GATE BECAUSE IT CANNOT BE WORKED AROUND.
Users route around missing features with exports, plugins and workarounds. Nobody routes around "your designs are public". Wherever your customers handle sensitive material, privacy is the strongest paywall available.
RULE 3 — BUNDLE THE ADJACENT PRODUCT CATEGORY INTO THE PRICE AND COMPARE AGAINST THE PAIR.
Onshape includes data management alongside CAD, and its own pricing argument compares $1,500/user/year Standard against a traditional perpetual CAD licence plus separate PDM plus maintenance — a comparison built explicitly on the stack, not the seat. Always pick the comparison basket in which you are cheapest.
RULE 4 — GIVE VIEWER LICENCES AWAY WITHOUT LIMIT.
Unlimited free viewers mean the whole organisation touches the product while only creators are billed. This is how a per-creator price penetrates an enterprise without an enterprise sales motion, and charging for viewers would tax your own distribution.
RULE 5 — PRICE ANNUALLY, PER USER, IN A CATEGORY TRAINED ON PERPETUAL LICENCES.
Published pricing runs approximately $1,500/user/year (Standard, commercial use and private documents) and $2,500/user/year (Professional), with Enterprise quoted. Note the trade honestly: at scale, per-seat annual subscription costs more than the incumbent's perpetual licence eventually did, and buyers do that arithmetic. The counter-argument must be the removed PDM server, IT overhead and version-control cost — not the sticker price.
RULE 6 — FREE EDUCATION TIERS ARE PRICING INFRASTRUCTURE FOR THE NEXT DECADE.
Onshape's free student and educator plans are explicitly benchmarked against the paid tiers ("comparable to the Standard Plan, valued at $1,500/year") with watermarked documents. In tool categories where universities train the workforce, whoever is free in the classroom sets the default in the workplace ten years later. Autodesk understood this first; the counter-move is to be free earlier.
THE WILLINGNESS-TO-PAY INSIGHT: An engineer is not paying for CAD — they are paying for the right to keep their client's design confidential and to use it commercially. Once you identify the single condition that makes free use professionally impossible, you can give away everything else and still convert, because the buyer is not weighing features against price. They are weighing a legal obligation against price.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
THE STANDARD: Inside a large parent, a fast-growing product's risk shifts from churn to visibility. When your numbers are never broken out, the constraint on your business becomes the parent's allocation decision, not your market.
RULE 1 — THE PARENT'S BLENDED GROWTH RATE IS THE CEILING ON PATIENCE.
PTC raised its annual ARR growth forecast to roughly 9.25% (Q3 FY2026), against Q1 FY2026 revenue of $686M and ARR of $2,494M. A single-digit-growth parent funds a high-growth asset only while the asset is visibly winning.
RULE 2 — SELLING CLOUD-NATIVE INTO A CONSERVATIVE, IP-SENSITIVE PROFESSION MEANS SECURITY IS THE SALES CYCLE.
Large manufacturers remain reluctant to place product IP in a multi-tenant cloud. One serious breach in this category would produce churn and a frozen enterprise pipeline simultaneously. The risk is binary and exogenous.
RULE 3 — THE INCUMBENT'S MOAT IS THE ECOSYSTEM, NOT THE SOFTWARE, AND IT DOES NOT EROSE ON PRODUCT MERIT.
SolidWorks and Autodesk own trained staff, university curricula, file-format expectations, reseller networks and supplier interoperability requirements. Winning the product comparison does not win the account.
RULE 4 — YOUR PARENT'S OTHER CAD PRODUCT IS ALSO YOUR COMPETITOR.
PTC sells Creo (on-premise) and Creo+ (SaaS) alongside Onshape. Internal channel conflict caps how aggressively either can be positioned, and the sales force will follow the larger commission.
RULE 5 — AUTODESK FUSION IS THE PRICE ANCHOR IN THE MID-MARKET AND IT IS BUNDLED.
Fusion targets the same buyer with aggressive pricing inside a collection customers already own. At $1,500-$3,000 per user per year, Onshape is priced against a product many prospects effectively get for free.
RULE 6 — AI DEMAND IS A REAL TAILWIND AND A REAL REPRICING RISK.
PTC reports API calls from AI-related startups tripling in months and cites Winnebago as Onshape's largest-ever win, positioning cloud-native architecture as ideal for AI-in-the-loop workflows. That same shift makes the seat the wrong unit: if agents do the modelling, per-seat annual pricing is measuring the thing being reduced.
WHAT IS NOT KNOWN: PTC does not disclose Onshape ARR, customer count, retention or churn separately. Third-party figures for Onshape's standalone revenue are modelled estimates only and should not be cited as data. PTC acquired Onshape in November 2019 for approximately $470M.
Where the model can break
4
MOTION
(part of PTC — check onshape.com/ptc.com for current official channels)
GROWTH EXPANSION MODEL
COMPETITIVE STRATEGY
motion ge cs
Product Line Expansion
HOW THEY EXPAND
Post-acquisition, expanded into AI-assisted design, CAM/toolpath generation, PLM integration, and Apple Vision Pro compatibility.
First-Mover Advantage
HOW THEY COMPETE
As the first genuinely native SaaS CAD platform, maintained a lead years after acquisition.
GROWTH ENGINE
GTM
ge n gtm
Platform Integrations
Loop: PTC's acquisition embedded Onshape in enterprise sales conversations → cloud-migration customers cross-sold rather than shopping competitors → adoption funds continued platform investment. Depends on PTC continuing to prioritize the cloud-native architecture.
Direct sales, cross-selling through PTC's existing enterprise relationships, and case-study content on cost/productivity savings.
SUSTAINING MOATS
Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)
moat
Once a team's full design history and real-time collaboration workflows live in Onshape's cloud, migrating back to desktop CAD means losing continuous version history.
| MOAT INTELLIGENCE
THE STANDARD: To displace an entrenched desktop incumbent you cannot ship a better version of their product. You must change WHERE THE WORK LIVES, so that your advantage is architectural and their retrofit is impossible.
RULE 1 — ATTACK THE FILE, NOT THE FEATURES.
Legacy CAD's real pain is file management: versions, copies, "final_v7", broken references. A database-backed model with built-in version control removes a category of pain rather than adding a capability — and an incumbent built on files cannot match it without rewriting everything.
RULE 2 — FOUNDERS WHO BUILT THE INCUMBENT ARE THE MOST CREDIBLE ATTACKERS, because they know precisely which architectural decision is unfixable. Credibility with sceptical engineers is otherwise near-impossible to buy.
RULE 3 — WHEN YOUR BEACHHEAD IS EDUCATION, YOU ARE BUYING A COHORT, NOT REVENUE. Free tiers for students and hobbyists seed the next decade's specifying engineers. It is a ten-year play and must be budgeted as one.
RULE 4 — AN EARLY STRATEGIC ACQUISITION CAN BE THE RIGHT ANSWER WHEN THE INCUMBENT'S SWITCHING COSTS ARE MEASURED IN DECADES.
Displacing a standard that has trained a generation and holds every legacy part file is a capital problem, not a product problem. Selling to a larger CAD/PLM player buys the balance sheet and the enterprise channel the fight requires.
RULE 5 — SAY THE TRADE-OFF PLAINLY: inside a parent, the product gains distribution and loses the freedom to cannibalise the parent's own installed base. That tension defines every acquired challenger.
EVIDENCE:
- Founded 2012 by Jon Hirschtick and colleagues from the SolidWorks founding team, as a fully cloud-native, browser-based CAD and PDM system with built-in version control, branching and real-time multi-user editing — no local files, no installs.
- Acquired by PTC in 2019 for a reported ~$470M. Onshape continues as a PTC product line and became the foundation for PTC's Atlas cloud platform and the Arena PLM pairing.
- I DID NOT VERIFY CURRENT ONSHAPE SEAT COUNT, ARR OR GROWTH IN THIS PASS. PTC does not break Onshape out as a separate reported line; any standalone figure in circulation is an estimate.
- Category context: Autodesk's CEO has publicly stated there will be no next-generation Revit, pointing to cloud-based Forma instead — the same architectural bet Onshape made a decade earlier, now conceded by the largest incumbent in an adjacent category.
THE SIGNAL TO COPY: Onshape's moat was never a feature list — it was that the incumbent's file-based architecture could not be retrofitted to the cloud. Find the structural decision your incumbent cannot reverse, build the product that decision forbids, and accept that displacing a standard may still require someone else's balance sheet.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — BUILD THE ARCHITECTURAL BET, NOT THE FEATURE BET
Enter a category with entrenched incumbents only where an architectural shift makes their design a liability. Cloud-native, browser-based CAD with real-time collaboration and version control is not a better file-based CAD; it is a different architecture the incumbent cannot retrofit without rewriting its core.
Assemble a founding team the market already trusts. Onshape was founded by the team behind SolidWorks — in conservative professional categories, credibility is the entry ticket and it cannot be bought.
Raise properly. This is a capital-intensive category with long sales cycles and a decade-long ecosystem to displace; Onshape raised roughly $169M before exit, in deliberate contrast to under-capitalised challengers in adjacent design categories.
REFUSE: file compatibility as your positioning. Interoperate, but sell the architecture.
$1–5M ARR — SELL TO THE TEAM THAT LOSES DAYS TO VERSIONING
Target the pain the incumbent's architecture creates rather than the tasks it performs: lost versions, licence lock-in, install and IT overhead, inability to collaborate simultaneously.
Land with small distributed engineering teams and educational users, where the incumbent's licensing model is most painful and the switching cost is lowest.
Price as a subscription against a perpetual-licence incumbent, and make the total-cost comparison explicit including IT and workstation costs.
WATCH: documents with more than one simultaneous editor. That is the metric only your architecture can produce.
$5–10M ARR — WIN EDUCATION, BECAUSE ECOSYSTEMS ARE GENERATIONAL
Give the product free to students and educators without limits. Professional tool ecosystems are reproduced through curricula, and every graduate trained on your product is a decade of downstream demand.
Build the API and app ecosystem early so third parties fill the vertical gaps you will never build.
Publish the release cadence advantage: continuous cloud updates against annual desktop releases is a compounding, visible proof of the architectural claim.
WATCH: named accounts converting from trial to a full team, not seat count in isolation.
$10–50M ARR — ACCEPT THAT THE ECOSYSTEM MOVES SLOWLY
Plan for adoption slower than the product deserves. Trained staff, consultants, file-format norms, customer and regulatory expectation, and liability all slow professional-tool adoption independently of product quality.
Expand into adjacent workflow — data management, release control, manufacturing handoff — where the cloud architecture gives you capability the incumbents ship as a separate, expensive product.
Sell to enterprise engineering leadership on IT cost and continuity, not to individual engineers on features.
DECIDE: whether you can fund a decade of ecosystem displacement, or whether a strategic owner should.
$50–100M ARR — SELL TO A STRATEGIC BUYER WHEN THE ARCHITECTURE IS THE ASSET
Recognise when a strategic acquirer values your architecture more than the public market will value your growth rate. (PTC acquired Onshape in 2019 for approximately $470M, with reported ARR in the region of $20M at the time — a multiple that reflected the platform, not the revenue.)
Negotiate for continued product investment and brand continuity, because in professional tools the customer's fear is abandonment.
Read the pricing lesson honestly: an architectural asset with modest revenue can command an outsized price from a buyer who needs the architecture. That is a strategy, not an accident.
$100M+ ARR — REACHED INSIDE A PARENT, NOT INDEPENDENTLY
State it plainly: Onshape did not reach this band as an independent company. It scaled inside PTC, where it now anchors a cloud-native product line alongside the acquired Arena and Onshape platform businesses.
The transferable instruction: in categories with entrenched ecosystems, the realistic winning move for a well-built challenger is to become the incumbent's future architecture rather than to outlast it.
If independence is the goal, you need capital sized to a fifteen-year displacement, and you should say so to investors before you take their money.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: To displace an entrenched desktop incumbent, do not build a better desktop product. Change WHERE THE DATA LIVES, then let the architecture generate the benefits (no installs, no file versions, real-time collaboration) that the incumbent cannot retrofit.
HOW TO COPY — THE SEQUENCE:
1. Identify a professional category where the incumbent's architecture — not its feature set — is the source of the customer's daily pain (file versions, licence servers, hardware requirements).
2. Rebuild it cloud-native from the database up, so the differentiators are structural rather than additive.
3. LEAD WITH THE TANGIBLE COST SAVING, not the philosophy: cheaper hardware because rendering happens server-side, no IT infrastructure, no per-machine installs. Engineers buy arithmetic.
4. Win the segments the incumbent serves worst — startups, hardware teams, distributed engineering groups, and education, where students become tomorrow's specifiers.
5. Sell to an incumbent platform when your architecture becomes strategically necessary to them (PTC acquired Onshape in 2019 for roughly $470M).
6. Post-acquisition, let the architecture become the parent's platform rather than remaining a product — Onshape's cloud core became the basis of PTC's Atlas platform, extending to Arena and beyond.
WHAT WORKED:
- Founder credibility as the entire entry strategy: Jon Hirschtick, who founded SOLIDWORKS, could credibly claim CAD needed rebuilding, which no outsider could.
- Architecture as a compounding advantage in the AI era. PTC's own framing is that Onshape captures every design decision in real time, creating the structured data AI needs to understand design intent — the cloud bet paid off a second time, roughly a decade later.
- Continued product investment post-acquisition rather than absorption: cloud-native Model-Based Definition (February 2026), Onshape AI Advisor embedded in the design environment (October 2025), Onshape Labs early-access programme (July 2026), and Onshape Government on AWS GovCloud for ITAR/EAR-regulated work.
WHAT DID NOT WORK / THE CAUTIONS:
1. THE INCUMBENT WAS NOT DISPLACED. PTC now runs a DUAL-CAD strategy — Creo for the installed base, Onshape for cloud-native — and PTC's own CAD line reported $254M in a recent fiscal quarter against $432M for PLM. Being architecturally right does not transfer the installed base; it earns you a seat next to it.
2. ONSHAPE'S STANDALONE REVENUE IS NOT SEPARATELY DISCLOSED by PTC, so any claim about its independent scale is inference, not data.
3. PROFESSIONAL CAD ADOPTION IS GENERATIONAL. File-format compatibility, trained staff, consultants and university curricula are the real moat, and beating the product does not beat the ecosystem.
4. ACQUISITION MEANS YOUR ROADMAP SERVES A PORTFOLIO. Onshape's cloud core was generalised into Atlas for the parent's benefit — good for PTC, and a reminder that the acquirer buys the architecture, not your independence.
bottom of page