Reduce unneeded npm packages in production builds with automated dependency pruning

Reduce unneeded npm packages in production builds with automated dependency pruning targets a $4.8B = 2,000,000 businesses x $2,400 ACV. Assumes 2M companies run Node backends or serverless services and would pay $200/month for a build-optimization subscription or equivalent enterprise contract. total addressable market with medium saturation and a year-over-year growth rate of 18%.

Key trends driving demand: serverless-adoption -- more production workloads are moving to functions where cold start and package size materially impact performance and cost; larger-orms-and-native-engines -- ORMs and packages with native engines (Prisma, others) embed large runtime artifacts that are not always required in production; standardized-ci -- CI/CD pipelines and package-lock determinism make automated pruning reproducible and automatable.