Make client bootstrap/instrumentation injectable via next.config.js (no source edits)

Modern web teams—observability vendors, security and privacy teams, and engineering orgs at roughly 1.5M companies—struggle to add client-side telemetry and instrumentation to Next.js apps without editing application source, a problem amplified by split runtimes (Edge, serverless) and strict CI/CD policies. The current workarounds—manual edits, wrapper libraries, or maintaining patched starters—create developer friction, inconsistent coverage, and auditability gaps that are especially problematic for compliance-conscious organizations. You could build a framework-native plugin that makes client bootstrap/instrumentation injectable via next.config.js: a runtime-aware injector that integrates with Next.js official plugin hooks, injects minimal bootstrap code without source edits, manages sourcemaps, and enforces consent-first loading and audit logs. Essential capabilities would include signed manifests for tamper resistance, runtime detection for Edge vs server runtimes, policy-driven consent controls, and performance-budget enforcement so teams can enable observability with predictable overhead. This is a timely opportunity: the total addressable market is about $15.0B (1.5M companies × $10K average yearly spend), the Market Score is high at 88/100, and industry trends—framework-native extensions and privacy-first telemetry—mean buyers are receptive to config-based, non-invasive tooling. The product can differentiate by adhering to Next.js plugin conventions, providing enterprise-grade governance and auditable consent flows, and minimizing runtime overhead, but it faces real challenges—keeping pace with Next.js and Edge runtime changes, overcoming trust concerns about injected code, and competing in a medium-competitive landscape where convincing platform maintainers and cautious engineering teams will be key.