Home / Playbooks / Anti-patterns
Anti-patterns · what not to do 25 mistakes · 5 categories · last revised May 22, 2026

25 outbound mistakes we've watched fail, with the fix.

The consultancy archive that became Mama. Each card has what it looks like in the wild (real example), why it's wrong, and what to do instead — with a link to the playbook where relevant. Filter by category up top, or scroll for the whole list. If your team has done five of these in the last quarter, that's normal; if you've done none, you probably aren't sending enough cold email yet.

DI
Discovery & demo · 5 anti-patterns
The mistakes that turn a good cold email into a wasted meeting.
AP-09 Epidemic
"Tell me about yourself" as the first disco question.
What it looks like
So before we get into it, tell me a bit about yourself and what you're working on these days…
Why it's wrong
The buyer knows you already looked them up. Pretending otherwise wastes both peoples' time and signals you didn't prep. They mentally downgrade the meeting in the first 90 seconds.
Do instead
Open by summarizing what you already know and asking them to correct: "I see you're heading RevOps post-Series B, focused on AE bench scale-up. Anything I'm missing?"
AP-10 Frequent
No agenda at the top of the call.
What it looks like
Great, well, thanks for taking the time. So — where would you like to start?
Why it's wrong
Without a stated agenda, the call drifts. The buyer can't tell if you've prepared, the rep can't redirect when things wander, and both leave the call uncertain whether anything was decided.
Do instead
First minute, every disco: state the 3-bullet agenda, ask if anything's missing, then start. "I had 3 things I wanted to cover — context on your stack, the brief flow, and what a free trial would look like — does that work?"
AP-11 Epidemic
Demoing every feature in the product.
What it looks like
Let me give you the full tour. Over here is the dashboard, then we have settings, then integrations, then…
Why it's wrong
Most features are noise to most buyers. Showing them all dilutes the 1-2 that actually solve the buyer's problem. The buyer leaves remembering the wrong features, or none of them.
Do instead
Show two features only, both tied to a specific pain the buyer just named. End with "want to see anything else specifically?" — not "want a longer tour?"
AP-12 Common
Ending the call without a written next step.
What it looks like
"Great, this was super helpful — let's stay in touch. I'll send you some info." [No specific commitment. No follow-up date.]
Why it's wrong
"Stay in touch" means "this deal is dead and we both know it." Without a specific written next step (action, owner, date), the buyer's interest decays at the rate of their inbox.
Do instead
Last 5 minutes of every call: write the next step in chat, both names, a specific date. Send the recap email within 90 minutes restating it. If you can't get to a specific next step, the call wasn't qualified.
AP-13 Frequent
Asking "what would it take to get this done?"
What it looks like
Late in the call: "So what would it take to get this across the line for you?"
Why it's wrong
It outsources the close to the buyer. They don't know what it would take — that's your job. They'll usually invent a reason (more time, more research, more references) that sounds reasonable and stalls the deal.
Do instead
Propose a specific path and ask if it works: "I think the next step is a 30-min technical review with your IT lead, then a 2-week paid pilot. Open to that, or is there a piece I'm missing?"
IC
ICP & CRM · 5 anti-patterns
Most teams' CRM has these. Cleanup pays back inside a quarter.
AP-14 Epidemic
60% of the CRM tagged "A-tier."
What it looks like
Account_Tier__c: A · 6,247 records · Account_Tier__c: B · 1,341 records · Account_Tier__c: C · 312 records.
Why it's wrong
When the top tier is 60%+ of the database, the tier means nothing. Reps stop trusting it; the working list collapses back to "whatever I worked yesterday." Marketing tags drift; nobody re-audits.
Do instead
Replace tier with a scored field (0–100) computed from a real rubric. Build views off score bands, not tier letters. See the ICP rubric entry for the 4-dimension model.
AP-15 Frequent
No defined ICP — just "B2B SaaS in North America."
What it looks like
Sales enablement deck slide: "Our ICP is mid-market B2B SaaS companies in North America."
Why it's wrong
That's not an ICP — that's a market. An ICP narrows down the market to "the kind of company that buys and retains." Without firmographic, technographic, and behavioral criteria, the field reps can't filter their list.
Do instead
Write a 5-criterion ICP with must-haves and nice-to-haves. Recalibrate after every 30 booked meetings. Workshop format playbook coming soon.
AP-16 Common
Letting reps pick their own accounts to work.
What it looks like
Sales meeting: "Pick the accounts you want to work this quarter — you know your patch best."
Why it's wrong
Reps pick the accounts they already know. That doesn't grow the pipeline; it re-works it. New accounts that scored high in the last week get ignored because they're unfamiliar.
Do instead
RevOps allocates the weekly score-jumped list; reps work from it. Allow rep override only with a written reason (so the override pattern is auditable later).
AP-17 Common
31 custom fields on the Account record.
What it looks like
Account record fields: MQL date, Lead source, Campaign attribution, Last MQA, Last MQL, Last SAL, Last SQL, Marketing-influenced flag, BDR-assigned date, AE-assigned date…
Why it's wrong
Most fields are marketing-attribution garbage masquerading as customer information. They don't tell the rep anything about what to say next. They slow down every record view and crowd out the fields that matter.
Do instead
Audit ruthlessly. The fields a rep needs are: ICP score, last signal, brief link, owner, last activity. Hide everything else from the rep view (the data can still live for reports).
AP-18 Frequent
No defined disqualification rules.
What it looks like
Sales handbook: contains qualification questions. Contains zero explicit "if any of these are true, disqualify" rules.
Why it's wrong
Without explicit disqualifiers, reps keep bad-fit accounts in the pipeline for emotional reasons (they already invested time). Disqualifiers save more rep-hours than qualifiers ever will.
Do instead
Define 3 hard "anti-ICP" rules. If any is true, the account is auto-out of working list regardless of score. Examples: "under 20 employees", "no CRM detected", "ICP fit < 40".
SQ
Sequencing & cadence · 4 anti-patterns
The patterns that make sequencers worse than sending one-offs.
AP-19 Epidemic
Same sequence for every signal type.
What it looks like
"Cold Outbound v3" — 8 steps, 18 days, same emails whether the account just closed a Series B or hired a new VP RevOps.
Why it's wrong
A funding round and a new exec are different windows with different appropriate cadences. Forcing them into the same sequence misses the timing of one and over-pressures the other.
Do instead
Build signal-specific sequences: funding (faster, 7 days), exec-move (slower, 21 days), stack-change (medium, 14 days). Mama's working list routes accounts to the right sequence automatically.
AP-20 Frequent
Continuing the sequence after a new strong signal fires.
What it looks like
Account is on day 6 of a generic sequence. Just hired a new VP RevOps. The next sequence step is "bumping this thread."
Why it's wrong
The new signal is much higher leverage than the bump. Continuing the cadence wastes the chance to anchor a fresh outreach on the new event.
Do instead
Auto-pause the sequence when a high-strength signal fires; push the account to a 1:1 hand-written reach-out using the new signal. This is built into Mama's signal-triggered exit flow.
AP-21 Frequent
10+ touch sequences "to make sure we're persistent."
What it looks like
12-touch sequence over 28 days. Steps 8–12 are bumps on bumps with no new content.
Why it's wrong
After 5–6 touches, additional emails burn the relationship faster than they create one. Reply rates flat-line, unsubscribes spike, and any future outreach is poisoned.
Do instead
5–7 touches max, mixed across email + LinkedIn + phone. Last touch is a polite breakup with permission to re-engage. Re-add the account to sequencing only when a new signal fires.
AP-22 Common
All touches on the same channel.
What it looks like
7-step sequence, all 7 are emails.
Why it's wrong
Single-channel sequences are easier for the buyer to ignore. The 4th email from the same sender in a week looks like spam regardless of content.
Do instead
Cross-channel: email → LinkedIn DM → call → email. The same message in a different channel reads completely differently. Especially the LinkedIn comment-then-DM pattern.
RP
Reporting & manager rituals · 3 anti-patterns
The metrics that look responsible but train bad behavior.
AP-23 Epidemic
Measuring activity (emails sent) instead of outcomes (booked meetings per signal worked).
What it looks like
Weekly SDR dashboard: emails sent (1,200), calls dialed (84), LinkedIn touches (210). Booked meetings: not on the dashboard.
Why it's wrong
Reps optimize for what's measured. Measuring activity gets you more bad activity. Reps spray rather than research, because the dashboard rewards spraying.
Do instead
Lead with booked meetings per signal worked and SQL conversion rate. Show activity metrics last, only as a debugging tool when the leading metrics are off.
AP-24 Frequent
No attribution from booked meetings back to triggering signal.
What it looks like
"How did we book that meeting?" "Uh… I think it was from a cold email? Maybe LinkedIn? Hard to say."
Why it's wrong
Without attribution, the team can't tell which signal types convert best. The ICP rubric weights don't get re-tuned. Resources keep flowing to whatever feels familiar rather than what works.
Do instead
Every booked meeting gets tagged with the triggering signal (funding, exec move, hiring, etc.). Weekly review compares conversion by signal type. Mama writes this attribution automatically.
AP-25 Common
Weekly pipeline review focused on stage, not on signal freshness.
What it looks like
Manager: "Walk me through your top 10 deals by stage." Rep: [walks through deals]. Manager: "OK keep pushing."
Why it's wrong
Stage tells you where the deal was last month, not what's happening now. Deals stall because nothing fresh has been added to the conversation; reviewing stage doesn't surface that.
Do instead
Review by "days since last signal fired". Any deal with no signal in 30+ days gets explicit discussion: re-engage with new evidence, or move to nurture.

No anti-patterns in that category yet.

If you've seen a recurring outbound mistake we haven't catalogued, email it over with a real example.

Got an anti-pattern we missed? Hit us with a real example — what it looked like, why you think it's wrong, what you ended up doing instead. We add the strong submissions with credit in the next revision of this page.
Submit an anti-pattern →
Avoid these by default

Mama is designed to make most of these impossible.

The signal-anchored frame, the score-jumped working list, the automatic attribution from booked meetings — they're all opinions about what NOT to do, baked into the product. Free up to 100 accounts, no card.

Start free → Read the opener playbook