Precogs Outbound HQ

Emails Sent

this week

Open Rate

target: >50%

Reply Rate

target: 3-8%

Meetings Booked
0
this week

Bounce Rate

target: <2%

Positive Replies

total

📊 Daily Log

Date	Sent	Opens	Replies	Positive	Bounced	Meetings

💰 Pipeline

Leads

→

Demos

→

Opps

→

Won

🌐 Domain & Email Setup

0/8

Buy 3-5 secondary domains (getprecogs.com, precogs-security.com, etc.) Create Google Workspace mailboxes (3 per domain) SPF records configured on ALL domains DKIM configured on ALL domains DMARC configured on ALL domains Custom tracking domain (track.getprecogs.com) Warmup running 14+ days on ALL mailboxes Inbox placement >95% confirmed

🚀 Product Readiness

0/8

App is stable and fully deployed (no critical bugs) GitHub scan working end-to-end (SAST, SCA, IaC, Container) GitLab scan working Auto-Fix feature working and tested Welcome email sent on signup (via Brevo) First scan completion email working Trial expiry email sequence active Onboarding flow tested by 3+ people

📬 Mailbox Health

Mailbox	Domain	Day	Inbox %	Status

✅ Compliance

0/5

Unsubscribe line in every cold email Company address in email signature GDPR: legitimate interest basis documented Global suppression list created Auto-remove non-responders after 90 days

🎯 Ideal Customer Profile

Primary: Security Buyer

Title	CISO, VP Security, Head of AppSec
Company	200-5000 employees
Industry	Fintech, SaaS, HealthTech, Banking
Tech	GitHub/GitLab, CI/CD, uses AI coding tools
Geo	UK → EMEA → US
Trigger	Recent funding, hiring security, posted DevSecOps job

Secondary: Engineering Buyer

Title	VP Engineering, CTO, DevSecOps Lead
Company	50-2000 employees
Industry	Same + Developer Tools
Tech	Actively using Copilot/Cursor
Geo	UK → US
Trigger	Growing dev team, scaling CI/CD

🔥 Multi-Channel Sequence (LinkedIn + Email)

LinkedIn pre-warming increases open rates by 40%. This is the full sequence — email alone gets 1-3% reply, multi-channel gets 5-12%.

Day -3

👤 LinkedIn: View Profile

View their profile. They see the notification and your name.

Just view — don't connect yet.

→

Day -1

🤝 LinkedIn: Connect

Send connection request with NO note (higher accept rate than with note).

No note = 40% accept vs 25% with note.

→

Day 0

✉️ Email 1: Pain + Curiosity

They recognise your name from LinkedIn → higher open rate. Lead with THEIR pain.

"What's your team's false positive rate on code scans right now?"

→

Day 2

👍 LinkedIn: Engage

Like or comment on their recent post. Stay on their radar.

Genuine comment — not "Great post!"

→

Day 3

✉️ Email 2: Social Proof

Share a data point or unique capability. Mention PII pre-LLM protection.

"We're the only platform catching PII before it's sent to AI assistants."

→

Day 5

💬 LinkedIn: DM

Short DM — different angle from email. Reference their work.

"Saw you're scaling the security team — built something you might find useful."

→

Day 7

✉️ Email 3: Free Scan Offer

Offer to scan one of their repos for free. Zero commitment, instant value.

"Want us to scan one repo? 5-min GitHub connect — we'll show you what we find. No call needed."

→

Day 12

✉️ Email 4: Breakup + Referral

Short, no pressure. Add referral ask for 5-10% internal warm intro rate.

"If you're not the right person, would you mind pointing me to who handles AppSec at {{company}}?"

⚡ 7 Multipliers That 3-5x Your Results

1. Free Scan Offer (replaces "Book a Demo")

Old CTA	"Worth a 15-min chat?"
New CTA	"Want us to scan one repo for free? Takes 5 min, no call needed."
Impact	3-5x higher conversion — zero commitment, instant value

2. Trigger-Based Timing

Funding	"Congrats on the round — scaling teams usually inherit security debt"
DevSecOps job	"Saw you're hiring — this might save you a headcount"
Major CVE	"CVE-2026-XXXXX impacts your stack — here's our analysis"
Impact	3-5x reply rate vs random timing

3. Reply Speed

<5 min	21% → meeting
<1 hour	8% → meeting
<24 hours	2% → meeting
Action	Set up Instantly → Slack webhook for instant alerts

4. Account-Based Multi-Threading

Method	Email 3 people at same company with different angles
CISO	"False positive fatigue" angle
VP Eng	"AI-generated code risk" angle
DevSecOps	"Free scan, see results in 5 min" angle
Impact	3x chance of getting a meeting per account

Sequence A: AI Code Security Gap

For VP Eng / CTO — the people who approved Copilot and are now worried

Email 1 — Day 0: Pain + Question
Subject: {{firstName}}, quick q about {{company}}'s AI code

Hi {{firstName}},

{{personalized_opening_line}}

Quick question — what percentage of your team's code is AI-generated now? Most engineering leads I talk to say 30-50%.

The challenge is that 34% of Copilot-generated functions contain OWASP Top 10 vulnerabilities, and traditional SAST tools weren't built to catch AI-specific patterns.

Curious how you're thinking about this at {{company}}.

Email 2 — Day 3: Insight + Data
Subject: re: AI code at {{company}}

One more data point — we built Precogs specifically for AI-generated code security. Early results show teams catch 3-4x more real vulnerabilities vs SonarQube or Snyk Code, with under 2% false positive rate.

The biggest surprise for most teams: PII and API keys leaking INTO AI assistants. Developers paste code containing customer data into Copilot prompts — that data goes to external servers. Under GDPR, that's a reportable incident.

No one's tooling for this yet.

Email 3 — Day 7: Free Scan
Subject: free scan for {{company}}?

Instead of a demo, want us to just scan one of your repos?

Takes 5 minutes to connect via GitHub — we'll run SAST, SCA, IaC, container, and PII detection, then show you what we find.

No call needed. No credit card. Just real results on YOUR code.

Want me to set it up?

Email 4 — Day 12: Breakup + Referral
Subject: closing the loop

If AI code security isn't a priority at {{company}} right now, totally understand. I'll close this thread.

If you're not the right person, would you mind pointing me to who handles AppSec? Happy to take an intro.

Sequence B: PII Leakage / Compliance

For CISO / DPO / Head of Compliance — the people who get fired when GDPR violations happen

Email 1 — Day 0
Subject: {{firstName}} — AI compliance gap at {{company}}?

Does {{company}} have visibility into what data developers are pasting into AI coding assistants?

We're seeing a pattern: developers copy-paste code containing API keys, database credentials, and customer PII into Copilot/Cursor prompts. That data is sent to external LLM servers.

Under GDPR and SOC2, that's potentially a reportable data breach — but most security teams have zero visibility into it.

Is this on your radar?

Email 2 — Day 3
Subject: re: PII in AI prompts

To put a number on it — in our scans, we find an average of 12 PII exposure events per 1,000 lines of AI-assisted code. API keys, connection strings, customer email addresses — all sent to third-party LLM providers.

Precogs is the only platform that catches this BEFORE the data leaves the developer's environment. Think of it as a DLP layer for AI coding tools.

Email 3 — Day 7
Subject: 5-min scan of one {{company}} repo?

No demo, no pitch — just results. Connect one GitHub/GitLab repo (takes 5 min). We'll run a full scan: SAST, SCA, IaC, container, and PII-in-AI detection.

You get a real report on real code. If the findings are useful, we talk. If not, you got a free audit for your next SOC2 review.

Email 4 — Day 12
Subject: closing this thread

If PII in AI tools isn't a priority right now, I'll drop this.

One thought — if {{company}} is going through SOC2 or ISO 27001 renewal, auditors are starting to ask about AI code governance. Might be worth having this in your back pocket.

If you're not the right person, who handles data protection or AppSec at {{company}}?

Sequence C: Competitor Displacement

For known Snyk/SonarQube users — detected via Clay/BuiltWith enrichment

Email 1 — Day 0
Subject: {{firstName}}, re: {{company}}'s Snyk setup

Not here to bash Snyk — they're genuinely good at SCA and dependency scanning.

But the teams I talk to who use Snyk still struggle with two things:
1. Noisy SAST results (Snyk Code's false positive rate)
2. Zero visibility into PII leaking into AI coding assistants

That's the specific gap Precogs fills. We're not a replacement — we're the layer that covers what Snyk doesn't.

Is this something you've noticed at {{company}}?

Email 2-4: Same cadence as Sequence A (insight → free scan → breakup + referral)

🧠 Smart Outreach Ideas

The 1% effort that makes 10x difference. Use these alongside sequences.

1. Reverse Trial: Scan Their Public Repo

How	Find target's public GitHub repos. Scan with Precogs. Email the real results.
Email	"Found 3 issues in {{company}}/{{repo}}: SQL injection in /api/users, hardcoded AWS key, PII in logs. Full report attached."
Impact	Highest-converting outbound email possible. You're giving value before asking.

2. "CVE of the Week" to Prospect List

How	Every Monday, email prospects about a CVE that affects their stack
Email	"CVE-2026-XXXXX affects Django (your stack). Most SAST tools miss it. We catch it. Details: [blog link]"
Impact	Positions you as helpful, not salesy. 10x reply rate vs cold pitch.

3. Scan Famous Open-Source Projects

How	Scan top 50 Python/JS packages. Write up findings. Share on LinkedIn/Reddit/HN.
Output	"We scanned the top 50 PyPI packages. Here's what we found." → viral content
Impact	Generates inbound AND social proof for cold email.

4. CISO Dinner in London

How	Host dinner for 8-10 CISOs. Theme: "AI Code Security in 2026". No pitch.
Cost	£500-800 at a nice restaurant
Impact	Direct relationships = 3-5 pipeline deals per dinner.

🔄 Lead Lifecycle: Touch → Newsletter → Close

Everyone who engages goes into Brevo. Cold outbound feeds warm nurture which feeds pipeline.

Stage	Action	Tool	Add to Brevo?
LinkedIn View/Connect	View profile Day -3, connect Day -1	LinkedIn	No
Email 1-4 (cold)	4 emails over 12 days	Instantly	No (cold list stays in Instantly)
Any Reply	Respond <5 min. Even "not interested" = awareness	Instantly → Slack	YES — add to newsletter
Positive Reply	Book Cal.com, offer free scan, move to pipeline	Cal.com	YES — "Warm Lead" segment
Free Scan	Connect repo, run scan, share results	Precogs app	YES — "Product User"
Demo	15-min screenshare showing THEIR results	Cal.com + Zoom	YES — "Demo Attended"
Trial	14-day full access + weekly check-in	App + Brevo auto	YES — "Trial Active"
Close	Proposal → negotiate → sign	Manual	Move to "Customer"
Post-Close	Onboard → case study → ask for referral	Brevo + Manual	"Customer" segment

📢 Other Channels (Feed the Same Pipeline)

LinkedIn Content (3x/week)

Tue	Data/insight: "We scanned 10K AI-generated functions. 34% had OWASP vulns..."
Thu	Controversial take: "Your SAST tool's 35% FP rate isn't a bug — it's a business model"
Sat	Behind-the-scenes: "Building Precogs — here's what we learned this week"
Why	When cold prospects Google you, LinkedIn = instant credibility

OWASP + Conferences

OWASP London	Speak on "AI Code Security Gap" — access to 100+ practitioners
BSides London	Lightning talk or sponsor — community credibility
InfoSec Europe	Attend, network (ExCeL, June)
Talk topic	"What Copilot-Generated Code Looks Like Under a Scanner"

UK Gov / NCSC

Cyber Essentials	Align messaging: "supports Cyber Essentials compliance"
NCSC Accelerator	Apply — credibility + gov pipeline
G-Cloud	Register on Digital Marketplace for gov procurement
FCA angle	Fintech targets: "FCA now requires code security governance"

Developer Communities

Reddit	r/netsec, r/devsecops — share research, never sell
Hacker News	"Show HN: Precogs" — time it with a strong data post
Dev.to	Technical blog posts on AI code security
Rule	NEVER sell in communities. Share insights. Let them find you.

📅 Cal.com Integration

Use Cal.com for frictionless booking. One-click scheduling = 2x meeting conversion vs back-and-forth emails.

Setup

Link	cal.com/rajnish-precogs/15min
In emails	Add to positive reply: "Here's my calendar — grab any slot: [link]"
In signature	Add to all email signatures (Instantly merge tag)
Buffer	Set 15-min buffer between meetings in Cal.com settings

Pro Tips

Don't	Put Cal.com link in first cold email — looks presumptuous
Do	Send it ONLY after they reply positively
Set	Confirmation + reminder emails in Cal.com (reduces no-shows by 40%)
Track	Cal.com webhooks → your pipeline tracker

⚙️ Apollo → Clay → Instantly Pipeline

🔍

1. Apollo

Find prospects by ICP filters

Title: CISO, VP Eng, CTO
Size: 200-5000 employees
Industry: Fintech, SaaS, Health
Geo: UK → EMEA → US
Export 500-1000 per segment
Verify emails (remove "guessed")

→

🧪

2. Clay

Enrich + personalise at scale

Tech stack (BuiltWith) — using Snyk?
Recent funding (Crunchbase)
Security hires (LinkedIn)
AI tool usage (job postings)
AI-generated personalised opening line
Remove existing customers/warm contacts

→

📧

3. Instantly

Send sequences + manage warmup

Import enriched CSV from Clay
Map Clay columns → merge tags
Assign sequence (A, B, or C)
Set limits: 20-50/day per mailbox
Schedule: Mon-Thu, 8-11 AM local
Enable reply detection + OOO pause

→

🔥

4. Positive Reply

Convert to pipeline

Respond within 2 hours
Book Cal.com meeting
Promote to MarketingContact DB
Add to Brevo warm nurture
Track in pipeline (Lead → Demo)
Never re-cold-email this person

📊 Benchmarks: Email Only vs With Multipliers

Metric	Email Only	+ LinkedIn	+ Free Scan	+ Triggers
Open Rate	45%	60%	60%	65%
Reply Rate	2%	5%	7%	10%
Positive Reply	0.8%	2%	3.5%	5%
Meeting/100	0.5	1.5	2.5	4+
Bounce Rate	<3%	<2%	<1%	<1%

🚫 Never Do

❌ Send cold email from precogs.ai — ruins your primary domain

❌ Send before warmup completes (14+ days)

❌ Blast email lists via Brevo — will get you banned

❌ Use HTML/images in cold email — triggers spam filters

❌ Pitch in first message — ask a question instead

❌ Skip email verification — >3% bounce = blacklist

❌ Re-email someone who said "not interested"

❌ Email competitors (Snyk, SonarQube, Checkmarx employees)

❌ Email personal Gmail/Yahoo — B2B only (company domains)

💬 Reply Templates (Objection Handling)

Most meetings are won or lost in the REPLY, not the cold email. Copy-paste these.

"Not interested"

Thanks for letting me know, {{firstName}}. Totally respect that.

Just curious — is it because the timing's off, or you're genuinely happy with your current setup?

Either way, I'll close this thread. Appreciate the reply.

Why: 15-20% of "not interested" replies convert when you ask WHY. The soft close removes pressure.

"Send me more info"

Sure thing! Here's a quick overview:

→ Precogs runs SAST + SCA + IaC + Container + PII detection in one platform
→ False positive rate under 2% (vs 30-40% industry avg)
→ Catches PII leaking into AI assistants (Copilot/Cursor) before it leaves your IDE

Easiest way to see it: we can scan one of your repos in 5 min — no call needed. Want me to set that up?

Why: Don't just send a PDF. Give 3 bullets + re-anchor to the free scan CTA.

"How much does it cost?"

Great question. Pricing depends on team size and scan volume, but most teams our size pay between £500-2,000/month.

Happy to get you exact pricing — would a quick 15-min call work? Or I can send you a self-serve trial link if you'd prefer to test first.

Why: Give a range (anchoring), then offer both paths — call for enterprise, self-serve for smaller.

"We already use Snyk/SonarQube"

Makes sense — they're solid tools, especially for SCA.

Most teams I speak to use Snyk for dependency scanning but still struggle with noisy SAST results and have zero visibility into PII leaking into AI code assistants.

We're not a rip-and-replace — we fill the gaps. Worth comparing results on one repo? Takes 5 min.

Why: Validate their choice, position as complementary, then re-anchor to free scan.

"Who are you?"

Fair question! I'm {{yourName}}, co-founder at Precogs. We build an AI-native code security platform — think SAST, SCA, and PII detection in one scan.

Reached out because {{company}} fits the profile of teams that get the most value from what we do. Happy to show you in 5 min — no commitment.

Positive reply → Book meeting

Awesome, glad this resonated! Here's my calendar — grab any slot that works for you:

→ https://cal.com/rajnish-precogs/15min

Looking forward to it. In the meantime, I can set up a free scan of one repo so we have real data to discuss on the call.

Why: Send Cal.com link immediately. Offer pre-scan so the demo has real data — much more compelling.

✍️ Email Signature Template

Use this in ALL cold email mailboxes. Plain text only — no images, no HTML.

Best, {{firstName}} {{lastName}} Co-founder, Precogs 🔗 precogs.ai | 📅 Book a chat AI-native code security — SAST, SCA, PII detection in one scan. Unsubscribe: {{unsubscribe}}

⚠️ Instantly auto-inserts {{unsubscribe}}. Cal.com link only after positive reply.

📦 Content Assets (have ready before Week 3)

One-pager / battle card PDF (1 page, 3 key differentiators) Precogs vs Snyk comparison table (for Seq C replies) Screenshot of scan results (anonymised) for "send me more info" replies Landing page for cold traffic: precogs.ai/security or precogs.ai/demo Case study or testimonial (even from beta user) 30-second Loom video: "Here's what a Precogs scan looks like"

🚫 Suppression List (Never Email)

❌ Existing customers & trial users (check Brevo/app DB)

❌ Competitor employees (Snyk, SonarQube, Checkmarx, Semgrep, Veracode)

❌ Investors, advisors, partners

❌ Anyone who previously unsubscribed or said "not interested"

❌ Government / public sector (different procurement, skip for now)

❌ Companies with <20 employees (too small for B2B sale)

Upload to Instantly as "Global Block List". Add to Clay as exclusion filter.

📋 Post-Meeting Follow-Up

Same day	Send recap email: key points discussed, next steps, attach one-pager
Day 2	If they said "need to check with team" — offer to do a 10-min demo for their team
Day 5	Follow up: "Any questions from the team? Happy to jump on a quick call"
Day 10	Share a relevant blog post, CVE analysis, or case study (stay top of mind)
Day 14	Soft close: "Where are you at on evaluating? Happy to extend the trial"
Day 21	Final: "Closing the loop — should I check back next quarter?"

Add to Brevo as automated nurture sequence for demo attendees.

💰 Monthly Budget

Tool	Plan	Cost/mo	What for
Apollo	Professional	$99	Prospecting, verified emails, saved searches
Clay	Explorer	$149	Enrichment, AI personalisation, tech stack data
Instantly	Growth	$97	Email sending, warmup, reply tracking
Domains (3)	—	~$5/ea	Secondary sending domains (one-time/year)
Google Workspace	Business Starter	$45	9 mailboxes × $5/ea
Cal.com	Free	$0	Meeting scheduling
Total		~$400/mo	ROI: 1 closed deal = £5K-20K ARR → 12-50x return

🟡 Week 1 — List Building & Sequences (Apr 28 - May 2)

0 emails — warmup day 3-7

Apollo List Building

Mon 28	Create Saved Search: CISO/VP Security, Fintech, 200-5000 emp, UK
Mon 28	Create Saved Search: VP Eng/CTO, SaaS, 50-2000 emp, UK
Tue 29	Export 500 prospects per segment (1000 total)
Tue 29	Remove "guessed" emails — only keep "verified"
Wed 30	Deduplicate against existing customers and warm contacts
Wed 30	Create 3rd Saved Search: DevSecOps/AppSec Engineer, 100-5000 emp
Thu 1	Export additional 500 from Segment 3
Fri 2	Final verified list: 1500 prospects ready for Clay

Write Email Sequences

Mon 28	Write Sequence A (4 emails): False Positive Fatigue — for CISOs
Tue 29	Write Sequence B (4 emails): AI Code Security — for VP Eng/CTO
Wed 30	Write Sequence C (4 emails): Competitor Displacement — for Snyk users
Thu 1	Create 3 A/B subject line variants per sequence
Thu 1	Set up Instantly → Slack webhook for reply alerts
Fri 2	Send test sequence to 5 internal accounts — check rendering

✅ Success criteria: 9 mailboxes warming, 1500 verified prospects exported, all sequences written.

🟡 Week 2 — Enrichment & Load (May 5-9)

0 emails — warmup day 10-14

Clay Enrichment

Mon	Import Apollo exports into Clay tables
Mon	Add enrichment: BuiltWith tech stack (detect Snyk/SonarQube users)
Tue	Add enrichment: Crunchbase funding (last 12 months)
Tue	Add enrichment: LinkedIn job postings (DevSecOps/Security hires)
Wed	Add AI column: personalised opening line per prospect
Wed	Segment: Snyk users → Sequence C, Recently funded → trigger email
Thu	Export enriched CSV, map columns to Instantly merge tags
Fri	Import into Instantly, assign to Sequence A (CISO) / B (VP Eng)

Write Email Sequences

Mon	Write Sequence A (4 emails): False Positive Fatigue — for CISOs
Tue	Write Sequence B (4 emails): AI Code Security — for VP Eng/CTO
Wed	Write Sequence C (4 emails): Competitor Displacement — for Snyk users
Thu	Create 3 A/B subject line variants per sequence
Thu	Set up Instantly → Slack webhook for reply alerts
Fri	Set up Cal.com booking link + confirmation emails
Fri	Send test sequence to 5 internal accounts — check rendering

✅ Success criteria: All 3 sequences written + A/B variants, Clay enrichment complete, prospects segmented and loaded into Instantly. Warmup at Day 10+.

🟢 Week 3 — Soft Launch (May 12-16)

~300 emails | 20/mailbox/day

Daily Actions

Mon	Verify inbox placement >95% on all mailboxes. GO/NO-GO decision.
Mon	Activate Sequence A ONLY — UK Fintech CISOs — 20/mailbox/day
Daily	LinkedIn pre-warm: View 20 profiles, send 10 connection requests
Daily	Check Instantly dashboard: opens, replies, bounces at 9 AM and 5 PM
Daily	Respond to ANY reply within 5 minutes (Slack alerts)
Fri	Week 3 review: open rate, reply rate, bounce rate. Kill any mailbox >3% bounce.

Expected Results

Sent	~300 (20/mailbox × 15 mailbox-days)
Opens	150-195 (50-65%)
Replies	3-9 (1-3%)
Positive	1-3
Meetings	0-1
🚨 Red flag	Open rate <30% = deliverability issue. STOP and investigate.

🟢 Week 4 — A/B Test & Expand (May 19-23)

~375 emails | 25/mailbox/day

Key Actions

Mon	Analyse Week 3: which subject line got highest open rate? Kill losers.
Mon	Increase volume to 25/mailbox/day
Tue	Activate Sequence B for VP Eng/CTO segment
Wed	Start LinkedIn DMs (Day 5) for Week 3 prospects who didn't reply
Daily	Continue LinkedIn pre-warming for new batch
Fri	A/B results: compare Seq A vs Seq B open + reply rates

Expected Results

Sent	~375
Replies	4-12
Meetings	1-2
Cumulative	675 sent, 7-21 replies, 1-3 meetings

🟢 Week 5-6 — Scale & Optimise (May 26 - Jun 6)

~525-600/wk | 35-40/mailbox/day

Week 5: Scale

Action	Add EMEA segments (Germany, Netherlands, Nordics)
Action	Activate Sequence C (Competitor Displacement) for Snyk users
Action	Kill lowest-performing subject line variant
Action	Start "Free Scan" CTA on Email 3 for all sequences
Volume	35/mailbox/day → ~525/week
Meetings	1-3 expected

Week 6: Optimise

Action	Double down on best-performing sequence (highest reply rate)
Action	Add US East Coast segments (NYC, Boston fintech)
Action	Review pipeline: how many replies → demos → opportunities?
Action	Account-based: pick top 20 accounts, email 3 people each
Volume	40/mailbox/day → ~600/week
Cumulative	~2,200 sent, 25-60 replies, 5-12 meetings

🔵 Week 7-8 — Cruise & Scale Up (Jun 9-20)

~675-750/wk | 45-50/mailbox/day

Week 7: Cruise

Action	Buy 2 more domains + create 6 new mailboxes (start warmup)
Action	Refine ICP: who actually replies? Narrow down best-fit profile.
Action	Create trigger-based sequences (funding alerts, CVE alerts)
Action	Set up Google Alerts for breach news + CVE drops
Volume	45/mailbox/day → ~675/week

Week 8: Scale Up

Action	New domains go live (warmup complete) — add to rotation
Action	Scale to 50/mailbox/day across 15 mailboxes → 750/week
Action	Evaluate: do you need an SDR to handle reply volume?
Action	Build Week 9-12 plan based on what's working
Cumulative	~3,600 sent, 40-100 replies, 15-40 meetings
With multipliers	60+ meetings achievable ✅

⏰ Best Send Times (Recipient's Local Time)

Instantly sends in the recipient's timezone automatically. These are the windows to set.

Tuesday

🇬🇧 8:00-10:30 AM BST · 🇺🇸 8:00-10:30 AM ET

🔥 Best day overall

Wednesday

🇬🇧 8:00-10:30 AM BST · 🇺🇸 8:00-10:30 AM ET

✅ Strong performer

Thursday

🇬🇧 8:00-10:30 AM BST · 🇺🇸 8:00-10:30 AM ET

✅ Good for follow-ups

Monday

🇬🇧 9:00-11:00 AM BST · 🇺🇸 9:00-11:00 AM ET

⚠️ Inbox overload — send later

Friday

—

❌ Avoid — low open rates

Weekends

—

❌ Never send — looks spammy

💡 In Instantly: set send window to 8:00-10:30 AM, enable "Send in contact's timezone". US East (ET) and UK (BST) are the same window — just different clocks.

📈 Cumulative Projections (8 weeks)

Metric	Email Only	With Multipliers
Total emails sent	3,000	3,000
Total opens	1,350 (45%)	1,950 (65%)
Total replies	60 (2%)	150 (5%)
Positive replies	24 (0.8%)	105 (3.5%)
Meetings booked	10-12	40-60 ✅
Pipeline value	£50K-80K	£200K-400K
Closed deals	1-2	4-8

🔗 End-to-End Pipeline Architecture

Click any tool below to see setup tasks. Data flows left-to-right automatically once connected.

🔍

SOURCE

Apollo

Find leads

⚡

ENRICH

Clay

Personalise

📧

SEND

Instantly

Email sequences

📅

BOOK

Cal.com

Schedule demos

💌

NURTURE

Brevo

Newsletter

☁️ Firebase — Connected 💬 Google Chat — Connected 📧 Brevo — Connected 📨 Instantly — Awaiting API Key

💰 Monthly Stack Cost

Instantly$97

Apollo$99

Clay$149

G Workspace~$54

Domains~$3

Cal.comFree

BrevoFree

FirebaseFree

VercelFree

Total~$402/mo

getprecogs.com
1.	yasi@getprecogs.com
2.	rajnish@getprecogs.com
3.	natasha@getprecogs.com
precogs-security.com
4.	yasi@precogs-security.com
5.	rajnish@precogs-security.com
6.	natasha@precogs-security.com
tryprecogs.com
7.	yasi@tryprecogs.com
8.	rajnish@tryprecogs.com
9.	natasha@tryprecogs.com

📊 Daily Log

💰 Pipeline

🌐 Domain & Email Setup

🚀 Product Readiness

📬 Mailbox Health

✅ Compliance

🎯 Ideal Customer Profile

Primary: Security Buyer

Secondary: Engineering Buyer

🔥 Multi-Channel Sequence (LinkedIn + Email)

⚡ 7 Multipliers That 3-5x Your Results

1. Free Scan Offer (replaces "Book a Demo")

2. Trigger-Based Timing

3. Reply Speed

4. Account-Based Multi-Threading

Sequence A: AI Code Security Gap

Sequence B: PII Leakage / Compliance

Sequence C: Competitor Displacement

🧠 Smart Outreach Ideas

1. Reverse Trial: Scan Their Public Repo

2. "CVE of the Week" to Prospect List

3. Scan Famous Open-Source Projects

4. CISO Dinner in London

🔄 Lead Lifecycle: Touch → Newsletter → Close

📢 Other Channels (Feed the Same Pipeline)

LinkedIn Content (3x/week)

OWASP + Conferences

UK Gov / NCSC

Developer Communities

📅 Cal.com Integration

Setup

Pro Tips

⚙️ Apollo → Clay → Instantly Pipeline

1. Apollo

2. Clay

3. Instantly

4. Positive Reply

📊 Benchmarks: Email Only vs With Multipliers

🚫 Never Do

💬 Reply Templates (Objection Handling)

"Not interested"

"Send me more info"

"How much does it cost?"

"We already use Snyk/SonarQube"

"Who are you?"

Positive reply → Book meeting

✍️ Email Signature Template

📦 Content Assets (have ready before Week 3)

🚫 Suppression List (Never Email)

📋 Post-Meeting Follow-Up

💰 Monthly Budget

🔴 Week 0 — Infra Sprint (Apr 23-25)

Infrastructure (complete by Friday Apr 25)

Product Readiness (verify this week)

🟡 Week 1 — List Building & Sequences (Apr 28 - May 2)

Apollo List Building

Write Email Sequences

🟡 Week 2 — Enrichment & Load (May 5-9)

Clay Enrichment

Write Email Sequences

🟢 Week 3 — Soft Launch (May 12-16)

Daily Actions

Expected Results

🟢 Week 4 — A/B Test & Expand (May 19-23)

Key Actions

Expected Results

🟢 Week 5-6 — Scale & Optimise (May 26 - Jun 6)

Week 5: Scale

Week 6: Optimise

🔵 Week 7-8 — Cruise & Scale Up (Jun 9-20)

Week 7: Cruise

Week 8: Scale Up

⏰ Best Send Times (Recipient's Local Time)

📈 Cumulative Projections (8 weeks)

🔗 End-to-End Pipeline Architecture

Apollo.io

Clay

Instantly

Cal.com

Brevo