top of page
Autodesk A360
Technology
SaaS Platforms
Cloud Design Collaboration
Won a foothold in cloud collaboration by giving Autodesk's massive desktop CAD user base a free, simple way to view and share 3D models online — a wedge product designed to normalize cloud workflows before Autodesk needed customers to pay for full cloud-based project delivery.
1
MODEL
BUSINESS MODEL
SaaS, Platform Ecosystem
model bm
HOW THEY BUILT IT
- Launched as Autodesk's cloud rendering, storage, and collaboration layer, letting desktop AutoCAD/Revit users view, share, and render 3D models via a browser without needing the full desktop application installed on the viewer's machine.
- Functioned primarily as a bridge product connecting Autodesk's legacy desktop CAD installed base to its longer-term cloud strategy, later folded into and superseded by the broader Autodesk Construction Cloud and Fusion Team platforms.
- Free or low-cost viewing/sharing tiers seeded broad usage among project stakeholders (clients, contractors) who didn't own full CAD licenses themselves, expanding Autodesk's footprint beyond paying seat-holders.
HOW TO ARCHITECT IT
1. Build a free, lightweight cloud companion product specifically to extend your paid desktop software's reach to non-licensed stakeholders (clients, contractors) who need to view but not edit files.
2. Use a bridge product to normalize cloud workflows gradually within a large, change-resistant desktop-software user base before asking them to fully migrate.
3. Expect bridge products to be superseded by more comprehensive platforms as your cloud strategy matures — treat them as a transitional wedge, not a permanent standalone product.
DISTRIBUTION MODEL
Platform Integrations, Direct Sales
dm
HOW THEY OPERATIONALIZED
Distributed as a bundled cloud service within existing AutoCAD/Revit subscriptions, extending reach to non-licensed collaborators (clients, contractors) who accessed shared models via free viewer links.
HOW TO REPLICATE WHAT WORKED
What worked: bundling a free, lightweight cloud viewer with an existing paid desktop product to extend reach to unlicensed stakeholders in a project. Trap if copied blindly: bridge products risk becoming a maintenance burden once superseded by a more comprehensive platform — Autodesk eventually folded A360 into broader Construction Cloud offerings, and a founder building an equivalent bridge product should plan its eventual sunset from the start.
| PATTERNS OF THIS MODEL
PATTERNS IN BRIDGE PRODUCTS BETWEEN OLD AND NEW ARCHITECTURES:
1. A FREE, LIGHTWEIGHT COMPANION EXTENDS PAID SOFTWARE'S REACH TO NON-LICENSED STAKEHOLDERS who need to see but not create. That widens influence without cannibalising licences.
2. USE A BRIDGE PRODUCT TO NORMALISE NEW WORKFLOWS INSIDE A CHANGE-RESISTANT BASE before asking for full migration.
3. TREAT BRIDGE PRODUCTS AS TRANSITIONAL BY DESIGN. They are superseded once the destination platform matures — plan the sunset rather than defending them.
4. VIEWER-TIER ADOPTION IS A LEADING INDICATOR of who else in the customer's ecosystem could eventually become a paying seat.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — SHIP A FREE CLOUD COMPANION FOR NON-LICENSED STAKEHOLDERS.
Standard: clients and contractors need to view, not edit. Serving them extends your footprint far beyond paying seats and puts your interface in front of the people who influence the next purchase.
GOLDMINE 2 — USE A BRIDGE PRODUCT TO NORMALISE CLOUD BEHAVIOUR GRADUALLY.
Standard: change-resistant desktop bases adopt cloud workflows incrementally. A bridge lowers the cost of the eventual migration you actually want.
GOLDMINE 3 — TREAT THE BRIDGE AS DISPOSABLE BY DESIGN.
Standard: A360 was superseded by Autodesk Construction Cloud and Fusion Team. Naming it a transitional wedge internally prevents sunk-cost defence later.
THE PIT — TRANSITIONAL PRODUCTS CONFUSE CUSTOMERS AND FRAGMENT THE BRAND.
Users invest in a workflow that is then deprecated, which teaches the base to wait rather than adopt the next cloud offering — a cost that lands on the successor product.
THE SECOND PIT — FREE VIEWERS ARE INFRASTRUCTURE COST WITH NO DIRECT REVENUE.
MOVE WITH CAUTION — A BRIDGE ONLY PAYS IF THE DESTINATION IS BUILT AND FUNDED IN PARALLEL.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
MARKET TYPE
Emerging Market
WHY THEY WON
Cloud-based 3D model collaboration was an emerging need as construction and engineering projects increasingly involved distributed teams; A360 addressed this emerging requirement using Autodesk's existing desktop dominance as a distribution advantage.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
A360 entered as a direct extension of Autodesk's existing subscription products rather than a standalone go-to-market effort, leveraging the installed base rather than acquiring new customers independently.
FOOTHOLD STRATEGY
fs
Wedge Strategy
The wedge was existing AutoCAD/Revit subscribers who needed to share models with non-CAD-owning collaborators (clients, contractors) — a low-friction expansion of Autodesk's existing paid relationship rather than a new customer acquisition motion.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
Bundling free viewer access within paid subscriptions; integration with Revit and AutoCAD desktop products to auto-sync models to the cloud for sharing.
KEY LEARNING
If you have a large installed base of desktop software users, consider a free, lightweight cloud companion product specifically to extend reach to non-paying stakeholders in the same workflow — this expands your product's footprint without requiring net-new customer acquisition.
gc
Market Context
| MARKET INTELLIGENCE
THE STANDARD: An incumbent entering an emerging need uses its installed base as the distribution advantage a startup must buy.
RULE 1 — DISTRIBUTION IS THE INCUMBENT'S ONLY REAL ADVANTAGE IN A NEW CATEGORY. Product quality rarely favours the incumbent early; reach always does.
RULE 2 — BOLTING CLOUD ONTO A DESKTOP PRODUCT IS NOT THE SAME AS BEING CLOUD-NATIVE. Buyers detect the difference, which is exactly the gap challengers exploit.
RULE 3 — INCUMBENT CLOUD PRODUCTS SERVE PORTFOLIO STRATEGY AND GET RESHUFFLED. Roadmap priority follows the parent, not the users.
RULE 4 — THE DEFENSIVE PRODUCT'S JOB IS TO STOP A CHALLENGER OWNING THE COLLABORATION LAYER. Judge it on that, not on standalone adoption.
MARKET TYPE: Emerging Market (cloud design collaboration), entered from incumbency.
| MARKET ENTRY PLAYBOOK
THE STANDARD: A PRODUCT LAUNCHED AS AN EXTENSION OF AN INSTALLED BASE IS MEASURED BY ATTACH RATE, NOT ACQUISITION.
RULE 1 — LEVERAGE, DO NOT REBUILD, THE CUSTOMER RELATIONSHIP.
Bundling into an existing subscription removes acquisition cost and removes the discipline that customer acquisition imposes.
RULE 2 — FREE-WITH-THE-SUITE PRODUCTS RARELY GET HONEST DEMAND SIGNALS.
Usage inflated by bundling hides whether anyone would have paid; instrument active use separately.
RULE 3 — COLLABORATION FEATURES BOLTED ONTO DESKTOP TOOLS INVITE A GROUND-UP COMPETITOR.
Retrofitting is where cloud-native entrants find their opening.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: The cheapest expansion is selling collaboration to people your existing customers already need to include.
RULE 1 — EXTEND AN EXISTING PAID RELATIONSHIP RATHER THAN ACQUIRING NEW CUSTOMERS. Subscribers needing to share models with non-owning collaborators are a warm, identified, immediate market.
RULE 2 — THE UNLICENSED COLLABORATOR IS A FREE TRIAL WITH CONTEXT. Clients and contractors experience the ecosystem without buying into it.
RULE 3 — COLLABORATION FEATURES BOLTED ONTO DESKTOP TOOLS LOSE TO NATIVELY COLLABORATIVE PRODUCTS. Architecture, not feature parity, decides this category.
RULE 4 — INTERNAL EXTENSIONS COMPETE FOR ATTENTION AGAINST THE CORE PRODUCT. A companion offering rarely receives the investment required to defend against a focused challenger.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
REVENUE MODEL
Subscription
PRICING MODEL
Bundled Pricing
WHY THEY WON
Bundled into existing Autodesk subscription tiers rather than sold as a standalone product, monetized indirectly through retention and expansion of the broader Autodesk subscription relationship.
Included as a value-add within AutoCAD/Revit subscriptions rather than priced separately, targeting existing subscribers who wanted cloud collaboration without an additional purchase decision.
TARGET AUDIENCE
CUSTOMER BUYING BEHAVIOUR
tg cb
Existing AutoCAD/Revit subscribers (wanting cloud sharing); project stakeholders without CAD licenses (clients, contractors needing to view shared models); AEC firms managing distributed project teams.
Included automatically with existing subscriptions rather than a discrete purchase decision; non-licensed viewers accessed shared links without any purchase at all.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Bundling collaboration into a design licence is a defensive move against a cloud-native challenger, and it makes the feature hard to value.
RULE 1 — INCLUDING CLOUD COLLABORATION IN THE SEAT PRICE NEUTRALISES A COMPETITOR'S WEDGE.
When the challenger's differentiator arrives free with your licence, its price advantage disappears.
RULE 2 — BUNDLED FEATURES ARE UNDER-ADOPTED BECAUSE NOBODY CHOSE THEM.
Free inclusion suppresses usage measurement and makes the capability impossible to price later.
RULE 3 — CLOUD STORAGE AND COMPUTE ARE A REAL COST INSIDE A FIXED SEAT FEE.
Bundling consumption into a flat price transfers variable cost to you with no meter.
RULE 4 — PRODUCT RATIONALISATION FOLLOWS OVERLAPPING CLOUD OFFERINGS.
Multiple adjacent platforms under one vendor eventually consolidate, and customers experience that as disruption.
Firms are getting collaboration they did not evaluate and often do not use. Bundling defends a market and destroys your ability to ever charge for the thing you bundled.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
A product bundled into existing subscriptions rather than sold standalone has no revenue of its own and no observable success metric — it can only be justified by retention it cannot prove.
Monetising indirectly means the product competes for engineering investment against lines that show revenue, and usually loses.
Collaboration layers inside a design suite are exactly what platform vendors ship free to defend the core.
Products in this position are typically absorbed, renamed or retired rather than grown.
Never separately monetised or disclosed; largely superseded within Autodesk's cloud offering.
Where the model can break
4
MOTION
GROWTH EXPANSION MODEL
COMPETITIVE STRATEGY
motion ge cs
Platform Expansion
HOW THEY EXPAND
A360's cloud collaboration capability was absorbed into and expanded upon by Autodesk Construction Cloud and Fusion Team, sequenced as Autodesk's broader cloud platform strategy matured beyond a simple viewer/sharing bridge.
Defensive Strategy
HOW THEY COMPETE
A360 functioned defensively, protecting Autodesk's desktop installed base from being displaced by cloud-native competitors by giving existing customers a cloud option within the Autodesk ecosystem before they felt compelled to evaluate outside alternatives.
GROWTH ENGINE
GTM
ge n gtm
Platform Integrations
Growth compounded as each shared model link exposed new, unlicensed viewers to the Autodesk ecosystem, some of whom later became paying subscribers themselves when they needed editing capability. It would break down without continued integration into Autodesk's evolving cloud platform strategy, which is precisely what happened as A360 was superseded.
Bundled distribution through existing Autodesk subscription relationships rather than independent go-to-market, extended via free-viewer virality to unlicensed project stakeholders.
SUSTAINING MOATS
Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)
moat
A360's moat was purely derivative of Autodesk's broader desktop CAD dominance — its value existed only because so many projects already used Autodesk file formats, a moat borrowed from the parent ecosystem rather than independently created.
| MOAT INTELLIGENCE
THE STANDARD: A collaboration layer bolted onto desktop products inherits their architecture and rarely wins against tools built cloud-native from the start.
RULE 1 — CLOUD AS A FEATURE IS NOT CLOUD AS AN ARCHITECTURE. Syncing files to a web service delivers storage and version history; it does not deliver simultaneous multi-user editing, which is what customers actually mean by collaboration.
RULE 2 — INCUMBENTS ADD COLLABORATION LATE BECAUSE THE INSTALLED BASE PENALISES REWRITES. Protecting existing customers is rational and it is exactly what creates the opening a challenger needs.
RULE 3 — PLATFORM CONSOLIDATION WITHIN A PORTFOLIO IS ROUTINE. Products serving as transitional layers get absorbed into successors once the strategy clarifies.
THE SIGNAL: if your cloud offering exists to extend a desktop product rather than replace it, you are defending an installed base rather than competing for the next one. Those are different investments and only one of them wins new customers.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M — THE HONEST FRAME: THIS IS A DISCONTINUED PRODUCT LINE
A360 was Autodesk's cloud collaboration and viewing platform for design data. It was progressively absorbed, renamed and retired as capabilities moved into BIM 360, Fusion and the Autodesk Construction Cloud.
Read the row as a lesson in internal product mortality, not as a growth story.
$1–5M — CLOUD LAYERS ON DESKTOP PRODUCTS STRUGGLE FOR A BUYER
When the desktop tool already has the customer and the budget, the cloud companion has no independent buying trigger.
Give a new product its own buyer and its own P&L or it will be measured as a feature.
$5–10M — VIEWING AND SHARING ARE FEATURES, NOT BUSINESSES
Any capability the incumbent product can absorb will be absorbed.
$10–50M — REBRANDING A PRODUCT REPEATEDLY IS A SIGNAL OF STRATEGIC INDECISION
Customers read successive renames as instability and delay adoption.
$50–100M — NOT REACHED AS A DISTINCT LINE
Standalone figures were never disclosed and the product no longer exists independently.
$100M+ — NOT APPLICABLE
Rule: inside a large company, a product without its own buyer, budget and metric will be folded into the one that has them. Give new lines commercial independence or expect this ending.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: A free lightweight viewer extends a paid desktop product's reach to unlicensed stakeholders. Bridge products should be designed with their own sunset in mind.
SEQUENCE:
1. Give the non-purchasing participants free read-only access to your customers' work.
2. Use their exposure to seed demand for the paid tool.
3. Plan the retirement path from the start.
WORKED: Free viewing extending a paid product's footprint to everyone in a project without adding licence cost.
CAUTION:
1. BRIDGE PRODUCTS BECOME A MAINTENANCE BURDEN ONCE SUPERSEDED. This one was folded into a broader platform — expect that, and design for graceful absorption rather than indefinite support.
2. FREE VIEWERS TRAIN THE MARKET TO EXPECT FREE ACCESS, which constrains later monetisation of collaboration.
bottom of page