Founder of Blueprint. I help companies stop sending emails nobody wants to read.
The problem with outbound isn't the message. It's the list. When you know WHO to target and WHY they need you right now, the message writes itself.
I built this system using government databases, public records, and 25 million job posts to find pain signals most companies miss. Predictable Revenue is dead. Data-driven intelligence is what works now.
Your GTM team is buying lists from ZoomInfo, adding "personalization" like mentioning a LinkedIn post, then blasting generic messages about features. Here's what it actually looks like:
The Typical WebExpenses SDR Email:
Why this fails: The prospect is an expert. They've seen this template 1,000 times. There's zero indication you understand their specific situation. Delete.
Blueprint flips the approach. Instead of interrupting prospects with pitches, you deliver insights so valuable they'd pay consulting fees to receive them.
Stop: "I see you're hiring compliance people" (job postings - everyone sees this)
Start: "Your sales team filed 47 out-of-policy expenses in Q4" (internal system data - only you have this)
PQS (Pain-Qualified Segment): Reflect their exact situation with such specificity they think "how did you know?" Use data from their own system with dates, counts, department names.
PVP (Permissionless Value Proposition): Deliver immediate value they can use today - analysis already done, patterns already identified - whether they buy or not.
Company: WebExpenses
Core Problem: Companies waste significant time and money processing employee expense reports manually, leading to delayed reimbursements, compliance violations, and poor visibility into spending patterns.
Target ICP: Mid-market to enterprise organizations (250-5000+ employees, sweet spot 500-2000) with distributed teams, high expense volume, and complex reimbursement policies. Industries include Manufacturing, Financial Services, Healthcare, Professional Services, and Aviation & Transportation.
Primary Buyer Persona: Finance Manager / Accounting Manager / Controller reporting to CFO. Responsible for expense management processes, policy compliance, ERP integration, and month-end reconciliation. Key KPIs: processing time reduction, administrative labor savings, policy compliance rate, days to close books.
These messages demonstrate precise understanding of the prospect's situation (PQS) or deliver immediate actionable value (PVP). Each play is built on verifiable data - either from public sources or from WebExpenses' internal system analytics.
Identify the specific employees driving the majority of policy violations within a department. This transforms a department-wide problem into actionable individual coaching opportunities.
Finance managers struggle with blanket policy reminders that don't move the needle. When you show them that 5 specific people are responsible for 68% of violations, you've given them exactly what they need for targeted intervention. The specificity (names and counts) proves you've done deep analysis on their exact situation.
This play requires submitter-level violation tracking with employee names and detailed per-person analytics across the customer's organization.
This is proprietary data only WebExpenses has - competitors cannot replicate this play without access to the customer's expense system.Drill down to a single employee's violation pattern, showing not just frequency but specific amounts and violation types. This enables manager-ready coaching conversations.
Generic "follow policy" conversations fail because they lack specifics. When you provide the exact dollar amounts ($82-$134) and the pattern (8 out of 11 violations are the same type), you transform the manager's conversation from accusatory to diagnostic. The insight about "unaware vs testing" helps frame the coaching approach.
This play requires detailed per-employee expense history with violation amounts, types, and dates across the customer's organization.
This level of individual pattern analysis is unique to WebExpenses' system data - competitors cannot provide this without access to the customer's expense records.Break down the total review time by specific violation types, showing which categories consume the most administrative labor. This enables targeted process improvements.
Finance managers know they're wasting time on expense reviews but lack visibility into which violation types drive the burden. When you show that 3 specific categories (missing receipts, over-limit meals, unclear business purpose) account for 29 of 38 hours, you've given them a clear action plan. The 65% reduction claim is backed by peer data.
This play requires review time tracking per expense report and aggregation by violation type across the customer's organization.
This synthesis of time-per-violation with submitter-level data is proprietary to WebExpenses - competitors cannot replicate without access to the customer's expense system.Use aggregated violation data from 200+ mid-market companies to show the prospect where they rank on department-level compliance. This creates competitive urgency and validates the ROI of process improvements.
Finance managers need business cases to justify process changes. When you show them they're at the 78th percentile for violations (meaning worse than 78% of peers) and quantify the hours saved at the 50th percentile, you've built the ROI case for them. The specific finding about their 47 violations combined with peer context passes the competitor test.
This play requires aggregated violation data across 200+ customers enabling percentile benchmarking by department and company size.
This benchmarking capability is unique to WebExpenses' multi-customer dataset - competitors cannot replicate without similar scale.Quantify the specific time burden caused by a single violation type (missing receipts) by showing both the count and the average resolution time. This makes the pain tangible and addressable.
Finance teams feel the pain of chasing missing receipts but haven't quantified it. When you show 23 specific instances consuming 37 minutes each (14 total hours), you've made the abstract pain concrete. The question about whether receipt capture is an ongoing pain point acknowledges their reality and invites collaboration.
This play requires violation tracking with resolution time calculation per violation type across the customer's organization.
Time-per-violation analytics require access to the customer's expense system - this is proprietary to WebExpenses.Alert Finance Directors that a specific department has significantly higher policy violation rates than other departments in the same organization, quantifying the administrative burden this creates.
The 3x comparison to marketing makes this feel like a department problem, not a company-wide policy issue. The 12 hours per month quantifies the recipient's direct pain. The specific number (47) proves this is researched, not generic. The routing question is easy to answer and moves the conversation forward.
This play requires department-level expense data with policy violation tracking across the customer's organization.
Cross-department comparison requires access to the customer's complete expense system - this is proprietary to WebExpenses.Show that a single violation type (missing receipts) accounts for nearly half of a department's total violations, creating both operational inefficiency and audit risk.
The 49% statistic shows this is THE dominant problem, not just one of many issues. The dual impact (2-3 days reimbursement delay affecting employee satisfaction + audit risk affecting compliance) gives the recipient multiple reasons to care. The routing question is appropriate and actionable.
This play requires violation type distribution calculation by department across the customer's organization.
Violation type analysis by department requires access to the customer's expense system - this is proprietary to WebExpenses.Compare two departments with similar headcount but dramatically different compliance rates, identifying potential root causes (unclear policies or inadequate controls).
The same-headcount comparison removes the "we're just bigger" excuse and points to a process or policy issue. Offering two potential root causes (policies vs controls) demonstrates thoughtful analysis beyond just reporting numbers. The yes/no question format is easy to respond to.
This play requires department-level expense data with headcount information across the customer's organization.
Same-headcount comparison requires access to the customer's complete expense and org structure data - this is proprietary to WebExpenses.Old way: Spray generic messages at job titles. Hope someone replies.
New way: Use internal system data to identify specific compliance gaps and operational inefficiencies. Then mirror that situation back with evidence.
Why this works: When you lead with "Your sales team filed 47 out-of-policy expenses in Q4 - 3x higher than marketing" instead of "I see you're hiring compliance people," you're not another sales email. You're the person who analyzed their actual data.
The messages above aren't templates. They're examples of what happens when you combine internal system analytics with department-level insights. Your team can replicate this using the data recipes in each play.
Every play traces back to verifiable data. Here are the sources used in this playbook:
| Source | Key Fields | Used For |
|---|---|---|
| WebExpenses Internal Data | policy_violation_rates_by_department, exception_approval_frequency, department_headcount, review_time_per_violation, submitter_names, violation_amounts | Department-level violation analysis, individual contributor patterns, peer benchmarking, time waste quantification |
| LinkedIn Company Data | department_headcount, new_hire_dates, organizational_structure | Cross-referencing hiring activity with compliance gaps |
Note on Internal Data: All plays in this playbook leverage WebExpenses' proprietary system data. This requires either existing customer relationships or aggregated benchmarking data from your customer base. The competitive moat is in the analytics layer - showing patterns customers can't see in their own raw data.