How I'd arm the AE to close a $58K expansion — from research and CRM setup through outreach, signals, and a scalable workflow for every account after this one.
Why FinServe Group is the highest-leverage expansion target — inbound demand, urgency, low risk, and strategic fit.
Five sections that build from research to the AE's hands: contacts sourced, CRM staged, sequences ready, signals configured, handoff packed.
A HITL Slack workflow that reduces 3–4 hours of manual account prep to a 2-minute form — and what it evolves into next.
FinServe is the highest-leverage expansion on the list — an existing Dagster+ customer with inbound demand from multiple buying groups, a defined expansion path, and an urgent budget window. Compared to the alternatives, the risk is low and the signal is strong.
Risk team requesting +30 seats. Compliance officer asking for better lineage. Trading desk exploring real-time pipelines. Three separate expansion vectors.
Q1 budget closing imminently. Contract expires end of Q2. Decision timeline is now, not later.
Green health score. Active champion (Maria Santos). Passed internal security audit. Unlike Phoenix Analytics (churn risk, 32% utilization) or SynthAI Labs (competing against Prefect).
Financial services demands enterprise compliance and governance features. Complex stack (Snowflake, dbt, Fivetran, Monte Carlo, Tableau) makes Dagster+ the orchestration layer tying everything together. High switching cost.
Expansion into enterprise accounts is where the GTM team is focusing investment — this is the right motion for the role.
Before we map people, we mine every data source we already have — CRM notes, call transcripts, CS handoff docs, support tickets — to build a complete picture of the deal. We're extracting the intelligence that turns a generic expansion pitch into a conversation the buyer feels was written for them.
What specific problems are driving each team's interest? "Need better lineage" is a start — but what's behind it? Regulatory pressure? Audit failures? Manual tracking that's breaking? The more specific, the sharper the outreach.
What's creating urgency beyond the Q1 budget window? New compliance mandates? A failed audit? Risk team scaling headcount? Leadership pressure to consolidate tooling? This is what gets the deal prioritized internally.
Are they migrating off a legacy orchestration tool? Building a new data governance program? Standing up a risk analytics function? Understanding the broader context lets us position Dagster+ as part of something they're already investing in.
Who signs off? What's the approval process? Has anyone mentioned budget constraints or competing priorities? Did a specific budget cycle or renewal trigger this conversation? These details shape the deal strategy.
This intelligence comes from the same internal sources we use to find people — but we're reading for different things. The AE doesn't just need names; they need to walk into every conversation knowing what the other person cares about and why they care about it right now.
We know our champion (Maria Santos) and economic buyer. We need to surface the compliance officer, risk management team lead, trading desk lead, and supporting contacts — that's what the sourcing workflow below produces.
FinServe is already a customer. Most of this data exists in our systems. Third-party sourcing is the fallback.
Compass connects to Gong + Salesforce. Access via @compass in Slack. No SQL or export needed — ask in plain English and Compass surfaces named contacts, pain point quotes, why-now signals, and buying group structure in minutes.
Example Compass queries — FinServe account prep
Active users by team, risk/compliance/trading logins (strongest buying signal), feature adoption (lineage, compliance reporting), support ticket themes, usage trends, community engagement.
For any contacts Compass couldn't surface internally, run a People Search filtered by FinServe Group + titles containing "Risk," "Compliance," "Trading," "Data Engineering." Waterfall enrichment (Apollo → ZoomInfo) for verified email, phone, LinkedIn URL. Clay is the fallback, not the default.
Key principle: Internal sources first, third-party enrichment only to fill gaps. Faster, more accurate, and reflects how expansion accounts differ from net-new.
FinServe already exists in Salesforce. We use the existing account and original deal opportunity ($78K), then create a new expansion opportunity alongside it.
Tasks auto-populate from Outreach — the AE works out of Outreach, activity syncs back to Salesforce automatically.
Intelligence surfaced by Compass (CRM data, usage signals, call transcripts) is used directly by Octave's /octave:campaign to draft personalized sequences per buying group, then pushes them into Outreach. The AE reviews, personalizes, and sends. Activity syncs back to Salesforce.
Octave also generates the account planning 1-pager via /octave:one-pager — pulling from the Compass intelligence to produce the account snapshot, buying committee summary, and recommended engagement sequence included in the AE handoff.
Automated LinkedIn connection requests to contacts across both original and expansion teams. Sent from AM/CS teams — not the AE — so it feels like a natural extension of the existing relationship. Multi-threads the account across channels.
Before configuring signals, sit down with the AE: What signals would change how you approach this account? Where do you prefer alerts? How often? What's noise vs. actionable? The infrastructure should fit how they work.
Delivery method is the AE's choice:
Real-time alerts in #acct-finserve. Best for AEs who live in Slack.
Consolidated daily/weekly summary. Best for batched consumption or a living reference doc.
Signals should be actionable and delivered where the AE already works. We configure based on their preference and iterate.
Three deliverables that let them work the account immediately:
/octave:one-pager from Dagster Compass intelligence: account snapshot ($78K → $136K), expansion opportunity and timeline, prioritized signals, buying committee and their needs, recommended engagement sequence.The AE should go from receiving this handoff to sending first outreach within 30 minutes. The account map gives them the "who," the 1-pager gives them the "why and when," and the sequences give them the "how."
Everything in Part 2 was manual. The one thing I'd build to make it repeatable: a Slack App that kicks off the entire flow.
/octave:campaign drafts sequences per buying group. /octave:one-pager builds the account doc.Build the full workflow, then QA test with 3-5 real accounts end-to-end before rollout. Verify CRM records, enrichment accuracy, email quality, and Outreach population. Test edge cases: existing contacts, failed enrichment, expansion vs. net-new forks.
What this changes: The manual process from Part 2 goes from 3-4 hours per account to a 2-minute Slack form + automated intelligence. Compass replaces manual CRM mining. Octave /octave:campaign and /octave:one-pager replace Clay for content generation. Clay only runs when internal data has gaps. The GTM Engineer's role shifts from doing the work to QA'ing the output and adding the strategic layer.
The workflow above automates the execution — but a human still initiates it. Once the HITL flow has run through enough accounts to build a feedback loop, the next evolution is proactive: the system surfaces expansion candidates automatically, before anyone asks.
After 15–20 accounts cycle through the workflow, there's a feedback loop worth training on: which signals correlated with expansion conversations, which were noise, how long the arc from activation to closed-won typically ran. That data trains a lightweight scoring model, orchestrated natively in Dagster, that ranks every account in the book each week.
Signals to weight
Every Monday, a ranked shortlist of 5–10 accounts arrives in Slack — score, top signals, one-click workflow trigger. The AE's job shifts from identifying accounts to reviewing a list.
FinServe is a stand-in — the real deliverable is the motion underneath it. A structured research-to-CRM workflow, outreach sequenced around intent signals, and a scoring model that surfaces the next opportunity before anyone has to look for it.