Write A JTBD Sales Email From Product Behavior
Draft a product-led sales email that links observed behavior to the customer's job, pain, and next progress step.
Draft a useful email after a user exports the same report three times and invites finance. Translate event -> job -> pain -> question. The common trap is attaching the event to the nearest paid feature and pitching immediately. That makes the outreach feel like a vendor trigger instead of a response to the customer's progress and unresolved job. Observe Event: report exported three times; finance teammate invited. Keep the observation factual. Do not overclaim what the user intended. Infer the job Likely job: turn a one-off analysis into a recurring finance update. The invite changes the meaning. This is…
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in