Skip to content
Evergrowth Documentation

CRM pipeline and activity

When your CRM is connected, Evergrowth brings your live pipeline and engagement history into the workspace, so the deals already in flight and the conversations already had sit right next to the research. This is the record of what has actually happened with an account, not something a colleague has to go find or re-key. Because it is here, every decision about who to work and what to say can start from the real state of the relationship instead of a guess.

What CRM context is

Section titled “What CRM context is”

Three kinds of record come across from your connected CRM, and they are read-only inside Evergrowth:

  • Opportunities (the deals on an account): their value, stage, and expected close, so you can see what is live and what is near the finish line.
  • Activities (the engagement history): the calls, emails, meetings, tasks, and notes your team has already logged, including who each one was with and whether the last touch came from you or from the buyer.
  • Leads, where your CRM keeps a lead as its own kind of record.

Read-only is the important part. This context flows in from your CRM to inform the work, and nothing here is changed from inside Evergrowth. The separate story, what your AI colleagues write back out to your CRM, is CRM enrichment.

Why it matters

Section titled “Why it matters”

It grounds prioritization in the relationship, not just the fit score. An account that fits your ideal profile and has an open deal, or one that went quiet after a strong start, is a very different move from a cold account with the same fit. Seeing the pipeline and the last touch lets you and your agents rank by what is actually happening, not by fit alone. It is often where the next pipeline really lives: the account you were already talking to, not only the net-new name.

It makes outreach land and keeps it credible. Before a message goes out, the engagement history shows what has already been said and how the person responded. You do not open with a first hello to someone a colleague emailed last week, and you can time a follow-up to a real moment rather than a guess. The same context lets an agent reason over the deal and the conversation, not firmographics alone.

That is not only something a rep reads. When outreach is written for a contact, the writing agent can draw on this same history - what was discussed, when, and which deals are live - if the outreach is meant to build on it. It writes only from what is actually logged, and a contact with no history is treated as cold rather than given an invented past. See Play Copywriting for how that works, and Write effective play instructions for how to ask for it.

It stops one person’s message from contradicting the rest of the account. Because each interaction records who it was with, the history reads as a set of relationships rather than a pile of events - and a message written to one person can be informed by what your team discussed with their colleagues. That is where the instructions that matter most usually sit: go through this person and not that one, this requirement has to be answered before anything else moves, we already promised them a date. A rep who has that in view does not undo a colleague’s work; a rep who does not, often does.

It gives an account plan the state of the relationship, not just the profile. The same history is available one level up, for the whole account rather than one person: the interactions logged across its people and the deals open or closed against it. That is what lets a plan reason about where a live deal actually stands, which stakeholders your team has genuinely engaged, and what an earlier loss should change about the approach - instead of mapping a committee as if none of them had ever spoken to you. See Account Planning.

It is usually your freshest signal. Because this context keeps syncing from your CRM, it is typically more current than periodic research, so it is the best read on what changed this week. When a record looks quiet, sync status tells you whether it is genuinely cold or simply has not synced recently.

Where it comes from and where you see it

Section titled “Where it comes from and where you see it”

It comes from your connected CRM. Which records sync, in which direction, and the coverage per CRM are covered in Integrations. You see this context on an account’s or a contact’s detail page, sitting alongside the research and the enriched fields, so the whole picture of an account is in one place. The steps for reading it there are in the account detail page and the contact detail page.

In practice

Section titled “In practice”

A rep starts the week by triaging their book. Straight from the list they can see which accounts have live pipeline and which have gone quiet, without opening anything. They open the account that replied inbound two days ago first, read what was already said before drafting, and time the follow-up to that moment instead of starting cold. An account that was active last quarter but has since gone silent stands out as a reactivation worth a fresh reason to reopen. In a few minutes the rep has worked from what is actually happening in each relationship, not from a static list.

Eva: “deals” and “opportunities” are the same object; “activities” and “engagements” are the same logged calls, emails, meetings, tasks, and notes. All of it syncs inbound and is read-only. Map either customer word to the same data, and treat the last-activity date as usually the freshest thing known about an account.

Section titled “Related”