See how Pulse surfaces timely account signals inside Dynamics 365, then review the AppSource install, tenant permissions, data flow, and security model your IT team will evaluate.
IT teams dread sales tools that require months of custom engineering, invasive tenant permissions, or fragile sync jobs. Pulse installs in about 2 hours as a Microsoft signed AppSource managed solution. All schema updates are packaged in that solution, so there is no custom schema work in your environment.
Solution imported. Three new views appear in the sitemap. No core tables modified.
Reads four read-only fields per record (name, website URL, city, and state) from your Leads and your Accounts, including the parent account of each opportunity. Runs the AI scoring job on the cadence you pick.
Scored cards, ranked lists, and AI-written angles written back to your Pulse entities.
For external sales-signal research, Pulse uses Leads and Accounts, including the parent account of each opportunity, and reads four fields on each: name, website URL, city, and state. Leads use the same read-only permissions as Accounts. Nothing about your contacts, conversations, opportunity values, or pipeline activity ever leaves your Dynamics tenant.
Pipeline Insights also uses opportunity data inside Dynamics 365 across four views: Pipeline Health, Needs Attention, Won vs Lost, and Opportunity Sales Cycle. The table below describes the external research data flow, rather than all data used by the product.
Zero retention. The four fields we read are used to run the research pass, then discarded. We don't keep a copy of your account list on our side. The scores, news URLs, and insights we generate are written back into your tenant. That's where they live.
| Field | Used for external research? | Leaves your tenant? |
|---|---|---|
| Account name & Lead name | Yes | Yes, for lookup |
| Account website URL & Lead website URL | Yes | Yes, for lookup |
| Account city & Lead city | Yes | Yes, lookup & signal matching |
| Account state & Lead state | Yes | Yes, lookup & signal matching |
| Contact records | No | Never |
| Opportunity values, stages, dates | No | Never |
| Email or activity history | No | Never |
| Notes, attachments, files | No | Never |
| Pulse score, news URL, and insights | Yes, written back | Stored in your tenant |
For every Account and Lead record we receive (name, website URL, city, and state), Pulse runs a focused research pass against public sources. City and state ground each signal to the right location, so a plant expansion in Ohio doesn't get matched to a same-named entity in Texas. The model isn't summarizing the internet. It's looking for a specific class of signal that sales teams actually act on.
Earnings calls, press releases, business-news coverage, regional trade publications. We index the sources, the AI doesn't crawl them itself.
SEC filings, public M&A announcements, funding rounds, public-tender awards.
Executive moves, role changes, named hires in functions you care about (we map your ICP roles up front).
Plant openings, capacity expansions, layoffs, technology stack changes mentioned in public sources.
We don't scrape LinkedIn DMs, private Slack channels, or anything behind a login. Only public surfaces.
Pulse doesn't know who your reps emailed or what they said. The scoring is about the world, not about your team.
For each signal that survives the relevance filter, the model writes a short "why this matters" paragraph in plain English and tags one or two source links. That's the artifact your rep sees on the card.
Pulse combines sales-signal views with four Pipeline Insights views inside Dynamics 365. Reps can prioritize relevant outreach, while managers and revenue leaders review Pipeline Health, Needs Attention, Won vs Lost, and Opportunity Sales Cycle.
Instead of starting the morning wondering which accounts are active or scrolling LinkedIn for context, reps open Dynamics 365 to a prioritized kanban of hot accounts. Every card delivers the exact news trigger, the AI written selling angle, and verified bullet highlights so outreach is relevant on the very first touch.
Managers waste hours every Monday interrogating reps for deal status. Pulse rolls every rep's pipeline into one prioritized view, flagging high value deals that have fresh market triggers so you can raise them in coaching before momentum dies.
Revenue executives usually discover deal decay only after a quarter is already lost. Pulse aggregates external market pressure, deal velocity, and pipeline risk across segments so leaders can spot forecast vulnerabilities weeks before the close.
Pulse is a Microsoft-signed AppSource solution. The connection between your Dynamics tenant and our service is OAuth 2.0, read-only, scoped to four fields on Accounts and Leads. We operate a strict zero-retention policy: those fields are read for a research pass and discarded. No copy of your account list lives on our side. Your Microsoft 365 admin can revoke the connection at any time, and the solution can be uninstalled cleanly, with no orphaned records and no residual data.
Read-only scope on four fields (name, website URL, city, and state) on both Accounts and Leads. Revoke from Microsoft 365 admin in two clicks.
The solution package is signed and listed on Microsoft Marketplace. Same install pattern as any other AppSource product.
By default, Pulse runs in US-East. EU-West and APAC regions available for enterprise tier on request.
The four fields we read are used for the research pass and discarded. We don't maintain a copy of your account list, your pipeline, or anything else outside your tenant.
Plan for about 2 hours of IT/admin time on install day, plus up to 24 hours for the first Pulse run to complete against your Accounts and Leads. Most teams are viewing live Pulse insights by the next business day. For Dynamics admins, the key details are below: what gets installed, which fields Pulse reads, how OAuth access works, and what needs to happen before the first run.
account.name, account.websiteurl, account city, account state, lead name, lead website URL, lead city, and lead state. All read-only.Our implementation engineer is on the line for all of the above. You don't need to do it from a documentation page.
Book a 30 minute walkthrough. We will bring an implementation engineer so revenue leaders and IT can get every question answered in one conversation.
Book a Demo →