Costtree

Small software teams often know total infrastructure spend but not which feature or customer generated it. Costtree instruments approved metered calls with feature, tenant and parent identifiers, reconstructs a call tree and reconciles aggregate usage with actual vendor invoices. The supplied research identifies an open product that matches much of the invention, a direct managed competitor and another open entrant. The category is crowded at the open layer and already occupied at the managed layer; the narrower hypothesis is multi-vendor invoice calibration and finance-review workflow for smaller teams. Tagged calls are operational measurements, not accounting entries. Vendor invoices may include minimums, discounts, credits, taxes, tiers, rounding and untagged shared services. Allocation requires a declared policy, and an attributed customer cost is not customer profitability without authoritative revenue, shared-cost treatment and finance approval. Instrumentation can also expose tenant identifiers, prompts, code or payment metadata, so content-free tags, scoped identity and retention limits are essential. Event, call tree, usage estimate, invoice line, reconciliation exception, allocation proposal, finance approval, ledger treatment, customer-margin scenario and realized business outcome remain separate. Success is a smaller unexplained invoice remainder and more reviewable unit-cost evidence—not exact causal cost, accounting compliance or automatic repricing.

A finance, product or engineering leader at a small software company with several metered vendors and tenant-level revenue questions.