Decision
Michael will handle the Ben G situation with a low-key temp check on the Aug 14 call. No escalation unless Ben escalates first. Tatem flags any new incidents in the meantime; Michael talks Ben down directly if he escalates early.
Context
Ben G submitted a girlfriend safari video for posting without flagging consent. After posting, he complained she hadn’t explicitly consented. He also complained a separate video “felt sped up” (it did not). Likely explanation: girlfriend got upset, Ben is redirecting frustration. Ben’s company is also winding down, adding stress. Ben is JOLT!‘s only current client so retention matters, but JOLT! has strong leverage: 0 to 11,000+ followers in a short period, including an a16z partner repost.
Options Considered
- Proactive outreach before Aug 14: rejected - Ben is on vacation, not urgent, no need to interrupt.
- Escalate concern internally: rejected - read as temporary friction, not a real churn signal.
- Wait and monitor: adopted, with Tatem as the early-warning signal.
Consequences
- Michael calls Ben Aug 14 for a casual temp check.
- If Ben escalates before then, Michael responds directly with the growth story as anchor: “We built you a 12,000-person audience. We want to get you to 100K.”
- Tatem to flag any further weird incidents promptly.
- Parallel path: get the funnel and VSL live ASAP so JOLT! can start acquiring new clients and reduce single-client dependency.
Source meeting: Huddle w/ Tatem on Ben G Concern