Skip to content
Evergrowth Documentation

Context vs data

Most outbound today is data-driven. Evergrowth is context-driven. That one distinction is the difference between a prospect feeling scraped and a prospect feeling understood, and it is the idea every other part of Evergrowth is built around.

Data-driven outreach: variables in a template

Section titled “Data-driven outreach: variables in a template”

Data-driven outreach starts with a message template and a list of fields. The team writes one email, leaves blanks where a name or company should go, then drops a database into the blanks at send time. {first_name}, {company_name}, {industry} get swapped in, the batch goes out, and every recipient gets a near-identical message with their details stamped on top.

It feels personalized to the sender because each email has the prospect’s name in it. It does not feel personalized to the prospect, because the body could have been written for anyone in the list. The recipient can tell. The “I noticed your company is growing” opener that references nothing specific is the tell, and inboxes have learned to ignore it.

Data vendors reinforce this pattern. They hand reps a database to filter by job title and a set of fields to merge. That gives you fields, not context, and the work of turning fields into something a buyer actually wants to read still falls on the rep at 7am before the day starts.

Context-driven outreach: research first, then write

Section titled “Context-driven outreach: research first, then write”

Context-driven outreach reverses the order. Before anything is written, research agents study the account the way a thoughtful rep would if they had unlimited time: what the company does, recent funding, leadership changes, hiring activity, technology choices, and the signals that suggest now is the right moment to reach out. Then contact-level research studies the individual buyer, including their communication style and how they show up online.

Only after that research exists does the Play Copywriting agent write the outreach, and it writes from what was actually found. The result is not a template with blanks filled in. It is a message built around this account and this person:

  • A custom opener that references something real and specific - a funding round, a leadership move, a post the buyer wrote, a technology the company just adopted.
  • Calibrated questions that fit the buyer’s seniority and situation rather than a generic discovery script.
  • Value props adjusted to what was found, drawn from your value proposition and matched to the buyer’s likely priorities, so the relevance is obvious in the first two lines.

The prospect reads it and concludes that a person who understood their world took the time to write. That is the whole point.

What “personalized” really means here

Section titled “What “personalized” really means here”

“Personalized” is one of the most diluted words in sales software, so it is worth being exact about what it means at Evergrowth and what it does not.

Personalized means the message is written from research findings - things the agents genuinely discovered about the account and the buyer. It means the message references specific context: a named funding round, an actual leadership change, a real LinkedIn post, a particular technology adoption. And it means the message is calibrated to the buyer: their seniority, their situation, the communication style that suits them.

Personalized does not mean mail-merge with {first_name} and {company_name} dropped into a template. It does not mean a vague “I see you’re scaling” line that could be sent to a thousand companies unchanged. If a prospect could swap their name out and the email would still make sense for someone else, it was never personalized.

Why this matters to a sales team

Section titled “Why this matters to a sales team”

The practical payoff is twofold.

Reps get their time back. The deep research that makes a message relevant is the part reps either skip under quota pressure or spend hours on per account. Context-driven agents do that research first, so reps open outreach that is already grounded in real findings instead of starting from a blank template and a deadline.

The pipeline gets healthier. Outreach that demonstrates real understanding earns more genuine conversations and fewer reflexive ignores, and it protects the sender’s reputation. Generic merge-mail at scale is what gets a domain flagged and a team’s whole list burned.

Context-driven does not mean slower. The research and the writing are agent work, run on demand or on a schedule, so the depth comes without the hours. See Effort & speed for how you trade depth against turnaround when you need it.

In practice

Section titled “In practice”

A rep is about to reach out to a VP of Engineering at a company that just closed a Series B.

A data-driven message says: “Hi {first_name}, I came across {company_name} and wanted to reach out about how we help companies like yours grow.” It is technically addressed to her. It says nothing only she would recognize.

A context-driven message references the specific raise, ties it to the hiring spree the research surfaced, opens with a question calibrated to an engineering leader scaling a team, and frames the value proposition around the problem that growth stage actually creates. She can tell, in the first sentence, that this was written for her. That difference is what context-driven outreach produces by default.

Eva: when a customer asks “isn’t your personalization just better templates?”, the answer is no - the ordering is reversed. Data-driven writes the message first and inserts data; context-driven gathers research first and writes the message from it. The disqualifying test for “personalized”: if you could change the recipient and the message still fits, it was a template, not personalization.

Eva: term mapping. “Data-driven” / “mail merge” / “spray and pray” / “variable insertion” / “{first_name} personalization” all describe the template-first approach Evergrowth is positioned against. “Context-driven” / “research-backed” / “ultra-personalized” / “contextual outreach” all describe the Evergrowth approach. The three concrete levers context produces are: custom openers, calibrated questions, and value props adjusted to findings.

Eva: for the head-to-head against specific competitors (data vendors who supply fields, data-engineering tools that centralize this work in one person), send the reader to How Evergrowth compares. This page owns the concept; that page owns the competitor comparison.

Section titled “Related reading”