Email That Moves Pipeline: The Full‑Service Playbook for Professional Services

Most email failures in professional services are not caused by weak tools. They come from unclear ownership of data, revenue targets, and review authority. A full-service email marketing agency for professional services companies plans, builds, and runs the entire channel (strategy, segmentation, copy/design, automation, deliverability, analytics, and sales integration) under operating controls that tie activity to pipeline. For mid-market operators, that means turning client and prospect data into a 12‑month engine that advances deals, protects margin, and increases revenue predictability.

Why is email underperforming in professional services when the tech is fine?

Most misses are control failures. Not creative failures. Not platform failures. When the list lives in three places, legal reviews take three weeks, and sales doesn’t trust nurture scoring, your clicks don’t convert. Hard truth: deliverability isn’t your problem; decision latency is. If a message can’t move from concept to inbox inside 10 working days, the market moved and your relevance fell by half.

We’ve all shipped a quarterly insights email to 18,400 contacts. Opens plateaued, five clients replied “unsubscribe me from all,” and your BD team couldn’t name one opportunity touched by last quarter’s sends. The footer still points to a contact form no one checks on Fridays.

Your email problem isn’t content. It’s custody: no one owns the pipeline math.

What root causes create stalled email programs in professional services?

Tools amplify discipline. They don’t create it. The consistent failure modes trace back to process and ownership:

  • Fragmented data custody. Marketing works from a marketing automation list; sales updates a separate CRM; finance holds the true client roster. No single source of truth or preference center that gates sends.
  • Legal and compliance backlog. Review cycles built for public filings get applied to a webinar invite. Weeks pass. The event is over; the email is perfect.
  • Undefined lifecycle. No shared model of the buyer and client lifecycle: suspect → lead → MQL → SQL → proposal → client → expansion. Nurtures aren’t aligned to stages, so messages lack jobs.
  • Creative without a messaging matrix. Teams write thought leadership without mapping objections, industry nuances, and CTAs by persona and stage. The copy speaks to everyone and persuades no one.
  • Attribution theater. UTM standards vary, reply handling is manual, and routed leads die in inboxes. Email’s revenue influence is undercounted, so it gets deprioritized.
  • Deliverability blind spots. Cold list uploads, parked domains, and ISP throttling get ignored until a major campaign faceplants. Then the fix becomes a crusade that fades after two weeks.

What is the economic exposure when email isn’t run like a revenue channel?

Exposure scales with three levers you already track: lead flow, win rate, and cycle time. When email underperforms, fewer opportunities enter the pipeline, fewer proposals get air cover, and cycles stretch because prospects wait for clarity they never receive.

Consider a $60M regional engineering consultancy with three practice lines and 14 BD managers. Weekly, they see new inbound inquiries, multiple open proposals, and a rolling backlog of dormant contacts who engaged once. If email doesn’t advance those segments with stage-specific content and timely follow-ups, here’s what happens:

  • Inquiries cool while they shop competitors with stronger nurture programs.
  • Proposals go dark without objection handling sequences nudging the buying committee.
  • Dormant contacts never re-engage because the firm sends newsletters instead of relevance.

Delay exposure grows with the number of open proposals, the value of each, and the length of silence between touches. Stretch that silence across a quarter and your forecast variance widens. Finance sees unpredictability. Sales blames price. Marketing gets its budget questioned. Nobody models the cost of letting warm demand cool.

Email remains a top owned distribution channel for B2B content programs. Owning a channel that reaches decision-makers directly is useful. Owning it without a routing SLA is just overhead.

Benchmarks and ranges are directional, based on industry patterns. Actual results vary by operation size, market conditions, volume, and provider capabilities. Validate all metrics with your specific providers and operational context.

Which mechanisms actually move revenue with email, and how do they interact?

Skip the feature list. Here’s how the levers interact, distort behavior, and create or remove friction:

Lifecycle segmentation only works when Sales validates stage definitions

Marketing wants volume. Sales wants qualified exploratory sessions. If Marketing unilaterally defines stages, Sales ignores scores and keeps working their own lists. Mechanism: stage drift. Threshold: if more than a third of MQLs get rejected in CRM, your scoring model is noise. Fix: Sales and Marketing co‑author entry and exit criteria with two acceptance tests (conversion rates and rep trust).

Messaging matrices create persuasion; generic content creates politeness

A messaging matrix ties persona, industry, and lifecycle stage to problems, proof, and calls to action. It’s the spine of your digital brand building process. Mechanism: specificity increases reply quality because you engage on an emotional level (fear of downtime, audit risk, or reputational harm) then resolve it with a next step. Threshold: if multiple personas share the same CTA, the matrix is unfinished. Failure mode: insights emails that never ask for an exploratory session.

Cadence without decision rights creates spam; cadence with SLAs creates momentum

Legal optimizes for risk; Marketing optimizes for timeliness. If Legal can hold a campaign without a timed escalation path, cadence degrades. Mechanism: review creep. Threshold: if review lead time exceeds five business days for non‑claims content, velocity collapses. Counterweight: pre‑approved content libraries, risk tiers, and a standing two‑hour micro‑review path for time-sensitive sends.

Deliverability is a management problem disguised as a technical problem

IT cares about domain health; Marketing cares about list growth. If incentives clash, cold imports and hard bounces burn your sender reputation. Mechanism: shared asset, split ownership. Threshold: if bounce rate rises above a tight internal limit across two campaigns, pause acquisition sources. Enforcement: IT veto on list imports; Marketing owns re‑permission campaigns.

Attribution discipline changes budget conversations

Finance funds what it can see. If email replies are not auto‑associated to contacts and opportunities in CRM, email’s influence looks weak. Mechanism: invisible touches don’t defend headcount. Threshold: if fewer than half of email replies auto‑log to the right record, your attribution is broken. Enforcement: a single owner for UTM taxonomy and reply‑to routing; weekly exception sweeps.

Sales routing SLAs turn interest into revenue

Response time kills or compounds interest. Responding to qualified inbound within an hour materially improves conversion versus next day. You spent six figures on automation and routed the reply to a shared inbox. Outcome: silence.

Web-to-email feedback loop is the multiplier

When the website operates like a decision‑making engine (built around buyer questions, objections, service clarity, proof, and conversion paths), email stops promoting and starts advancing deals. Mechanism: each email links to assets that resolve a real buying obstacle. Threshold: if more than half of email traffic bounces on arrival, your landing destinations aren’t answering the question asked.

What are the trade-offs you must choose knowingly?

Decision Upside Trade-off When to choose
Higher send frequency More touchpoints, faster learning cycles List fatigue risk; greater creative load When you have fresh, stage‑specific content and suppression rules
Deeper personalization Higher relevance and reply quality Data dependency; segmentation complexity; QA overhead When CRM hygiene is high and personas are well‑defined
Automation-heavy nurture Adaptable, always‑on revenue support Initial build time; change‑control rigor required When lifecycle is stable and content library is comprehensive
Live campaign focus Timeliness; event and offer amplification Volatility; review bottlenecks can stall impact When Legal SLA is tight and teams can shift quickly
Single domain sending Brand consistency; simpler DNS management Reputation concentration risk When deliverability management is mature
Multiple subdomains Isolation of risk; testing freedom More IT work; potential brand dilution When running high‑volume programs across practices

Where does a full-service email program fail inside a professional services firm?

Failure isn’t subtle. It’s patterned. Here are the native friction points and what causes them:

  • Shadow spreadsheets. Reps run their own lists because they don’t trust Marketing’s segments. Cause: scoring misfires and poor feedback loops. Result: off‑platform sends that poison domain health.
  • Content that defends the firm, not the decision. Pages that talk about credentials instead of solving the buying obstacle. Result: clicks without exploratory sessions. This is where a decision‑making website matters; it converts email attention into progress.
  • Legal review gridlock. Risk tiers aren’t defined, so every send is treated like a press release. Real failure insight: on regulated teams, a webinar invite can take 14 business days to clear. By then, the seats are gone and your last chance email lands after the event. That outcome is avoidable with clear SLAs.
  • Deliverability death by cold import. A partner dumps a list from a conference into the tool. Hard bounces spike, ISPs throttle, and campaign performance tanks for weeks. Mechanism: reputation damage spreads across sends.
  • Inconsistent reply routing. A prospect replies “Can we talk next week?” to a no‑reply address. No ticket. No alert. No exploratory session. Business problem, not a tech quirk.
  • Automation entropy. Nurtures built last year point to retired assets, expired offers, or old leadership bios. Without expiry controls and content audits, your always‑on engine quietly runs in the wrong direction.
  • Testing theater. Teams run A/B tests on subject lines while ignoring the real lever: CTA and landing experience. Mechanism: safe tests that don’t threaten the calendar but don’t change revenue.
  • Preference center theater. You have one. It’s hidden, generic, and doesn’t map to services or industries. Result: unsubscribes you could have saved if recipients could choose frequency or topics that match their role.

How should you run a full-service agency relationship so email drives revenue?

Control is decision rights, risk allocation, and enforcement. Not another meeting. Define these layers up front:

Commercial (investment, scope, and risk)

  • Scope clarity. Agency owns strategy, creative, automation, deliverability, and analytics; internal team owns CRM integrity and sales routing. Change orders require written approval by the Marketing VP.
  • Performance incentives. Tie a portion of fees to stage‑movement KPIs you already trust: exploratory sessions set from email touches, proposal advancement, reactivation of dormant accounts. Beware vanity metrics.
  • Risk allocation. Who absorbs remediation if deliverability tanks due to a process breach? Codify it. List import rules and sender reputation protections are non‑negotiable.

Operational (SLAs, data, and exceptions)

  • Data ownership. The firm owns the list and preference center. The agency maintains hygiene under documented standards. Thresholds for bounces, complaints, and removal rules are explicit.
  • Approval authority. Risk‑tiered review: Tier 1 (no claims) → 24‑hour turnaround; Tier 2 (light claims) → 72 hours; Tier 3 (regulated claims) → 5 business days. Escalation to GC if breached.
  • Routing SLA. All qualified replies and form completions triggered by email hit CRM with owner assignment within two hours during business days. Sales leadership owns the SLA; agency audits exceptions weekly.
  • Change control. Any automation logic change moves through a defined ticket, staging environment, and QA checklist. Operations owns the checklist; agency executes.

Strategic (direction, investment, and exit)

  • Quarterly direction. Agree on lifecycle priorities: new logo acquisition, proposal advancement, client expansion, or reactivation. Budgets follow the priority; testing plans support the theme.
  • Joint assets. Invest in content that answers objections you hear on calls (videos, calculators, on-brand, accessible, visually appealing infographics, case briefs). Email then distributes assets with clear CTAs to drive quality traffic back to the decision‑making site.
  • Exit triggers. Performance below agreed thresholds for two consecutive quarters, persistent process breaches, or sender reputation at risk initiates a reset or transition plan.

How does this play out in a real mid‑market scenario?

Imagine a $55M environmental engineering firm with three regional offices and account teams split by industry. They hire a full‑service email partner to build a 12‑month engine around four plays: net‑new demand, proposal advancement, client education, and cross‑sell.

  • Data cleanup and controls. One source of truth, mapped preferences, suppression lists, and reply‑to routing tested under load.
  • Messaging matrix creation. Personas by role (plant manager, EHS director, procurement) and stage, with objections and proof mapped to each. CTAs ladder from “see the audit checklist” to “book a scoping call.”
  • Automation build. Stage‑based nurtures, proposal‑support sequences, and quarterly re‑engagement for dormant contacts.
  • Legal risk tiers. Pre‑approved libraries for routine content; a 48‑hour path for invites and recaps.
  • Website alignment. Landing destinations reworked to function like a digital sales associate: questions answered, proof visible, next steps obvious.

Result after stabilization: faster proposal cycles and clearer attribution. Not magic. Just discipline tied to sales motion. The agency didn’t add noise; it added a system you can manage.

What frictions should you plan (and budget time) for in months 1–6?

  • Implementation drag. Data hygiene takes longer than your SOW suggests because duplicates and naming conventions resist automation. Accept it; sloppiness bleeds into every send.
  • Temporary performance dips. As you warm domains and tighten list standards, volumes may shrink before reply quality rises. That’s not failure; that’s exposure coming into view.
  • Internal resistance. BD reps initially prefer ad‑hoc blasts. Plan enablement sessions and early wins tied to their accounts.
  • Content gaps. Objection‑handling assets don’t exist yet. Build them in parallel (short videos and briefs mapped to the matrix).
  • Change‑control learning curve. Staging and QA feel slow in month two. By month four, they prevent the wrong link email from hitting 12,000 inboxes. Worth it.

How do agency decisions shift power dynamics inside your firm?

Owned channels shift power away from rented audiences. When email becomes a disciplined engine, Sales brings opportunities; Marketing brings acceleration; Finance gets predictability. Legal still protects the brand, but within response‑time rules. The portfolio of assets (list, preference center, automations, and a website that actually helps buyers decide) becomes an appreciating asset that compounds every quarter.

The agencies that produce the most durable results tend to start with the distribution question (who you’re emailing, why, and where you send them) before they write a single subject line.

Email does not create discipline. It enforces it. Firms that lack it experience exposure, not improvement. Operating discipline determines which side you land on.

Key Takeaways

  • Most email failures in professional services are control failures: fix decision rights and SLAs before tools.
  • Create a messaging matrix that ties persona and stage to objections, proof, and CTAs to convert attention into exploratory sessions.
  • Measure revenue impact by stage movement and response time; attribution discipline protects investment and headcount.
  • Define agency operating rules: data custody, legal risk tiers, routing SLAs, and exit triggers to keep velocity and reputation intact.
  • Align email with a decision‑making website so every click advances a deal, not just a session.

Frequently Asked Questions

How fast should a full‑service agency be able to launch our first campaigns?

With clean data and clear controls, expect first sends inside four to six weeks. If data hygiene is poor or legal review is unscoped, it can extend. The critical variable is decision latency: predefine risk tiers and SLAs so velocity holds. Don’t trade speed for deliverability; warm sending domains methodically.

What KPIs should we hold the agency accountable to beyond open and click rates?

Track stage movement, qualified reply rate, exploratory sessions set from email touches, proposal advancement, and reactivation of dormant accounts. Response time on routed leads matters because it compounds conversion. Opens and clicks are diagnostics, not board metrics; tie compensation to pipeline impact you already trust.

How do we handle legal and compliance without slowing everything down?

Build risk tiers with pre‑approved content libraries and explicit timelines: 24 hours for routine communications, 72 hours for light claims, and five business days for regulated claims. Escalate deadlocks to the GC. The agency should provide templates, footers, and claims tracking so reviews are focused and fast.

Should we send from our primary domain or set up subdomains?

Single domains simplify brand control but concentrate risk. Subdomains isolate sending reputation and allow parallel programs across practices. Choose based on your deliverability maturity and program volume. Whatever the path, IT must own DNS, DKIM, SPF, and DMARC with clear change control.

What content mix works best for professional services email?

Map content to lifecycle: invites and primers for net‑new, objection‑handling assets for proposals, onboarding and education for clients, and signals‑based cross‑sell for expansion. Short videos, calculators, and concise briefs outperform thought pieces when the job is to secure an exploratory session. Link to landing pages that answer the next question.

How do we prove revenue impact to Finance?

Standardize UTM parameters, auto‑log replies to CRM records, and instrument stage movement dashboards. Finance cares about predictability; show shorter cycle times and higher conversion where email touched the deal. Run holdout tests quarterly to validate incrementality and protect the budget conversation.

How to Evaluate a Full-Service Email Marketing Agency for Professional Services Companies

Most agencies can send emails. Far fewer can orchestrate pipeline with compliant data operations and change management across sales, marketing, service, and finance. Use this lens:

  • Industry fluency: Can they show programs and artifacts for manufacturing, logistics, engineering, financial and alt‑finance, skilled trades, landscaping, or hospitality? Ask for regulated‑industry examples (review workflows, disclaimers, approvals).
  • Lifecycle architecture: Do they map the entire 12‑month journey across acquisition, onboarding, adoption, expansion, and win‑back? Request a journey map and trigger matrix sample.
  • Data and integration: Can they own the event model, identity resolution, and integrations (CRM, ERP, booking/PMS, finance)? Confirm they have developers skilled in APIs, webhooks, and middleware.
  • Deliverability and reputation: Do they manage IP and domain warmup, DMARC/DKIM/SPF, and run list hygiene and spam trap monitoring? Ask for a remediation playbook.
  • Creative systems at scale: Can they deliver modular design systems, content ops, and dynamic personalization without breaking brand or accessibility?
  • Testing and analytics: Do they commit to test design (A/B, MVT, holdouts) and decision‑quality reporting tied to pipeline stages?
  • Security and compliance: SOC 2 posture, DPA, subprocessors, role‑based access, consent management, and knowledge of CAN‑SPAM, CASL, GDPR, CCPA/CPRA, SEC/FINRA review flows, and HIPAA where applicable.
  • Change management: Can they build SLAs, RACI, and an operating cadence (WBR/MBR/QBR) that aligns GTM and finance?
  • Resourcing: Dedicated strategist, marketing ops, copy, design, dev and integration, deliverability, QA, and analytics (not a single email specialist).
  • Documentation: Do they provide runbooks, QA checklists, and recovery procedures? If it’s not documented, it won’t scale.

RFP Questions and a 100‑Point Scorecard

Issue a focused RFP and score with discipline. Weighting below is a starting point.

Essential RFP Questions

  • Show a recent 12‑month lifecycle program you architected for a company like ours. Include KPIs, org model, and tech diagram.
  • Explain your integration approach with our CRM and ERP. Provide a sample event schema and error‑handling protocol.
  • Walk through your deliverability warmup plan for a new subdomain and how you manage reputation ongoing.
  • Provide your QA checklist from data pull to deployment, and your rollback plan if an error is detected post‑send.
  • Describe your testing philosophy, minimum test cell sizes, and how you determine significance and rollouts.
  • Outline your operating rules: SLAs, RACI, approval stages, content ops, and audit trails for regulated reviews.
  • Share three anonymized dashboards that tie email touches to opportunity stage movement and revenue.
  • Detail your accessibility and localization standards (WCAG, reading level, alt text, RTL languages if needed).
  • List your security certifications, DPAs, subprocessors, and incident response SLAs.
  • Propose a 90‑day onboarding with resourcing, milestones, and decision gates.

Scorecard (100 Points)

  • Lifecycle Strategy and Content System – 25
  • Data, Integration, and QA – 20
  • Deliverability and Compliance – 15
  • Testing and Analytics Rigor – 15
  • Team Depth and Resourcing – 10
  • Change Management – 10
  • Cultural Fit and Communication – 5

Engagement and Pricing Models to Expect

Know how costs align with outcomes and control scope creep before kickoff.

  • Retainer (most common): Monthly fee covering strategy, ops, creative, QA, reporting, and operating controls. Add‑ons for major integrations or migrations.
  • Project‑Based: Fixed fee for migrations, redesigns, or discrete automations. Pair with a small retainer for optimization after launch.
  • Hybrid: Retainer core plus drawdown hours for flex capacity during seasonality or product launches.
  • Performance Components: Bonuses tied to qualified stage movement or net revenue lift validated via holdouts. Avoid pure CPL or CPA in long‑cycle B2B.
  • Platform Pass‑Through: ESP, CDP, and automation licenses billed directly to you; the agency should not mark these up.

Ask for a transparent staffing plan, hourly rate card by role, and an assumptions log so expansions are structured, not surprise invoices.

The First 90 Days: A Practical Plan

Days 0–30: Assessment and Foundation

  • Discovery: Decision-maker interviews across Sales, Marketing, Service, Finance, IT. Document SLAs and pain points.
  • Data Audit: Map sources, consent status, identity resolution, and event coverage. Draft unified schema.
  • Deliverability Baseline: Domain health, DNS, spam complaint rates, list quality, and IP decisions (shared vs. dedicated).
  • Quick Wins: Sunset policy, list hygiene, preference center patches, top 5 template accessibility fixes.
  • Operating Rhythm Kickoff: Approvals, review routes (legal and compliance), and weekly operating rhythm.

Days 31–60: Build and Pilot

  • Architecture: Trigger matrix, content model, and modular design system.
  • Integration: CRM and ERP syncs, event ingestion, testing environments, and observability (alerts and logs).
  • Pilot Programs: Reactivation, lead nurture v1, onboarding v1 with basic personalization.
  • Testing: A/B subject, send time, and CTA framing. Define minimum sample sizes.
  • Dashboards: WBR view for channel health; MBR view tying to funnel stages.

Days 61–90: Scale and Govern

  • Expand: Add lifecycle branches (expansion, cross‑sell, renewal). Introduce product or content recommendations where data allows.
  • Deliverability: Start or continue warmup; implement DMARC enforcement if not already.
  • Sales Enablement: Surface next best email triggers inside CRM with snippets and playbooks.
  • QBR #1: Review results, reset quarterly OKRs, lock test roadmap and budget guardrails.

Deliverability, Consent, and Compliance for Professional Services

Your brand equity and legal exposure ride on this stack. Non‑negotiables:

  • Authentication: SPF, DKIM, DMARC (monitor → quarantine → reject), BIMI where eligible.
  • Reputation: Warm new sending domains and subdomains gradually; segment by engagement during warmup.
  • List Integrity: Double opt‑in where viable; verifiable consent capture and synced suppression lists across systems.
  • Regulatory: CAN‑SPAM, CASL, GDPR, CCPA/CPRA; sector overlays like SEC Marketing Rule and FINRA 2210 (financial), HIPAA and BAA (health‑adjacent services), ADA and WCAG for accessibility.
  • Retention: Data minimization and purpose limitation; time‑bound retention and defensible deletion policies.
  • Audit Trails: Immutable logs for approvals, content changes, and deployments. Store evidence for exams or discovery.

Reference Stack Blueprint

Choose tools your team can operate, not just what wins a slide. A pragmatic stack:

  • ESP and Marketing Automation: Iterable, HubSpot, Salesforce Marketing Cloud, Klaviyo (for SMB and mid), Marketo (B2B complex). Fit to data model and team skills.
  • CRM: Salesforce, HubSpot, Microsoft Dynamics (must be the attribution and activity source of truth).
  • CDP and Identity: Segment, mParticle, Tealium, or native CDP (standardize events and consent).
  • Data Warehouse and BI: Snowflake, BigQuery, or Redshift plus Looker, Power BI, or Tableau for stage movement dashboards.
  • Integration and Middleware: Workato, Make, custom serverless (AWS Lambda, GCP Cloud Functions) for reliable, observable syncs.
  • QA and Monitoring: Litmus or Email on Acid for rendering; Postmark or seedlists for inboxing; custom alerting for sync failures.

Benchmarks and What Good Looks Like by Vertical

Benchmarks are directional; measure against your baseline and market. Reasonable targets after two to three quarters of disciplined execution:

  • Manufacturing and Engineering (B2B):
    • Engagement: 25–35% open rate (post‑Apple MPP adjusted), 2–4% click rate
    • Pipeline: 10–20% faster stage velocity where email is present; 5–10% higher SQO‑to‑win when nurtured
  • Logistics:
    • Engagement: 22–32% open, 2–3% click
    • Pipeline: Improved conversion from discovery to proposal by 5–8%
  • Financial and Alt‑Finance:
    • Engagement: 20–28% open, 1.5–3% click (compliance‑heavy content)
    • Pipeline: 8–12% lift in qualified applications with pre‑approval nurture
  • Skilled Trades and Landscaping (B2B and Commercial):
    • Engagement: 28–38% open, 3–5% click
    • Revenue: 5–10% higher contract renewals with seasonal service cadences
  • Hospitality (group/events and corporate):
    • Engagement: 30–40% open, 3–6% click
    • Revenue: 6–12% lift in off‑peak bookings via segmented offers

Run quarterly holdouts and lift studies to validate incrementality against these targets.

Common Pitfalls and How to Avoid Them

  • List‑first mindset: Buying lists or emailing cold contacts erodes domain reputation. Build consented audiences and partnerships instead.
  • One‑off campaigns: Without lifecycle automation, you’ll see churn and seasonality whiplash. Prioritize always‑on journeys.
  • Attribution myopia: Overweighting last‑click email starves top‑of‑funnel. Balance with stage movement and holdout testing.
  • Underfunded data work: Creative without clean data caps performance. Fund integrations and event quality early.
  • No content ops: If content isn’t systematized, velocity dies. Invest in a modular system and a living content calendar.
  • Skipping deliverability hygiene: Poor list practices and misconfigured DNS undo months of work. Make hygiene a weekly ritual.

Executive Checklist

  • Do we have a 12‑month lifecycle map with SLAs, content modules, and triggers?
  • Is DMARC enforced and are we actively monitoring domain reputation?
  • Are dashboards showing stage movement and time‑to‑close where email is present?
  • Have we approved a quarterly test and holdout plan tied to budget decisions?
  • Is there a documented RACI and audit trail that satisfies compliance and legal?
  • Do Sales and Service have playbooks for following up on email intent signals?