Sales Team

Documentation Index

Fetch the complete documentation index at: https://docs.ideaboxai.com/llms.txt

Use this file to discover all available pages before exploring further.

Every Account Executive knows the Sunday evening dread. Eight deals on the forecast. Two have gone quiet. One has a close date this Friday that everyone knows is slipping. Your manager wants a pipeline update at 9am Monday, and you still have not updated Salesforce from last week’s calls. Every Sales Engineer knows the 4pm scramble. A discovery call just ended. The prospect shared data volumes, query times, and stack details. You need to capture all of it, assess fit, and scope a POC, before you forget what was said. Instead, you open a blank document and start typing from memory. Every SDR knows the Monday morning paralysis. Forty-seven leads in the queue. No signal on which ones are worth calling first. You pick one at random, spend 20 minutes researching, draft an email, and hope it lands. Multiply that by five and your morning is gone. The Sales Team Co-Pilot solves all three. It connects directly to Salesforce, Confluence, Google Drive, LinkedIn, and the public web. It understands your role, pulls live data, and answers your actual questions, in seconds, not hours.

​

The Co-Pilot knows your role before you ask

A Persona in IdeaBoxAI is the AI’s understanding of who you are, what you need, and what your data looks like. When you log in as an Account Executive, you get a deal-management intelligence layer tuned to pipeline health, meeting prep, and forecast accuracy. When you log in as a Sales Engineer, you get a technical layer tuned to discovery, POC design, and objection handling. The Sales Team Co-Pilot ships with three purpose-built personas. Each connects to the data sources relevant to their role. The persona you are assigned to determines which data you see, which skills are available, and which scenario cards appear on your home screen. The following table summarises the three personas. Each persona also comes with pre-configured scenario cards on the home screen. Click any card to pre-fill the chat input with a common workflow prompt. You can also type your request directly in plain language, the Co-Pilot auto-detects the right skill. To browse all available skills, type / in the chat bar to open the skill picker.

​

AE scenario: account research before a first meeting

Jordan Reeves · Account Executive Mid-market territory · 14 active opportunities · First call with Meridian Health tomorrow at 10am Jordan has a first meeting with Meridian Health in the morning. Normally, this means 45 minutes of tab-switching, LinkedIn for the org chart, the company website for strategic priorities, Salesforce for prior activity, and Google for recent news. By the time the research is done, there is no time left to build a talk track. Jordan types: “Prep me for my meeting with Meridian Health tomorrow.” The Co-Pilot responds:

Account brief, Meridian Health Prepared for Jordan Reeves · Meeting: Apr 24, 10:00am · First call Company snapshot

Attribute	Detail
Industry	Healthcare / Hospital systems
HQ	Minneapolis, MN
Revenue	$2.1B (FY25)
Employees	8,400
Data infrastructure spend	Estimated $14M annually (based on job postings and vendor signals)

Strategic priorities and signals

• Announced a $40M data modernisation initiative in Q1 earnings call, migrating from on-prem Teradata to a hybrid cloud architecture.
• Posted 6 data engineering roles in the last 90 days. Three mention “real-time analytics” and two mention “query performance at scale.”
• New VP of Data Platform (Anika Patel) started 4 months ago. LinkedIn shows she came from UnitedHealth where she led a similar migration.

Tech stack gaps

Current stack	Signal source	Actian fit
Teradata (on-prem)	Job postings, Confluence notes	🟢 High, migration path from Teradata is a proven use case.
Snowflake (evaluation)	Salesforce competitor field	🟡 Moderate, they are evaluating, not committed. Real-time query gap is the angle.
Informatica ETL	Job postings	🟢 High, DataConnect replacement opportunity if pipeline modernisation is in scope.

Competitive context Snowflake is listed as a competitor on this opportunity in Salesforce. Based on their data volumes (likely 500M+ rows given their patient record count) and their real-time requirements, the positioning angle is query latency at high concurrency, not migration ease. Recommended talk track Lead with the data modernisation initiative, it is their stated priority, not something you are inferring. Acknowledge that Snowflake is strong for warehousing, then pivot to the real-time gap: “The question is not whether Snowflake is a good warehouse, it is whether it is the right engine for sub-second queries at your projected data volumes.” Reference the FinServ customer running 3.8PB with sub-500ms average query time, healthcare and financial services share the same concurrency and compliance requirements. Suggested questions for the call

• “What does your timeline look like for the Teradata migration, and what is driving the deadline?”
• “When you say real-time analytics, what query response time does your clinical team need to make decisions?”
• “How are you handling the compliance side of the migration, is HIPAA driving any of your architecture choices?”

Suggested follow-ups: Align my SE for this meeting · Build a pre-meeting checklist · Show me similar closed-won deals in healthcare · Save this brief to Salesforce

Jordan reviews the brief in 4 minutes. The talk track is ready. The competitive angle is specific. The questions are tailored to what the prospect actually cares about, not a generic discovery script. Jordan types: “I’m bringing my SE to this meeting. Brief my SE.” The Co-Pilot responds:

SE alignment brief, Meridian Health For: SE assigned to Meridian Health · Meeting: Apr 24, 10:00am · Stage 1 (First Call) Account context

• Healthcare system, $2.1B revenue, migrating from Teradata to hybrid cloud.
• Evaluating Snowflake. New VP of Data Platform (Anika Patel) is driving the initiative.
• Key signal: 6 data engineering hires in 90 days, 3 mention real-time analytics.

Your role in this meeting

• Listen for data volume numbers, current query times, and concurrency requirements. These are the inputs for the competitive angle.
• Be ready to address the Snowflake comparison, but do not lead with it. Wait for them to bring it up or for Jordan to set up the positioning.

Capabilities to demonstrate

• Vector AI DB real-time query performance at high row counts, the Teradata replacement story.
• DataConnect as an Informatica ETL alternative, only if they raise pipeline modernisation.

POC design outline If the call goes well and they share specific data volumes, a 2-week POC on their patient analytics dataset would demonstrate the latency gap. Target metric: sub-2s query on a 30-day rolling window across their projected row count. What NOT to lead with Do not lead with pricing or benchmarks in a Stage 1 call. Do not position against Snowflake unless they raise it first. Do not suggest a POC until discovery is complete.

The results:

• Account research reduced from 45 minutes to under 5 minutes.
• Talk track tailored to the prospect’s stated priorities, competitive situation, and tech stack, not a generic pitch.
• SE briefed with role-specific context and a clear POC outline in 30 seconds.
• All research auto-saved to Salesforce and Google Drive.

​

AE scenario: deal health check before forecast

Rachel Torres · Account Executive Enterprise territory · 11 active opportunities · Forecast call with VP at 2pm Rachel has a forecast call in two hours. She knows her pipeline has problems but cannot pinpoint which deals are actually at risk versus which ones just feel slow. Before IdeaBoxAI, she would open each opportunity in Salesforce one by one and try to piece together the story from activity logs and her own memory. Rachel types: “Run a deal health check on NovaTech. They’ve gone quiet and I’m worried about the close date.” The Co-Pilot responds:

Deal health scorecard, NovaTech Opportunity: NovaTech, Enterprise Data Platform · ARR: $185,000 · Stage 4 · Close date: May 16 Overall score: 54 / 100, Recovering 🟡

Dimension	Score	Evidence
Activity momentum	35 / 100 🔴	Last activity was 18 days ago (email from Rachel, no reply). Prior to that, 3 calls in 2 weeks. The drop is sharp.
Stakeholder coverage	45 / 100 🔴	Only 1 contact engaged (David Cho, Sr. Data Engineer). No executive sponsor identified. No procurement contact. Single-threaded.
Artifact completeness	70 / 100 🟡	Account brief on file. Discovery notes on file. Missing: mutual action plan, proposal, executive sponsor alignment.
Close date integrity	50 / 100 🟡	Close date has been pushed once already (from Apr 30 to May 16). At current velocity, May 16 requires a stage progression within 5 business days, which has not happened.
Competitive exposure	65 / 100 🟡	Databricks listed as competitor. No update on competitive status since Stage 2. Last mention: “They’re also talking to Databricks but haven’t started a POC.” That was 4 weeks ago.

Risk flags

• Stale activity (critical): 18 days since last response. Your average deal at Stage 4 has contact every 4.2 days. NovaTech is 4x the norm.
• Single-threaded (high): Only David Cho is engaged. He is a Sr. Data Engineer, not a decision-maker. No executive sponsor on record.
• Close date drift (medium): Already pushed once. Current trajectory does not support May 16 without immediate re-engagement.

Benchmark: Deals at the same stage and ARR that closed-won had an average health score of 78. NovaTech is 24 points below that benchmark. Suggested follow-ups: View next actions for this deal · Draft a re-engagement email for David Cho · Generate a mutual action plan · Update Salesforce with forecast category

Rachel clicks the suggested follow-up. Rachel types: “What should I do today to save this deal?” The Co-Pilot responds:

Next actions, NovaTech Based on deal health score (54/100) and 3 open risk flags. Today

#	Action	Channel	Why	Exact words
1	Re-engage David Cho	Call (not email)	18 days silent. Email has failed, David has not replied to the last 2. A call breaks the pattern.	”David, I wanted to check in directly. Last time we spoke you were comparing timelines with your Databricks evaluation, I have some new benchmark data that might help with that. Do you have 10 minutes this week?“
2	Ask David for an exec intro	Same call	Single-threaded risk. You need a second contact before this deal can progress.	”One thing that would help me build the best proposal for your team, would it make sense to include your VP in a 15-minute alignment call? I want to make sure the business case lands, not just the technical one.”
3	Update Salesforce	Co-Pilot	Log today’s call attempt, update next step date, flag the single-threaded risk in the opportunity notes.	I can update Salesforce for you after the call, just tell me what happened.

This week

#	Action	Goal
4	Generate a mutual action plan working back from May 16.	Creates a shared timeline that forces both sides to commit to milestones, or reveals that May 16 is not realistic.
5	Draft a re-engagement email with the Databricks benchmark as the hook.	Backup if the call does not connect. Subject references the benchmark, not “checking in.”
6	Update forecast category to Best Case with a note.	Score is 54 with active re-engagement. Commit requires a score above 90 with no open flags.

Rachel walks into her forecast call with a clear story: NovaTech is at risk, here is why, here is what she is doing about it today, and here is what the forecast category should be, with evidence behind each point. The results:

• Deal risk surfaced across 5 dimensions with specific Salesforce evidence, not gut feel.
• 18-day silence flagged and benchmarked against similar deals at the same stage.
• Prioritised action plan split into today and this week, with exact words for each conversation.
• Forecast category recommended with rationale the VP can audit.

​

SE scenario: post-discovery debrief and POC scoping

Marcus Liu · Sales Engineer Assigned to 6 active evaluations · Just finished a discovery call with DataStream Analytics Marcus just got off a 45-minute technical discovery call with DataStream Analytics. The champion shared volumes, query requirements, stack details, and a decision timeline. Marcus needs to capture all of it before the details blur, and assess whether this is a strong fit. Marcus types: “Call done, here’s what I learned. DataStream Analytics, VP of Engineering is the champion. They’re running Redshift today with about 800M rows, growing 15% quarterly. Current dashboard queries take 12-18 seconds, they need sub-2 second. They’re evaluating us alongside BigQuery. Decision by end of June, POC needs to start by mid-May. Stack is Python, Airflow, dbt. Main concern is migration complexity from Redshift.” The Co-Pilot responds:

Post-discovery summary, DataStream Analytics Key facts card

Attribute	Detail
Company	DataStream Analytics
Champion	VP of Engineering
Current stack	Redshift, Python, Airflow, dbt
Data volume	800M rows, growing 15% quarterly
Current query time	12–18 seconds (dashboard queries)
Required query time	Sub-2 seconds
Competitor	BigQuery
Decision deadline	End of June
POC start window	Mid-May

Actian fit assessment: Strong 🟢 The fit is strong for three reasons:

• Their query performance gap is significant. 12–18 seconds down to sub-2 seconds is exactly the use case where Vector AI DB outperforms both Redshift and BigQuery at their row count.
• 800M rows growing 15% quarterly puts them at 1.2B rows within 12 months. BigQuery charges per query at that scale. Vector AI DB has no per-query cost, the TCO argument strengthens as they grow.
• Their stack (Python, Airflow, dbt) integrates cleanly. No exotic dependencies.

Migration risk note: The champion flagged migration complexity as their main concern. This is a category 2 objection (Migration Risk). Acknowledge the real cost first, do not minimise it. Then reframe: the question is not whether migration has a cost, but whether staying on Redshift at 12–18 second query times has a higher one. Recommended next step: Generate a POC proposal scoped to their dashboard use case. Target metric: sub-2s query on a 30-day rolling window at 800M rows. Suggested follow-ups: Generate a POC proposal for DataStream · Draft an email to the champion with POC scope · Update Salesforce stage · Pull benchmark data for Redshift vs Vector AI DB

Marcus clicks the POC suggestion. Marcus types: “Generate a POC proposal for DataStream.” The Co-Pilot responds:

POC scope card, DataStream Analytics

Attribute	Detail
Dataset	Production dashboard dataset, live Redshift export (preferred over synthetic).
Dataset size	800M rows current, test at 1.2B to demonstrate growth headroom.
Success metric	Sub-2s query on 30-day rolling window aggregation at 800M rows. Stretch: sub-1s at 1.2B rows.
Champion	VP of Engineering
Duration	2 weeks (standard, integration complexity is low given Python/Airflow/dbt stack).
DataConnect	Not included. Their Airflow pipeline handles ingestion today, no ETL replacement needed.
Vector AI DB use case	Real-time dashboard analytics replacing Redshift.

Suggested next steps

1. Send the POC scope to the champion for sign-off on dataset and success metric.
2. Schedule a 30-minute POC kickoff call with Marcus and the champion’s engineering lead.
3. Request a Redshift export of 30 days of dashboard query data for baseline comparison.
4. Draft a post-call email to the champion confirming the POC timeline and what both sides need to deliver.

The results:

• Discovery findings captured and structured in under 60 seconds, no manual note formatting.
• Actian fit scored with specific reasoning tied to data points from the call, not generic categories.
• POC scoped with a quantified success metric, realistic timeline, and clear next steps.
• All findings auto-logged to Salesforce.

​

AE scenario: post-meeting log and follow-up email

Sarah Park · Account Executive Enterprise territory · Just finished a Stage 3 call with Vertex Financial Sarah just walked out of a meeting with Vertex Financial. She has 12 minutes before her next call and needs to log what happened, update Salesforce, and send a follow-up email. Before IdeaBoxAI, two of those three would not get done until the end of the day, if at all. Sarah types: “Meeting done with Vertex Financial, here’s what happened. Good energy overall. CFO joined for the first 15 minutes which was unexpected. She asked about SOC 2 compliance and whether we support data residency in the EU. I confirmed SOC 2 Type II and said I’d follow up on EU residency. David (champion) confirmed they want to move to POC but needs budget approval from the CFO first. Competitor is Snowflake, they’ve done a POC with Snowflake already but weren’t happy with query latency on their risk modelling workload. Next step is a technical deep-dive with their data engineering team next week. One risk: David mentioned the project could get deprioritised if Q2 revenue comes in below target.” The Co-Pilot responds:

Post-meeting log, Vertex Financial Meeting date: Apr 23, 2026 · Stage 3 · Attendees: Sarah Park (AE), David (Champion), CFO (new contact) What went well

• CFO joined unprompted, signals executive interest. This is unusual at Stage 3 and suggests the initiative has visibility at the C-level.
• Champion confirmed intent to move to POC. Budget approval is the remaining gate.
• Snowflake POC completed but did not meet latency requirements on risk modelling. This is a significant competitive advantage, they have already experienced the gap you are positioning against.

Deal status Stage stays at 3. Move to Stage 4 when budget approval is confirmed and the technical deep-dive is scheduled with a date. Open risks

Risk	Severity	Specific action	Exact words
EU data residency question unanswered	🟡 Medium	Follow up within 24 hours. Delayed response on a CFO question erodes trust.	Include in the follow-up email with a clear answer or a specific date when you will have one.
Budget deprioritisation if Q2 misses	🟡 Medium	Accelerate the timeline. The longer this deal sits at Stage 3, the higher the risk of a freeze.	In your next call with David: “What does the budget approval process look like, and is there a way to get sign-off before the Q2 review?”
CFO is a new stakeholder, no record	🟢 Low	Add the CFO as a contact in Salesforce today. Log her SOC 2 and residency questions.	I can add her to the opportunity record when you confirm the update.

Immediate next actions

1. Send follow-up email to David confirming the technical deep-dive and addressing the EU residency question. (Due: today.)
2. Add CFO as a contact in Salesforce with meeting notes. (Due: today.)
3. Schedule the technical deep-dive with David’s data engineering team. (Due: this week.)

Suggested follow-ups: Draft the follow-up email · Update Salesforce with these notes · Generate a mutual action plan for Vertex · Prepare objection prep for the next call

Sarah immediately follows up. Sarah types: “Draft the follow-up email to David.” The Co-Pilot responds:

Email draft, Post-meeting follow-up To: David · Vertex Financial Subject: Vertex risk modelling POC, next steps and residency answer David, Good speaking with you and your CFO today. Two follow-ups from the conversation. First, on EU data residency, I am confirming the specifics with our compliance team and will have a documented answer for you by Friday. SOC 2 Type II certification is current and I can share the report directly if helpful for your CFO’s review. Second, the technical deep-dive. Are you available next Tuesday or Wednesday for a 60-minute session with your data engineering team? Marcus (our SE) will walk through the architecture and how it maps to your risk modelling workload, specifically the latency gap you experienced in the Snowflake POC. Let me know what works. Sarah

The results:

• Meeting logged with structured outcomes, risk flags, and next actions in under 90 seconds.
• Follow-up email drafted with a specific hook (the Snowflake latency gap) and a concrete ask (deep-dive date), no generic opener.
• CFO flagged as a new stakeholder with her specific concerns captured for future reference.
• 12-minute window between meetings used productively instead of lost.

​

SDR scenario: weekly lead scoring and outbound

Priya Mehta · Sales Development Rep Assigned territory: West Coast mid-market · 47 unworked leads in Salesforce Priya starts every Monday the same way, staring at a list of leads with no idea which ones to call first. She used to pick accounts alphabetically or by the order they came in. Half her outreach went to companies that were never going to buy. The other half went out with a generic template. Priya types: “Set up my week. Where should I start?” The Co-Pilot responds:

Weekly priority checklist, Priya Mehta Territory: West Coast mid-market · 47 assigned leads · Week of Apr 21 Step 1 of 10: ICP scoring complete 47 leads scored across 4 dimensions (Firmographic, Technographic, Intent Signals, Win Pattern Match).

Tier	Count	Action
🔥 HOT (75+)	5	Prioritise above everything else this week.
🟡 WARM (50–74)	12	Reach out this week if time permits, next week at latest.
❄️ LOW (< 50)	30	Route to segmentation, do not discard without guidance.

Top 5 HOT accounts

Account	Score	Top signal	Recommended first action
Cascade Data Systems	92	Posted VP of Data Platform role 3 weeks ago. Stack matches (Teradata, Python). Closest closed-won match: MedTech Corp ($142K ARR, 4-month cycle).	Build a prospect profile and draft a personalised email to the hiring manager.
Ridgeline Analytics	88	Raised $28M Series C 6 weeks ago. Job postings mention “real-time analytics at scale.”	Research the VP of Engineering on LinkedIn, then build an outreach sequence.
Apex Financial Group	84	Existing Snowflake customer posting about query performance issues on their engineering blog.	Draft a cold email using the blog post as the hook.
Pacific Logistics	79	Data engineering team doubled in 6 months. Current stack includes Redshift.	Build a prospect profile to identify the right contact.
Westfield Manufacturing	76	SAP integration need identified from job postings. Manufacturing vertical, 38% historical close rate.	Research the Head of Data and draft outreach leading with SAP integration.

Remaining 42 leads: 12 WARM accounts summarised with top signal. 30 LOW accounts ready for segmentation when you finish Tier 1 outreach. Suggested follow-ups: Show me the full score for Cascade Data Systems · Build a prospect profile for the VP of Data Platform at Cascade · Start outreach for the top 5 · Segment my low-fit leads

Priya starts with her top lead. Priya types: “Build a prospect profile for the VP of Data Platform at Cascade Data Systems.” The Co-Pilot responds:

Prospect profile, Cascade Data Systems Company snapshot

Attribute	Detail
Industry	Data infrastructure / SaaS
HQ	Portland, OR
Revenue	$85M (estimated)
Employees	420
Data stack	Teradata (migrating), Python, Apache Spark

Trigger events (last 90 days)

• Posted VP of Data Platform role 3 weeks ago, job description mentions “migrate from legacy warehouse to a modern, high-performance analytics engine.”
• Hired 4 data engineers in the last 60 days.
• CTO spoke at a Portland data meetup about “the cost of slow queries on product decisions.”

Tech stack signals

Technology	Signal	Actian fit
Teradata (legacy)	Job postings explicitly reference migration	🟢 HIGH, proven migration path, DataConnect accelerates ETL lift
Apache Spark	Engineering blog	🟡 MODERATE, Vector AI DB complements Spark as the query layer
Python	Job postings	🟢 HIGH, native Python SDK, clean integration

Contact profiling

• Target: VP of Data Platform (role posted, not yet filled, hiring manager is likely the CTO or a Sr. Director of Engineering).
• Pain hypothesis: Migrating from Teradata means they need a replacement that delivers query performance at scale without the licensing cost. The CTO’s public comments about “slow queries” confirm this is a business-level pain, not just a technical wish.

Personalisation hooks

1. Trigger: The VP of Data Platform job posting mentions “high-performance analytics engine”, this is their own language for what Vector AI DB delivers.
2. Pain: Their CTO publicly called out slow queries as a product blocker. Query latency is not an infrastructure issue for them, it is a revenue issue.
3. Proof: MedTech Corp (similar size, similar Teradata migration) closed at $142K ARR in 4 months. Sub-500ms query times on 600M rows.

Suggested follow-ups: Draft an outreach email using the CTO’s meetup talk as the hook · Build a LinkedIn message for the CTO · Create a full outreach sequence · Save this profile to Salesforce

Priya drafts the email in one click, sends the LinkedIn message, and loads the full sequence into Salesforce, all before 9:30am. The rest of her top 5 follow the same pattern. The results:

• 47 leads scored and ranked in under 8 seconds, with the specific signal driving each score.
• Top 5 accounts identified with a clear first action for each, grounded in real signals.
• Prospect profile built from Salesforce, LinkedIn, and the public web in under 30 seconds, including personalisation hooks ready to paste into outreach.
• Monday morning paralysis replaced with a structured 10-step plan.

​

Skills that power all three personas

Each persona in IdeaBoxAI is powered by a set of Skills, AI capabilities that define how the Co-Pilot handles specific types of requests. The Sales Team Co-Pilot ships with 32 skills out of the box, split across the three personas. You can trigger a skill in three ways:

• Click a scenario card on the home screen to pre-fill the prompt and run the skill immediately.
• Type your request in plain language. The Co-Pilot auto-detects the appropriate skill from your message.
• Type / in the chat bar to open the skill picker and select a skill by name.

​

Account Executive skills

The following skills handle deal management, meeting preparation, and pipeline workflows.

​

Sales Engineer skills

The following skills handle technical discovery, POC design, and competitive objection handling.

​

Sales Development Rep skills

The following skills handle lead scoring, prospect research, and outbound sequencing.

​

Connected to your sales data

The Sales Team Co-Pilot is grounded in your live data, not a sample, not a simulation. It connects to the systems your sales team already uses, pulling information in real time to inform every response. When an AE asks “prep me for my meeting with Meridian Health,” the Co-Pilot queries Salesforce for opportunity data, searches LinkedIn for recent activity, scans job postings for tech stack signals, and pulls prior notes from Confluence, all in parallel, in under 5 minutes. Each persona only sees the data relevant to their role. An AE sees opportunities, contacts, and deal activity. An SE sees technical notes, discovery records, and POC status. An SDR sees leads, ICP scores, and outreach history. The platform connects through the following layers:

• Salesforce for CRM data, opportunities, contacts, leads, activity history, and forecast categories.
• Confluence for internal knowledge, battlecards, case studies, prior SE notes, and RFP templates.
• Google Drive for deal documents, proposals, account briefs, and mutual action plans.
• LinkedIn for prospect research, role changes, company signals, and professional context.
• Public web for company intelligence, news, job postings, financial filings, and tech stack signals.

​

Getting started

Setting up the Sales Team Co-Pilot for your team takes less than a day.

​

Next steps

Explore these guides to learn more about the platform capabilities behind the Sales Team Co-Pilot.