Account Snapshot
Product
QA consulting + test automation
Geography
US and Canada
ICP
B2B SaaS (20-500 employees)
Verticals
PropTech, Construction Tech, Logistics, Field Service
Leads Promised
2,000/month
Lead Source
Lead411 (PIQ sources)
Domains
6 domains, 27 days old
Status
2 active campaigns, transitioning to new infra
Executive Summary
Cold Email Viability: Moderate
QA automation is a real pain point for scaling SaaS teams, especially in asset-heavy verticals where downtime is expensive. The challenge is differentiation — every dev shop pitches "automated testing." The ownership model ("we maintain it, you don't") is the sharp edge, but the copy buries it.
Account Health: Yellow
Reply rates are 0.21% across both campaigns (5 replies from 2,357 contacted). Bounce rate on catch-all is 15.4% (list hygiene issue). Primary issue: ICP is too broad (4 distinct verticals, one generic sequence) and copy lacks vertical specificity.
Priority Actions
- Urgent Split into vertical-specific campaigns. One sequence cannot speak to PropTech, Construction Tech, Logistics, and Field Service simultaneously.
- This Week Get the case study PDFs. Extract specific numbers/outcomes for Step 3 and P.S. lines. Current copy references claims without proof.
- This Week Fix Step 2. It's 2 sentences with an empty paragraph. Zero value, zero reason to reply.
- Ongoing Monitor domain performance. At 6 months (Sept 17, 2026), if results haven't improved, flag for deeper infra review.
What's Working
- Infrastructure is clean. All 5 sending domains have valid SPF/DKIM/DMARC. New domains mean fresh reputation — no burn history.
- Sender persona is consistent (Skye Hood across all mailboxes). No identity confusion.
- 6-step sequence structure is appropriate for this market. SaaS buyers need multiple touches.
- Lead411 source isn't exhausted. Volume is achievable without hitting list fatigue.
What's Limiting Results
- Vertical-generic copy kills relevance. A PropTech CTO worries about resident portal uptime. A Construction Tech CTO worries about job site connectivity. A Logistics CTO worries about EDI integrations. The current sequence speaks to none of these.
- Heavy spintax reads AI-generated. Step 1 has 9 spintax points, but they're shallow synonym swaps. This doesn't vary the angle — it just shuffles words. Recipients can smell it.
- Claims without proof destroy credibility. "$50k-$80k per engineer" and "cut regression time by 70%" — specific numbers with zero attribution. Engineering buyers dismiss this instantly.
- Step 2 is a wasted touch. Two sentences, one empty paragraph. No new angle, no asset, no reason to engage.
- CTA repetition. Every email asks some variation of "want to see it?" By Step 4, recipients know the pattern and ignore it.
Campaign Performance
2,357
Total Leads Contacted
5
Total Replies
0.21%
Overall Reply Rate
15.4%
Catch-all Bounce Rate
| Campaign | Leads/Day | Contacted | Replies | Reply Rate | Bounces |
|---|---|---|---|---|---|
| Catch-all | 30 | 737 | 3 | 0.76% | 61 (15.4%) |
| Valids | 48 | 1,620 | 2 | 0.33% | 6 (1%) |
ICP + Campaign Lanes
Recommended Split
| Lane | Vertical | Core Pain | Personalization Hook |
|---|---|---|---|
| 1 | PropTech / Facility Management | Portal uptime, resident experience, PM system integration | {{property_management_platform}} or recent portfolio growth |
| 2 | Construction Tech | Job site connectivity, offline-first apps, subcontractor coordination | {{primary_app_type}} or equipment tracking |
| 3 | Logistics / Fleet / Supply Chain | EDI integrations, carrier API reliability, release velocity | {{primary_integration_type}} or tech stack mentions |
| 4 | Field Service | Dispatch reliability, mobile tech apps, SLA compliance | {{field_service_platform}} |
Questions for Client
- Can you share the case study PDFs? We need specific numbers and outcomes to make social proof credible.
- Which of the 4 verticals has your strongest track record? We should weight campaigns accordingly.
- Can you define the "QA automation roadmap" deliverable more concretely? Specificity increases reply rates.
- Do you have any current clients willing to do a quick reference call? Named testimonials beat generic claims.
Top 3 Copy Priority Actions
- Priority 1 Rewrite Step 1 with vertical-specific angles and kill 50% of the spintax. Use homework-based hooks (specific observations about their product, tech stack, or recent news). Move away from generic "manual regression" language.
- Priority 2 Get case study details and rewrite Steps 3 and 5. Replace "70% reduction" and "SaaS analytics team" with specific, verifiable outcomes from real clients.