Built for teams running cold email as a primary channel
Templates are the easy part. The system around them is the hard part.
Any SDR can copy a template off a thread on LinkedIn. The sequence that actually generates meetings has 40 variables under the surface: inbox warm-up schedule, send-time jitter, reply classifier, bounce-handling, suppression discipline, personalization token quality, and a reply attribution loop that tells you which template actually worked. Strkr ships the sequence engine, the template library, and the attribution surface together so a rep running cold email on a Tuesday morning is not also running a deliverability experiment.
Four facts about cold email in 2026 define the problem space. First, Google and Microsoft tightened sender-authentication requirements in February 2024 (bulk senders over 5,000 messages a day must set DMARC, DKIM, SPF with alignment, and keep spam complaint rate under 0.3 percent). Second, Mailshake benchmarks across 4 million outbound campaigns show average open rates fell from 36 percent in 2021 to 21 percent in 2025 as inbox filtering tightened. Third, reply rates on cold email now cluster at 1 to 5 percent for well-run B2B campaigns, meaning a 500-prospect send yields 5 to 25 replies, of which maybe 2 to 8 convert to meetings. Fourth, the template libraries sold by vendors (Mailshake, Lemlist, Smartlead, Instantly) are useful starting points but become identical after a quarter of inbox saturation. The teams that keep hitting the top 10 percent of reply rates run their own template library on top of a serious deliverability stack and a reply-classification loop.
Template fatigue in the buyer inbox
The "did you see my last note?" opener now reads as spam.
The template patterns that worked in 2019 have been copied into every outbound stack, and buyers have pattern-matched to ignore them. The specific openers that trip spam filters by 2025 include "Just circling back," "Did you see my last note," "Quick question," and the "I noticed you..." LinkedIn-stalker opener. Strkr ships a template health check that flags the 23 phrases Mailgun and Spamhaus flag as reduce-sender-reputation triggers, which cuts the bounce-to-spam-folder rate meaningfully.
Deliverability stack is the hidden gatekeeper
DMARC alignment fails and your sequence hits 2 percent delivery.
In 2024, Google began bulk-mail sender enforcement: DMARC with p=none at minimum, DKIM alignment, and SPF alignment, plus a one-click unsubscribe for marketing-flagged mail. A sender that fails any of these drops into Gmail's Promotions tab at best and the spam folder at worst. Strkr's outbound engine verifies DKIM, SPF, and DMARC alignment on every connected sending domain and refuses to run sequences on domains that fail the check, which prevents the common 90-day silent-failure pattern.
Mailbox rotation that nobody actually configures
One sender account sending 500 emails a day burns out in three weeks.
Mailbox warm-up and rotation are mandatory for any cold outbound at scale. A single Google Workspace mailbox should send under 150 cold emails per day during warm-up and under 300 at steady state. Teams running 10 reps with 5 mailboxes each on rotation can push 15,000 daily sends without sender-reputation damage, but configuring the rotation manually is error-prone. Strkr automates the rotation with per-mailbox send caps and a central deliverability dashboard that shows which mailboxes are approaching reputation thresholds.
Reply classification by hand
Who had time to read 400 replies and tag each one?
When a sequence generates 100 to 500 replies, the SDR has to triage: positive interest, out-of-office, "please remove," wrong-contact-forward, meeting-booked, defer-to-later-quarter. Doing this manually consumes 60 to 90 minutes a day per SDR. Strkr runs a reply classifier (Strkr AI with explicit confidence surfaced) that tags each reply, pushes positive replies to the top, auto-handles out-of-office and unsubscribe-request, and leaves the ambiguous ones for human review.
Template attribution lost at the sequence level
The vendor says the sequence reply rate is 4 percent.
Vendor dashboards report at the sequence level, which averages across every step and template variant. The actual useful question is "which specific step and variant drove this reply?" The answer informs iteration: double down on the step-2 variant that pulls 7 percent, retire the step-4 variant that pulls 0.4. Strkr tracks reply attribution per step per variant per cohort, so iteration happens on specific templates rather than vague sequence-level averages.
Suppression discipline is a legal issue, not a feature
Three sequences, one prospect, two "please remove" replies ignored.
When a prospect replies "please stop" or "unsubscribe me," the vendor sometimes handles the sequence they are in but not the other two sequences they are a prospect in on your tenant. The next quarter they get the sequence again and this time they file a CAN-SPAM complaint. Strkr runs tenant-level suppression that intersects every sequence immediately on reply classification, with explicit audit of what was suppressed when and why.
What Strkr ships for cold email programs
The sequence engine, template library, and attribution loop in one place.
Below is the cold-email surface that lives inside Strkr. The pattern that drives customer adoption: the sequence engine, the template library, the deliverability stack, and the CRM record all live in the same system, so a reply from a 5-step sequence becomes a Strkr task on the deal record without a middleware hop.
Starter template library
40-plus cold email templates by motion.
The template library ships 40-plus openers organized by motion: outbound SDR to AE handoff, event-triggered (fundraise, exec hire, product launch), reactivation (dormant lead, lost opp), referral intro, breakup. Every template is annotated with the historical reply rate across the Strkr customer base in similar segments, so the SDR picks a starting point based on observed performance, not vendor marketing.
Variable library and personalization
First-mention tokens with fallback logic.
Templates reference variables like {{first_name}}, {{company}}, {{recent_funding}}, {{tech_stack_signal}}, {{mutual_connection}}. Each variable has a fallback rule: if the primary token is empty, use the fallback, if fallback is empty, skip the sentence rather than send "Hi there, I noticed your company {{company}} is..." which flags as a mail-merge failure to the buyer and the filter.
Sequence builder
Visual multi-step cadence with branching.
Build a 3 to 7 step sequence on a visual canvas: initial email, follow-up with wait days, LinkedIn connection request, voicemail task, final breakup. Branch on reply, open, or no response. The builder shows the daily send volume projection against mailbox cap, which prevents the common error of running a 20,000-prospect sequence through 2 mailboxes.
Mailbox warm-up
Automated warm-up over 30 days.
A new mailbox gets a 30-day automated warm-up: Strkr sends 5 to 50 messages a day to a reciprocating network of warmed inboxes, replies open and respond on a human-like cadence, and the sender-reputation score ramps from "cold" to "trusted" by day 30. The warm-up runs continuously in low volume even on active mailboxes to maintain the reputation.
DKIM, SPF, DMARC verifier
Pre-flight check before the sequence runs.
Before a sequence runs, Strkr verifies DKIM alignment, SPF alignment, and DMARC alignment on the sending domain. If any check fails, the sequence does not launch and the admin sees a specific remediation step. The pre-flight pattern catches the deliverability issues that would otherwise burn two weeks of send volume before the SDR notices.
Reply classifier
Positive, neutral, negative, OOO, unsubscribe.
Strkr AI classifies every reply into one of six buckets with confidence surfaced. Positive replies pop to the top of the SDR's queue with the deal auto-created on the matched contact. OOO replies trigger a resume-sequence delay to the OOO return date. Unsubscribe replies trigger immediate tenant-wide suppression. The 60 to 90 minutes of daily triage drops to 5 to 10 minutes.
Per-step attribution
See which step pulled which reply.
The sequence analytics shows reply rate per step per variant: step 1 is pulling 2.1 percent, step 2 is pulling 4.7, step 4 is pulling 0.3 (and should probably be retired). The variant-level view compares two subject lines on step 1 or two body variants on step 3, so iteration lands on specific templates with specific performance deltas.
Suppression at tenant scope
Unsubscribe once, suppressed everywhere.
When a prospect replies "please remove" or hits the unsubscribe link, the contact enters tenant-level suppression that intersects every current and future sequence. The audit log shows which sequence the suppression was triggered on and the exact reply or link click that triggered it, which satisfies the CAN-SPAM, CASL, and GDPR audit requirements in one surface.
Bounce handling
Hard bounces removed, soft bounces retried.
Hard bounces (invalid address) are automatically removed from the sequence and marked on the contact record. Soft bounces (mailbox full, server error) retry on a backoff schedule up to 3 attempts. The bounce rate per sequence is tracked on the deliverability dashboard, with the rule-of-thumb threshold that a sequence over 2 percent hard bounce should pause and audit the list source.
Templates by motion
The library organized by what the sequence is actually doing.
A template is only useful if it fits the motion. The library is sliced by motion so the SDR picks a starting point that matches the specific job to be done, not a generic "best cold email" list. Each motion has 4 to 7 templates with the common pattern annotations: when it works, when it fails, what to vary.
Event-triggered outreach
Funding, exec hire, product launch, acquisition.
Templates built around a specific trigger event: Series B announcement, new VP of Sales hired, product launch, acquisition. These convert at 2 to 4 times the generic baseline because the opener names a specific thing. The library ships 6 variants per trigger type, with the fallback rules for when the event detail is thin.
Account-based outreach
Named-account multi-contact cadence.
An ABM template suite coordinates outreach across 3 to 5 contacts at a named account: the VP, the director, the manager, the practitioner. The templates are coordinated so each contact gets different messaging, nobody gets the same email the other person at the company just got, and the account thread shows the full outreach landscape on the Strkr account record.
Reactivation of dormant leads
Reach back to leads from 6 to 24 months ago.
A reactivation template suite re-engages leads from prior quarters that did not close. The opener acknowledges the gap, references the previous conversation if the Strkr record has it, and offers a new reason to reconnect (new product, new case study, specific industry development). Reactivation campaigns typically pull 3 to 5 percent reply on a well-maintained list.
Breakup / final touch
The last email of a sequence that keeps 40 percent of the response volume.
The breakup email at the end of a 5 to 7 step sequence often pulls more replies than any single middle step. The library ships 5 breakup variants ranging from humorous to direct to acknowledging-the-noise. Breakup emails are the most-copied template in B2B outbound, which is also why vendor libraries have burned through most of them. Strkr's variants are re-authored quarterly against reply-rate data.
Mutual-connection warm intro
The "{{mutual_connection}} suggested I reach out" opener.
When a Strkr contact record has a LinkedIn-detected mutual connection with the prospect, the template references the mutual by name with a fallback that skips the sentence if no mutual exists. These templates convert at 4 to 7 times the cold baseline, which is why the token-fallback logic matters: a template that reads "Hi Sarah, {{mutual}} suggested I reach out" with an empty mutual flags as spammy immediately.
Vertical-specific openers
Templates seasoned for 12 specific verticals.
A SaaS buyer and a legal firm partner respond to very different cold outreach. The library ships vertical-specific template packs for SaaS, financial services, legal, healthcare, manufacturing, retail, education, non-profit, government, logistics, agencies, and professional services. Each pack has 4 to 6 openers calibrated for the vocabulary and friction patterns of the vertical.
Referral-request templates
Ask a current contact for a routed intro.
The highest-converting outbound is a referral intro from a current customer or warm contact. The library ships 4 templates for the referral-request motion: ask the champion for an intro to a peer, ask the executive for an intro at a related company, ask a former colleague for an intro at their new company. The templates are brief, specific, and offer the recipient an easy "yes/no/can't help" exit.
Industry-trigger reactive
React to an industry news item that affects the buyer.
When an industry event moves the buyer's priorities (a regulatory change, a competitor exit, a market shift), reactive outbound converts well. The library ships template patterns for industry-trigger openers, with the key variable being the specific event that moved. These templates have a short useful life (reactive outbound burns out in 2 to 4 weeks after the trigger) and are built to be customized before send.
The attribution and iteration layer
What separates a 3 percent reply program from a 7 percent one.
Teams that pull consistent 5-plus percent reply rates share a specific pattern: they treat the template library as a living inventory with attribution, variant testing, and quarterly retirement of underperforming variants. The capabilities below are the infrastructure that enables that pattern.
A/B variant testing
Two subject lines, 50-50 split, winner declared at 500 sends.
Set up a 50-50 variant test on a single step: variant A subject line, variant B subject line. Strkr sends the first 500 messages 50-50 and declares a winner at statistical significance (chi-squared test over opens and replies). The winning variant then runs on the remaining list. The experiment is logged with the full statistical trace so a RevOps lead can audit the methodology.
Cohort analysis
Compare the May SaaS cohort to the June SaaS cohort.
The analytics layer slices sends by cohort: the SDR running the sequence, the vertical, the month, the template version. The May cohort for a specific vertical pulled 4.1 percent reply; the June cohort pulled 2.8. The drop surfaces as a question: did the template get stale, did the market shift, did the ICP widen. The cohort view makes the question legible.
Reply-reason tagging
Why did they reply positively?
When a reply classifier marks a reply positive, the SDR can tag the reply reason: timing (ready to evaluate), specific pain (named a problem), referral (passed to someone else), warm interest (not now, but keep in touch). Reply-reason data drives the next quarter's template design: if timing-based positives spike, the sequence can lead with urgency; if pain-specific replies dominate, the opener should name the pain explicitly.
Deliverability score
Per-mailbox reputation tracked daily.
The deliverability dashboard shows a reputation score per connected mailbox updated daily: spam complaint rate, bounce rate, inbox-placement sample, and the overall reputation grade. A mailbox trending down gets flagged before the deliverability tanks completely, with specific remediation steps (reduce daily send, extend warm-up, retire the subject line that spiked complaints).
Reply attribution to deal
The positive reply becomes a Strkr task on the deal.
When the reply classifier tags a reply positive, Strkr opens a deal on the matched contact (or updates the existing deal), creates a task for the AE, and attaches the full email thread to the deal record. The handoff from outbound to deal cycle happens in the same system, which eliminates the common pattern of positive replies going cold in a shared inbox for 3 days before anyone sees them.
Template retirement workflow
Retire variants that drop below the threshold.
Each quarter, the analytics layer flags template variants that pulled below the retire-threshold (common defaults: below 1.5 percent reply after 1,000 sends, or 10 percent spam complaint rate). The RevOps lead reviews the flagged variants, retires them from active sequences, and the template library stays alive instead of calcifying. The common failure mode in cold outbound programs is running the same templates for 18 months after they stopped working.
Head-to-head
Strkr vs Smartlead or Instantly for cold email specifically.
Smartlead and Instantly are the leaders in the standalone cold-email vendor category, both strong on deliverability stack and sender rotation. The structural question is what happens after a positive reply, which is where a standalone tool hands off to a different system and the thread goes cold.
Feature
Strkr
Smartlead / Instantly
Template library size
40-plus annotated by motion with reply-rate data
Shared templates community-contributed
Mailbox warm-up
Native 30-day warm-up on connected domain
Yes, native warm-up pool
DKIM/SPF/DMARC pre-flight
Blocked send on alignment failure
Warning in UI, send not blocked
Reply classification
Strkr AI with confidence, six-bucket taxonomy
Native reply tagging in standalone tool
Attribution of reply to deal
Native on the Strkr deal record
Via CRM push integration
Variant A/B testing
Statistical significance declaration
Yes, in-app
Suppression scope
Tenant-wide across every sequence
Workspace-scoped
Deliverability dashboard
Per-mailbox reputation score tracked daily
Per-campaign stats, mailbox view available
Pricing
Included on paid Strkr tiers
~97 USD/mo per 10k sends plus mailbox fees
Does CRM live in same system
Yes, same record for cadence and deal
No, CRM is a separate integration
How teams use Strkr
How teams run cold email programs on Strkr today.
The patterns below come from customer tenants running cold email as a primary outbound channel. The common pattern across all five: deliverability stack ran correctly, templates got iterated monthly against reply data, and the handoff from positive reply to AE deal happened inside the same system.
Series A SaaS, 4-SDR team
Six-template rotation across SMB and mid-market.
A 4-SDR Series A team runs a 6-template rotation across SMB (3 templates) and mid-market (3 templates) with 30-day A/B rotation on step 1 subject lines. Steady-state send volume: 1,800 cold emails per SDR per week. Reply rate: 4.3 percent on SMB, 6.1 percent on mid-market. The templates are retired every quarter against the reply-rate floor and replaced with new variants built against the latest industry triggers. First meeting booked per 100 sends: roughly 1.2 at SMB, 1.8 at mid-market.
Agency with 12 client campaigns
Per-client sequence with shared deliverability pool.
A 12-client agency runs a separate cold email program per client with shared infrastructure: per-client sending domain, per-client mailbox pool, shared Strkr tenant with workspace separation. The warm-up and rotation happens automatically; the agency only touches the strategy layer. The agency bills a fixed-fee per client plus a success fee on meetings booked, and the margin runs 50 to 60 percent after infrastructure cost because the ops layer is automated.
Dev-tools company, OSS-adjacent outbound
Templates seasoned for CTO and VP of Engineering buyers.
A dev-tools company sells to CTOs and VPs of Engineering, who respond poorly to generic SaaS templates. They run a 4-step sequence with templates that reference the specific GitHub repo activity, the recent conference talk, or the open-source contribution of the recipient. Reply rate: 7.4 percent, which is 3 times the vendor-reported benchmark for cold outbound. The template library is maintained by the founder, not an SDR, because the technical fluency requirement is high.
Enterprise ABM, 65-rep team
Account-coordinated multi-contact outreach.
A 65-rep enterprise team runs ABM: 400 named accounts, 3 to 5 contacts per account, coordinated outreach so the VP, the director, and the manager at the same company get different openers over a 4-week window. The templates are coordinated through a per-account playbook on the Strkr account record. Meeting-set rate on named accounts runs 18 percent over the 4-week window, which is a step-change above the per-contact cold baseline because the account thread converges on a single conversation.
Reactivation program, 24-month book
Lost-deal reactivation runs 3.9 percent reply.
A mid-market team ran a reactivation campaign against 2,100 lost deals from the previous 24 months. The template referenced the previous conversation (pulled from the Strkr deal record), acknowledged the gap, and offered a new reason to reconnect. Reply rate on reactivation: 3.9 percent, well above the vendor benchmark for cold outbound. Of the 82 positive replies, 14 converted to active deals, which is a 68,000 dollar revenue contribution against a two-week campaign spend of under 200 dollars.
Templates that iterate against actual reply data.
Start a 14-day Strkr trial, connect your sending domain, pass the DMARC pre-flight, and launch a sequence from the shipped template library. Positive replies land as Strkr tasks on the deal record, which is where the cold-email motion is supposed to end.
What does the Strkr template library actually include?
The library ships 40-plus annotated templates organized by motion: event-triggered outbound (6 funding/exec-hire/product-launch variants), account-based coordinated outreach (per-persona variants for the VP, director, manager, practitioner), reactivation (6 lost-deal and dormant-lead variants), breakup/final-touch (5 variants ranging from humorous to direct), mutual-connection intro (with fallback logic for missing mutual), vertical-specific packs (SaaS, financial services, legal, healthcare, manufacturing, retail, education, nonprofit, government, logistics, agencies, professional services), and industry-trigger reactive templates. Every template carries the observed reply-rate band from the Strkr customer base in similar segments, so the SDR picks starting points based on data, not vendor marketing.
How does Strkr handle Google and Microsoft bulk-sender authentication?
Before a sequence runs, Strkr performs a pre-flight check on the sending domain: DKIM alignment, SPF alignment, DMARC alignment (p=none at minimum), and the one-click unsubscribe header requirement that both Google and Microsoft enforce as of February 2024. If any check fails, the sequence does not launch and the admin surface shows a specific remediation path with the DNS records required. This prevents the common silent failure where a team runs cold outbound for two weeks before realizing their delivery rate collapsed because the DMARC policy was wrong.
What is the recommended daily send volume per mailbox?
Industry-safe thresholds for cold email in 2026: a new Google Workspace or Microsoft 365 mailbox should send under 50 cold emails per day during the first 10 days of warm-up, ramping to 150 by day 30, and holding at 200 to 300 at steady state. Mailboxes over 300 daily cold sends have measurably higher inbox-placement risk. For a team pushing 10,000 daily sends, that implies roughly 40 to 50 active mailboxes on rotation. Strkr's warm-up and rotation engine handles the ramp automatically and prevents a single mailbox from exceeding the configured cap.
How does the reply classifier handle ambiguous or multi-signal replies?
The classifier returns a bucket (positive, neutral, negative, out-of-office, unsubscribe, auto-reply) with a confidence score. Replies above the high-confidence threshold auto-route (positive replies open a deal, OOO replies defer the sequence to the return date, unsubscribes trigger suppression). Replies below the high-confidence threshold queue for human review on the SDR surface with the classifier's best guess and the reasoning. The confidence surfacing is deliberate: it gives the SDR a 90-second review on edge cases rather than a false auto-handling that costs a lead.
Can I bring my own templates into the Strkr library?
Yes. Every tenant can import custom templates alongside the shipped library. Imported templates participate in the same analytics layer: reply rate per step per variant, cohort analysis, retirement workflow. Teams that already run successful cold outreach keep their winning templates and layer in the Strkr starter library for new motions they are not currently running. The variable library (first_name, company, recent_funding, tech_stack_signal) is shared, so imported templates can reference the same fallback-aware tokens.
Does Strkr support LinkedIn automation alongside cold email?
LinkedIn connection requests and messages are supported as cadence steps alongside email, voicemail tasks, and manual tasks. The implementation respects LinkedIn's terms of service and the per-day connection limits (Strkr enforces a conservative 20 to 25 connection requests per day per account to stay well under the throttle thresholds LinkedIn applies to high-volume senders). The multi-channel sequence (email step, LinkedIn connection, follow-up email, LinkedIn message) runs on the same Strkr record and attribution logic, which is a meaningful advantage over running email in Smartlead and LinkedIn in a separate automation tool like Phantombuster.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
