Pick a depth. Each prompt opens in your AI pre-loaded with the lesson. Click a row to preview the prompt.
What separates people who get good at sales from people who quit is not reply rate - it is what they do with the result. Beginners collapse every outcome into one feeling ('rejection') and either spiral or shrug; professionals read outcomes as data, because a no, a not-now, and silence are three different signals pointing at three different fixes. A 'no' with a reason is the most valuable free consulting you will ever get. A 'not now' is a calendar entry, not a defeat - budgets and quarters change. And silence, the most common outcome, is statistically almost meaningless at a sample size of one: even strong cold outreach converts well under 20%, so one unanswered email tells you close to nothing about you. The three-line retro you write in this task is the habit that compounds across the whole course - every send becomes a lesson about target, research, or message, and by module ten you will have a written record of exactly how your loop improved.
The reading guide, outcome by outcome. A positive reply ('sure, send the example'): deliver exactly what you offered within 24 hours, nothing more - do not smuggle a meeting request into what was promised as no-call. A no with a reason ('we already use Scribe for this'): gold - you just learned a competitor, an objection, or a targeting miss for free; thank them in one sentence and log the reason verbatim in your sheet. A bare no: accept gracefully and ask one tiny question - 'totally fair; out of curiosity, wrong problem or wrong timing?' - about a third of people answer, and the answer tells you which loop stage to fix. A not-now ('interesting, but we're mid-migration - try me in Q4'): reply 'will do', create an actual dated reminder for early Q4, and consider it a live lead, because it is one. Silence after the bump: close the thread, mark the outcome 'no response', and resist inventing a story - at n=1 the honest label is 'no data', and the causes (vacation, reorg, spam folder, busy quarter) are mostly not about you.
Then the retro - three lines, written into your Pipeline sheet next to the outcome, one line per loop stage. Here is a real-looking example for a silent outcome: 'Target: right role, but a 120-person company may have this problem less acutely than a 40-person one - try smaller next. Research: brief was strong, but I led with the job-posts fact when her own repeat-tickets post was the warmer door. Message: 85 words was good; the escape-hatch sentence read slightly stiff - say it more like me.' Each line names something you would change, not something you feel. One honest rule to end the module on: run this retro after every attempt in this course, but do not change your whole approach on one data point - the retro's power shows up when five retros in a row point at the same stage. That pattern-reading is exactly what the rest of this course builds toward: more targets, better research at scale, and a pipeline where outcomes become strategy.