Outbound Sales for DevTools at Pre-Seed
A step-by-step playbook for implementing outbound sales at a Pre-Seed-stage DevTools company. This guide covers everything from initial setup and team requirements to execution, measurement, and optimization — tailored specifically for DevTools companies with near-zero marketing budget and founders doing everything themselves. Includes specific KPIs, recommended tools, common pitfalls to avoid, and expert insights from Ehsan Jahandarpour.
Timeline: 3-6 months
Prerequisites
- ✓ Working MVP or beta product with at least 10 active users
- ✓ Clear understanding of target customer persona
- ✓ SOC 2 and supply chain security (SBOM) are increasingly required by enterprise buyers — ensure compliance before scaling
- ✓ CRM and email sequencing tools configured
- ✓ At least 5 closed deals to validate ICP assumptions
Step-by-Step Guide
Define your ideal customer profile
Build a detailed ICP based on company size, industry, tech stack, funding stage, and pain points. The more specific, the higher your response rates. For DevTools companies at the Pre-Seed stage, this step is particularly important given validating problem-solution fit.
Pro tip: Analyze your last 20 closed-won deals — what do those companies have in common? In the DevTools context, also consider: developer adoption resistance.
Build targeted prospect lists
Use data tools to build lists of companies and decision-makers that match your ICP. Enrich with intent signals and technographic data. For DevTools companies at the Pre-Seed stage, this step is particularly important given validating problem-solution fit.
Pro tip: Prioritize companies showing buying signals: hiring for relevant roles, using competitor tools, or raising funding. In the DevTools context, also consider: open-source competition.
Write personalized outreach sequences
Create multi-touch sequences across email, LinkedIn, and phone. Each message should reference something specific about the prospect company. For DevTools companies at the Pre-Seed stage, this step is particularly important given validating problem-solution fit.
Pro tip: First email should be under 100 words. Lead with their problem, not your product. In the DevTools context, also consider: bottom-up vs top-down sales tension.
Set up sales tech stack
Implement a CRM, email sequencer, dialer, and LinkedIn automation tool. Connect everything for unified tracking and reporting. For DevTools companies at the Pre-Seed stage, this step is particularly important given validating problem-solution fit.
Pro tip: Start with HubSpot or Salesforce + Apollo or Outreach. Do not over-tool early. In the DevTools context, also consider: proving ROI beyond developer happiness.
Execute and iterate on outreach
Launch sequences, track open/reply rates, A/B test subject lines and CTAs. Aim for 30-50% open rates and 5-10% reply rates. For DevTools companies at the Pre-Seed stage, this step is particularly important given validating problem-solution fit.
Pro tip: Send outbound Tuesday through Thursday, 8-10am in the prospect timezone for best response rates. In the DevTools context, also consider: developer adoption resistance.
Build the handoff to AEs
Create a clear process for SDRs to qualify and hand off meetings to account executives. Define qualification criteria and handoff protocols. For DevTools companies at the Pre-Seed stage, this step is particularly important given validating problem-solution fit.
Pro tip: Record every discovery call and review weekly as a team — pattern recognition improves qualification. In the DevTools context, also consider: open-source competition.
Expected Outcomes
- ✓ 15-25 qualified meetings booked per SDR per month targeting DevTools
- ✓ Email reply rate above 8% for personalized outbound sequences
- ✓ Outbound-sourced pipeline contributing 30-50% of total pipeline
KPIs to Track
- ● SDR-sourced revenue
- ● Cost per meeting
- ● Sales cycle length
- ● Win rate from outbound
Common Mistakes to Avoid
Ehsan's Growth Commentary
DevTools outbound sales has a paradox: the buyer (engineering leader) was recently an individual developer who hated sales emails. Engineering leaders evaluate tools by trying them, not by sitting through demos. The DevTools outbound approach: do not sell the product — sell the outcome. "Three companies in your space (name them) reduced deployment time by 60% last quarter" is interesting. "Would you like a demo of our CI/CD platform?" is annoying. The highest-converting DevTools outbound tactic: send a personalized technical analysis. "I noticed your GitHub repos use [technology]. Here's how [specific company similar to them] handles [specific problem] using our tool." This requires research (30 minutes per prospect) but converts at 10-15% versus 1-2% for template outreach. DevTools outbound should feel like a technical conversation between peers, not a sales pitch from a vendor. If your SDRs cannot have a technical conversation about the prospect's stack, they should not be doing DevTools outbound.
The first email should be about them, not you. Lead with a specific observation about their company or role. In DevTools, multi-threaded outreach (contacting 3+ people at the same account) increases response rates by 50%. Follow up at least 5 times. 80% of deals require 5+ touches, but 90% of salespeople give up after 2.
Ehsan Jahandarpour
AI Growth Strategist & Fractional CMO
Forbes Top 20 Growth Hacker · TEDx Speaker · 716 Academic Citations · Ex-Microsoft · CMO at FirstWave (ASX:FCT) · Forbes Communications Council