Contents
  1. Customer work and campaign objectives
  2. Customer records, identity, and lifecycle state
  3. Audience selection and account evidence
  4. Purpose, consent, and contact eligibility
  5. Research that preserves evidence and uncertainty
  6. Campaign content and revision-specific review
  7. Qualification and accountable sales handoffs
  8. Outreach, replies, and stopping conditions
  9. Conversions and downstream quality
  10. Attribution rules and their limits
  11. Evidence of incremental improvement
  12. Operating value, ownership, and expansion
  13. Check understanding
  14. Open questions
  15. Selected talks
  16. References
  17. Talk library
← All topics

AI in Sales and Marketing

AI can help teams research customers, prepare communication, and route potential business. Its usefulness depends on what happens afterward: whether the information is correct, contact is permitted, someone accepts responsibility, and customers make useful progress. Faster generation alone cannot establish better sales, stronger relationships, or profitable growth.

Customer work and campaign objectives

Marketing develops and communicates offerings that provide value, using customer research to inform decisions. Sales helps prospective customers assess and complete purchases. A campaign coordinates activity around a defined audience and objective. A conversion is a specified desired action, such as requesting a consultation; it need not be a purchase. The American Marketing Association’s definition places customer value beyond promotional output.

An individual may choose and buy an offering personally. An organizational purchase can involve finance assessing affordability, operations assessing suitability, and other participants approving adoption. This buying group shares a purchase decision without sharing identical needs. Account-based selling coordinates attention across those participants; the Salesforce introduction illustrates that distinction.

A customer journey describes experiences across discovery, assessment, purchase, and use. A marketing funnel summarizes progression toward selected actions; a sales pipeline organizes potential deals by working stage. Retention means customers continue the relationship or use. These are organizing views: a customer can revisit research, defer a decision, or involve another participant rather than advance through one fixed sequence.

Responsibilities and evidence of progress
WorkCustomer and team responsibilitiesUseful AI contribution
ResearchCustomers describe circumstances; marketing investigates needs.Prepare source-backed summaries for human interpretation.
Communication and responseTeams make accurate offers; customers respond or decline.Draft follow-ups and surface replies for accountable action.
QualificationSales assesses whether further discussion is useful.Organize evidence and meeting preparation.
Purchase and continued useCustomers decide; teams verify completion and subsequent usefulness.Support the work without treating a recorded stage as the outcome.

A sales development representative, or SDR, sources prospects, contacts them, and arranges meetings. Positive replies and booked meetings are closer to this role’s purpose than email volume, but they remain intermediate outcomes. Define the workflow boundary around the intended improvement, including human follow-up when completion depends on it.

Customer records, identity, and lifecycle state

Customer relationship management software, or CRM, organizes customer information and interactions. A contact represents a person; an account represents a managed organization or customer relationship; a lead represents an unqualified prospect; an opportunity represents potential business. Implementations differ, including whether leads are separate records. Salesforce’s object introduction provides one concrete model.

Identity, stage, ownership, and evidence are separate. Duplicate person records can split interaction history or generate duplicate assignments. Several legitimate contacts can participate in one deal. A stale stage can misrepresent current work. A system of record is the designated authority for a particular fact; the CRM need not govern payment or continued use. Establish field meanings and authority before accepting generated updates.

People and a potential deal

Example

Two contacts can share one opportunity.

A constructed relationship snapshot. Arrows identify associations, not stage advancement or completed purchases.
Read the diagram as text
  • Contact A.
  • Contact B.
  • Account.
  • Opportunity.
  • Recorded interaction.
  • Contact AAccount: associated with.
  • Contact BAccount: associated with.
  • AccountOpportunity: has potential business.
  • Recorded interactionContact A: involves.
A proposed review contract for CRM updates
Proposed changeRequired evidence and authorityCompletion evidence
Save a meeting summaryAn operator checks the source conversation and mapped fields.The intended record contains the reviewed values.
Advance qualificationAn authorized owner applies the organization’s stage criteria.The recorded change and its supporting reason remain inspectable.
Record a purchase outcomeUse the designated business evidence, not a generated stage recommendation.Reconcile the outcome with its authoritative record; valid JSON alone is insufficient.

Audience selection and account evidence

An audience segment groups records using explicit criteria. An ideal customer profile, or ICP, describes customers whose circumstances and needs fit the offering. Account-based marketing coordinates activity around selected organizations and their buying groups. Selection should expose its conditions: AND requires all listed conditions; OR permits alternatives. Documented segment filters make that logic inspectable.

First-party data comes from the organization’s direct interactions. Enrichment adds information from another source. Intent signals are observations interpreted as possible interest, not direct access to a person’s intentions. Keep customer statements, observed behavior, external facts, and inferred interests distinguishable. Their origin, age, uncertainty, and permitted use belong with the selection decision; collection and identity explain the broader discipline.

Example selection record: an account may qualify for research while its contacts remain unqualified for outreach.
CriterionEntity and sourceAge and uncertaintyPermitted useDecision
Target industryAccount; company descriptionObserved this month; business mix may varyAccount researchPass this condition only
Demonstrated needContact; direct responseDated response; purchasing scope unclearFollow-up assessmentInvestigate scope
Recent engagementContact; recorded eventRecent; event may not indicate buying readinessPrioritization under campaign policyRank separately from fit

Fit scores summarize properties; engagement scores summarize events. Neither is automatically a purchase probability. A former champion changing employers can justify researching the new account, but does not establish current authority or demand. Revise ICP criteria using wins, losses, and deferred decisions; updating a knowledge base is not necessarily retraining model parameters.

Purpose, consent, and contact eligibility

A lawful basis is an applicable legal ground for processing personal information. Consent is a specific, informed affirmative permission under the relevant requirements; it is not the only possible lawful basis. Purpose limitation constrains why information may be used. Processing authority, contact rules, recipient preferences, and provider restrictions require separate decisions. Privacy decision authority develops these distinctions.

Under UK PECR guidance, unsolicited electronic marketing to individual subscribers generally needs consent or a qualifying soft opt-in, a conditional exception. Corporate subscribers have different rules; sole traders can be individual subscribers. Public details or a purchased list do not establish consent where required. Suppression means retaining contact details to prevent further unwanted marketing, not treating them as a reusable audience.

A stale audience survives an opt-out

Example

Current restrictions govern dispatch.

1 / 3 · Selected

Eligibility supports export and queueing.

The same contact, export, and queued message persist. A new restriction blocks sending without rewriting historical eligibility.
Read the diagram as text
  • Contact.
  • Audience export.
  • Queued message.
  • Earlier eligibility snapshot.
  • New opt-out recorded.
  • Dispatch blocked.
  • ContactEarlier eligibility snapshot: historical state.
  • Earlier eligibility snapshotAudience export: inclusion basis.
  • Audience exportQueued message: selected recipient.
  • ContactNew opt-out recorded: current restriction.
  • New opt-out recordedDispatch blocked: prohibits contact.
  • Queued messageDispatch blocked: dispatch recheck.
  1. Selected. Eligibility supports export and queueing. Active: Contact, Earlier eligibility snapshot, Audience export, Queued message. New: Contact, Earlier eligibility snapshot, Audience export, Queued message.
  2. Preference changed. The export remains historical. Active: Contact, Earlier eligibility snapshot, Audience export, Queued message, New opt-out recorded. New: New opt-out recorded.
  3. Dispatch withheld. The local dispatch gate applies the current restriction. Active: Contact, Earlier eligibility snapshot, Audience export, Queued message, New opt-out recorded, Dispatch blocked. New: Dispatch blocked.

US CAN-SPAM guidance requires accurate sender information and subject lines, advertising identification, a postal address, and an opt-out method for commercial email. Opt-outs must be honored within ten business days; that deadline is not a recommended automation delay. Outsourcing sending does not remove responsibility. Message purpose matters even for existing customers. These rules do not establish permission for calls, texts, or every jurisdiction.

In the campaign contract illustrated below, dispatch checks current eligibility even when an older export included the recipient. Record which exports and provider queues need action, and whether those actions are confirmed. A requested cancellation is not evidence that an already accepted provider message was stopped. Authorization must account for changed permissions at the consequential operation.

Withdrawal stops reliance on the withdrawn permission. An unsubscribe can concern one channel; an objection can have broader scope. Correction changes inaccurate information; erasure removes information where applicable. Suppression serves prevention. Determine its necessary contents and permitted retention separately rather than inventing a universal period. Lifecycle fulfillment tracks these different obligations across copies.

Research that preserves evidence and uncertainty

Retrieval-backed research supplies relevant source material to an assistant preparing an answer. It can reduce manual offer selection while preserving access to supporting passages. A visible source is useful only if it supports the associated claim and its conditions. Claim-level grounding explains that boundary; retrieval does not itself verify the generated conclusion.

Constructed account brief: assume the following source records. Preserve their distinctions rather than merging them into confident personalization.
RecordSupported statementBoundary and next use
Public announcement, June 5The company announced a new site.Account fact; does not establish this contact’s project.
Restricted meeting note, June 12The contact reported manual scheduling work.Attributed customer statement; retain the internal audience restriction.
Product documentation, version 2The specified plan includes scheduling export.Product fact; do not extend it to every plan.
Analyst interpretationThe export feature may address part of the reported work.Hypothesis; confirm workflow fit and budget with the customer.

An unsupported budget inference should become an unresolved field and a seller follow-up task, not a claim that funding exists. Preserve disagreements between sources and distinguish their dates. Product comparisons need matching versions and conditions. Meeting preparation needs attributed statements, not reconstructed customer intentions. These distinctions let an incomplete brief remain useful without pretending it is complete.

Voice-of-the-customer analysis synthesizes actual customer feedback into recurring needs or problems. Structured call summaries can support that work after review. Generated personas and simulated reactions instead supply hypotheses: they are not observed testimony. Their usefulness requires comparison with real customer evidence, following the distinction developed in Synthetic Data.

Campaign content and revision-specific review

A creative brief specifies audience, customer problem, offer, channel, desired action, and supported claims. For a scheduling product, it might request an email inviting operations teams to an assessment, using only documented capabilities. AI can draft variants or a meeting follow-up. Sales enablement means preparing material that helps sellers explain the offering and conduct those conversations.

Brand voice is the organization’s chosen communication style. Tone adapts that style to the situation and reader. Mailchimp’s guide distinguishes the two and prioritizes clarity over forced humor. A reassuring style cannot establish availability, correct pricing, or authority to promise an outcome. Localization adapts material for a language and market; review must preserve meaning and applicable offer conditions.

Review the artifact being released

Example

A changed promise needs a new decision.

This local policy separates factual checks from release authority. A changed revision ends at renewed review, not automatic approval.
Read the diagram as text
  • Brief and supported facts.
  • Draft A.
  • Check claims.
  • Commercial and brand review.
  • Approve A for specified use.
  • Withhold for revision.
  • Changed draft B: re-review.
  • Brief and supported factsDraft A: data: drafting basis.
  • Draft ACheck claims: data: actual content.
  • Check claimsCommercial and brand review: control: checks pass.
  • Check claimsWithhold for revision: control: unsupported claim.
  • Commercial and brand reviewApprove A for specified use: control: authorized approval.
  • Commercial and brand reviewWithhold for revision: control: changes required.
  • Approve A for specified useChanged draft B: re-review: control: offer subsequently edited.

Claims substantiation means having evidence for consequential assertions. The FTC’s US policy requires a reasonable basis for objective advertising claims before dissemination; implied evidence standards also matter. A fluent generated claim supplies no such basis. Review product promises, comparative assertions, pricing qualifications, endorsements, and audience suitability against their applicable evidence and requirements.

Post-generation checks can reject unsupported dates or figures and flag ambiguous claims for review. Isadora Martin-Dye’s example describes an assistant offering an unavailable date without calendar evidence. Style instructions had not supplied the missing fact. Exact allowed-value checks help only for the facts they cover; examples of good wording do not guarantee correct future output.

Adobe documents review comments, requested changes, and version comparison. A useful local policy additionally binds release approval to the exact revision, audience, and intended use. Changing an offer requires renewed review under that policy; general brand approval cannot authorize the changed promise. Asset rights require their own check, as explained in media release responsibility.

Qualification and accountable sales handoffs

Qualification assesses whether and how a prospect should proceed. Lead routing assigns the resulting work to a responsible recipient. A marketing-qualified lead, or MQL, meets marketing’s criteria for sales attention; a sales-qualified lead, or SQL, meets sales’ criteria for potential business. These are organization-defined classifications, not universal facts or substitutes for supporting evidence.

BANT organizes assessment around budget, authority, need, and timeline. It is a conversation aid, not a universal gate. A buying group may lack one decision maker or a settled purchasing date. Unknown budget differs from an explicit statement that no budget is available; forcing both into a negative value loses useful information.

Routing is not acceptance

Example

Silence leaves an owner responsible.

A proposed operating contract: qualification selects the next work; recipient acceptance transfers responsibility. Rejection or an expired response deadline returns follow-up to the originator.
Read the diagram as text
  • Assess qualification evidence.
  • Originator obtains missing facts.
  • Record unsuitable or deferred.
  • Request seller acceptance.
  • Seller owns continuation.
  • Originator retains responsibility.
  • Assess qualification evidenceOriginator obtains missing facts: required facts unknown.
  • Assess qualification evidenceRecord unsuitable or deferred: evidence supports deferral or rejection.
  • Assess qualification evidenceRequest seller acceptance: ready under local criteria.
  • Request seller acceptanceSeller owns continuation: capable recipient accepts.
  • Request seller acceptanceOriginator retains responsibility: rejected or deadline expires.
A proposed qualification record keeps separate decisions separate.
DimensionAvailable evidenceDisposition
FitAccount matches explicit industry criteria.Suitable for further assessment, not proven demand.
Need and readinessProblem stated; budget and timing absent.Preserve unknowns and obtain missing information.
Contact eligibilityRelevant restriction or preference applies.Apply independently of commercial attractiveness.
Next ownerA seller has been proposed but has not accepted.Keep the originating owner responsible.

Historical outcomes can reflect earlier attention: if only contacted prospects receive follow-up, untouched prospects have less observed evidence. Missing outcomes cannot establish poor fit. Microsoft’s qualification-agent documentation describes research, matching, email-quality, and groundedness evaluations. Those tests assess components of qualification; they do not establish incremental revenue or successful acceptance by receiving sellers.

Specify an operating agreement for the handoff: evidence, unresolved fields, current owner, proposed recipient, response deadline, and rejection reasons. Under the agreement illustrated below, silence leaves responsibility with the originator. Acceptance requires a recipient able and authorized to act. Accepted handoffs explain why a notification alone does not transfer an obligation.

Outreach, replies, and stopping conditions

An outreach sequence schedules contacts and waiting periods; cadence describes their timing and pattern. Its lifecycle includes selection, drafting, approval, a current eligibility check, sending, delivery feedback, and response handling. Separate authority to draft, send, publish publicly, and make commercial commitments. Permission for one operation does not authorize the others.

A frequency cap limits contacts over a defined interval. A proposed account policy should count automated campaigns and human outreach together where they share a relationship. Otherwise, independently reasonable sequences can produce excessive contact. A substantive reply can pause the account’s automation while an owner handles the request; stopping the sequence does not complete that customer obligation.

The next action depends on state

Example

Waiting, stopping, and reconciliation differ.

Send restrictions block further marketing, not recovery. Outstanding sends and customer obligations retain accountable handling under separate authorization. For eligible contact, unresolved sends and human obligations take precedence over timing and contact limits.
Read the diagram as text
  • Check current eligibility.
  • Stop further marketing; retain recovery. The responsible owner still reconciles uncertain prior sends and handles outstanding customer obligations under their own authorization. Neither task permits another prohibited marketing send; an opt-out does not resolve a prior timeout.
  • Check remaining state.
  • Reconcile send.
  • Pause; owner resolves.
  • Wait.
  • Permit scheduled step.
  • Sequence finished.
  • Check current eligibilityStop further marketing; retain recovery: prohibited.
  • Check current eligibilityPause; owner resolves: unknown.
  • Check current eligibilityCheck remaining state: eligible.
  • Check remaining stateReconcile send: send outcome unknown.
  • Check remaining statePause; owner resolves: otherwise: reply or human obligation.
  • Check remaining stateSequence finished: otherwise: no steps remain.
  • Check remaining stateWait: otherwise: timing or cap blocks.
  • Check remaining statePermit scheduled step: otherwise: due and within limits.
Proposed reply-handling policy; classification accuracy must be evaluated separately.
Observed responseOperational treatment
Interest, substantive question, or objectionPause the automated sequence and retain an owner for a relevant response; an objection is not automatically an opt-out.
Automated or ambiguous responseDo not count it as positive intent. Apply the configured wait or route uncertainty for review.
Opt-outStop the relevant marketing and update suppression handling.

Deliverability concerns whether messages reach their intended destination. A bounce reports a delivery failure; a deferral postpones delivery. Gmail’s guidance links spam complaints to sender reputation and later filtering, including effects from shared sending IPs. Monitor delivery responses and reduce volume when failures or deferrals rise. Provider compliance does not guarantee inbox placement or establish customer interest.

An uncertain send needs reconciliation, not blind repetition. A timeout can occur after a provider accepted the operation. Repeated requests avoid duplicate effects only when the receiving service enforces an appropriate idempotency contract. Confirmed effects and business recovery cover this boundary. Stopping upcoming steps cannot recall messages already sent.

Conversions and downstream quality

A cohort is a group defined by a shared entry condition or period. A sales cycle is the interval from a specified starting event to the purchase decision. Leading indicators arrive earlier, such as replies; lagging indicators arrive later, such as purchases or retention. Guardrail metrics track harms or unacceptable deterioration rather than quantities to maximize.

Evaluation compares observations with stated criteria. Separate task quality, such as supported claims; workflow performance, such as review effort; customer outcomes, such as a useful held meeting; and business outcomes, such as purchases. Define each event, counting unit, eligible denominator, and observation window before calculating rates. Metrics and proxy failures explains why those boundaries change the meaning of a result.

Example metric dictionary; deduplicate using the stated unit and keep unresolved records visible.
ObservationAuthority and unitDenominator and windowInterpretation
Prepared and sent messagesReviewed artifacts and confirmed send recordsAssigned tasks during the campaignActivity and execution, not customer benefit
Positive responseReviewed reply; unique contactContacts reached, within a declared response periodEarly progress, distinct from a meeting
Booked versus held meetingBooking versus confirmed attendance; unique meetingEligible accounts, within the same follow-up periodCancellation or nonattendance prevents a booking from counting as held
Accepted opportunityReceiving seller’s decision; unique dealSubmitted handoffs by the response deadlineReport accepted, rejected, and unanswered separately
Purchase and retentionDesignated purchase and continued-use records; customer or accountEntry cohort with sufficient follow-upSpecify purchase and retention horizons; unfinished observation remains unfinished

In a constructed ledger, two contacts belong to one account and attend one meeting. The record contains two participating people, one held meeting, and one account with a held meeting. If ten eligible accounts received complete follow-up, the account-level held-meeting conversion is one divided by ten, or 10%. Dividing by contacts answers a different question.

Opens and clicks can arise from security scanners, privacy-related processing, or link previews before a person acts. Filtering changes can move reported engagement without changing behavior. Mailchimp’s bot-activity documentation illustrates these mechanisms and their imperfect detection. Compare engagement with confirmed outcomes, bounces, complaints, opt-outs, and sales rejection rather than treating a click as buying intent.

Suppose an account has not purchased at an interim cutoff but purchases before the declared observation window ends. Its earlier record was immature, not a confirmed final failure. After a complete window, no observed purchase means no observed purchase within that window—not nonconversion forever. Missing tracking is a separate problem from a known absence of the event.

Attribution rules and their limits

A touchpoint is a recorded interaction. Attribution assigns conversion credit to touchpoints under a rule; an attribution window limits which interactions qualify. First-touch assigns credit to the earliest eligible interaction, last-touch to the latest, and linear multi-touch divides it equally. HubSpot’s documentation describes these alternatives. The diagram fixes one journey while the table changes only the rule.

Credit for one purchase
RuleAd interactionProduct emailSales call
First-touch100
Last-touch001
Linear1/31/31/3

One observed journey

Example

Changing credit does not change events.

Arrows mean recorded order, not causation or elapsed time.
Read the diagram as text
  • Ad interaction.
  • Product email.
  • Sales call.
  • One purchase.
  • Ad interactionProduct email: next recorded.
  • Product emailSales call: next recorded.
  • Sales callOne purchase: next recorded.

Coverage constrains interpretation. Unlogged calls, broken identity links, multiple account contacts, sampled histories, and incompatible windows can produce different reports. Overlapping campaigns may claim the same purchase under separate rules. Reconcile units and coverage before combining totals. A generated narrative cannot recover an interaction that was never observed.

Campaign-associated pipeline is potential business linked to campaign activity. Credited revenue is an allocation under an attribution rule. Neither substitutes for the authoritative purchase or payment record. Nor does either establish incremental revenue: the customer might have purchased anyway. Evidence-cited analysts can make an allocation more inspectable without resolving that counterfactual.

Evidence of incremental improvement

Incrementality is the additional outcome caused by an intervention relative to its counterfactual: what would otherwise have happened. The treatment receives the intervention; the control receives the defined alternative. Conversion lift compares downstream conversions between those conditions. Google’s lift description uses advertising eligibility versus a held-back audience, which tests advertising rather than AI assistance itself.

The comparator determines the business claim.
TreatmentControlEffect being investigated
Campaign exposureHoldout from that campaignThe campaign’s additional conversions
AI-assisted campaign workExisting campaign workThe effect of the defined AI-assisted process

Compare the assistance intervention

Example

Both groups need comparable outcome evidence.

Account assignment requires shared purchasing or intervention exposure within accounts and adequately contained exposure across them. Shared sellers or reused material may require seller/team assignment, reducing independent groups. Shared follow-up capacity can alter both arms; results remain conditional on trial staffing. Compare outcomes over the same declared follow-up period.
Read the diagram as text
  • Eligible accounts.
  • AI-assisted work.
  • Existing work.
  • Assisted-group outcomes.
  • Existing-work outcomes.
  • Compare outcomes and harms.
  • Eligible accountsAI-assisted work: random assignment: treatment.
  • Eligible accountsExisting work: random assignment: control.
  • AI-assisted workAssisted-group outcomes: declared follow-up window.
  • Existing workExisting-work outcomes: same follow-up contract.
  • Assisted-group outcomesCompare outcomes and harms: defined account outcomes.
  • Existing-work outcomesCompare outcomes and harms: same definitions.

Random assignment uses chance to allocate eligible units rather than selecting treatment recipients for their apparent likelihood of success. Targeting makes observational comparison difficult: people likely to buy may also be more likely to receive advertising. In randomized advertising studies, extensive observed customer information often failed to reproduce experimental effects. That finding motivates careful comparison; it does not measure AI-assisted selling.

Assign a purchasing account together when participants share the intervention or purchasing process. This cluster assignment keeps a group in one arm; membership alone does not justify it. Contamination occurs when shared sellers or reused drafts expose controls to treatment. Seller or team assignment may help. With shared, constrained follow-up capacity, serving one arm can delay the other; account assignment alone cannot contain that interaction.

Predeclare eligible accounts, outcome definitions, follow-up periods, benefit requirements, and unacceptable harms. Record exposure and missing observations without dropping inconvenient accounts. Report uncertainty rather than promoting a noisy difference into a guarantee. Live evaluation supplies the general method; the sales-specific decision depends on mature purchases, accepted work, and customer consequences.

Observed, modeled, and projected outcomes must remain distinct. Google’s lift documentation describes modeling for missing linkage and, for specified studies, projections of delayed conversions. A projected future purchase is not an observed purchase. Align follow-up windows and wait for the planned study endpoint before interpreting immature totals as the final effect.

Operating value, ownership, and expansion

Revenue operations, often shortened to RevOps, coordinates revenue-related processes and data. Adoption means sustained appropriate use in those processes, not merely access to a tool. Compare the complete work before and after assistance. Time saved in research may be consumed by review, exception handling, or seller follow-up; additional capacity creates value only when it serves useful work.

A matched process audit, without assumed time savings
WorkBefore assistanceAfter assistanceEvidence to collect
Research and preparationRead sources and assemble notesInspect retrieved evidence and repair omissionsHandling effort and unsupported claims
Content reviewReview human draftsReview generated drafts and revisionsEditing effort, rejection reasons, queue age
Seller follow-upPrepare and conduct conversationsHandle routed interest and prepared meetingsAccepted workload and unanswered requests
Record maintenanceEnter summaries and correct recordsValidate generated fields and repair downstream errorsCorrection work and confirmed persistence

Track labor separately from elapsed waiting, software, model calls, and cleanup costs. Backlog is accumulated unresolved work. João Moura’s account of marketing and qualification assistance describes subsequent demand for customer calls, illustrating a possible shift in work rather than measured labor elimination. Whole-process measurement prevents a faster upstream step from hiding that downstream burden.

CAC=SN\mathrm{CAC}=\frac{S}{N} Customer acquisition cost, CAC, divides stated acquisition spending SS by new customers acquired NN, with N>0N>0. Specify the period, customer definition, and allocation rules. Include relevant production, software, and labor costs; long sales cycles complicate matching spending to outcomes. Shopify’s convention supplies one explicit boundary, not a universal accounting standard.
CM=RV\mathrm{CM}=R-V Contribution margin, CM, is revenue RR minus specified variable costs VV. It remains available to cover fixed expenses before profit. OpenStax’s explanation separates these quantities. For an AI rollout, reconcile cost categories so acquisition spending and variable costs are not subtracted twice. Attributed revenue alone establishes neither contribution nor profit.
Proposed ownership agreement
OwnerDecision responsibility
Campaign ownerAudience, objective, contact schedule, unresolved handoffs, and pause decisions
Sales ownerAccept or reject routed work; handle customer needs and record dispositions
Data ownerIdentity, field authority, permitted use, and correction propagation
Brand and commercial reviewersExpression, claim support, offer authority, and approval scope
Engineering ownerEnforced permissions, execution evidence, recovery, and operating limits

Expand a bounded workflow when accepted outcomes improve and review, customer harms, and operating costs remain within declared limits. Pause when unsupported promises escape, contact restrictions fail, or unresolved work exceeds responsible capacity. Correct the affected records and process before reassessment. Track bypasses and duplicate checking through adoption evidence; neither saved minutes nor favorable anecdotes establish realized cash savings.

Open questions

  1. Reliable intent assessment remains unresolved when engagement reflects automated events or uncertain identity. Wrong interpretations waste attention and distort personalization. Progress would include independently checked person/account matches and evidence that selected signals predict relevant customer responses across changing conditions.

  2. Preference changes need verifiable fulfillment across exports and provider queues. This matters because a correct central record can coexist with unwanted downstream contact, while provider acceptance complicates cancellation. Progress would include destination-specific completion evidence and explicit unresolved states without retaining unnecessary personal information.

  3. AI-assisted sales experiments need credible treatment boundaries when sellers and follow-up capacity are shared. One account’s treatment can change another’s experience, obscuring the effect being estimated. Progress would include measured exposure and spillovers, mature outcomes, and a design whose comparison remains interpretable under those interactions.

  4. Net operating value remains uncertain when preparation improves but review and customer follow-up expand. Saved effort may become useful capacity, duplicate checking, or an unmanaged backlog. Progress would pair accepted customer outcomes with complete work accounting and evidence that displaced effort actually changes costs or delivered value.

Follow the curated reading path through the speakers and demonstrations behind this entry.

Explore more talks

The rest of the library, beyond the curated path. Cited talks support this entry; reviewed transcripts were processed in full. Metadata candidates have not been reviewed as sources or verified as topic members.

11 matching talks

TalkSpeakerEventYear
Dax RaadAI Engineer Code 20252025
Rita KozlovAI Engineer World's Fair 20252025
Kshitij GroverAI Engineer Summit 20252025
Angus J. McLeanAI Engineer Europe 20262026
Matthias LuebkenAI Engineer Europe 20262026
João MouraAI Engineer World's Fair 20242024
Zhou YuAI Engineer Summit 20252025
Yegor Denisov-BlanchAI Engineer Code 20252025
Alvaro MoralesAI Engineer World's Fair 20252025
Beyang LiuAI Engineer World's Fair 20242024
Kyle MisteleAI Engineer World's Fair 20262026

References

Coverage and source review
Processed transcripts
16 processed in full · 5 in the curated path
Automated source review
Passed
Metadata candidates
0 unreviewed; not verified topic membership
Corpus version
1bd8e407b26a07b33815594e1b2db5f41827119a2b3cb6fbf240f9fc571fc767

Automated review checks source support; it is not publication approval.

A synthesis of selected conference talks and technical references. Citations link to the source material; they do not imply that every talk on this subject is included.

  1. American Marketing Association: Definitions of Marketing

    Professional association definitions of marketing and marketing research; introductory domain vocabulary.

  2. Salesforce Trailhead: Meet Salesforce Campaigns

    Campaign definition and the published All Seasons Outdoor Cooking teaching scenario.

  3. Salesforce: Sales Pipeline Management

    Sales-pipeline definition, pipeline-management explanation, deferral discussion and stage criteria.

  4. Google Ads Help: About Conversion Lift

    Campaign-versus-holdout incrementality and outcome-specific cost measurement.

  5. Salesforce Trailhead: Get Started with Account-Based Selling

    Account selection, ICP vocabulary, organizational buying participants and cross-functional responsibilities.

  6. HubSpot: Use contact and company lifecycle stages

    Default lifecycle definitions and mechanisms for updating contact and company stages.

  7. Salesforce: Marketing Funnels And Customer Journey Maps Work Harder Together

    Sections distinguishing funnel categories from individual journeys and revisited touchpoints.

  8. Using agents to build an agent company

    The reported marketing workflow combined specialized agents, social research, internet research, and the author's experience to produce drafts for the author to publish.

  9. Building Agents (the hard parts!)

    The proposed CRM workflow combines contact retrieval, email drafting, human approval before sending, and notification when a customer replies.

  10. Using agents to build an agent company

    The described lead qualification crew combined lead responses, CRM data, and industry research to produce a score, candidate use cases, and meeting talking points.

  11. Building Alice’s Brain: an AI Sales Rep that Learns Like a Human - Sherwood & Satwik, 11x

    The talk identifies positive replies and meetings booked as SDR success metrics, distinct from email throughput.

  12. Salesforce Trailhead: Get Started with Salesforce CRM

    CRM definition and Salesforce standard-object introduction.

  13. JSON Schema: Objects

    Official JSON Schema object reference; properties, required and additionalProperties examples.

  14. VoiceOps-fying Low-Latency Intelligence Extraction from Messy Audio Streams — Dippu Kumar Singh

    Map model output to the customer's CRM schema and retain an operator verification step.

  15. OWASP Access Control

    OWASP; overview, least privilege, centralized checks and protected-resource examples. AI application is an engineering inference.

  16. HubSpot: Determine filter criteria

    Segments, filter logic and published marketing-list and company-fit examples.

  17. Build the AI GTM Agent That Knows the Buyer Before the First Message

    Identity resolution remains a limiting dependency even when multiple identification providers are combined.

  18. Regulation (EU) 2016/679: definitions, processing principles and correction

    EU GDPR Articles 4–6, 16 and 19; terminology and distinct handling obligations.

  19. Salesforce: What is BANT?

    Qualification vocabulary and the author's stated limitations of the framework.

  20. HubSpot: Build lead scores to qualify contacts, companies, and deals

    Documented scoring mechanisms and examples for contacts, companies and deals.

  21. Build the AI GTM Agent That Knows the Buyer Before the First Message

    A known executive sponsor moving employers can provide a concrete signal to add a new target account.

  22. Build the AI GTM Agent That Knows the Buyer Before the First Message

    Refresh the knowledge base using sales outcomes so agents do not keep selecting accounts against an outdated ideal customer profile.

  23. ICO: How do we comply with the PECR electronic mail marketing rules?

    UK electronic-mail marketing; subscriber distinctions, consent, purchased and public details, and changed preferences.

  24. FTC: CAN-SPAM Act—A Compliance Guide for Business

    US CAN-SPAM commercial-email compliance and outsourced sending responsibilities.

  25. Saltzer and Schroeder: Basic Principles of Information Protection

    Original 1975 information-protection paper, section A design principles. Agent-specific application is an explicit engineering inference from the general principles.

  26. Making Retries Safe with Idempotent APIs

    Retries and semantic equivalence; Late arriving requests and the life span of unique client request identifiers; Same client request ID, different intent.

  27. Building Alice’s Brain: an AI Sales Rep that Learns Like a Human - Sherwood & Satwik, 11x

    Alice's manual offer library created onboarding friction and forced a tradeoff between narrow offer coverage and excessive generation context.

  28. Building Alice’s Brain: an AI Sales Rep that Learns Like a Human - Sherwood & Satwik, 11x

    Alice exposes both a UMAP knowledge visualization and the retrieved chunks behind campaign Q&A.

  29. Microsoft Learn: Draft an email message in Sales pane

    Documented drafting and meeting-follow-up workflows; source visibility and human review.

  30. VoiceOps-fying Low-Latency Intelligence Extraction from Messy Audio Streams — Dippu Kumar Singh

    Reuse structured voice-of-the-customer data for FAQ discovery and, as a roadmap extension, topic-specific staffing forecasts.

  31. Microsoft Learn: Responsible AI FAQ about the Research and engage mode of Sales Qualification Agent

    Concrete AI sales-development workflow, configuration responsibilities and disclosed evaluation methods.

  32. How Juries and Librarians Can Solve GTM's AI Trust Problem

    Use commander's intent: explain why the task matters and keep agent self-improvement focused on that purpose.

  33. Mailchimp Content Style Guide: Voice and Tone

    First-use explanation of brand voice and tone through an organization's own style rules.

  34. Adobe GenStudio for Performance Marketing: Review and Edit Content

    Documented marketing-content review, revision and proof-comparison interfaces.

  35. FTC Policy Statement Regarding Advertising Substantiation

    US advertising substantiation policy; factual product promises and comparative assertions.

  36. Stop Writing Tone Instructions. Layer Them.

    Example-anchored voice can teach preferred expression and incorporate coordinator feedback, but it cannot replace constraints, situational context, or output checks.

  37. Stop Writing Tone Instructions. Layer Them.

    Validate generated offers against authoritative allowed values before sending them; tone instructions cannot establish availability.

  38. Stop Writing Tone Instructions. Layer Them.

    Separate review flags from hard rejection, using rejection for expensive factual failures.

  39. NIST AI 100-4: Reducing Risks Posed by Synthetic Content

    Sections 3.1.1–3.2, 4.2, and 5.2–5.5; Appendix F authentication definition.

  40. OWASP authorization checks for operations and resources

    Deny by Default; Validate the Permissions on Every Request; Ensure Lookup IDs are Not Accessible Even When Guessed or Cannot Be Tampered With.

  41. Building Agents (the hard parts!)

    The talk separates an agent into client, AI reasoning, workflows, and tools, with the workflow tracking execution progress.

  42. HubSpot: Unenroll contacts from a sequence

    Concrete state-dependent outreach controls, company coordination and duplicate-send risk.

  43. Gmail Help: Email sender guidelines

    Delivery to personal Gmail accounts; sender reputation, feedback, volume and unsubscribe controls.

  44. How to Quantify AI ROI in Software Engineering (Stanford Study / 120k Devs)

    The proposed framework increases a primary engineering-output metric while keeping guardrail metrics healthy rather than maximizing them.

  45. The ROI of AI: Why You Need Eval Frameworks

    Define shared success criteria rather than promise a precise, universal measure of AI ROI.

  46. Monetizing AI — Alvaro Morales, Orb

    Outcome-based pricing requires a mutually agreed definition of success and a reasonably objective way to observe it.

  47. Building Agents (the hard parts!)

    The talk reports business benefits and recommends iterative evaluation, but supplies insufficient evidence to attribute revenue or time savings to agents.

  48. Modeling delayed conversion feedback

    Sections 2.1–2.3 and 3; equations 2–5 and the delayed-feedback likelihood. CDF expression is an equivalent mathematical restatement.

  49. Mailchimp: About Bot Activity and Bot Filtering

    Mechanisms limiting interpretation of email engagement events and one provider's filtering behavior.

  50. HubSpot: Understand attribution reporting

    Credit-allocation rules, recorded touchpoints and reporting coverage.

  51. Google Ads Help: Understand your Conversion Lift based on users measurement data

    Attribution-versus-lift reporting, observation periods, missing linkage and delayed-outcome modeling.

  52. How Juries and Librarians Can Solve GTM's AI Trust Problem

    Use a jury-and-judge workflow: independent analysts produce cited opinions, and a separate consensus judge weighs their reasoning.

  53. The ROI of AI: Why You Need Eval Frameworks

    A/B testing velocity compares tool access against a control group using delivery timelines, but team differences and operational disruptions complicate attribution.

  54. A Comparison of Approaches to Advertising Measurement: Evidence from Big Field Experiments at Facebook

    Original 2019 research paper, experimental design and comparison of observational and randomized advertising measurement.

  55. Hemming and Taljaard: Key considerations for designing, conducting and analysing a cluster randomized trial

    Sections 2–3, 5 and 7; B2B account, seller and material-sharing examples are explicit methodological applications, not observed sales results.

  56. Boutilier et al.: Operational Dosage—Implications of Capacity Constraints for the Design and Interpretation of Experiments

    December 2025 version, introduction and queueing-model setup; sales follow-up and shared-arm capacity are explicit applications of the mechanism.

  57. How to Quantify AI ROI in Software Engineering (Stanford Study / 120k Devs)

    Engineering outcomes can provide a more interpretable AI-impact signal than revenue, but translating capacity into value requires explicit assumptions.

  58. Build the AI GTM Agent That Knows the Buyer Before the First Message

    Approval queues become unsustainable when AI drafts require enough editing that users would rather write messages themselves.

  59. Using agents to build an agent company

    The speaker's marketing and lead qualification sequence was followed by a heavy customer-call workload rather than the elimination of personal work.

  60. Shopify: Ecommerce Customer Acquisition—Channels and Formula

    Ecommerce CAC vocabulary and an explicit published acquisition-cost boundary.

  61. OpenStax: Explain Contribution Margin and Calculate Contribution Margin

    Managerial-accounting definitions and the published kiosk teaching example.

  62. Build the AI GTM Agent That Knows the Buyer Before the First Message

    The proposed architecture separates signals, buyer intelligence, and action, with explicit qualification and CRM matching before outreach decisions.

  63. NIST Privacy Framework, Version 1.0

    Section 1.2; Appendix A: GV.PO-P1, CT.PO-P1–P3, CT.DM-P4–P8, CT.DP-P1–P4, CM.PO-P1, and CM.AW-P1/P5/P8.

  64. Build the AI GTM Agent That Knows the Buyer Before the First Message

    The context graph connects person-level signals to accounts and deal activity so that individual interactions can inform buying-committee visibility and account prioritization.