How it works

Built for the sales conversation and the IT review.

The first sections show sales leaders how Pulse turns Dynamics 365 data into timely account signals. The technical sections give Dynamics admins the context they need to review installation, permissions, data access, OAuth, and the first Pulse run.

For IT & admins · 03

Install one solution package.

Pulse ships as a signed Microsoft AppSource solution. Your Dynamics admin imports it the same way you'd import any other managed solution. It registers three entities and three model-driven views, then opens an OAuth handshake to our hosted service.

In your tenant

Dynamics 365

Solution imported. Three new views appear in the sitemap. No core tables modified.

OAuth · scoped

Pulse Service

Reads four read-only fields per record (name, website URL, city, and state) from both your Accounts and your Leads. Runs the AI scoring job on the cadence you pick.

Back into Dynamics

Pulse Views

Scored cards, ranked lists, and AI-written angles written back to your Pulse entities.

For IT & admins · 04

The data model is small, by design.

Pulse looks at two record types in your Dynamics environment (Accounts and Leads) and reads the same 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.

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 Read by Pulse? Leaves your tenant?
Account name & Lead nameYesYes, for lookup
Account website URL & Lead website URLYesYes, for lookup
Account city & Lead cityYesYes, lookup & signal matching
Account state & Lead stateYesYes, lookup & signal matching
Contact recordsNoNever
Opportunity values, stages, datesNoNever
Email or activity historyNoNever
Notes, attachments, filesNoNever
Pulse score, news URL, and insightsYes, written backStored in your tenant
For sales leaders · 01

What the AI actually looks at.

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.

Reads

Public news & press

Earnings calls, press releases, business-news coverage, regional trade publications. We index the sources, the AI doesn't crawl them itself.

Reads

Regulatory & financial filings

SEC filings, public M&A announcements, funding rounds, public-tender awards.

Reads

Leadership & org changes

Executive moves, role changes, named hires in functions you care about (we map your ICP roles up front).

Reads

Operational signals

Plant openings, capacity expansions, layoffs, technology stack changes mentioned in public sources.

Does not read

Social media DMs & private content

We don't scrape LinkedIn DMs, private Slack channels, or anything behind a login. Only public surfaces.

Does not read

Your CRM activity

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.

For sales leaders · 02

What each role sees.

Three Pulse views, scoped by Dynamics security role. Each is built for a specific job: the one your rep, manager, or exec is actually doing when they open the CRM.

Lands in · Opportunity Pulse / Lead Pulse · Mobile-first

A ranked list of accounts worth calling today, on whatever screen is open.

The rep view is built for the phone first, the laptop second. Reps open Dynamics 365 mobile to a kanban of their pipeline sorted top-down by Pulse score; hot cards float to the top with a red badge. Tap any card and the latest news, the AI-written angle, and three bullet highlights are right there. The same view renders on the desktop for the back-at-the-desk hour.

  • Mobile-native: uses the Dynamics 365 mobile app reps already have on their phone
  • Sort, filter, and group cards the same way they already do in Dynamics
  • One-tap jump to the source articles cited on each card
  • Dismiss a signal as "not useful". The model learns from those
  • Set a personal watchlist for accounts they want hot-pinged on
Lands in · Pulse Summary

The whole pipeline, weighted by what's actually moving.

Managers see every rep's open opportunities rolled into one view, sorted by aggregate Pulse score. The "Needs attention" feed at the top lists deals that have new signal but no new activity. Those are the gaps the Monday call should focus on.

  • Per-rep view of how many high-Pulse accounts went un-worked last week
  • Filter by stage, segment, region, or named opportunity owner
  • Export a Monday-call agenda directly from the view
  • See which signals fired across the team. Patterns become visible
Lands in · Pulse Summary (exec view)

Where the pipeline is shifting in real time.

Execs get the rolled-up version: which segments are heating up, what classes of signal are driving movement, and which named deals have the most signal pressure on them right now. Designed for the QBR conversation, not the daily one.

  • Segment-level signal heatmap (by industry, region, ICP)
  • Trendlines on signal volume vs. pipeline movement
  • Top-15 active accounts board, refreshed weekly
  • Read-only: no rep-level activity surveillance
For IT & admins · 05

Security model, in one paragraph.

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. We hold a SOC 2 Type II report and will share it under NDA on request.

SOC 2 Type II

Audited annually

Independent audit covering security, availability, and confidentiality controls. Report available under NDA.

OAuth 2.0

Scoped, revocable connection

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.

AppSource signed

Microsoft-reviewed solution

The solution package is signed and listed on Microsoft AppSource. Same install pattern as any other AppSource product.

Region pinned

Data residency, by request

By default, Pulse runs in US-East. EU-West and APAC regions available for enterprise tier on request.

Zero retention

Nothing is stored on our side

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.

For IT & admins · 06

What your IT team will need to do.

Plan for about one hour 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.

IT install checklist

  • Confirm your Dynamics 365 environment is hosted online. We support 9.2+ and will confirm this on the call.
  • Schedule a one-hour window with an admin who can import managed solutions.
  • Import the signed Pulse solution from the AppSource link we send.
  • Approve the OAuth scope: account.name, account.websiteurl, account city, account state, lead name, lead website URL, lead city, and lead state. All read-only.
  • Assign the three new Pulse security roles to the sales-team Dataverse roles.
  • Allow up to 24 hours for the first Pulse run to complete against your Accounts and Leads. We monitor the first run and reach out if anything needs attention.

Our implementation engineer is on the line for all of the above. You don't need to do it from a documentation page.

Want to see it for yourself?

Book a 30-minute walkthrough. We'll bring an implementation engineer so IT and sales can ask their questions in the same room.

Request a Demo