Key Takeaway The market still prices these four companies as belonging to the same category of "high-margin, vertical SaaS under AI pressure." However, this research shows that they actually occupy four entirely different levels of control points, requiring a differentiated valuation language.
Navigation and How to Read This Report
Framework Dictionary Upfront
This report is not written according to traditional financial templates; instead, it analyzes companies based on a "business control points" framework. The complete dictionary is presented first, before moving into the main body of the report.
What Exactly Are I1-I8?
I1-I8 are not financial line items, but rather 8 "business control points." You can think of them as: which layer a company truly controls in the age of AI.
Code
Plain Language Explanation
What This Report Truly Aims to Ask
I1
Why Do Customers Actually Pay?
Do they pay for software usage rights, results, commissions, or a responsibility premium?
I2
Whose Data and Context Are Decisions Reliant On?
Who possesses the truly valuable historical data?
I3
Who Can Actually Get Things Done?
Who can change status, trigger processes, and drive the next step of execution?
I4
Who Has the Authority to Make Final Decisions, and Who Bears Formal Responsibility?
Who is ultimately responsible for audits, compliance, approvals, and formal liabilities?
I5
Where Does the Budget Originate From?
Does the money come from IT budgets, business budgets, consumer spending, or transaction commissions?
I6
For Every Extra Dollar Earned, How Much Is Ultimately Retained?
Does the incremental value remain within the company, or is it consumed by channels and costs?
I7
Who Cleans Up the Mess After Something Goes Wrong?
After errors, complaints, or failures, who compensates, who repairs, and who provides the backstop?
I8
Where Do Users Default to Start Their Work?
Who holds the primary entry point, the default entry, and the workflow starting point?
Why Are I4 / I7 / I8 Particularly Important?
This report most frequently refers to I4 / I7 / I8, as these three items best distinguish between a company that is "just a tool" and one that "truly controls the workflow."
Code
Plain Language Explanation
What This Report Frequently Asks
I4
Who Has the Authority to Make Final Decisions, Who Bears Formal Responsibility
For example, if taxes are filed incorrectly, product changes go wrong, or an audit occurs, who is ultimately responsible?
I7
Who Cleans Up the Mess After Something Goes Wrong
For example, if there are customer complaints, failed processes, or system errors, who compensates, who repairs, and who appeases?
I8
Where Do Users Default to Start Their Work
That is, the primary entry point, the first click, the default workflow starting point.
Therefore, when you see a company with strong I4 + I7 + I8, do not interpret it as merely having a "high framework score," but rather understand it as:
This company not only controls the entry point, but also bears responsibility, and furthermore, must step in to handle things when errors occur. Such companies are typically harder to bypass in the age of AI.
What Are P1 / P4 / P11?
These three are not scores, but rather three different company "archetypes."
Archetype
Plain Language Explanation
Representative Companies in this Report
P1
Control Layer Company: Does not necessarily bear the ultimate outcome itself, but already controls processes, permissions, collaboration, and execution paths.
Industrial Workflow Control Layer with Governance Capability
AI helps it deepen its control layer.
I2 + I3 + I4 Integrated Prototype
Scale and distribution are still inferior to INTU.
P1 Growth Alpha - Healthy
The sole purpose of this table is to first differentiate these four companies from being categorized as "the same type of software stock." All subsequent chapters essentially answer the same question:
At which layer of the software workflow are these four companies positioned, and is AI helping them deepen this layer, or is it circumventing it?
Core Judgement
The market continues to price INTU / ADBE / ADSK / PTC as "a family of high-profit, vertical SaaS companies under AI pressure," but the latest paradigm shift framework reveals that they actually occupy four completely different control point tiers:
INTU → Authority + Distribution Owner, which is an SME financial operating system with "both responsibility assumption and default distribution."
PTC → Operational Control Layer, which is a product lifecycle execution layer that "truly controls processes and governance."
ADSK → Workflow Default is moving towards the Control Layer, meaning "the default entry point is still in its hands, but the governance layer is still maturing."
ADBE → Legacy Workflow Platform Defending with AI, meaning "the legacy platform relies on AI to retain core users, but entry points have partially shifted outward."
Pricing these four companies using the same P/E language essentially forces four different assets into a single template. The task of this report is to analyze these four assets separately and then re-sort them.
Five Core Views
#
Core View
1
These four companies are not a homogenous group of assets; they represent four distinct control point tiers, corresponding to the P4 / P1 / P11→P1 / P11 archetypes, respectively.
2
INTU's strength is not merely in its "numerous features," but in the simultaneous establishment of responsibility assumption + anomaly backstop + default entry point; in framework language, this is an I4+I7+I8 triangular structure.
3
ADBE's AI fate is a schism: six business lines show an AIAS range from -9 to +13, spanning 22 grades; if assessed with a single company-wide AIAS, it would mistakenly project the pessimism of CC Consumer onto Document Cloud and GenStudio.
4
PTC is closer to the P1 control layer than ADSK, not because PTC is larger, but because PTC's I4 governance has incorporated the compliance stack of FDA / TÜV / AS9100; ADSK's BIM mandate is merely a client-side mandate, not a Revit-exclusive mandate.
5
The valuation language for these four companies must diverge: INTU should use an Authority multiple, PTC should use PEG + control-layer option, ADSK should use a platform-migration multiple, and ADBE should use a franchise-defense multiple. Using the same P/E anchor will consistently misallocate capital.
Glossary
Term
Actual Meaning in This Context
How to Understand It
Authority
Not just "the ability to act," but "accountability for consequences."
For example, who pays if tax filings are wrong, or who handles an audit.
Control Layer
The layer in the workflow that truly controls processes, permissions, auditing, and state changes.
Not a toolbar, but the "master switch."
Workflow Default
Where users default to starting their work.
The first click, the primary entry point.
AIAS
A diagnostic score that measures whether a business line is more likely to benefit, differentiate, or be eroded by AI impact.
Can be understood as a directional thermometer for "whether AI is a tailwind or a headwind for this line," not a final valuation conclusion.
Chapter 1: Applying This Framework to Four Companies: A Visual Introduction
1.1 What Three Questions This Chapter Addresses First
Question
Answer Provided in This Chapter
Why does the market always group these four companies together?
Because common views only consider growth, gross margin, and valuation, without dissecting business control points.
What exactly does this framework look at beyond the usual?
It examines who owns the context, who can execute, who bears responsibility, and who controls the entry point.
Why must we analyze by business line, not just the overall company?
Because AI's impact on different business lines within the same company can be entirely opposite.
1.2 Why the Market Puts These Four Companies in One Bucket
A market snapshot of the four companies on 2026-04-23 looks like this:
flowchart TD
subgraph "Common Market Tests"
A1[Is revenue growth still double-digit?] --> B[Apply a mature SaaS discount]
A2[Are gross margin/FCF still expanding?] --> B
A3[Do AI products constitute a new narrative?] --> B
A4[Is valuation cheap relative to historical levels?] --> B
end
B --> C[The same valuation template]
C --> D[Implicit: They are the same type of asset]
D -.-> E[But this assumption is incorrect]
style E fill:#fdd,stroke:#c00
The problem with this template isn't that it's wrong, but that it stops at financial commonalities and fails to capture differentiation in business control points. The impact of AI, for instance, affects Photoshop / QuickBooks / Revit / Windchill in entirely different ways; likewise, for high-gross-margin software, there are vast differences in who truly owns the I2 decision context / I3 execution / I4 authority / I8 entry point.
1.3 How This Framework Uncovers the True Structure of the Four Companies
The paradigm shift framework doesn't ask "does this company have AI" or "is this company impacted by AI"; it asks:
flowchart TB
subgraph "Five Questions That Truly Determine Revaluation in the AI Era"
Q1[Q1 — At which layer does the customer pay I1 Value Unit]
Q2[Q2 — Whose data accumulates the decision context I2 Decision Context]
Q3[Q3 — Who can truly trigger state changes I3 Execution Rights]
Q4[Q4 — Who bears compliance, audit, and anomaly responsibility I4 + I7]
Q5[Q5 — Whose door is the default entry for work I8 Entry Point]
end
Q1 & Q2 & Q3 & Q4 & Q5 --> Diag[Structural Diagnosis]
Diag --> D1[INTU leads in Q4 Q5]
Diag --> D2[PTC leads in Q2 Q3]
Diag --> D3[ADSK maintains Q5, Q4 is growing]
Diag --> D4[ADBE's Q5 partially shifts externally, Q4 is weakest]
style D1 fill:#c8e6c9
style D2 fill:#c8e6c9
style D3 fill:#fff9c4
style D4 fill:#ffcdd2
Intuition Trap: Simplifying AI enhancement and AI impact into unidirectional assumptions is the most common mistake. AI's true impact on a company depends on the interplay of the answers to these five questions:
If a company's I2 has accumulated historical data across entities and cycles, AI training will strengthen it further (INTU's GenOS is based on 860 million filings).
If a company's I4 bears compliance or audit responsibility, an LLM cannot directly replace it (IRS e-filer identity cannot be given to ChatGPT).
If a company's I8 is at the discovery layer, it is most vulnerable to being co-opted by general LLMs / new tools (the logic of Canva acquiring Express).
If a company genuinely triggers state changes in I3 (BOM modification / tax submission / construction drawing approval), tools may be replaceable, but the workflow continuity is hard to replace.
This is why it's essential to dissect by control points rather than label by AI tags.
The starting point of the paradigm shift framework is to dissect a company's value creation into 8 invariants (I1-I8). These are not financial metrics, but rather dimensions of business control points:
flowchart TB
subgraph "8 Invariants = Value Anatomy of a Software/Platform Company"
I1[I1 Value Unit Revenue Unit 11 Points]
I2[I2 Decision Context Decision Context 9 Points]
I3[I3 Execution Rights Execution Rights 10 Points]
I4[I4 Authority + Accountability Authority/Accountability 10 Points]
I5[I5 Budget Owner Budget Pocket 9 Points]
I6[I6 Incremental Value Capture Incremental Value Retention 9 Points]
I7[I7 Exception Ownership Exception Responsibility 7 Points]
I8[I8 Entry Point + Routing Entry Point & Routing 5 Points]
I5 --> I1
I2 --> I3
I3 --> I4
I6 --> I7
I8 --> I2
end
style I1 fill:#e3f2fd
style I5 fill:#e3f2fd
style I6 fill:#e3f2fd
style I2 fill:#fff3e0
style I3 fill:#fff3e0
style I4 fill:#fff3e0
style I7 fill:#f3e5f5
style I8 fill:#f3e5f5
Understanding Each Invariant in One Sentence:
Invariant
Common Question
Example — INTU Answer
Example — ADBE Answer
I1 Revenue Unit
What does the customer pay for?
Seat + Live expert + CK financial product commissions
Final draft creation / PDF signing / Content publishing
I4 Authority/Accountability
Who bears compliance and consequences?
IRS authorized e-filer, INTU responsible for tax filing errors
Almost none (not responsible for design flaws)
I5 Budget Pocket
From which layer is the budget spent?
Tax filing budget + SMB financial budget
Creative / Marketing / Legal PDF budget
I6 Incremental Value Retention
How much of every additional dollar falls to FCF?
32% FCF Margin
89% Gross Margin, 50% OPM
I7 Exception Responsibility
Who cleans up when problems arise?
Audit assistance, professional indemnity insurance
Customer handles it themselves
I8 Entry Point & Routing
Through whose gate does the workflow enter?
Tax season default entry point + CK year-round entry point
Professional creation entry point (but discovery shifts externally)
1.5 Archetype Library: Four Structures Corresponding to Four Companies
In the v1.0 Archetype Library, four companies correspond to fourdifferent archetypes:
graph TB
subgraph "v1.0 Archetype Library — Structures of Four Companies"
P4[P4 Compliance-Backed Authority Owner Typical Range 85-95]
P4 --> INTU[INTU Score 93 Broad Alpha]
P1[P1 Operational Control Layer Typical Range 72-82]
P1 --> PTC[PTC Score 74 Growth Alpha - Healthy]
P11[P11 Legacy Workflow Platform Defending with AI Typical Range 68-76]
P11 --> ADSK[ADSK Score 72 Growth Alpha - Low End]
P11 --> ADBE[ADBE Score 71-74 P11 Defensive Growth Variant]
end
style INTU fill:#c8e6c9,stroke:#2e7d32
style PTC fill:#bbdefb,stroke:#1565c0
style ADSK fill:#fff9c4,stroke:#f9a825
style ADBE fill:#ffccbc,stroke:#d84315
Key: Although ADSK and ADBE are both classified as P11, their positions differ — ADSK is a P11 → P1 migration path sample, ADBE is a pure P11 defensive sample. Chapters 3 and 4 of this report will dissect this difference: Their I4 / I8 / Stack Coherence have a structural gap of about 5 points and cannot be covered by the same label.
1.6 BSM: Why "Aggregate Scoring" Can Deceive You
BSM (Business Split Mechanism) is a mandatory discipline of the framework: any business line with revenue >5% of a company's total must be analyzed separately.
flowchart TD
Start[A company enters scoring] --> T1{Does I5 Budget Pocket cross categories?}
T1 -->|Yes| Split[BSM Required]
T1 -->|No| T2
T2{Does I1 PS or EE cross models?} -->|Yes| Split
T2 -->|No| T3
T3{Does I3 execution cross different workflows?} -->|Yes| Split
T3 -->|No| Single[Can be Single Table]
Split --> U7{Has divestiture been completed?}
U7 -->|Yes| Exclude[Divested business not included in active BSM Marked as A3 Spill historical annotation]
U7 -->|No| Include[Score based on report-date structure]
style Split fill:#ffe0b2
style Single fill:#e8f5e9
style Exclude fill:#f5f5f5
GBS (incl. Mailchimp) / Consumer (TurboTax) / CK / ProTax
For FY2026, the official consolidation merges Consumer+CK+ProTax into the "Consumer" segment, but BSM must revert to the original split to examine control points.
Kepware+ThingWorx have been divested, U7 exception applies; should no longer burden the main scoring.
Not performing BSM scoring is equivalent to saying "INTU as a whole = GBS's moat + CK's growth + Mailchimp's drag" averaged into a meaningless median.
1.7 Four Gates + Modifiers: Scoring Does Not Equal Conclusion
The framework requires each company to pass through four gates:
flowchart LR
Score["Original Base Score"] --> G1{"Structural Gate At least one C ≥0.8×max?"}
G1 -->|No| Fail1["Structural Hollow Score Not Counted"]
G1 -->|Yes| G2{"Economic Gate I1+I5+I6 ≥12?"}
G2 -->|No| Fail2["Economic Incoherence"]
G2 -->|Yes| G3{"Validation Gate At least 3 P2 or 1 P3 independent sources?"}
G3 -->|No| Fail3["Insufficient Evidence"]
G3 -->|Yes| G4["Sequencing Gate Good / Neutral / Bad"]
G4 --> Over["Overlay Modifiers"]
Over --> OAI["AI Asymmetry -8 ~ +8"]
Over --> OAP["AP / EP"]
Over --> ODEB["D/E/B"]
Over --> OStack["Stack Coherence"]
Over --> OWarn["Warnings Accountability-Thin / Legacy-Defending"]
OAI --> Final["Final Score + Alpha Type"]
OAP --> Final
ODEB --> Final
OStack --> Final
OWarn --> Final
style Final fill:#c8e6c9,stroke:#2e7d32
Scoring is not the conclusion; the mechanism is. This report requires a clear explanation for every score of every company: where the score comes from, why it isn't higher, and why it isn't lower.
Chapter 2: INTU — Not Tax Software, But an SMB Financial Operating System with Authority
Core Judgment: INTU's true identity is not a "vertical SaaS leader," but an **American SMB financial operating system that simultaneously possesses I4 authority, I7 exception and I8 distribution**. The combined scores of the other three companies in these three categories do not surpass INTU's individual score. This is the fundamental difference between P4 and P11, and the only true reason INTU deserves to be revalued.
2.1 Conclusions First
Item
Conclusion
What it most resembles now
SMB Financial Operating System with Accountability, not standalone tax software
What the market most easily misunderstands
Views INTU as a “tax-season revenue stock,” underestimating its year-round financial distribution and assumption of liability
Strongest Control Point
The I4 authority, I7 exception, and I8 distribution triangle together
What AI is more like for it
Accelerator. AI makes existing data and distribution more valuable, rather than directly replacing it
What this chapter aims to prove
The core reason INTU is not in the same bucket as the other three is not its growth rate, but its liability structure
2.2 Five-Layer Business Structure
While INTU will merge its segments into a single "Consumer" disclosure starting in FY2026, it structurally remains a five-layer business:
flowchart TB
subgraph "INTU Five-Layer Business (FY2025 Scope)"
SMB["Small Business & Self-Employed SSE - $11.1B, +18% Core Moat"]
SMB --> QBO["QuickBooks Online Ecosystem 7M+ Subscribers, 62-80% US SMB Share"]
SMB --> MC["Mailchimp ~$1.35B, ≈0% Growth Goodwill Impairment Risk"]
SMB --> IES["IES Mid-Market TAM $89B 18-Month Validation Window"]
Con["Consumer $4.9B, +10% Peak Season Q3 Jan-Apr"]
Con --> TTD["TurboTax DIY ~$2.9B, Low Single Digits 62% Market Share, 79% Retention"]
Con --> TTL["TurboTax Live ~$2.0B, +47% Cannibalizing Traditional CPAs"]
CK["Credit Karma $2.3B, +32% $8.1B Acquisition Has Paid Off"]
CK --> CKL["Lead Gen: Loans/Credit Cards/Insurance"]
CK --> CKD["150M+ Registrations, 37M MAU"]
Pro["ProTax $621M, +4% 60-65% OPM"]
Pro --> ProA["Lacerte / ProSeries"]
Pro --> ProB["700K+ Accountant Network Anchor Point"]
AI["GenOS + Intuit Assist Cross-Product Line AI Embeddings"]
end
SMB -.-> AI
Con -.-> AI
CK -.-> AI
Pro -.-> AI
style SMB fill:#c8e6c9
style CK fill:#e3f2fd
style Pro fill:#fff3e0
style TTL fill:#c8e6c9
style MC fill:#ffcdd2
2.3 I1 — What Customers Are Really Paying For
flowchart LR
subgraph "INTU's I1 is the Most Heterogeneous Among the Four"
AC["Access Layer Subscription / Seat"]
OC["Outcome Layer Tax Outcome / Loan Disbursement / Matching"]
AP["Authority Premium IRS e-filer + Audit Support + Error Insurance"]
DI["Distribution Premium CPA Network + CK Lead Gen"]
AC --> INTU_I1
OC --> INTU_I1
AP --> INTU_I1
DI --> INTU_I1
end
INTU_I1["INTU I1 = 9.5/11"]
style INTU_I1 fill:#c8e6c9,stroke:#2e7d32
style AP fill:#fff59d
style DI fill:#fff59d
Compared to the other three: ADBE/ADSK/PTC only have the Access layer (I1 = 8/11 soft cap triggered). Only INTU simultaneously has:
Outcome — CK earns commissions through loan leads; revenue is tied to whether the client **obtains a loan**.
Authority Premium — TurboTax Max Defend ($80) / Error Insurance / Compliance premium from IRS authorized e-filer status.
Distribution Premium — 46,000 CPA firms recommend QuickBooks at a 75% rate; this is not subscription revenue, but a distribution structure.
This is why INTU's I1 is 9.5/11, while the other three top out at 8/11: It transcends the soft cap of pure access.
2.4 I2 — Deepest Financial Context
graph TB
subgraph "INTU I2 — Cross-Entity Financial Historical Accumulation"
T[TurboTax 860M Historical Tax Filings]
Q[QuickBooks 8.9M+ SMB Ledgers Years of Transaction History]
C[Credit Karma 150M+ Credit Files 37M MAU Year-Round Engagement]
P[ProTax 700K+ Accountant Workflows]
M[Mailchimp SMB Marketing History In Integration]
T --> Ctx[Cross-Entity Financial Context]
Q --> Ctx
C --> Ctx
P --> Ctx
M --> Ctx
Ctx --> Use1[GenOS AI Training]
Ctx --> Use2[Product Recommendation Accuracy 60% → 78%]
Ctx --> Use3[NRR 108-112% Evidence]
Ctx --> Use4[High AI Migration Cost]
end
style Ctx fill:#c8e6c9,stroke:#2e7d32
style T fill:#fff9c4
style Q fill:#fff9c4
style C fill:#fff9c4
Why this category scores 8.5/9: No competitor simultaneously possesses a multi-year history across all four dimensions: **Tax + Accounting + Credit + Accountants**. Xero has accounting but no tax, H&R Block has tax but no year-round credit, NerdWallet has credit but no transaction flow. INTU's I2 is a true **cross-entity, cross-cycle closed loop**.
2.5 I4 + I7 — The True Chasm Between INTU and the Other Three
This subsection is one of the most important parts of the entire report, because it explains why INTU is P4 and the other three are not.
flowchart LR
subgraph INTU["INTU's Scope of Responsibility"]
I_REG["IRS Authorized e-filer Government Authorization Barrier"]
I_MAX["Max Defend Audit Defense Paid for and borne by INTU"]
I_ACC["Accuracy Guarantee Calculation errors compensated by INTU"]
I_IRS["Clients audited by IRS INTU dispatches EA/CPA to assist"]
I_REG --> I_CORE["Assumption of Real Responsibility and Consequences"]
I_MAX --> I_CORE
I_ACC --> I_CORE
I_IRS --> I_CORE
end
subgraph ADBE["ADBE's Scope of Responsibility"]
A_PD["Platform Availability"]
A_SEC["Data Security"]
A_CP["Copyright Compliance Firefly IP Indemnification"]
A_X["Incorrect design results Client is responsible"]
A_PD --> A_CORE["Primarily provides tools Limited liability assumption"]
A_SEC --> A_CORE
A_CP --> A_CORE
A_X --> A_CORE
end
subgraph ADSK["ADSK's Scope of Responsibility"]
D_PD["Platform Availability"]
D_V["Versions / Permissions / Usability"]
D_X["Engineering accidents Client is responsible"]
D_PD --> D_CORE["Primarily provides tools Does not assume outcome responsibility"]
D_V --> D_CORE
D_X --> D_CORE
end
subgraph PTC["PTC's Scope of Responsibility"]
P_PD["Platform Availability"]
P_TR["Codebeamer Certification TUV Trusted Tool"]
P_AU["Windchill Audit Trail"]
P_X["Product recall Client is responsible"]
P_PD --> P_CORE["Stronger compliance tools but outcome responsibility is still limited"]
P_TR --> P_CORE
P_AU --> P_CORE
P_X --> P_CORE
end
I_CORE --> GAP["INTU steps into the layer of responsibility on I4 + I7"]
A_CORE --> GAP
D_CORE --> GAP
P_CORE --> GAP
style I_REG fill:#c8e6c9
style I_MAX fill:#c8e6c9
style I_ACC fill:#c8e6c9
style I_IRS fill:#c8e6c9
style I_CORE fill:#c8e6c9,stroke:#2e7d32,stroke-width:2px
style A_X fill:#ffcdd2
style D_X fill:#ffcdd2
style P_X fill:#ffcdd2
style GAP fill:#fff9c4,stroke:#f9a825,stroke-width:2px
Quantification Comparison:
Company
I4 Authority/Responsibility
I7 Anomaly Bearing
I4 + I7 Total
I4+I7/combined-max
INTU
8/10
5.5/7
13.5
79%
PTC
6/10
3.5/7
9.5
56%
ADSK
5/10
2.5/7
7.5
44%
ADBE
4.5/10
2.5/7
7.0
41%
Conclusion: INTU's I4+I7 total is 42% higher than the second-ranked PTC. This is not a quantitative difference; it's a qualitative difference. INTU is truly **assuming responsibility**, while the other three are **providing tools**.
Why this difference is valuable:
In the AI era, tools will be commoditized, but **assuming responsibility** will be at a premium. LLMs can achieve 90% accuracy in PDF search, but an LLM cannot become an IRS e-filer.
The migration cost for tools is "learning a new interface." The migration cost for responsibility is "re-obtaining regulatory authorization + rebuilding distribution networks + re-purchasing actuarial insurance data."
The market's current premium for INTU (18x P/E) vs. ADBE (9.6x P/E) primarily prices in the I1 growth differential. It **has not yet fully priced in the structural difference of I4**.
2.6 I8 — Dual-Layer Entry Points of the Distribution Network
flowchart TB
subgraph "INTU's Entry Structure — Two Default Layers"
subgraph "B2C Entry"
C_T[Tax Season Q3 TurboTax Default]
C_CK[Year-round Credit Karma]
C_LIVE[High ARPC TT Live replaces CPA]
end
subgraph "B2B Entry"
B_QB[SMB Starting Point QuickBooks]
B_AP[Accountant Starting Point ProTax / ProConnect]
B_CPA[46K CPA Firms 75% recommend QBO]
end
C_T --> Flywheel[Data Flywheel I2 Accumulation]
C_CK --> Flywheel
B_QB --> Flywheel
B_AP --> Flywheel
B_CPA --> Flywheel
Flywheel --> Rev[I1 Revenue Mix]
Flywheel --> Aut[I4 Authority Signals]
end
style Flywheel fill:#c8e6c9,stroke:#2e7d32
Quantification:
TurboTax 62% federal e-file market share
QuickBooks 62-80% U.S. SMB market share
Credit Karma: 37M MAU
46,000 CPA firms, 75% recommend QuickBooks
Comparison: ADBE has creative entry points but discovery has shifted externally. ADSK has AECO entry points but the discovery layer is under AI threat. PTC has domain-specific multiple entry points but a small scope. Only INTU has default entry points simultaneously in both B2C (year-round + tax season) and B2B (SMB + accountants).
2.7 Why AI acts more as an accelerator than a substitute for INTU
flowchart LR
subgraph "AI Paradox — INTU Is a Net Beneficiary"
subgraph "Enhancer Direction (50%)"
E1[GenOS trained on 860M filings Generic LLMs cannot match]
E2[Intuit Assist reduces operational time by 30-40%]
E3[TT Live expert time -20% Annualized savings $90M]
E4[ARPC from $400 → $580 in 5 years]
end
subgraph "Dissolvent Direction (50%)"
D1[Xero JAX 97.5% auto reconciliation Test environment]
D2[IRS Direct File coverage expansion]
D3[2028 election is a binary risk]
D4[GPT-5 level models may cover medium complexity]
end
Net[Net Impact Assessment +4 Neutral Positive]
E1 --> Net
E2 --> Net
E3 --> Net
E4 --> Net
D1 --> Net
D2 --> Net
D3 --> Net
D4 --> Net
end
style Net fill:#fff9c4
style E3 fill:#c8e6c9
style E4 fill:#c8e6c9
style D2 fill:#ffcdd2
style D3 fill:#ffcdd2
Key Judgment: AI cannot directly replace TurboTax, because TurboTax's core value is not "tax calculation capability" (LLMs are already strong enough), but rather IRS authorization + audit defense + error insurance + historical migration costs. AI places 50% weight on the dissolvent side, but 50% weight on the enhancer side (especially TT Live human replacement), resulting in a net score of +4 (Neutral Positive).
2.8 INTU Main Table
Invariant
Score
Brief Rationale
I1
9.5/11
Access + Outcome (CK) + Authority premium + Distribution premium, breaking through access soft ceiling
I2
8.5/9
Multi-year history across four dimensions: tax/accounting/credit/accountant
I3
8/10
Tax filing / payroll processing / CK loan matching are all real state changes
I4
8/10
IRS e-filer government authorization + Max Defend + Accuracy Guarantee
Audit defense + error compensation + distribution liability
I8
4.5/5
B2C + B2B dual-layer default, across tax season/full year/accountant network
Base Score
60/70
—
+Stack Coherence
+2
Strong combination of I2+I3+I4 (PLTR-style)
+AI Asymmetry
+4
Neutral Positive
+Sequencing
+4
Good
+AP/EP
+10
10/10
+D/E/B
+3
Execution + CK expansion leg
+Warnings
-2
AI timing uncertainty
Total Score
91-93/100
P4 Broad Alpha
2.9 INTU Kill Switch
#
Condition
Current
Threshold
Impact
1
TurboTax market share collapse
62%
<55%
I4 structural downgrade, P4 → P11
2
Direct File relaunches and expands
Closed
>30% coverage after 2028 election
I1 structural pressure
3
Mailchimp impairment
$12B goodwill
FY26 10-K disclosure
Capital allocation confidence
4
CK growth persistently <15%
+32%
<15% for 2 quarters
Platform narrative fails
5
IES 18-month validation fails
Pending validation
FY27 Q2 review
Second curve fails
You’ve just finished the first 2 chapters of the free section
15 more deep-dive chapters are waiting to be unlocked
Including full financial analysis, competitive structure, valuation models, risk matrices, and other in-depth sections
72468
words of deep analysis
34
data tables
76
visual charts
17
chapters
Registration is completely free · Email verification only · No credit card required
🔒
Unlock this report
Invite 1 friend to register for direct access to this report, or use an available credit.
Full report unlocked!
Invite friends to register and earn unlock credits that can be used on any deep research report
Each friend who registers = 1 unlock credit
Chapter 3: ADBE — A Standard Sample of P11, and a Textbook Example of "AI Split Personality"
Core Judgment: ADBE is neither dying nor winning. It is **six completely different AI destinies** being compressed by the market into a single AIAS score. Separating these six lines reveals: **Creative Cloud Consumer is bleeding, but Document Cloud and GenStudio are gaining market share; Firefly's strategy has shifted from "building the strongest model" to "creating the best model supermarket."**
3.1 Key Takeaways of this Chapter
Item
Conclusion
What it most resembles now
A **legacy workflow platform using AI to defend its position**, not merely an AI victim
What the market most easily misinterprets
Viewing Adobe with a single overall score, ignoring that it is actually 6 business lines with completely different AI destinies
Strongest Control Point
I6 Economic engine and final delivery stage of professional workflows
Biggest Weakness
I8 Entry point has partially shifted externally, and I4 / I7 are weak
What this chapter aims to prove
Adobe's key challenge is not "whether AI works," but whether its revenue structure can complete its migration before weaker businesses are depleted
3.2 AI Split Personality — Six Business Line Heatmap
flowchart TB
subgraph "AI Destinies of ADBE's Six Business Lines (AIAS Score)"
CCP[CC Pro ~$9.5B, 40% AIAS +3 AI enhances stickiness]
CCC[CC Consumer/SMB ~$4.5B, 19% AIAS -9 Being eaten by Canva]
FF[Firefly ~$250M+, 1% AIAS +13 Model Supermarket]
DC[Document Cloud ~$3.5B, 15% AIAS +6 Biz Pro +16%]
EC[Experience Cloud ~$5.5B, 23% AIAS +5 GenStudio >$1B]
EX[Express ~$500M, 2% AIAS -1 Can't catch up with Canva]
end
style CCP fill:#c8e6c9
style CCC fill:#ffcdd2
style FF fill:#c8e6c9
style DC fill:#c8e6c9
style EC fill:#c8e6c9
style EX fill:#fff9c4
Key Data Points:
CC Pro: 62% of users call Firefly "essential"
CC Consumer: Canva 265M MAU >> Express 80M MAU
Firefly: ARR >$250M, QoQ +75%
Document Cloud: Business Pro +16% YoY
GenStudio: ARR >$1B, +30%, Top 50 clients 90% adopt AI-first
Structural Observation: Averaging the 22 AIAS scores (from -9 to +13) into an "overall company AIAS +0.42 red team adjusted" essentially **erases information**. The true diagnostic method is to **weight each business line and examine its AI destiny**, then assess whether the revenue structure shift can occur before the declining lines are exhausted — this is the correct way to approach the P11 split personality.
3.3 The Divergent AI Destinies of CC Pro vs. CC Consumer
graph LR
subgraph "Why CC Pro Lives, While CC Consumer Dies"
CCP1["CC Pro Core Selling Points"]
CCP1 --> CCPA[Professional creative workflow Dynamic Link across products]
CCP1 --> CCPB[Firefly embedded in PS/PR/AE 2-hour cutout becomes 10 seconds]
CCP1 --> CCPC[62% of users call Firefly 'essential']
CCPA & CCPB & CCPC --> CCPRes[Increased stickiness but seat growth stagnates]
CCC1["CC Consumer Core Selling Points"]
CCC1 --> CCCA["'Good enough' lightweight creation"]
CCC1 --> CCCB[$54.99/month vs Canva $12.99/month 4.2x price difference]
CCC1 --> CCCC[Canva Magic Layers one-step image decomposition]
CCCA & CCCB & CCCC --> CCCRes[Structural churn AIAS -9]
end
style CCPRes fill:#c8e6c9
style CCCRes fill:#ffcdd2
This chart explains the true meaning of the P11 Defensive Growth Variant — the key is to differentiate "what to defend / what not to defend / what to attack":
Defend: CC Pro professional creation + Document Cloud enterprise PDF + GenStudio content supply chain
Do not defend / Concede: CC Consumer / Express → Let Canva take over; Adobe is **strategically retreating** from the individual creator market
Attack: Firefly model supermarket + Experience Cloud agentic automation
3.4 I1-I8 Master Table + Mechanisms
flowchart TB
subgraph "ADBE 8 Invariant Diagnosis"
I1A["I1 = 8/11 Pure access soft cap CC/DC subscriptions + GenStudio ARR"]
I2A["I2 = 7/9 PSD/AI format standard 42% share but discovery shift erodes context value"]
I3A["I3 = 7/10 Final creative drafts + PDF signing but Canva / Figma penetrate execution"]
I4A["I4 = 4.5/10 IP compensation is the only true authority everything else is tooling"]
I5A["I5 = 6/9 Creative + Marketing + Legal PDF budgets multiple pockets but not a mandate"]
I6A["I6 = 8/9 89% Gross Margin, 48-50% OPM Strongest economic engine"]
I7A["I7 = 2.5/7 No liability for design errors"]
I8A["I8 = 2.5/5 Discovery has shifted externally only completion entry point remains"]
end
I1A --> Base["Core Score 45.5/70"]
I2A --> Base
I3A --> Base
I4A --> Base
I5A --> Base
I6A --> Base
I7A --> Base
I8A --> Base
Base --> Mods["+AI Asymmetry Split Personality Weighted +2 +AP/EP 10/10 +Sequencing Neutral +3 +Stack Coherence 0 Weak +Warnings Legacy-Defending"]
Mods --> Total["Total Score 71-74/100"]
style I6A fill:#c8e6c9
style I8A fill:#ffcdd2
style I4A fill:#ffcdd2
style Total fill:#fff9c4
3.5 Strategic Significance of Firefly's "Model Supermarket" Strategy
flowchart LR
subgraph "Firefly's Strategy Shifted from 'Building the Strongest Model' to 'Creating the Best Supermarket'"
ADB["Adobe Photoshop"]
ADB --> F["Firefly In-house"]
ADB --> G["Google Gemini 2.5"]
ADB --> B["Black Forest Labs FLUX"]
ADB --> M["Midjourney Integration"]
ADB --> R["Runway Gen-4.5 Premiere Pro"]
F --> W["Workflow Embedding Layer"]
G --> W
B --> W
M --> W
R --> W
W --> P["Professional Workflow Lock-in"]
W --> IP["Firefly IP Indemnification Protection"]
W --> E["Enterprise Compliance"]
end
style W fill:#c8e6c9,stroke:#2e7d32
style P fill:#fff9c4
style IP fill:#fff9c4
style E fill:#fff9c4
Core Insight: If Midjourney releases a better model tomorrow, Adobe only needs to integrate it in the next update; models are commodities, workflows are infrastructure. This is Adobe's true defense in I3 + I8 – not contending "whose model is best," but contending "who owns the default starting and ending points of professional creative workflows."
3.6 Why ADBE's I8 is the Weakest Among the Four Companies
graph TB
subgraph "Discovery Shift Outward — Adobe's Structural Blood Loss"
U[User wants to create marketing materials]
U --> U1[Old Path]
U1 --> U1A[Open Photoshop / Illustrator]
U --> U2[New Path a]
U2 --> U2A[ChatGPT / Claude Generate Draft]
U2A --> U2B[Direct Publish or Simple Adjustment]
U --> U3[New Path b]
U3 --> U3A[Canva Magic Studio One-stop]
U3A --> U3B[Publish]
U --> U4[New Path c]
U4 --> U4A[Midjourney / DALL-E Draft]
U4A --> U4B[Figma Make Edit]
end
U1A --> Adobe[Adobe Gets Entry Point]
U2B -.-> Adobe
U3B -.-> Adobe
U4B -.-> Adobe
style U1A fill:#c8e6c9
style U2B fill:#ffcdd2
style U3B fill:#ffcdd2
style U4B fill:#ffcdd2
Quantification: Canva 265M MAU vs Express 80M MAU; Midjourney is estimated to have 20M+ active users, Runway several million. Adobe has lost significant traffic at the "first click of work" step. This is the core reason why I8 dropped from ADSK's 4/5 to ADBE's 2.5/5.
3.7 ADBE Master Table + Differentiating Points
Invariant
Score
Relative to INTU
Relative to ADSK
Relative to PTC
I1
8/11
1.5 notches lower
Flat
Flat
I2
7/9
1.5 notches lower
Flat (for Pro)
Flat
I3
7/10
1 notch lower
0.5 notches lower
1 notch lower
I4
4.5/10
3.5 notches lower
0.5 notches lower
1.5 notches lower
I5
6/9
2 notches lower
1 notch lower
1.5 notches lower
I6
8/9
Flat
Flat
Flat
I7
2.5/7
3 notches lower
Flat
1 notch lower
I8
2.5/5
2 notches lower
1.5 notches lower
1.5 notches lower
Base
45.5/70
vs INTU 60, 14.5 lower
vs ADSK 49.5, 4 lower
vs PTC 53, 7.5 lower
Structural Diagnosis: ADBE is flat in I6 (economic engine equally strong), but is entirely weaker than the other three companies in I4 / I7 / I8. This is a typical symptom of P11 — the economic engine steps down before the control points, with franchise quality supporting the P/E.
3.8 ADBE Kill Switch
#
Condition
Current
Threshold
Impact
1
CC Consumer churn accelerates
Steady state
Single quarter >8% churn
I8 + I2 further collapse
2
Firefly ARR growth falls below 30%
QoQ +75%
2 consecutive quarters <30%
AI narrative fails
3
GenStudio ARR stalls at $1B, no expansion
>$1B +30%
FY28 still <$2B
P11 → P6 defensive rather than offensive
4
Canva launches enterprise version impacting DX
—
If Canva launches an enterprise offering with >$500M ARR
DX side begins to lose revenue/market share
5
DOJ settlement escalates to structural reform
$150M
Forced unbundling of subscription pricing
Brand signal turns negative
Chapter 4: ADSK — The King of Workflow Default, Moving Up the Control Layer
Core Judgment: Both ADSK and ADBE are categorized as P11, but they are not in the same P11 position. ADBE is a pure defensive P11 sample (discovery has shifted outward), while ADSK is a sample on the P11→P1 migration path (discovery is still retained, and authority is slowly emerging). This structural gap of approximately 5 points, if covered by a single "P11 defensive growth" label, would lead to misaligned investment judgments. This chapter will clarify the evidence and mechanisms of this gap.
4.1 This Chapter's Conclusions First
Item
Conclusion
What it most resembles now
Default design workflow platform, moving from P11 to P1
What the market is most likely to misinterpret
Categorizing ADSK and ADBE together as “legacy software under AI pressure”
Strongest control points
I8 Default entry + I3 Execution authority, especially in AECO / Revit / BIM workflows
Biggest weakness
I4 is not yet hard authority, more like slowly emerging
What this chapter aims to prove
ADSK's value is not just the Revit moat, but that it still occupies the default starting point for work
Billings +30% shows active new subscriptions but with transition noise
4.3 BIM Mandate — Umbrella or Misunderstood?
flowchart LR
subgraph "True Structure of BIM Mandate"
subgraph "What is Mandated"
M1["20+ countries require BIM"]
M1 --> M2["UK/Germany/Singapore Mature Markets Mandate Clear"]
M1 --> M3["France/Spain/Nordics In Progress"]
M1 --> M4["China/India Emerging Demo Projects Only"]
end
subgraph "What is Not Mandated"
N1["Mandate requires BIM tools"]
N1 --> N2["Does not require Revit proprietary format"]
N1 --> N3["If moving to IFC open standard ArchiCAD/Allplan/Bentley also benefit"]
N1 --> N4["Revit Share Mature Markets >60%, Emerging <40%"]
end
end
M1 -.-> Conclusion["I5 Score 7/9 High, but not Frozen"]
N1 -.-> Conclusion
style Conclusion fill:#fff9c4
style M2 fill:#c8e6c9
style N3 fill:#ffcdd2
Key Insight: The mandate is derived protection, not direct protection. The government mandates BIM workflows, not Revit products. This makes ADSK's I5 one notch stronger than ADBE's but weaker than PTC's Codebeamer FDA-21-CFR-Part-11 / AS9100 compliance stack — because PTC handles actual tooling-for-compliance, while ADSK handles only tooling-for-a-mandate-that-requires-BIM. This distinction between derived vs. direct is key to understanding why the BIM mandate is only a high-probability moat, not a definitive one.
graph LR
subgraph "ADSK's Upgrade Path"
Now["Current State P11 + Upgrade Prototype"]
Now --> A["APS + MCP Platform as AI backend"]
Now --> B["Assistant in Revit Tech Preview"]
Now --> C["Make / Construction Cloud Faster than Design"]
Now --> D["Fusion mid-market MFG"]
A & B & C & D --> Target["Potential End State P1 Operational Control Layer"]
Target --> Cond1["I3 +0.5 if Assistant launches GA"]
Target --> Cond2["I4 +1 if takes on more governance"]
Target --> Cond3["I8 +0.5 if APS becomes a true AI backend"]
Target --> Cond4["Stack Coherence +1 if unified"]
Cond1 & Cond2 & Cond3 & Cond4 --> Upside["Potential Upside Revision +3 ~ +5 points Approaching PTC 74-76"]
end
style Now fill:#fff9c4
style Target fill:#c8e6c9
style Upside fill:#c8e6c9
Key Evidence:
APS updated on 2025-12-07, providing data APIs + MCP servers + marketplace + usage model for agentic AI
Revit Assistant Tech Preview launched on 2026-04-22, capable of querying models / generating schedules / automating documentation
4.6 Why ADSK is "More Stable in the Same Tier" than ADBE
flowchart LR
subgraph "Both P11, Divergent Fates"
direction TB
subgraph "ADBE's P11"
A1[Discovery shifted outwards ★★★]
A2[AI impact on the consumer end]
A3[Canva/Figma genuinely eroding market share]
A4[Weak Stack Coherence]
end
subgraph "ADSK's P11"
D1[Discovery largely retained ★]
D2[AI growing within AECO first]
D3[AutoCAD drafting under pressure but no alternative]
D4[Stack Coherence partial +1]
end
end
A1 & A2 & A3 & A4 --> AC[ADBE I8 = 2.5/5 Needs to maintain completion]
D1 & D2 & D3 & D4 --> DC[ADSK I8 = 4/5 Still holds initiation]
style AC fill:#ffcdd2
style DC fill:#c8e6c9
4.7 ADSK Kill Switch
#
Condition
Current
Threshold
Impact
1
Revit BIM Share
63.5%
<55%
I3+I2 Structural downward revision
2
BIM mandate shifts to IFC mainstream
Not occurred
3 major markets officially support IFC
I5 Decreases from 7 to 5
3
AutoCAD seat YoY decline
Steady state
2 consecutive quarters >5%
I8 Decreases from 4 to 2, AI Asymmetry turns negative
4
AECO Growth Rate
+11% (down from +15%)
<8%
I5 + I8 Linked downward revision
5
MFG Fusion vs PTC Creo Share
Parity
Lags by 10pp+
MFG segment loses momentum
Chapter 5: PTC — The Industrial Software Most Resembling a "True Control Layer" Among the Four Companies
Core Assessment: PTC is not a patchwork of industrial software, not merely a CAD company, nor solely a PLM subscription provider. Post the divestment of Kepware/ThingWorx, it is converging PLM + ALM + SLM + cloud CAD into an Intelligent Product Lifecycle Layer. This is the only company among the four where the primary archetype is P1 rather than P11. Owner Economics are the cleanest (SBC 4.8%), and I4 has already incorporated the governance stack of TÜV Trusted Tool and FDA 21 CFR Part 11.
5.1 Key Takeaways for This Chapter
Item
Conclusion
What it most resembles now
Industrial workflow control layer with governance capabilities, not a CAD patchwork
What the market most easily misinterprets
Only viewing PTC as an industrial software portfolio, failing to see its integration at the lifecycle governance layer
Strongest Control Point
I2 + I3 + I4 most comprehensively integrated, especially product change and compliance processes
Biggest Shortcoming
Scale and default entry weaker than INTU, not yet Broad Alpha
What this chapter aims to prove
PTC is closer to a true control layer than ADSK; the key is not scale but depth of governance
5.2 Intelligent Product Lifecycle — A Unified Control Layer Across Design/Change/Service
SBC/Revenue 4.8% (Lowest among the four, half of ADSK's 10.9%)
FCF $857M, FY26 Guidance $850M (excl. divested)
2026-03-16 Kepware+ThingWorx Divestment completed, Net Debt/EBITDA Decreases from 2.28x to 1.05x
5.3 BSM Structure Comparison Before and After IoT Divestment
flowchart LR
subgraph "Before Divestment (FY2025)"
B_CAD["CAD ~35%"]
B_PLM["PLM ~40%"]
B_ALM["ALM/Codebeamer ~10%"]
B_SLM["SLM/ServiceMax ~10%"]
B_IoT["IoT ~5-8% ThingWorx/Kepware"]
end
subgraph "After Divestment (FY2026)"
A_CAD["CAD 38%"]
A_PLM["PLM 62% Incl. ALM+SLM"]
end
B_IoT -.->|A3 Spill U7 Exception| Drop["Not included in active BSM"]
B_CAD --> A_CAD
B_PLM --> A_PLM
B_ALM --> A_PLM
B_SLM --> A_PLM
A_CAD --> P11["P11 Attribute 38%"]
A_PLM --> P1["P1 Attribute 62%"]
style Drop fill:#eeeeee
style P1 fill:#c8e6c9
style P11 fill:#fff9c4
Key Observation: The true value of the IoT divestment is not a "0.5pp increase in growth rate," but rather the **purification of the core structure** — the PLM family becomes the 62% core, with P1 attributes overshadowing P11. This is why one cannot solely judge divestment value by the ARR difference before and after (only 50bp); the real change is a **shift in archetype focus**, which has a far greater impact on valuation language selection than 50bp ARR.
5.4 Windchill — Mechanisms of Governed Execution
sequenceDiagram
participant Eng as Engineer
participant CAD as Creo/Onshape
participant WC as Windchill
participant Qua as Quality Department
participant Reg as Regulatory Audit
Eng->>CAD: Modify Part Design
CAD->>WC: Write New BOM Version
WC->>WC: Trigger ECO Process
WC->>Qua: Approval Request
Qua->>WC: Approve / Reject
Note over WC: All Changes auditable trail
WC->>Eng: Release to Manufacturing
WC->>Reg: FDA 21 CFR Part 11 AS9100 Audit Records
Reg-->>WC: Trusted Tool Certification
Why this is governed execution, not just a tool:
Changes are not suggestions, but actual state modifications: BOM / part master / ECO in Windchill is the single source of truth
Embedded Audit Stack: TÜV certified Codebeamer as a Trusted Tool, meeting IEC 62304 / ISO 26262 / FDA 21 CFR Part 11
BMW Case Study (2026-04-01): BMW Group's enterprise-level standardization of Codebeamer illustrates that "governed requirements engineering" has been standardized within large clients.
5.5 I4 — Where PTC Excels Over ADSK
graph TB
subgraph "Four-tier Gradient of I4 Authority"
L1[Level 1: Tool Layer Provides Functionality]
L2[Level 2: Tooling for Compliance Provides Audit Tools]
L3[Level 3: Derived Compliance Users must use you due to regulations]
L4[Level 4: Direct Authority You bear consequential responsibility]
ADB["ADBE"] --> L1
ADB -.-> |"IP Indemnification Firefly"| L2
ADSK["ADSK"] --> L2
ADSK --> |"BIM mandate client-side derived"| L3
PTC["PTC"] --> L2
PTC --> |"FDA 21 CFR Part 11 client derived TÜV Trusted Tool Third-Party Certification"| L3
INTU["INTU"] --> L3
INTU --> |"IRS e-filer Authorization Max Defend Indemnification Accuracy Guarantee"| L4
end
style L1 fill:#ffcdd2
style L2 fill:#fff9c4
style L3 fill:#c8e6c9
style L4 fill:#2e7d32,color:#fff
Quantification:
Company
I4 Level Position
I4 Score
ADBE
L1 + Minor L2
4.5/10
ADSK
L2 + Slight L3
5/10
PTC
L2 + L3 + Third-party Certification
6/10
INTU
L3 + L4
8/10
5.6 I6 Owner Economics — PTC is the Cleanest Among the Four
flowchart LR
subgraph "SBC/Revenue Comparison (FY25)"
P[PTC 4.8%]
A[ADSK 10.9%]
AD[ADBE ~10-11%]
IN[INTU 10.4%]
end
P -.-> PE[Owner PE ≈ Standard PE]
A -.-> AE[Owner PE 37x vs Std 19x 2x Difference]
AD -.-> AdE[Owner PE Expansion ~30%]
IN -.-> InE[Owner PE Expansion ~30%]
style P fill:#c8e6c9
style PE fill:#c8e6c9
style A fill:#ffcdd2
style AE fill:#ffcdd2
Structural Implications: PTC's Non-GAAP OPM of 48% is almost exactly the true Owner OPM. The Non-GAAP OPMs of the other three companies need to be discounted for SBC. This is why PTC's FWD PE of 19.4x is not considered cheap — its "Standard PE" is essentially its "Owner PE".
Chapter 6: Cross-Company Comparison of Four Companies — Placing the 8 Invariants on the Same Table
6.1 How to Read This Chapter Most Quickly
If you have already read the previous four chapters, the purpose of this chapter is to bring all judgments back to the same table. If you don't have time to read the full text, then focus on these three tables:
6.2 — Overall Table of 8 Invariants for Four Companies
Key Insight: Treating ADBE as a single score would overestimate the true risk. The worst of its six business lines is -9, the best is +13, with a weighted average of +0.42, which is the **split entity's pivot**; the investment implication depends on whether the absolute scale of GenStudio / DC / Firefly can shift revenue mix before CC Consumer collapses.
6.5 Sequencing Gate Comparison
flowchart TB
subgraph "Four States of the Sequencing Gate"
direction LR
G[Good — Craftsmanship precedes pricing +4]
N[Neutral — No obvious mismatch +3]
IN[Industry-Neutral — Standard for the industry +2]
B[Bad — Pricing precedes craftsmanship -2 ~ 0]
end
INTU[INTU] --> G
PTC[PTC] --> N
ADSK[ADSK] --> N
ADBE[ADBE] --> N
style G fill:#2e7d32,color:#fff
style B fill:#c62828,color:#fff
style INTU fill:#c8e6c9
Why INTU is Good:
I1 vs I6: Outcome + Authority premium has been truly monetized in CK/TT Live, not just a narrative.
I8 vs I5: Distribution (CPA network) has brought in B2B budget, not a mere story.
I3 vs I4: Authority and Execution are strengthening synchronously.
Why the other three are Neutral and not Good: All have a "craftsmanship stronger than pricing" structure (high I6), but **pricing has not truly monetized a new level**. ADBE has a GenStudio prototype but only $1B, ADSK has APS/Flex but it remains marginal, PTC has Onshape+Codebeamer but its CAD leg is still P11.
6.6 Budget Pocket Quality Ranking
graph LR
subgraph "I5 Quality Gradient"
F1[Frozen pocket Regulatory/physically irreplaceable]
F2[Structural pocket Industry standard-backed]
F3[Professional pocket High value but replaceable]
F4[General pocket Regular IT budget item]
end
INTU[INTU 8/9] --> F1
PTC[PTC 7.5/9] --> F2
ADSK[ADSK 7/9] --> F2
ADBE[ADBE 6/9] --> F3
ADBE --> F4
style INTU fill:#c8e6c9
style PTC fill:#fff9c4
style ADSK fill:#fff9c4
style ADBE fill:#ffcdd2
6.7 AP / EP / D / E / B Comparison
Dimension
INTU
ADBE
ADSK
PTC
AP (Adoption Proof)
5/5
5/5
5/5
5/5
EP (Economic Proof)
5/5
5/5
5/5
5/5
D (Depth)
3/3
2/3
2/3
3/3
E (Expansion)
3/3
2/3
2/3
2/3
B (Bridge)
3/3
2/3
2/3
2/3
Stack Coherence
+2 strong
0
+1 partial
+1 partial
Burden
0
0
0
0
Legacy-Defending
No
Yes
Yes
Partial
Chapter 7: Valuation Language Must Follow Business Control Points
Key Takeaway: The four companies occupy different tiers in terms of "new control points," and forcing the use of the same P/E language is equivalent to comparing four different types of errors. This chapter provides each company with a **valuation anchor + fair multiple range + adjustment rationale**.
7.1 Why the Same P/E Can No Longer Be Used
flowchart LR
subgraph "Systemic Errors of the Old P/E Language"
PE["Unified P/E Anchor"]
PE --> E1["For INTU Ignores authority premium Result: Undervalues 15-25%"]
PE --> E2["For ADBE Ignores split entity Result: May undervalue or overvalue Depends on DC/GenStudio realization"]
PE --> E3["For ADSK Ignores platform uplift optionality Result: Slightly undervalues 5-10%"]
PE --> E4["For PTC Ignores Owner Economics cleanliness Result: Owner P/E 19x is actually not expensive"]
end
style E1 fill:#c8e6c9
style E2 fill:#fff9c4
style E3 fill:#fff9c4
style E4 fill:#c8e6c9
7.2 INTU's Valuation Language — Authority Owner Multiple
Valuation Anchor: Benchmark INTU against an authority owner of the caliber of FICO / Moody's / MSCI, rather than a software leader of the caliber of CRM / ADBE.
flowchart TB
subgraph "INTU Valuation Three Layers"
L1[Core Tools Revenue SSE + Consumer + ProTax PE 18-22x]
L2[Authority Premium TT Max Defend + IRS Authorization +25% premium]
L3[Distribution Premium CPA Network + CK Lead Gen +15% premium]
L1 --> M[Multiple 25-30x FICO Range]
L2 --> M
L3 --> M
M --> V[SOTP Midpoint $490 v3.0 Report Confirmed]
M --> Range[Reasonable Range $480-550 Slightly Bullish 10-20% vs. Current]
end
style M fill:#c8e6c9
style V fill:#fff9c4
7.3 ADBE's Valuation Language — Franchise Defense Multiple
Valuation Anchor: ADBE should not be valued as "AI creative software"; it should be valued in layers based on "legacy franchise quality + AI nascent option."
flowchart TB
subgraph "ADBE Valuation Layers"
CORE["Core Franchise CC Pro + Document Cloud Accounts for 55% of revenue"]
CORE --> CMul["PE 12-16x Mature Franchise"]
RISK["Risk Franchise CC Consumer + Express Accounts for 21% of revenue"]
RISK --> RMul["PE 8-10x AI Risk Discount"]
OPT["Option Franchise Firefly + GenStudio + Experience Accounts for 24% of revenue"]
OPT --> OMul["PE 20-30x Option Premium"]
CMul --> W["Weighted PE 14-18x Midpoint"]
RMul --> W
OMul --> W
end
style CORE fill:#c8e6c9
style OPT fill:#fff9c4
style RISK fill:#ffcdd2
style W fill:#fff9c4
Key Implication: Current 9.6x PE might be cheap, but the degree of cheapness depends on whether GenStudio can reach $2B by FY28 (management's target) — this is a CQ2 (whether the central axis of the split entity can lean towards the Option side).
7.4 ADSK's Valuation Language — Platform Migration Multiple
Valuation Anchor: ADSK should be valued by "strong workflow default franchise + P1 migration option," not purely by CAD seat.
flowchart LR
subgraph "ADSK Valuation Dual Scenarios"
S1["Scenario A: Single Engine Mature AECO Growth Continues to Decline MFG Lags PTC"]
S1 --> V1["Fair Value $190 PE 16-18x"]
S2["Scenario B: Multi-Engine Growth Re-accelerates APS+Assistant Successful MFG+Water Complements AECO"]
S2 --> V2["Fair Value $300 PE 22-24x"]
S1 -.-> R["Midpoint $245-260 Current $247.57 Watch the Lower Bound"]
S2 -.-> R
end
style V1 fill:#ffcdd2
style V2 fill:#c8e6c9
style R fill:#fff9c4
7.5 PTC's Valuation Language — PEG + Control Layer Option
Valuation Anchor: PTC's Non-GAAP PE is already approximately equal to Owner PE, so 19.4x seems reasonable — but the market has not priced in the P1 control layer option.
flowchart TB
subgraph "PTC Valuation = Base + Optionality"
Base[Base Case ARR 8-9% Perpetual FY2026 FCF $850M PEG 2.3x Consistent with ADSK]
Base --> BV[Fair Value $145-155 Current $140.60 ≈ Neutral]
Opt[Optionality P1 Deepening +2~+4 points]
Opt --> OV[If Realized +10-20%]
Opt2[Optionality Onshape Becomes Cloud Control Surface +2~+3 points]
Opt2 --> OV2[If Realized +5-15%]
Base --> Total[Reasonable Range $140-180]
Opt --> Total
Opt2 --> Total
end
style Total fill:#fff9c4
7.6 Comparison Table of Four Companies' Valuation Languages
Company
Valuation Anchor
Reasonable PE Range
Key Optionality
Current PE vs. Anchor Position
INTU
Authority Owner
25-30x
CK/IES Second Curve
18x → 15-25% Undervalued
ADBE
Franchise Defense
14-18x Weighted
GenStudio $2B Milestone
9.6x → Possibly Undervalued, Depends on Execution
ADSK
Platform Migration
19-24x
APS/Assistant Success
19x → Watch the Lower Bound
PTC
PEG + Control Layer Option
19-24x
P1 Deepening
19.4x → Base Reasonable, Optionality Not Priced In
Chapter 8: Five Most Easily Misjudged Things
8.1 Misjudgment 1 — "INTU is just tax software; it will be disrupted by Direct File and AI tax filing"
flowchart LR
subgraph "True Structure of the Direct File Threat"
DF["IRS Direct File"]
DF --> W["Will TurboTax be disrupted?"]
W -->|2026| NO1["Already Closed No Short-Term Threat"]
W -->|2028 Election| Q1["Democrats Win: Potential Expansion"]
Q1 --> P1a["TAM Compression 10-20%"]
W -->|Long-Term| Q2["AI Capabilities Improve GPT-5 Level Models"]
Q2 --> P2["Simple Tax Filing Could Be Free"]
NO1 -.-> FC["But TT Live +47% Is Eroding the CPA Market"]
P1a -.-> FC
P2 -.-> FC
FC --> Real["Real Risk: TT Shrinks 20-30% But CK + SSE Platforms Can Compensate"]
end
style Real fill:#fff9c4
Counter-Evidence: TurboTax accounts for 35-40% of INTU's total revenue; even if TT revenue decreases by 30%, the overall revenue impact is approximately -10-12%. CK +32% + SSE +18% can compensate within 2-3 years.
8.2 Misjudgment 2 — "ADBE's moat has been breached by AI"
graph LR
subgraph "Layered Impact of AI on ADBE"
I["AI Impact"]
I --> X1["Discovery takes away Authenticity"]
I --> X2["CC Consumer Eaten by Canva (Actual Impact)"]
I --> X3["CC Pro Professional Workflow AI Enhances Stickiness"]
I --> X4["Document Cloud AI Makes PDF More Critical"]
I --> X5["GenStudio Enterprise Content Governance AI Creates New Markets"]
end
X1 -.->|True| CON1["- Lacks a discovery entry point"]
X2 -.->|True| CON2["- 19% of revenue is bleeding"]
X3 -.->|False| CON3["+ Professionals still hold ground"]
X4 -.->|False| CON4["+ 15% is the fastest revenue growth"]
X5 -.->|False| CON5["+ $1B ARR nascent stage"]
style CON1 fill:#ffcdd2
style CON2 fill:#ffcdd2
style CON3 fill:#c8e6c9
style CON4 fill:#c8e6c9
style CON5 fill:#c8e6c9
Counter-evidence: DC +16%, GenStudio >$1B +30%, Firefly >$250M QoQ+75%. The narrative that "AI breaks Adobe" only holds true for 21% of revenue; 79% of revenue is benefiting or stable.
8.3 Misjudgment 3 — "ADSK's BIM mandate is a permanent moat"
flowchart TB
M["BIM Mandate Moat"]
M --> L1["Guarantee: BIM demand is eternal"]
M --> L2["Not guaranteed: Revit must be used"]
L2 --> IFC["If IFC open standard becomes mainstream"]
IFC --> C1["ArchiCAD benefits"]
IFC --> C2["Allplan benefits"]
IFC --> C3["Bentley benefits"]
IFC --> C4["Revit share 55→45%"]
C1 & C2 & C3 & C4 --> R["I5 drops from 7 to 5 ADSK total score -7~-10"]
style L1 fill:#c8e6c9
style L2 fill:#fff9c4
style R fill:#ffcdd2
Actual Judgment: The mandate is a high-probability moat (80%), not a certainty moat. In mature markets, Revit is stable at 60%+, while in emerging markets (China/India), Revit <40% has real room for alternatives.
8.4 Misjudgment 4 — "PTC is a patchwork of industrial software assets"
flowchart TB
subgraph "Patchwork Theory vs. Control Layer Theory"
PB["Patchwork Theory"]
PB --> PB1["CAD weaker than DSY"]
PB --> PB2["PLM weaker than Siemens Teamcenter"]
PB --> PB3["ALM is niche"]
PB --> PB4["SLM merged into obscurity"]
PB --> PB_C["Conclusion: PE 15-18x is reasonable"]
CL["Control Layer Theory"]
CL --> CL1["Windchill is the true system of record for BOM/ECO"]
CL --> CL2["Codebeamer TÜV certified"]
CL --> CL3["ServiceMax entitlements engine"]
CL --> CL4["Onshape cloud-native CAD incremental"]
CL --> CL_C["Conclusion: PE 19-24x is reasonable Options not priced in"]
end
PB_C -.-> R["Current 19.4x PE"]
CL_C -.-> R
R --> JUDG["Judgment depends on whether the governed action layer materializes within 2-3 years"]
style JUDG fill:#fff9c4
8.5 Misjudgment 5 — "All four companies are impacted by AI simultaneously"
graph TB
AI["AI Impact"]
AI --> T1["Discovery moves downmarket All four affected"]
AI --> T2["Orchestration moves upmarket Four companies benefit differently"]
AI --> T3["Pure access is compressed All four affected"]
AI --> T4["Authority is revalued Biggest difference among the four"]
T4 --> IN["INTU benefits most"]
T4 --> PT["PTC second"]
T4 --> AS["ADSK third"]
T4 --> AD["ADBE least"]
style IN fill:#c8e6c9
style PT fill:#c8e6c9
style AS fill:#fff9c4
style AD fill:#ffcdd2
Actual Implication: The net impact of AI on the four companies is in different directions. Whoever takes on more responsibility will benefit more from the revaluation of authority in the AI era.
Q3 FY26, will tax season data continue to demonstrate the advantages of distribution and the authority layer.
INTU
2026-08
Q4 FY26 + FY27 guidance, observe full-year continuity after the tax season.
INTU
2026-09
FY26 10-K, focus on Mailchimp and segment disclosure definitions.
INTU
2027-05
Q3 FY27, re-verify if the tax season and full-year consumer finance flywheel are still strengthening.
INTU
2028-11
US election and Direct File policy direction, a long-term institutional variable.
ADBE
2026-06
Q2 FY26, first observe if CC Consumer customer attrition has slowed.
ADBE
2026-09
Q3 FY26, focus on the three-way divergence of Firefly / Document Cloud / GenStudio.
ADBE
2026-12
Q4 FY26, assess whether GenStudio has truly crossed into a higher ARR tier.
ADSK
2026-05
FY27 Q1, first quarter post-transition, verify if the breakdown of revenue and billings is becoming clear.
ADSK
2026-08
FY27 Q2, continue to observe market share signals for AECO, AutoCAD, and Revit.
ADSK
2027-02
FY27 Q4 + FY28 guidance, determine if migration samples can continue to align with P1.
PTC
2026-05
FY26 Q2, first quarter post-pure divestiture, examine if the P1 narrative continues to hold.
PTC
2026-08
FY26 Q3, continue to observe if the divergence of PLM / SLM / Onshape converges into a clearer structure.
PTC
2026-10
BMW Codebeamer replication test, a key external anchor point for the P1 narrative.
PTC
2026-11
FY26 Q4 + FY27 guidance, confirm whether governance layer and Owner Economics can be maintained simultaneously.
9.3 Leading Indicators vs. Lagging Indicators
graph LR
subgraph "Leading (3-6 Months)"
L1["Direct File Political Trends INTU"]
L2["Canva Enterprise Customers ADBE"]
L3["IFC Share in Dodge BIM Projects ADSK"]
L4["Onshape CR Ranking PTC"]
end
subgraph "Coincident (Quarterly)"
S1["Segment ARR Growth All Four Companies"]
S2["FCF Margin All Four Companies"]
S3["Non-GAAP OPM All Four Companies"]
end
subgraph "Lagging (1-2 Years)"
T1["Market Share Change All Four Companies"]
T2["AI Replacement Rate All Four Companies"]
T3["Moat Migration Completion All Four Companies"]
end
L1 --> S1
S1 --> T1
L2 --> S1
L3 --> S1
S1 --> T2
L4 --> S1
S1 --> T3
style L1 fill:#c8e6c9
style L2 fill:#c8e6c9
style L3 fill:#c8e6c9
style L4 fill:#c8e6c9
Chapter 10: Red Team — Where Our Framework Could Be Wrong
Red Team Objective: If the conclusions of this report are wrong, these are the five most likely paths for error. For each path, we provide the "what to observe for a reversal" trigger conditions.
10.1 Red Team 1 — Have We Overestimated INTU's Authority Monetization Capability?
Attack: INTU's I4 = 8/10 is based on IRS e-filer + Max Defend + Accuracy Guarantee. However, Max Defend is only an $80 add-on package, and it has not truly priced authority as its core business. Compared to MCO / FICO, its authority monetization depth is still an order of magnitude lower.
flowchart TB
subgraph "Authority Monetization Depth"
direction LR
A_INTU["INTU Max Defend $80 +Audit Assistance +Accuracy Guarantee"]
A_FICO["FICO Credit score itself is the product 100% Revenue = Authority"]
A_MCO["MCO Rating itself is the product Rating Fees >90% Revenue"]
end
A_INTU -.-> Scale["INTU authority as % of revenue < 5%"]
A_FICO -.-> Scale2["FICO authority as % of revenue 100%"]
A_MCO -.-> Scale3["MCO authority as % of revenue >90%"]
style A_INTU fill:#fff9c4
style A_FICO fill:#c8e6c9
style A_MCO fill:#c8e6c9
Rebuttal: This report acknowledges that INTU's authority does not yet account for a primary proportion of revenue like FICO/MCO. However, the significance of I4 lies in its **structural barrier** rather than **direct revenue**. INTU's IRS e-filer status grants it **regulatory authorization** in the question of "who can be the tax filing entry point," which is a structural advantage pure software companies cannot replace — it manifests in pricing as **customer stickiness** rather than direct revenue. This is more akin to Visa's interchange — not the primary revenue, but the cornerstone of the entire ecosystem.
Reversal Trigger: If the IRS lowers the e-filer authorization threshold to a point where any LLM provider can pass → INTU's authority transforms from structural to ordinary → I4 drops from 8 to 6 → Total score drops by 8-10 points → P4 downgrade.
10.2 Red Team 2 — Will ADBE Reclaim the Entry Point?
Attack: If the Firefly model marketplace strategy succeeds, ADBE could reposition ChatGPT/Midjourney as **pipelines** rather than **competitors** within the "professional creative workflow." This would imply that ADBE's I8 = 2.5/5 is an **underestimation**.
flowchart LR
subgraph "Firefly Marketplace Model Bull Case"
U[User opens Photoshop] --> F[Firefly Entry Point]
F --> F1[Firefly In-house Development]
F --> F2[Gemini 2.5]
F --> F3[FLUX]
F --> F4[Midjourney Integration]
F1 & F2 & F3 & F4 --> W[User always remains within Adobe]
W --> I8_REV[I8 Rebounds to 3.5/5]
end
style W fill:#c8e6c9
style I8_REV fill:#c8e6c9
Rebuttal: This report acknowledges that the Firefly strategy is sound, but it's necessary to differentiate between "professional Pro workflow" and "SMB/Consumer initiated." Firefly can hold its ground within the Pro segment, but consumer-level users are already intercepted by ChatGPT/Canva **before opening Photoshop**. I8 = 2.5/5 is company-wide weighted, where the Pro side might be 4/5, and the Consumer side might be 1/5.
Reversal Trigger: If Canva MAU starts to decline from 265M + Express monthly active users exceed 200M + Midjourney users publicly report "it's more convenient to use via Adobe" → I8 might rebound to 3.5/5 → Total score +3~+5 → ADBE approaches ADSK levels.
10.3 Red Team 3 — Is ADSK's Workflow Default Actually Unstable?
Attack: This report assigns ADSK an I8 = 4/5, which is higher than ADBE's 2.5/5 and PTC's 4/5. However, AutoCAD drafting faces a real AI replacement threat, discussions around Revit's IFC open standard are intensifying, and Fusion lags PTC in MFG market share. ADSK's default appeal might stem from quantity rather than quality — multiple products layered together look good, but each line is fragile.
Rebuttal: This report acknowledges the risk of "default appeal looks good but each leg is fragile," but ADSK's I8 score primarily comes from:
Professional first-click — Engineers still start with Revit/AutoCAD/Fusion/ACC, not ChatGPT
Project-level institutional lock — BIM collaboration at the project level is a team decision, not an individual one, making it difficult for AI to replace
APS/Assistant native integration — The Assistant is embedded in Revit, not an external add-on; if the Assistant succeeds, I8 will rise further
Reversal Trigger: If Autodesk Assistant remains in Tech Preview after 18 months + APS call volume does not pick up + AutoCAD seat YoY consecutively drops -5% for 2 quarters → I8 falls from 4 to 2.5 → Total score -5 → ADSK drops back to ADBE's tier (67-68).
10.4 Red Team 4 — Is PTC still not P1 enough?
Attack: This report assigns PTC P1 Primary Archetype + P11 Secondary Archetype, but the report itself admits that 38% of the CAD family still has P11 attributes. 38% is not an insignificant number — if Creo cannot transition to Onshape, PTC might forever be stuck as P11 + Clean Owner Economics, rather than a true P1.
Rebuttal: This report acknowledges this is a true binary path. Currently, Onshape ARR is approximately $90-120M vs Creo's ~$600-700M, so Onshape's share is still small. However, Onshape's user profile (startup / education / new team) represents future incremental growth, while Creo represents existing users — even if Creo remains stable, Onshape's growth is sufficient to gradually increase the P1 attributes of the CAD family.
Reversal Trigger: Onshape ARR in 2027 remains <$150M + Creo YoY turns negative → Confirms no transition on the CAD side → P1 weighting downgraded → PTC total score -2~-4.
10.5 Red Team 5 — Correct Structure Does Not Equal Correct Odds
Attack: This report ranks business quality as INTU > PTC > ADSK > ADBE, but this does not imply the same investment return ranking.
graph LR
subgraph "Decoupling of Business Quality vs. Odds"
BQ[Business Quality]
BQ --> INTU1[INTU Best]
BQ --> PTC1[PTC Second]
BQ --> ADSK1[ADSK Third]
BQ --> ADBE1[ADBE Worst]
PR[Current Odds]
PR --> INTU2[INTU 18x PE Odds Neutral]
PR --> PTC2[PTC 19.4x PE Odds Neutral]
PR --> ADSK2[ADSK 19x PE Odds Slightly Neutral]
PR --> ADBE2[ADBE 9.6x PE Odds Potentially Best]
end
ADBE1 -.->|Poor business| ADBE2
ADBE2 -.->|But low PE| Paradox[Worst Business + Lowest PE Odds Could Outperform]
style Paradox fill:#fff9c4
Rebuttal: This report's business quality ranking is not investment advice, but rather a structural observation. Each company's actual return depends on the magnitude of (Current PE - Fair PE) / Current PE:
Company
Business Quality Ranking
Fair PE
Current PE
Upside/Downside Potential
INTU
#1
25-30x
18x
+38-67%
ADBE
#4
14-18x weighted
9.6x
+45-87% (if GenStudio delivers)
PTC
#2
19-24x
19.4x
0-24%
ADSK
#3
19-24x
19x
0-26%
Conclusion: Business Quality #1 (INTU) and Business Quality #4 (ADBE) may both offer the best odds, as the former is undervalued for its authority, and the latter for its advantageous businesses within its fragmented structure. While PTC and ADSK have good structural quality, their PEs already reflect this. Business quality ranking + odds are not necessarily in the same order — this is the most important distinction between this report and single-dimension analysis.
10.6 Five Conclusions That Still Hold After the Red Team Challenge
INTU's structural advantage across the I4 + I7 + I8 three grids remains unshaken by the red team — even if the IRS e-filer threshold is lowered, the relative height of authority L3+L4 persists.
ADBE is a fragmented entity rather than a single-line decline — this diagnosis is evidenced by the six business line AIAS heatmap.
ADSK is more stable than ADBE — because I8 = 4 and I8 = 2.5 represent differences in business structure, not valuation techniques.
PTC's Clean Owner Economics remain unshaken by the red team — SBC 4.8% is hard data.
Business quality ranking ≠ odds ranking — this is a dimension that requires independent judgment, which this report has discussed separately in Chapter 7.
The first half (Ch 1-10) provides the overall structure and cross-sectional comparisons. The second half (Ch 11-16) conducts deep dives into mechanisms: for each company, a single most severely undervalued business line / structural mechanism is selected for a pinpoint penetration analysis.
Deep dive rationale: Market misjudgments are usually not "completely wrong" but rather occur when a specific detail is overlooked, leading to overall valuation deviation. This chapter specifically identifies that line for each company, providing quantifiable evidence and the magnitude of its impact.
Billing Noise, Workflow Default, FY27 Validation Year
Explaining why superficial growth rates can be misleading
Ch 14 PTC
BMW, Codebeamer × Windchill, ServiceMax
Explaining why PTC is more like a control layer than a product assortment
Ch 15-16
Flywheel Comparison and Valuation Back-calculation
Translating the above structural conclusions back into investment language
Chapter 11: INTU Mechanism Deep Dive — Credit Karma is Already "$5.7B in Hidden Value" Yet the Market Still Discounts It Based on Mailchimp
11.1 Market Confusion: $12B Was Not CK's Acquisition Price
First, let's correct a widespread misconception — the "$12B mistake".
flowchart LR
subgraph "True Comparison of INTU's Two Major M&A Deals"
CK["Credit Karma Acquired Dec 2020 $8.1B"]
CK --> CKR["FY25 Revenue $2.3B FY25 Growth +32% Standalone Valuation $11.5-18.4B ~ $5.7B Value Created"]
MC["Mailchimp Acquired Nov 2021 $12B Cash+Stock"]
MC --> MCR["FY25 Revenue ~$1.35B Growth ≈0% Standalone Valuation ~$4.7B Implied Impairment $5-8B"]
end
CKR --> V1["Comparison 1: Valued by EV/Revenue"]
V1 --> V1A["CK Implied 3.5x rev SoFi ~5x Anchor Undervalued"]
V1 --> V1B["Mailchimp Implied 8.9x rev Current Peers 3-5x Overvalued"]
style CKR fill:#c8e6c9
style MCR fill:#ffcdd2
style V1A fill:#c8e6c9
style V1B fill:#ffcdd2
Key Observation: The market remembers the $12B lesson from Mailchimp and misapplies it to CK, severely discounting CK's true contribution.
11.2 Credit Karma's Three-Driver Lead Gen Model
CK's monetization model does not directly come from its 150M+ registered users, but rather from a B2B advertising/lead generation model.
flowchart TB
subgraph "CK's True Economic Engine"
U["150M Registered Users 37M MAU"]
U --> P["Free Credit Monitoring Scores/Reports/Alerts"]
P --> PD["Three Lead Gen Products"]
PD --> L1["Loans Mortgage/Auto/Student/Personal Loans"]
PD --> L2["Credit Cards Application Matching"]
PD --> L3["Insurance Auto/Home Insurance"]
L1 --> M1["Banks Pay CK $50-400 per Successful Loan Disbursement"]
L2 --> M2["Issuers Pay CK $100-500 per New Card Activation"]
L3 --> M3["Insurers Pay CK $20-150 per Policy Underwritten"]
M1 & M2 & M3 --> Rev["FY25 Revenue $2.3B"]
Rev --> Circle["Cyclical Investment"]
Circle --> CAC["Lower Customer Acquisition Cost"]
Circle --> Match["Improve Matching Algorithm"]
Circle --> More["Cover More Financial Products"]
end
style Rev fill:#c8e6c9
style Match fill:#c8e6c9
Data Anchor Points:
CK Contribution: FY25 $2.3B, +32%
Q1 FY26 +27%, Q2 FY26 +23%
Interest Rate Sensitivity: FY23-24 suppressed by high interest rates (fewer loans disbursed) → FY25 recovery indicates cyclicality ≠ structural failure
11.3 CK × TurboTax Data Crossover — The Flywheel Truly Begins
sequenceDiagram
participant U as User
participant T as TurboTax
participant C as Credit Karma
participant A as Intuit Assist
U->>T: Feb 2026 Tax Filing (1-2 times/year)
T->>T: Extract Income/Assets/Debts/Family Structure
T-->>C: Push Financial Profile (with user authorization)
C->>C: Integrate Credit/Historical Financial Decisions
C->>A: Trigger AI Financial Recommendations
A->>U: "Potentially suitable mortgage products for you: Interest Rate X%, Match Score 78%"
U->>A: Accept / Reject / Save
Note over A: Recommendation Accuracy Before Crossover 60% Recommendation Accuracy After Crossover 78%
U->>C: Continuous Feedback on Other Financial Decisions Throughout the Year
C-->>T: Pre-populate User Financial Status for Next Tax Season
T->>U: For 2027 Tax Filing, New Financial Changes Automatically Incorporated
Core Insight: This is INTU's sole asymmetric advantage over QBO/Stripe/Plaid/Credit Sesame in I2 (cross-entity financial context) — tax filing is a complete declaration of annual income/assets, while other companies only have fragmented data.
Significance of 60% → 78% Accuracy Rate:
18pp improvement = 30% relative improvement
Based on CK's FY25 $2.3B Lead Gen model, a 30% conversion rate improvement ≈ incremental $400-500M in revenue
This incremental revenue can only be achieved through CK × TurboTax data crossover; CK alone cannot achieve it.
11.4 ProTax — The Most Unassuming Yet Most Important "Ecosystem Anchor"
ProTax FY25 revenue of $621M (only 3% of total), with +4% growth, is the smallest and slowest-growing of all INTU segments. However, it is the cornerstone of the QuickBooks ecosystem.
Key Quantification: ProTax's $621M revenue × 3% growth may seem mediocre, but its Lead Gen value is a significant source of low-cost customer acquisition for QBO's approximately $11B in revenue. If ProTax were to be discontinued, QBO's S&M costs would increase by at least 5-8%.
Why AI Cannot Bypass This Layer:
AI can replace simple tax filing, but cannot gain the professional trust of accountants
Accountants' tool choices are based on years of training + client migration costs, not "whose model is best"
INTU's launch of Intuit Accountant Suite (AI-native accountant platform) in Dec 2025 indicates management's proactive defense of this layer
11.5 INTU's Mechanism Synthesis — Why P4 Instead of P11
flowchart TB
subgraph "INTU's Trinity — The Truth of P4"
A["Authority I4 = 8/10"]
E["Exception Ownership I7 = 5.5/7"]
D["Distribution I8 = 4.5/5"]
A --> AE["IRS e-filer Authorization Max Defend Indemnification Accuracy Guarantee"]
E --> EE["Audit Defense Error Reimbursement Errors and Omissions Insurance"]
D --> DE["B2C Tax Season + Year-round CK B2B CPA Network 75% Referrals"]
AE & EE & DE --> T["Trinity More valuable than any single element alone"]
T --> Va["Mutually Reinforcing"]
Va --> Va1["Authority makes customers willing to pay a premium"]
Va --> Va2["Exception makes users unwilling to switch"]
Va --> R3["Distribution creates barriers to entry"]
end
style T fill:#c8e6c9,stroke:#2e7d32,stroke-width:3px
Comparison: ADBE/ADSK/PTC cover at most 1 to 1.5 of the three segments (ADBE's I8 creative workflow + partial I4 IP indemnification; ADSK's I8 workflow default; PTC's partial I4 TÜV). Only INTU possesses all three segments, which is the structural definition of P4.
Chapter 12: ADBE Mechanism Deep Dive — Document Cloud is the Most Severely Underestimated "Second Curve"
12.1 Why DC Deserves More Attention Than CC
When the market discusses ADBE, 80% of the time is spent on Photoshop / Illustrator / Firefly, but Document Cloud is ADBE's business line with the fastest growth + deepest moat.
graph LR
subgraph "ADBE Business Line Growth vs. Moat Comparison"
CC[Creative Cloud ~40%+19% = 59% Revenue +11% Moat: PSD Format + Brand]
DC[Document Cloud 15% Revenue +16% Fastest Moat: PDF ISO Standard + Enterprise Compliance]
EC[Experience Cloud 23% +15% Moat: Enterprise Relationships]
FF[Firefly 1% QoQ +75% Moat: Model Marketplace]
end
CC -.->|Discussed 80%| Attn[Market Attention]
DC -.->|Discussed 5%| Attn
EC -.->|Discussed 10%| Attn
FF -.->|Discussed 5%| Attn
style DC fill:#c8e6c9,stroke:#2e7d32,stroke-width:3px
style Attn fill:#fff9c4
Key Data:
DC +16% YoY, Business Pro Subscriptions
Nearly 50% of enterprise ETLA upgraded to AI version
Acrobat AI Unique Advantages: Clickable Citations + Privacy Assurance (documents remain within the enterprise)
12.2 PDF ISO Standard — A Harder Moat Than Photoshop
flowchart TB
subgraph "Structural Layers of the PDF Moat"
L1["ISO Standard Layer PDF is ISO 32000 International Document Format Standard"]
L1 --> L2["Legal/Government Reliance Layer All Court Documents All Government Forms Most Contracts"]
L2 --> L3["Enterprise Compliance Layer SOX/GDPR/HIPAA Requires Auditable and Archivable"]
L3 --> L4["AI Acceleration Layer Acrobat AI Can Search and Sign LLMs Cannot Replace Workflow"]
L4 --> L5["Network Effect Layer All OS All Browsers Default PDF Support"]
end
L1 & L2 & L3 & L4 & L5 --> Val["ADBE's I3 + I4 Strength in DC"]
style L1 fill:#c8e6c9
style L4 fill:#c8e6c9
style Val fill:#c8e6c9,stroke:#2e7d32,stroke-width:3px
Core Insight: PSD (Photoshop format) is an industry convention, while PDF is an ISO international standard. These are two magnitudes of moats.
Quantification:
Approximately 20 billion documents are generated globally in PDF format daily
Adobe Acrobat accounts for >60% of the enterprise PDF editor market
No LLM or AI-native alternative possesses global ISO standard certification + local encryption + government compatibility
12.3 Differences Between Acrobat AI and General LLMs
flowchart LR
subgraph "Acrobat AI Unique Advantages"
U["User Uploads Contract PDF"]
U --> A["Acrobat AI"]
U --> G["General LLM GPT/Claude"]
A --> A1["Local Processing Documents Do Not Leave Enterprise"]
A --> A2["Clickable Citations Each Answer Linked to Specific PDF Page/Line"]
A --> A3["Integrated with Signing/Editing/Archiving"]
A --> A4["GDPR/HIPAA Compliant"]
G --> G1["Cloud Processing Data May Be Used for Training"]
G --> G2["Citations are AI-generated Not Specific PDF Pages"]
G --> G3["Standalone Tool Requires Export"]
G --> G4["Fails Enterprise Compliance"]
end
A1 & A2 & A3 & A4 -.-> Ent["Enterprise First Choice"]
G1 & G2 & G3 & G4 -.-> NE["Unacceptable"]
style Ent fill:#c8e6c9
style NE fill:#ffcdd2
Structural Implications: Enterprise legal/compliance/HR PDF workflows cannot migrate to ChatGPT, because these documents cannot leave the enterprise firewall. Acrobat AI's "clickable citations" are not a nice-to-have, but a necessity in legal scenarios — judges see "AI says contract Y is on page 15, line Z" rather than "AI said Y".
12.4 GenStudio — A Substantial Leap in Enterprise Content Governance
GenStudio is ADBE's most aggressive attempt to migrate to the I2+I3+I4 control layer.
Requires enterprise historical creative data — Midjourney/Runway generates "generic" creative, GenStudio generates creative "for this brand"
Requires workflow integration — Brand approval + legal compliance + localization are workflows, not features
Requires Top 50 client relationships — 90% adoption rate indicates it has been selected within enterprises
Implications for Valuation: If GenStudio scales from the current $1B ARR to $2B ARR by FY28, Adobe's label would shift from "creative tool company" to "AI-era enterprise content governance platform". A corresponding market P/E from 9.6x to 15-18x would be reasonable, implying a stock price from $256 to $400-480, with an upside of 56-87%.
12.5 Comparison of "Three Transformations" — Adobe is Undergoing Its Most Difficult One
timeline
title Comparison of Adobe's Three Transformations
1985 : First Transformation: PostScript
: From printing language to DTP tools
: Difficulty: Low (New market)
: Duration: ~5 years
: Result: Photoshop/Illustrator born
2012 : Second Transformation: CC Subscription
: From boxed software to SaaS
: Difficulty: Medium (Just a packaging change)
: Duration: ~4 years (2012-2016)
: Result: ARR doubled, market cap 10x
2023 : Third Transformation: AI Workflow
: From tools to governance layer
: Difficulty: High (Value layer migration)
: Estimated: ~5-7 years
: Milestones: Firefly → Foundry → GenStudio → Adobe+Nvidia
Key Difference: In the first two transformations, Adobe's value remained at the same layer (tool layer), merely changing packaging. The third transformation requires Adobe's value to migrate to the governance layer — this is a leap "from selling tools to selling standards," a feat historically accomplished by only a handful of companies (Visa/Mastercard/FICO/Moody's).
Conditions Adobe Possesses:
Cash flow support from legacy businesses CC Pro + DC: $13B+ annual revenue, $5B+ FCF
Enterprise relationships: 90% of Top 50 have adopted AI-first
Model aggregation capability: Firefly model supermarket strategy
Legal IP guarantee: Firefly 100% legally trained commitment + IP compensation
Risks:
Firefly training data controversy
CC Consumer's continuous bleeding may exhaust patience before FY28
DOJ $150M settlement, if escalated, could trigger pricing restructuring
Chapter 13: ADSK Mechanism Deep Dive — The $200M Noise Problem of Billing Transformation
13.1 Is the +18% reported revenue for FY26 fake?
The market's biggest confusion about ADSK is: FY26 officially reported revenue +18%, but management's FY27 guidance is +12-13%, with organic growth ~13%. Where does this gap come from?
flowchart LR
subgraph "Mechanical Effects of ADSK's Billing Transformation"
Old[Old Model Multi-year contract prepayment]
Old --> Old1[Sign 3-year contract Prepay $3x in Year 1]
Old1 --> Old2[Year 1 billings = $3x Years 2-3 billings = $0]
New[New Model Annual Billing]
New --> New1[Sign 3-year contract Pay $1x annually]
New1 --> New2[Year 1/2/3 billings all $1x]
Bridge[Transition Period Mixed Effects]
Old2 --> Bridge
New2 --> Bridge
Bridge --> Rev[FY26 Reported Revenue +18%]
Bridge --> Real[Organic Revenue +12-13%]
Bridge --> Bill[FY26 Billings +30%]
Rev --> Gap[+5~6pp from transition catch-up One-time]
Bill --> Gap2[Billings 12pp higher than Revenue Proves there's noise]
end
style Gap fill:#fff9c4
style Gap2 fill:#fff9c4
13.2 Mechanical Nature of the Catch-up Effect — Not a Business Improvement in Figures
sequenceDiagram
participant C as Client (Original EBA multi-year prepayment)
participant A as ADSK
participant IR as Investor
Note over C,IR: Pre-FY23 — Old Model
C->>A: 2022 signs 3-year contract for $3M one-time payment
A->>A: FY22 billings +$3M
A->>A: FY23/24 billings +$0
Note over C,IR: Starting FY25 — New Model
C->>A: 2025 renews 3-year contract, pays $1.2M annually
A->>A: FY25 billings +$1.2M
A->>A: FY26 billings +$1.2M
A->>A: FY27 billings +$1.2M
Note over C,IR: Actual situation in FY26 reporting period
C->>A: Old contract complete (0 billings)
C->>A: New contract begins ($1.2M)
A->>IR: Billings +30% (more new contracts signed)
A->>IR: Revenue +18% (ASC 606 amortization)
IR->>A: What is the true growth rate?
A->>IR: Stripping out catch-up, approx. +12-13% organic
13.3 FY27 is the Key Validation Year
flowchart TB
subgraph "FY27 Validates Three Signals"
FY27["FY27 Full Disclosure"]
FY27 --> S1["Revenue Growth Rate"]
S1 --> S1A["If < 11% → Catch-up masking real slowdown P/E compresses to 16-17x"]
S1 --> S1B["If 13-14% → Organic momentum P/E recovers to 21-22x"]
FY27 --> S2["Billings Growth Rate"]
S2 --> S2A["If +8-10% → Catch-up normalizes as it fades"]
FY27 --> S3["FCF Growth"]
S3 --> S3A["If >$2.75B → Strong operating leverage"]
S3 --> S3B["If =$2.65B → $200-300M still catch-up"]
S1A & S2A & S3A --> Good["Good Scenario Value $280-300"]
S1B & S2A & S3B --> Neutral["Neutral Value $240-260"]
end
style Good fill:#c8e6c9
style Neutral fill:#fff9c4
Key Observation: ADSK's valuation is directly anchored to a set of FY27 numbers. This differs from ADBE/INTU/PTC — the other three's valuations focus on long-term structure, while ADSK's relies on a three-pronged triangulation of Revenue/Billings/FCF for the next 12 months.
13.4 The Dual-Caliber Dilemma of Owner Economics
flowchart LR
subgraph "ADSK Owner Economics Dual Reverse DCF"
SP[Standard Reverse DCF]
SP --> SP1[FCF including SBC $2.41B]
SP1 --> SP2[Implied CAGR 10.9%]
SP2 --> SP3[Mildly bearish 1.6pp below guidance of 12.5%]
OP[Owner Reverse DCF]
OP --> OP1[FCF after deducting SBC $2.41B - $786M = $1.63B]
OP1 --> OP2[Implied CAGR 18.4%]
OP2 --> OP3[Demanding 5.9pp above guidance]
SP3 --> Ques[Which one is correct?]
OP3 --> Ques
Ques --> A[Depends on whether SBC is a permanent tax]
A --> A1[If SBC is permanent → Owner is correct $239 reasonably high]
A --> A2[If SBC converges → Standard is correct $239 low]
end
style Ques fill:#fff9c4
SBC Convergence Evidence:
FY22 12.6% → FY26 10.9% → FY27 guidance <10%
PTC SBC/Rev 4.8%, Bentley 4.8% — suggesting industrial software SBC has the potential to converge to 5-7%
However, ADSK PSU terms are tied to Revenue + FCF targets — as long as management continues to pursue growth, SBC will not be significantly compressed
Chapter Judgment: The truth lies between Standard and Owner, with an **implied CAGR of approximately 13-14%**, slightly higher than guidance — indicating that the market is **slightly** pricing in AI capability improvements and APS options.
13.5 ADSK's Workflow Default Mechanism — Why It Remains Stable in the AI Era
flowchart TB
subgraph "Why AI Is Difficult to Replace Revit as the Entry Point"
E1[Engineers work on building projects]
E1 --> E2[Projects use BIM 360 for collaboration]
E2 --> E3[Other team members are in Revit]
E3 --> E4[Changes must be synchronized to the Revit model]
E4 --> E5[Construction drawing output must be in RVT/DWG format]
E5 --> E6[Revit is the only tool that can ingest all data]
E6 --> L[Individual engineers may try AI-generated designs]
L --> L1[But the final version must be completed in Revit]
L --> L2[This is a team decision, not an individual one]
L --> L3[AI draft + Revit refinement = enhancement, not replacement]
end
E6 --> Val[Root cause of I8 = 4/5]
L3 --> Val
style Val fill:#c8e6c9,stroke:#2e7d32
Core Difference vs ADBE: Most professional creative work (photos/videos/documents) is an **individual decision**, so Canva can penetrate at a single point. Professional engineering (BIM/projects) is a **team collaboration decision**, so AI-native tools need to **replace the entire team's workflow** to shake Revit — which is a challenge of a different magnitude.
Chapter 14: Deep Dive into PTC Mechanism — BMW Case Study + The True Cross-Product Value of Codebeamer × Windchill
14.1 Why BMW's News on 2026-04-01 is a Significant Signal
On 2026-04-01, BMW Group announced the enterprise-wide adoption of Codebeamer as the standard for requirements/testing/traceability. This may seem like ordinary news, but it is the most critical verifiable anchor for the PTC P1 narrative.
flowchart TB
subgraph "Structural Significance of BMW's Codebeamer Adoption"
BMW[BMW Group 2026-04-01 Announcement]
BMW --> B1[Enterprise-wide Standardization]
BMW --> B2[Across All Vehicle Models ICE + EV + Software-Defined Vehicles]
BMW --> B3[Across All Development Teams Mechanical+Electrical+Software+Quality]
B1 & B2 & B3 --> Impl[Implications]
Impl --> I1[Codebeamer is an Enterprise-Level Standard for Large Clients Not an Individual Project Tool]
Impl --> I2[Automotive ISO 26262 Compliance Requirements Replicable]
Impl --> I3[Medical IEC 62304 Compliance Requirements Replicable]
Impl --> I4[Aerospace DO-178C Compliance Requirements Replicable]
I1 & I2 & I3 & I4 --> NA[New Client Space]
NA --> NA1[Mercedes / Audi / Stellantis High Probability of Industry Follow-up]
NA --> NA2[Large Medical Device Manufacturers Medtronic/BSX/JnJ]
NA --> NA3[Aerospace OEMs Boeing/Airbus/Lockheed]
end
style BMW fill:#c8e6c9,stroke:#2e7d32,stroke-width:3px
style NA fill:#c8e6c9
Neither Windchill alone nor Codebeamer alone constitutes a P1 control layer, but their unification creates a true governed execution layer for regulated discrete manufacturing clients.
flowchart LR
subgraph "Traditional Layering (Without Unification)"
T1[Requirements Definition] --> T2[Managed by Codebeamer]
T3[Mechanical Design] --> T4[Managed by Creo/Windchill]
T5[Electrical Software] --> T6[Other Tools]
T7[Change Management] --> T8[Managed by Windchill]
T9[Verification] --> T10[Managed by Codebeamer]
T1 & T3 & T5 & T7 & T9 -.-> TDis[Data Siloed Traceability Broken]
end
subgraph "After Unification (PTC's Approach)"
C1[Requirements Definition Codebeamer]
C2[Cross-Disciplinary Design Creo+Windchill+ECAD/Software]
C3[Change Windchill]
C4[Verification Codebeamer]
C5[Release Windchill]
C6[Field Service ServiceMax]
C1 --> C2 --> C3 --> C4 --> C5 --> C6
C6 -.->|Feedback| C1
C1 & C2 & C3 & C4 & C5 & C6 -.-> CInt[Integrated traceability Single Source of Truth]
end
TDis -.-> AR[Audit Report Requirements]
CInt -.-> AR
AR --> AR1[Traditional: Manual Assembly of Cross-System Evidence 6-12 Weeks]
AR --> AR2[Unification: Automated Generation of Full Traceability 2-4 Days]
style CInt fill:#c8e6c9
style AR2 fill:#c8e6c9
style TDis fill:#ffcdd2
style AR1 fill:#ffcdd2
Quantified Value: Each new vehicle model approval + ISO 26262 report in the automotive industry currently requires 6-12 weeks of manual work, reduced to 2-4 days after unification. A BMW-level enterprise with 6-10 major models per year × 5-10 person-months saved per model = annualized savings of $5-20M. This is not PTC's revenue, but **the economic reason why customers cannot switch**.
14.3 ServiceMax — The Most Overlooked I4 + I7 Contribution
ServiceMax is a Service Lifecycle Management (SLM) product acquired by PTC in 2022 for $1.46B. The market often considers it "a small SaaS patch," but it is PTC's only business line with **true exception ownership** (I7).
flowchart TB
subgraph "ServiceMax's Depth of Exception Ownership"
Event["Equipment Failure Field Repair Request"]
Event --> SM["ServiceMax Receives"]
SM --> S1["Automated Entitlement Check Contract/Warranty/SLA"]
SM --> S2["Dispatch Nearest Technician"]
SM --> S3["Push Pre-installed Parts Information"]
SM --> S4["Work Order Generation and Tracking"]
S1 & S2 & S3 --> T["Technician On-site Processing"]
T --> T1["Successful Repair"]
T --> T2["Requires Additional Parts"]
T --> T3["Requires Engineering Escalation"]
T1 --> C1["Contract SLA Fulfillment"]
T2 --> C2["Servigistics Parts Dispatch"]
T3 --> C3["Windchill Trace Back to Original Design"]
C1 & C2 & C3 --> Done["Work Order Closed Data Fed Back to Windchill/Codebeamer"]
end
Done --> Next["Next Product Design Improvement"]
style SM fill:#c8e6c9,stroke:#2e7d32
style Next fill:#c8e6c9
I7 Value-Add Mechanism:
SLA Commitment — Contract-level response time commitment (e.g., 24 hours); if not met, PTC compensates the client (client-side compliance)
Entitlement engine — Which failures are covered by warranty and which are not; ServiceMax directly determines this
Service board governance — Approval / escalation / exception handling of service workflows
These are capabilities that ADBE/ADSK completely **lack**.
14.4 Purest Owner Economics — Why PTC is the Only One Among Four
flowchart TB
subgraph "Source of PTC's Pure Owner Economics"
P["PTC FY25"]
P --> P1["Revenue $2.74B"]
P --> P2["SBC $131M"]
P --> P3["SBC/Revenue 4.8%"]
P3 --> Why["Why it's Low"]
Why --> W1["High proportion of executive cash compensation Unlike Big Tech's large equity grants"]
Why --> W2["Acquired employee retention plans Partially cash rather than full RSUs"]
Why --> W3["Mid-sized company No SBC inflation like tech giants"]
P3 --> Implica["Implications"]
Implica --> Im1["Non-GAAP OPM 48% ≈ Owner OPM"]
Implica --> Im2["FCF $857M ≈ Owner FCF"]
Implica --> Im3["PE 19.4x ≈ Owner PE"]
Implica --> Im4["No need to adjust PE for Owner's perspective"]
end
style P3 fill:#c8e6c9
style Implica fill:#c8e6c9
Direct Implications for Valuation: When investors see PTC's 19.4x P/E and ADSK's 19x P/E, **these two figures are not comparable**. ADSK's 19x is **artificially inflated**; its actual Owner P/E is 37x; PTC's 19x is already its Owner P/E. This is a frequently overlooked valuation misinterpretation.
Chapter 15: Comparison of Four Companies' Flywheel Models — Structural Enhancement vs. Stall in the AI Era
The paradigm shift framework not only examines **static control points** but also **dynamic flywheels**. Whether each action of a company strengthens the next I2/I3/I4 determines if it is undergoing **structural enhancement** or **structural stall**.
15.1 INTU's Flywheel — The Most Complete Data Loop
flowchart LR
subgraph "INTU Data Flywheel v2.0"
U["User Tax Filing / Accounting / Lending"]
U --> D["Generate Multi-Year Financial History"]
D --> G["GenOS Trained on 860M+ Filings"]
G --> A["Intuit Assist More Accurate 60%→78% Accuracy Rate"]
A --> ARPC["ARPC from $400 → $580"]
ARPC --> NewU["New Users Recommended by CPAs"]
NewU --> U
end
U --> CK["Credit Karma Year-Round Engagement"]
CK -.-> D
style G fill:#c8e6c9
style A fill:#c8e6c9
15.2 ADBE's Flywheel — Split Flywheel (CC Pro vs Consumer)
flowchart LR
subgraph "ADBE CC Pro Flywheel (Enhanced)"
UP["Professional User Creation"]
UP --> FP["Firefly Generation 10 seconds instead of 2 hours"]
FP --> WF["Deeper Workflow Integration"]
WF --> UP
end
subgraph "ADBE CC Consumer Flywheel (Stalled)"
UC["Consumer User Light Creation"]
UC --> CA["Choose Canva AI"]
CA --> CB["More and more MAU join Canva"]
CB --> CC["Canva Feature Evolution"]
CC --> UC
end
WF --> P1["CC Pro Stickiness ↑"]
CC --> N1["Express Trapped at 80M MAU"]
style P1 fill:#c8e6c9
style N1 fill:#ffcdd2
15.3 ADSK's Flywheel — Platform Uplift Prototype
flowchart LR
subgraph "ADSK Design & Make Flywheel"
U[Engineers / Architects Use Revit/AutoCAD/Fusion]
U --> M[Model + Project Data Stored in DWG/RVT]
M --> APS[APS Exposes Data APIs]
APS --> AI[Assistant + Agentic AI Executing within Workflow]
AI --> Eff[Efficiency Improvement + Flex token usage]
Eff --> U
M --> ACC[ACC Collaboration Keeps Teams Sticky]
ACC --> U
end
style AI fill:#fff9c4
style Eff fill:#fff9c4
Status: Flywheel is starting but not closed-loop — Assistant is still Tech Preview, Flex token usage data not disclosed.
15.4 PTC's Flywheel — Most Complete Governed Execution
flowchart LR
subgraph "PTC Intelligent Product Lifecycle Flywheel"
S[Users Design with Creo/Onshape]
S --> W[Windchill Records BOM + ECO]
W --> CB[Codebeamer Attaches Requirements + Tests]
CB --> P[Production + Release]
P --> SM[ServiceMax Collects Field Data]
SM --> SG[Servigistics Optimizes Parts + Services]
SG -.-> S
SM --> T[Traceability Closed-Loop]
T --> R[Compliance Reports Generated Faster]
R --> More[More Large Customers Willing to Standardize]
More --> S
end
style T fill:#c8e6c9
style More fill:#c8e6c9
15.5 Four Companies' Flywheel Strength Comparison
flowchart TB
subgraph "Flywheel Strength (Five Tiers)"
direction LR
L5[⭐⭐⭐⭐⭐ Fully Closed-Loop + AI Acceleration]
L4[⭐⭐⭐⭐ Basically Closed-Loop + Partial AI Integration]
L3[⭐⭐⭐ Partially Closed-Loop + AI Prototype]
L2[⭐⭐ Single-Point Closed-Loop]
L1[⭐ No Closed-Loop]
end
INTU[INTU Tax + SMB + Lending + Accountant Four-Loop] --> L5
PTC[PTC Design + Change + Service Four-Loop] --> L4
ADSK[ADSK Design + Collaboration Two-Loop + Prototype] --> L3
ADBE[ADBE Split, Pro Has Loop Consumer Lacks Loop] --> L3
style INTU fill:#2e7d32,color:#fff
style PTC fill:#66bb6a,color:#fff
style ADSK fill:#fff59d
style ADBE fill:#fff59d
Chapter 16: Valuation Recalculation — Establishing a Reasonable Price Range for the Four Companies Based on This Framework
This chapter does not provide a precise target price, but rather uses the structural framework of this report to give a reasonable price range, allowing readers to judge the odds themselves.
flowchart LR
Core[Core Tool Layer FY28 FCF ~$6B P/E 18-20x] --> CV[$108-120B]
Auth[Authority Premium +25% on Core FCF] --> AV[+$27-30B]
Dist[Distribution Premium +15% on Core FCF] --> DV[+$16-18B]
CV --> Total[Total EV $151-168B mkt cap similar - net debt]
AV --> Total
DV --> Total
Total --> PS[Per share $550-615]
PS --> Curr[Current $408.68 +35-50% Upside]
style Total fill:#c8e6c9
style Curr fill:#fff9c4
16.5 Summary of Four Companies' Valuation Recalculations
flowchart TB
subgraph "Current vs. Probability-Weighted Fair Value (Paradigm Shift Framework)"
direction LR
INTU[INTU $408.68 → $550-615 +35-50%]
ADBE[ADBE $255.94 → $340-390 +33-52%]
ADSK[ADSK $247.57 → $332 +34%]
PTC[PTC $140.60 → $198 +41%]
end
INTU -.-> Re1[Business #1 + Favorable Odds]
ADBE -.-> Re2[Business #4 but Excellent Odds See GenStudio Delivery]
ADSK -.-> Re3[Business #3, Moderate Odds See FY27 Validation]
PTC -.-> Re4[Business #2, Favorable Odds See BMW Replication]
style INTU fill:#2e7d32,color:#fff
style ADBE fill:#66bb6a,color:#fff
style ADSK fill:#fff59d
style PTC fill:#66bb6a,color:#fff
Key Observation: All four companies show positive upside (+34% ~ +52%). This is because the valuation anchor of this framework is structural control points, not the current market's financial valuation. The market is currently systemically underpricing these four companies, but the degree and path of underpricing vary:
INTU: Authority premium is not priced in
ADBE: Weighted advantage businesses within the fragmented entity are undervalued
ADSK: P11→P1 migration option is not priced in
PTC: Owner Economics cleanliness is not priced in
16.6 Why the Four Companies Cannot Be Directly Weighted and Bought — Correlation Considerations
graph TB
subgraph "Overlap of Risk Factors for Four Companies"
Sys1[AI Impact on Professional Workflow All Four Exposed]
Sys2[SaaS Sector Valuation Re-rating All Four Exposed]
Sys3[US Interest Rate Cycle All Four Exposed]
Id1[Direct File Policy INTU Only]
Id2[BIM Mandate Changes ADSK Only]
Id3[Automaker ISO 26262 Standard PTC Only]
Id4[Canva/Figma Personal Market ADBE Only]
end
Sys1 & Sys2 & Sys3 --> S1[Systemic Risk Co-directional]
Id1 & Id2 & Id3 & Id4 --> S2[Idiosyncratic Risk Independent]
style S1 fill:#ffcdd2
style S2 fill:#c8e6c9
Meaning: The four companies have a high overlap in systemic risks (AI impact / SaaS valuations / interest rates), so an "equal-weighted four-stock" portfolio cannot lower beta but can diversify idiosyncratic risk. A more reasonable portfolio is weighted by odds, rather than by business quality:
INTU 35% (Optimal Portfolio)
ADBE 30% (High odds but volatile)
PTC 20% (Stable structure)
ADSK 15% (No further additions before FY27 validation)
When these two reports are put together, the core difference is not in the wording, but that the map has changed. "AI's Left Hand and Right Hand" is more like an action report under an old framework: it reminds investors which names seem to have a story, but that position sizing and timing should not be rushed. When writing this report, we shifted to a more fundamental question: instead of first asking who most resembles an AI beneficiary stock, we first asked which type of control point each of the four companies occupies. Once the question changes, the ranking, risk language, and valuation language will diverge accordingly.
Precisely because the question has changed, the rankings given by the two reports will not be entirely consistent. The core tension in the old report was AI's left-hand and right-hand rewrite of the software value chain, making it more conservative on PTC and ADSK; the core tension in this report is the reordering of control points, responsibility layers, and default entry points, thus bringing these two companies back to the center of structural discussion. The difference here is not simply bullish or bearish, but that the definition of the research subject has changed.
17.2 If the Conclusions of the Two Reports Conflict, Which One Should Take Precedence?
If the question is simply which report is more suitable as the main framework currently, we would prioritize this one. The reason is not that it is newer, but that it breaks down the four companies in more detail: INTU is no longer just a software leader but an authority owner; PTC is not just industrial software but an execution control layer with cleaner owner economics; ADSK is not a pure toolbox but a sample migrating from P11 to P1; and ADBE is certainly not a monolithic AI loser, but a collection of six business lines with diverging fates. Only by separating these four types of assets first does subsequent valuation comparison become meaningful.
However, this does not mean the old report is invalid. While "AI's Left Hand and Right Hand" has an older framework, it is more cautious at the action layer, and more sensitive to path risk, realization pace, market sentiment, and disclosure quality. If this report is understood as the steering wheel, the old report is more like the brakes. What is truly useful is not to choose between the two, but to clarify that they are each responsible for different levels.
17.3 A More Reasonable Comprehensive Judgment When Considering the Four Companies Together
Not a unified asset but a fragmented entity; high odds, but relies on business line breakdown rather than a company-wide narrative
The old report already warned that it's cheap but contentious, and shouldn't be viewed as a simple AI winner/loser
More suitable for a high-odds secondary core position, not the most stable primary position. One must accept higher volatility and a longer validation period here
Its core is not a toolbox but a migration option from P11 to P1, with value higher than its neutral positioning in the old framework
The old report was much more conservative, believing it needed to wait for migration and execution realization
We can acknowledge that it has more value than in the old report, but actual actions still need to be slow. Research priority is upgraded, but position sizing priority need not be synchronously upgraded
17.4 How to Truly Use Both Reports Together for Investment Decisions
A more reasonable approach is not to dwell on "who is right or wrong," but to let each report do what it does best. This report is responsible for answering what these four companies truly are; the old report is responsible for reminding investors that even if the direction is right, the timing cannot be wrong. The former determines the map, the latter determines the speed.
Applying this combined approach at the action level, a more reasonable ranking is: INTU > ADBE ≈ PTC > ADSK. This ranking does not imply that ADBE and PTC are of the same quality, but rather that one has higher odds and the other has a cleaner structure; one is more like a value bet position, and the other is more like a research-upgraded position. As for ADSK, the more appropriate positioning is still "re-evaluated in terms of framework, but action still awaits validation."
Final point: If one only reads the old report, these four companies would be interpreted as "four degrees of vulnerability to AI impact"; if one only reads this report, they would be interpreted as "four different control point assets." After truly combining both reports, the more stable approach is not to overturn the old report, but to acknowledge: the new map dictates where to look, and the old map reminds us not to drive too fast.
Related In-Depth Reports
Among the companies covered in this report, the following independent in-depth research reports are available for reference: