Finance needs SDR attempt-mix and time-per-channel inputs for CAC
Why
Platform is ready to wire the SDR dollar slice into buildCacRows per
2026-05-27-platform-finance-cac-sdr-compute-status. The blocking item is
that Finance needs to commit assumption constants before Platform can land
the compute: a volume signal, a minutes-per-unit figure, and an operator rate.
Phone attempts and text attempts carry materially different time costs. A phone attempt where the SDR reaches the lead is roughly 6 minutes; a text touch is a fraction of that. Using a single flat rate across both would overstate SDR cost if texts are a large share of volume, or understate it if calls dominate. Finance needs to know the mix before versioning an assumption.
Asks
Two questions for Sales:
Does
sales.lead_sdr_summaryalready separate phone attempts from text touches in its column set, or doestouch_countlump them together? If there is a channel-level breakdown available in the silver, Finance can weight the time estimate by channel rather than applying a flat rate.What is Sales's rough feel for time per channel? Finance has an informal estimate of around 6 minutes for a phone attempt where contact is made, but no estimate for text touches or for no-answer dials. Even a directional answer (for example, "texts are under a minute, missed dials are under 2") is enough for Finance to set a defensible blended rate.
Finance will hold the Platform reply open until this lands, then file
sdr_rate_v1 as a named assumption version so future periods can be audited
against it.
References
- Platform CAC compute status ask:
2026-05-27-platform-finance-cac-sdr-compute-status - CAC payback manifest:
contracts/finance-mart/cac-payback.md