What's new

The latest improvements & new capabilities in Fluint.

Product Updates

Loop Console: Your GTM Data and Model Results, in One Place

Loop Console is where you explore the context graph, check the data logs, and see how each team is doing against the predictors that matter.

Why it matters

Dashboards and CRM reports show totals. They rarely show the change history behind a number, and they can't show which behaviors actually win, so debates about what works come down to opinion or a vendor's benchmark.

Loop Console shows the deals, events and model results behind each number. Click any predictor or play to see the deals, calls and emails behind it, down to the moment each one happened. RevOps, Enablement and sales leaders can settle debates with what's proven in your own won and lost deals, see where open deals are missing a step, and coach the behaviors that move the win rate.

How it works

The console gives you four views on the same data, so you can check the work behind every predictor and play: the context graph (how deals, contacts and activity connect), data logs (every sync, change and backfill, with timestamps), Explore (questions about your data, with the deals behind each answer), and team views (each team's results against the predictors that matter). It's included with Fluint, updates daily, and sits alongside your BI tool to cover what BI can't.

Getting Started

  1. Connect your sources. Salesforce, your call recorder, email and calendar sync into one history.
  2. Watch the data land. Data logs show every sync, change and backfill, so nothing happens out of sight.
  3. Explore by team. Filter by team, segment or stage to see who is running the steps that win.
  4. Share what you find. Team views can be shared with anyone who has access to those deals.
Read less more

The Context MCP: One Connection for Context Every Agent Can Trust

The Context MCP serves Fluint's briefs, predictors and plays to Claude, ChatGPT, Cursor or your own agents, already scored against outcomes and cited.

Why it matters

Most agents get GTM context the hard way. Per-tool connectors and raw APIs hand them raw records, so the model has to re-read the data and reason it out again on every call. And the hand-written SKILL files that tell agents which plays to run go out of date the moment anything changes.

The Context MCP gives any AI tool access to your GTM context through one connection. It carries the guidance on which plays win and how to run them, refreshes it as your deals close, and returns context that's already cleaned, scored against outcomes and cited. Your agents follow what's working now, and every agent gets the same answer.

How it works

The Context MCP runs as an always-on pipeline. Each brief is built and refreshed the moment your data changes, so a call returns ready context instead of raw records, which cuts latency and the token cost of every request. Access follows the permissions in your source systems, so each user only gets context they can already see.

Getting Started

  1. Connect your agent. Point Claude, ChatGPT, Cursor or your own agent at the Fluint MCP endpoint. Any MCP client works.
  2. Call a tool. Ask for a brief on a deal, account, contact or meeting, the top predictors by segment and stage, or the play for a deal.
  3. Get cited context. Every response includes the deals, calls and emails behind it.
  4. Use it everywhere. One connection serves the same context to every model, tool and agent you use. Swap vendors, and the context comes with you.
Read less more

Proactive Agents: Act on Deals Before Anyone Asks

Proactive agents watch your pipeline for the moments that matter, then send the right next step to the rep or run it for them.

Why it matters

Chat assistants wait for a prompt. Automation platforms can run agents, but you have to wire up the trigger and supply the logic for what wins yourself. Either way, nothing happens on a deal until someone asks or builds it.

Proactive agents act when a deal needs it, based on what wins in your data. Each agent runs one of your plays on its own, starting from something that happens in your deal data, like a call ending with no next meeting. Agents take minutes to launch, so you can close a high-value gap the moment you spot it. Olli, the default agent powered by Loop, is now part of proactive agents, with the same briefs and drafts, now guided by your predictors.

How it works

Each agent starts from a trigger and runs a play. Depending on the play, it drafts emails and briefs, updates CRM fields, reminds reps, or posts to Slack, and it can send its work to Slack, the CRM, email or any MCP client. You can also add an agent to Slack under your own name and branding, where it flags deals that need something, runs the play, and answers anyone's questions.

Getting Started

  1. Pick a play. Choose one of your plays, or let Fluint suggest the one with the biggest expected impact.
  2. Set the trigger and channel. Decide what starts the agent and where the rep sees its work.
  3. Keep the rep in the loop. By default the agent drafts and the rep reviews and sends. It only sends on its own if you allow it.
  4. Review what it did. Every action is logged, and its effect on win rate is measured like any play.

Building your own agents? They can call the Context MCP to get the same predictors and plays.

Read less more

Plays: Turn What Wins Into a Next Step Reps Can Take

Each play comes from one of your top predictors and tells reps what to do, on which deals, and how much it's expected to raise the win rate.

Why it matters

A playbook is written once and goes stale. It tells reps what to do in general, like "multi-thread more," sends the same advice to everyone, and never measures whether it's working in your pipeline.

Plays in Loop are built from your own won and lost deals. Each one names the exact move for a stage, shows the past similar deals where it moved the win rate, and tracks how often your team actually runs it. Because plays retrain on every closed deal, they show what's winning in your pipeline right now and drop the moves that stopped working.

How it works

Fluint drafts each play from your predictors. A play pairs a predictor with the specific move and phrasing shown to raise that outcome in past deals, like "book the next meeting before the call ends," and its expected impact is measured on similar deals in the same segment and stage.

Getting Started

  1. Start from what matters at a stage. Fluint finds which predictors move deals through a specific stage, for each segment.
  2. Review the drafted plays. Your team can edit the wording, pause a play, or add your own.
  3. See where each play applies. Plays target the deals that are missing a specific step.
  4. Track adoption and act. See how often reps run each play, then nudge them or hand the play to a proactive agent that finds the right deals and drafts the step for the rep.
  5. Watch for flags. When a play's measured impact drops as new deals close, Fluint flags it so you can pause or replace it.
Read less more

Predictors: See What Actually Raises Your Win Rate

Loop now measures how much each part of your sales process adds to your win rate, using a private model trained on your own won and lost deals.

Why it matters

Most of what reps do barely moves a deal. The hard part has always been knowing which few things do, and by how much. A call tracker can tell you a topic came up, and a context graph can map who touched a deal, but neither tells you what changed the outcome.

Predictors does. Loop by Fluint trains a private model on your own won and lost deals and measures how much each behavior is worth, in win-rate points. It controls for deal size, segment, stage and timing, ranks the results separately for each segment and stage, and retrains daily as deals close. You know what to do more of, and the top predictor becomes a next step your team can take.

How it works

A predictor is anything that happens on a deal that shows up far more often in the deals you win than the ones you lose, like a next meeting booked, a second buyer joining, or a pricing page visit. Predictors compares the win rate of deals where a behavior happened with similar deals where it didn't, using each deal as it looked at that moment so later information doesn't skew the result.

Getting Started

  1. Connect Salesforce and your call recorder. Calls, emails and CRM updates are matched to the deal they belonged to, with a record of when each one happened.
  2. Let Fluint compare similar deals. For each behavior, the difference in win rate comes from that behavior and not from deal size or timing.
  3. Review your ranked predictors. Each segment and stage gets its own ranking, because what wins enterprise deals is rarely what wins SMB deals.
  4. Add your own signals if there's something specific you want measured.
  5. Check back as deals close. Each night, newly closed deals go back into the model and the rankings update for every segment and stage.
Read less more

Microsoft Dynamics 365 is Here

If your team runs on Dynamics, Fluint now syncs your CRM, answers questions about your pipeline, and pushes documents back to your opportunities, at full parity with Salesforce and HubSpot.

Why it matters

Dynamics customers have spent years getting second-class treatment from the sales-tool ecosystem. Most platforms ship Salesforce and HubSpot integrations first, then maybe-someday Dynamics, and when it does land, it's usually a stripped-down version of what other CRMs get.

Fluint now connects to Microsoft Dynamics 365 with full parity. Your accounts, contacts, opportunities, and pipeline stages sync into Fluint; Olli answers questions about your Dynamics data directly in chat; and document revisions push back to the opportunity timeline automatically. Same intelligence, same workflows, same Olli, wherever your CRM lives.

How it works

Once connected, Fluint pulls your full Dynamics workspace: accounts, contacts, opportunities, users, and pipeline stages. Opportunities become deals in Fluint automatically and are assigned to the right rep based on email matching, so your team sees their book of business from day one.

Olli queries your synced Dynamics data directly. Ask "What's the pipeline value of my deals closing this quarter?" or "Show me all open opportunities for Acme Corp" and Olli responds in chat without you needing to log into Dynamics.

Document revisions flow back into Dynamics too. When you publish a revision on a Dynamics-connected deal, it lands on the opportunity timeline as a Note with the rendered document attached. Subsequent revisions update the same Note rather than spawning duplicates, so your Dynamics record stays clean.

If you only want certain pipeline stages to become Fluint deals, set stage filters in your integration settings, and Fluint will only pull opportunities matching those stages on the next sync.

Getting Started

  1. Go to Settings > Integrations and click Microsoft Dynamics 365
  2. Enter your Dynamics org subdomain (e.g. yourorg.crm.dynamics.com) and click Continue
  3. Sign in with your Microsoft account and approve the permissions Fluint requests
  4. Wait for the first sync to complete (a few minutes to a couple of hours depending on your instance size)
  5. Ask Olli "What's in my Dynamics pipeline?" to confirm everything is connected
  6. Set stage filters in Settings > Integrations > Microsoft Dynamics 365 > Filters if you want to limit which opportunities become deals
Read less more
A close-up headshot of the Nate Nasralla, with dark curly hair, a full beard, and patterned glasses.

Let’s see if there’s a good fit

We’ll look at how other GTM teams are already:

Engaging exec-level buyers
Engaging exec-level buyers with a strong point of view.
Driving 10.4X sales velocity
Driving 10.4X sales velocity with more calm, less chaos.
Confidently forecasting
Confidently forecasting, with deal reviews based on written evidence.
Enabling champions
Enabling champions to multithreaded and sell internally.
Are you a Sales Rep or AE?
Watch a video demo and jump right in to an account: