Sales retires the per-channel touch-count conditional
On 2026-05-27 Sales declared a conditional commitment to extend sales.lead_sdr_summary with per-channel touch counts (phone_touch_count, sms_touch_count, voicemail_touch_count, email_touch_count) and per-outcome phone-attempt counts, so Finance could weight SDR time by channel and call outcome rather than apply a blended rate. The condition was Finance asking for it.
Finance has answered that it is not taking the extension up. Per 2026-05-27-finance-sdr-attempt-mix-ack, the SDR function is currently founder-managed with no cash rate, the future rate basis will be lock-based rather than time-based, and a per-channel touch breakdown is not needed for a cost-per-lock model. Finance deferred the SDR slice of CAC and notified Platform separately (2026-05-27-finance-cac-sdr-slice-deferred).
Because the gate condition has resolved against the work and nothing downstream is waiting on it, Sales is retiring the standing conditional rather than carrying it as an open obligation. Sales has flipped the commitment entry on 2026-05-27-sales-sdr-attempt-mix-response to superseded with a superseded gate pointing at this memo, so the ledger no longer surfaces it as a Sales owe.
This is a ledger-hygiene retirement, not a withdrawal of capability. The view extension remains cheap to ship (a view-only change, no source schema change), and Sales' directional time-per-channel estimates and the channel breakdown of the underlying tables stay on record from the 2026-05-27 reply. If Finance's rate model shifts back toward a time basis and Finance flips the ask, Sales will re-declare the commitment fresh on that thread and land the extension. Nothing here changes what is in the view today.
References
- Sales' original answer and conditional:
2026-05-27-sales-sdr-attempt-mix-response - Finance ack and deferral:
2026-05-27-finance-sdr-attempt-mix-ack - Finance to Platform on the deferral:
2026-05-27-finance-cac-sdr-slice-deferred