For Sales Leaders, VPs of Sales, CROs

Insights, forecasts, and dashboards you can trust. Because your team actually uses Salesforce.

The processes your Salesforce team builds, running inside Outlook or Gmail. Users log activity in the moment, not Friday from memory. Your pipeline view, your forecast, and your dashboards finally reflect the team's actual day.

We can run the demo in your own sandbox org.

A Screen Flow from your team's Salesforce, running in a user's Outlook. The activity is in Salesforce the moment they hit save.

Used by sales teams at

Het Nationale Theater
"FlowRunner was the only way to truly integrate Salesforce into our existing workflow. The plugin works so seamlessly within Outlook that our team barely even needs to log into Salesforce anymore." — Stijn Terhorst, Sales Manager, Het Nationale Theater

The bottleneck isn't your team. It's the gap between your team and Salesforce.

Every Monday's pipeline review starts with the same problem. Stages don't match reality. Activity stops at last quarter. The deals you remember from your 1:1s aren't on the dashboard.

01

Pipeline reviews start with users backfilling Salesforce on the call.

The fields they update are the fields you ask about, in the order you ask. Nothing else gets updated.

02

Activity logging happens Friday afternoon, from memory.

Half the calls land in Salesforce. The other half live in a notebook, a Slack thread, or nowhere.

03

Your forecast is the manager's gut, not the system's calculation.

The dashboard's number is what you defend in the QBR. Your real number is the one you write on a sticky note before the call.

Make using Salesforce the easy path for your team.

Take the Salesforce processes your team builds. Qualifying a lead. Creating an opportunity. Logging a call. Opening a case. Running an approval. They open inside the user's inbox, with the email context already filled in. The user clicks through. The data lands in Salesforce. No second tab, no separate app, no end-of-week catch-up.

What happens when the friction goes away.

Every leader's dashboard problem traces back to one beat: the user's activity didn't make it into Salesforce. Fix that beat and everything downstream rebuilds itself.

Frictionless onboarding

Adoption stops being a project.

Users don't open a new tab. They don't learn a new app.

They keep doing what they were already doing, opening email, and the Salesforce process arrives in the same place. The matched account, the open opportunity, the renewal due this month — it's all in the sidebar the moment the email opens.

No rollout meeting. No training deck. No "here's the new app we bought" Slack announcement that gets ignored. The Salesforce step is in the inbox, where the work already lives.

Integrated workflow

Activity lands the moment it happens.

Calls, replies, qualifications, approvals, case creations.

Logged in the inbox session, with the email context attached. The EmailMessage record, every participant, the thread, and the user identity are available as Flow inputs. Friday-from-memory disappears.

The user doesn't choose between "log it now" and "ship the next reply." Both happen in the same window, in the same minute.

Results follow data

Insights, forecasts, and dashboards reflect reality.

The data is current because the data was logged in the moment.

Your pipeline view shows the deal stages your users actually believe. Your forecast adds up. Your dashboards stop showing last quarter's optimism. The QBR stops being archaeology — the 1:1 is about the deal, not about updating the deal record.

The forecast call becomes a conversation about probability and risk, not about whose number to trust.

Your decisions get easier. QBRs read off the dashboard. The dashboard reflects what actually happened.

The patterns sales leaders ship first.

Each card below is a Salesforce process your admin already builds — running where your users already work. If it's a Screen Flow, it runs in FlowRunner.

MEDDIC or BANT discipline, in the inbox.

Your qualification framework as a Screen Flow. Metrics, Economic Buyer, Decision Criteria — captured on the email that prompted them, not reconstructed three weeks later from notes.

Account stickiness, not just deals.

The lookup Flow surfaces every open opportunity, every renewal, and every active case for the account in thread. Users see the full account, not just their deal.

Approvals without leaving the reply.

Discount approvals, contract terms, and pricing exceptions trigger from the customer's email. The submitter and approver both stay in the inbox; the audit trail lands in Salesforce.

Whatever your team's Salesforce processes are.

The admin owns the process. We own the delivery. If it runs in Salesforce as a Screen Flow, it runs in FlowRunner — for sales, service, success, ops, and whatever team uses your CRM.

Before and after one rollout.

Screenshot this. Paste it into the message you send your CFO when you ask for the demo on the calendar.

Before FlowRunner With FlowRunner
Pipeline reviews start with five minutes of "let me update this." Pipeline reviews start with the deal. The data is already current.
Activity logging happens Friday from memory. Activity logs the moment the user handles the email. The email context is attached.
Your forecast is the gut number you defend, not the system number you trust. The system numbers add up. The conversation moves to probability and risk, not data hygiene.
QBRs are archaeology. Users reconstruct the quarter from notes. QBRs read off the dashboard. The dashboard reflects what actually happened.
New users take a quarter to learn what to log and where. New users log into Outlook or Gmail and get guided Salesforce processes right away. No learning curve.
You roll out a sales tool. Adoption stalls. You blame the tool. You roll out a guided process in the user's workflow.
Your dashboard tells you what was true last quarter. Your dashboard tells you what is true today.
The board asks why CRM ROI is hard to measure. The CRM gets used because using it isn't the work.

How a sales leader rolls FlowRunner out.

You don't roll out a tool. Your admin pins one Flow, your users notice it on Tuesday, and the dashboard catches up by the end of the week.

  1. 1

    Pick the one Salesforce process that hurts most.

    MEDDIC qualification? Approval routing? Account lookups? Pick the one process your admin already built that your users don't run, and start there. One Flow, one rollout.

  2. 2

    Your admin installs the FlowRunner managed package.

    Salesforce managed package, plus the Outlook add-in or Chrome extension for Gmail. Deployed via Microsoft 365 Admin Center or Google Workspace. Verified apps, your existing IT process.

  3. 3

    Assign the Flow to the right users.

    Your admin pins the Flow in the FlowRunner admin panel and adds the FLR input variables so the email context is available. Sales sees "Create Opportunity"; other teams see whatever fits their job.

  4. 4

    Users get a guided workflow right where they already work.

    No training deck. The Flow is in the sidebar when an email opens, with the matched record and pre-filled fields. The user clicks through, the data lands in Salesforce, the activity is logged.

  5. 5

    The dashboard catches up.

    Activity counts climb. Stage updates fill in. The forecast call on Friday is against current data, not last week's. Add the next Flow next sprint.

The admin owns the process. We own the delivery. Your team gets the outcome.

One product. Three jobs done well.

Most sales tools win one constituency and frustrate the other two. FlowRunner is built so each side gets what they actually want.

For your admin.

Builds the process in Flow Builder, the way they always have. No new automation tool to learn. No parallel system to maintain. What they ship gets used.

For your users.

Stay in Outlook or Gmail. The Salesforce step happens in the same window, with the email context filled in. One less tab, one less password, one less reason to skip the log.

For you.

The dashboard fills itself. Forecast adds up. QBR reads off the system. The board question about CRM ROI becomes easier to answer.

Hosted on Azure in your region of choice. EU tenancy for EU customers. Data Processing Agreement available. ISO 27001 in progress. GDPR-aligned by architecture.

"Salesforce is incredibly powerful, but its biggest pitfall is that it offers too much. For users without an IT background, it can be overwhelming. FlowRunner solves this by stripping away the noise, ensuring our team only sees the information and buttons they actually need to do their job."
Stijn Terhorst
Sales Manager, Het Nationale Theater

Sales-leader questions, answered.

Is this another sales engagement platform or sync tool?
No. FlowRunner is not a sales engagement platform, a sync tool, or a tracking layer. It is the surface that runs your Salesforce processes — the Flows your admin builds — inside Outlook and Gmail. There is no parallel data model, no second source of truth, no sequencer.
Will my users actually use it?
Users don't open a new tab or learn a new app. They keep doing what they were already doing — opening email — and the Salesforce process arrives in the same place. Adoption stops being a project because the workflow is integrated with where users work.
How does this make my forecast more accurate?
The forecast is only as good as the activity behind it. When the user logs activity the moment the email is handled — with the email context attached — the system numbers add up. Friday-from-memory disappears, and the dashboard reflects what actually happened this week.
What does my admin have to build?
Your admin builds the process in Flow Builder, the way they always have. No new automation tool to learn, no parallel system to maintain. They pin the Flow in the FlowRunner admin panel; users see it the next time they open Outlook or Gmail.
How is this different from Einstein Activity Capture or a sync tool?
Sync tools duplicate contacts and stack new data-quality problems on top of the ones you already have. FlowRunner has no sync layer. Every edit runs through your validation rules, Permission Sets, and field-level security — because the edit happens in Salesforce, performed by the user.
What happens to QBRs and pipeline reviews?
Pipeline reviews start with the deal, not with five minutes of "let me update this." QBRs read off the dashboard because the dashboard reflects what actually happened. The 1:1 is about the deal, not about updating the deal record.
Can I uninstall if it isn't a fit?
Yes. Your admin keeps the keys. Your data stays in Salesforce. If it isn't a fit in two weeks, you uninstall and your team's setup is exactly where it was — Flows, fields, Permission Sets, all unchanged.
Does it work for Gmail and Outlook teams equally?
Yes. Every Flow, every Permission Set rule, every matching feature works identically in Gmail and Outlook. They share the same FlowRunner backend; only the host add-in shell differs. Mixed teams get one rollout, not two.

See your forecast change shape.

Thirty minutes, your own Salesforce, your own Outlook or Gmail. We'll wire one of your team's processes into the inbox and update a record live on the call.

Your admin keeps the keys. Your data stays in Salesforce. If it isn't a fit in two weeks, you uninstall and your team's setup is exactly where it was.