What is Height doing strategically?

Height announced its shutdown in March 2025 and ceased operations on September 24, 2025, forcing thousands of product and engineering teams onto the open market. The company raised $18.3M total and had a paying customer base that already believed in AI-native project management.

Users who migrated off Height are the highest-intent AI PM buyers in the market. They do not need to be educated on the category. They need a product that delivers on the autonomous workflow promise Height made but could not sustain. Whoever captures this cohort in the next two quarters builds a reference customer base with genuine credibility.

This window is short. ClickUp, Linear, and Dart are all running explicit Height migration messaging. The teams that have not yet settled on a replacement are the laggards, typically smaller and more price-sensitive, but still worth winning. If you can name the exact Height workflow you replace on your homepage and pricing page, you cut acquisition cost on this cohort significantly.

Height 2.0 launched in September 2024 with autonomous features including bug triage, backlog pruning, and live product document updates. Despite strong design reception, product update velocity dropped sharply after launch. Social channels went quiet by early 2025 and the shutdown followed in March.

The pattern is instructive: autonomous AI in PM tools generates genuine excitement in evaluation but struggles to produce the kind of daily workflow lock-in that drives NRR. Buyers in product and engineering teams still own their task structure personally. A PM tool that takes over too much autonomy too fast creates anxiety, not retention. The feature that saves time in a demo can be the feature that gets turned off in week three.

Build toward autonomous features incrementally and tie each one to a measurable time saving that the buyer can report internally. One credible outcome, such as thirty minutes saved per sprint on triage, beats five autonomous features that feel ambient.

Height's pricing gave all plans full feature access and priced differences primarily on the volume of autonomous AI feature usage rather than feature gating. At $6.99 per user per month for the Team tier, it was competitive with mid-market tools while offering AI capabilities not available at that price point elsewhere.

Feature gating AI in a product category defined by AI is a positioning error. Height got this right and it gave them strong initial conversion. The lesson for you is that usage-based AI pricing is the correct architecture for this category. Flat per-seat pricing without an AI usage tier leaves money on the table as teams scale usage; hard feature gating loses trials at the top of the funnel.

Height's pricing model was a structural advantage that did not save the company, but only because retention failed. If you have better workflow lock-in, the same pricing architecture compounds.