BMO Capital raises Atlassian stock price target on revenue mix

BMO raised its Atlassian price target to $225 from $170 and maintained Outperform, citing potential revenue upside from product mix, bundles, cloud conversions, pricing and seat growth. For HubSpot, BMO raised its target to $255 from $250 but kept Market Perform, citing modest upside while warning that SMB buying cycles may stay elongated amid consideration of more AI solutions. The article also notes HubSpot’s November 4 earnings date, a potential 12% post-earnings move indicated by options, and a previously announced 7% workforce reduction affecting about 660 employees.

Analysis

TEAM’s setup is more than an analyst-target revision if cloud conversions and bundle adoption are producing durable seat expansion: those would support recurring revenue and reduce reliance on one-off pricing actions. The key risk is quality of upside—pricing and conversion timing can lift a quarter without proving stronger underlying demand. Check net seat growth, cloud migration progress, and forward guidance before treating a beat as a re-rating catalyst. Microsoft’s bundled collaboration stack remains a competitive constraint.

HUBS faces a less favorable second-order dynamic: more AI vendors can lengthen SMB evaluation cycles and raise customer-acquisition friction, even if demand for automation remains intact. That pressure could defer bookings before it appears in reported revenue. Salesforce and other suite vendors may benefit if buyers favor vendor consolidation over specialized tools. Layoff-related savings could cushion expenses, but are not evidence of demand recovery.

Near term, both earnings are binary events; the reported options-implied move for HUBS is a risk marker, not a reliable forecast. Over 1–3 months, guidance on seats, bookings, and sales cycles matters more than price targets. Over 6–18 months, the differentiator is whether AI drives paid adoption or simply adds evaluation complexity. The cautious consensus may underweight TEAM’s monetization levers, but a TEAM beat based mainly on pricing would weaken that contrarian case. Falsify the relative thesis if TEAM reports slowing seat/cloud adoption or HUBS shows improving bookings and shorter sales cycles.

Key Decisions for Investors

• Consider a modest, event-aware long TEAM / short HUBS pair after earnings, rather than carrying full binary exposure into both reports. Reassess on relative guidance for seat growth, cloud conversion, bookings, and sales-cycle duration; cap risk if either company gaps materially against the thesis.
• For TEAM, treat a revenue beat as lower quality if it is primarily pricing or conversion timing without accompanying seat growth or stronger forward guidance; that would argue against chasing the analyst-driven move.
• For HUBS, avoid selling event volatility solely because options imply a large move. Wait for the report and monitor bookings/customer additions and management commentary on SMB buying cycles; improving indicators would invalidate the short leg.
• Do not treat the analyst targets or platform valuation claim as independent valuation evidence. Revisit the setup against reported results and subsequent guidance, not target changes.