Many cloud‑native and enterprise application operators—roughly 120,000 organizations paying about $100K ACV for observability suites—are struggling with an explosion in trace volume as server‑side rendering and edge compute add client and intermediary spans. Instrumented requests can generate 5–20× more spans per transaction, and short‑lived processes make in‑memory sorting expensive or impossible at scale. The result is rising ingestion CPU and storage costs and ballooning invoices that make per‑span pricing and synchronous end‑to‑end sorting increasingly untenable. You could build a high‑throughput trace ingestion pipeline that defers strict ordering by combining lazy sorting with pre‑sorted span event blocks: accept append‑only spans at tens to hundreds of thousands of spans per second per cluster node, attach lightweight sequence metadata via OpenTelemetry, and assemble fully ordered traces on demand or for sampled tails. That design can reduce sorting CPU and temporary storage by an estimated 30–50% for heavy workloads while remaining compatible with existing instrumentation. Tradeoffs are real—expect slightly higher worst‑case query latency for complex, highly concurrent traces and nontrivial engineering to validate correctness across heterogeneous SDKs. This is an attractive time to pursue the idea—the TAM is about $12.0B, OpenTelemetry is becoming a de facto standard, and cost sensitivity is driving buyers to consider ingestion‑level optimizations. To stand out you’ll need measurable, reproducible cost savings, drop‑in SDK compatibility, and an open‑source or transparent core to build trust; challenges include persuading platform owners to change pipelines, proving SLA parity on latency and accuracy, and fending off established observability vendors who can add similar optimizations.