Skill 105 · Managing Self Driving Spend
Subchapter 105.8
references/report-template.mdMarkdown3 KBView on GitHub
Keep the report proportional to the question. For a full review, show:
as_of.pricing.usd_per_credit; sources plus scout execution reconcile to the total. Always show processing, research, scout execution, and implementation separately, including any that are zero.posthog:billing-limits-get, separately from recorded usage. Identify exempt credits as a subset; non-exempt usage is not necessarily the invoice.Resolution yield uses reports first shown at least 14 days ago, looking back 60 days. Write “too new” below 20 settled reports. In the report, say “resolved” and never “settled”. Explain it once: “Resolved: of reports first shown at least 14 days ago, the share that got resolved.” Cost per resolved report is an estimate: period spend divided by reports created times the settled resolution rate. Its spend and report cohorts differ. Below about 3 expected resolved reports, write “too few reports to estimate”. Automatic implementation costs are measured; savings from a proposed threshold or steering change still require an estimate. When you report implementation spend, say that it excludes fixes a person starts from a report, which are metered as PostHog AI. Apply only changes the user explicitly confirms and read each setting back.