---
title: "Customer Success"
description: "The Customer Success function owns the customer relationship after the commercial
close: onboarding, adoption, renewals, and expansion. The Customer Success
Manager (CSM) is the role within Customer Success, accountable for account
health and for the value customers realize from FlowFuse — measured by customer
outcomes, not just retention."
canonical_url: "https://flowfuse.com/handbook/sales/customer-success/"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

# Customer Success

The Customer Success function owns the customer relationship after the commercial
close: onboarding, adoption, renewals, and expansion. The **Customer Success
Manager (CSM)** is the role within Customer Success, accountable for account
health and for the value customers realize from FlowFuse — measured by customer
outcomes, not just retention.

FlowFuse CSMs are to drive adoption and expansion within accounts. Customers
should be provided help and support to connect their assets, build applications
for their organisation, and automate workflows. To do so, a playbook is created
to build one way we do things and have one asset to update with the learnings.
The purpose of this playbook is to ensure FlowFuse customers build applications
to optimize their operations, thereby positioning FlowFuse as the platform over
traditional Manufacturing Execution Systems (MES) and Supervisory Control and
Data Acquisition (SCADA) systems. FlowFuse is focussed on
farming/growing/cultivation. We're a hunter organization at first, though, the
market currently accepts our product mostly through internal growth.

## Engagement and Responsibilities

CSM should be involved as soon as account executives **commit to a deal**. This
is before a deal closes and is signed. From the moment an AE commits to a deal
onboarding starts for CSM. To understand what their high-level goals are with
our product, and what the company as vendor can provide soon to a new customer.
The AE will
[close the deal](https://flowfuse.com/handbook/sales/engagements/#closing-a-deal), at which
point CSM takes over.

Onwards, CSM is responsible for the full customer lifecycle, from establishing
onboarding progress and completing this process, managing and tracking what's
being built on our platform and the strategic significance, and ensuring
inspiration to build new things right after. Throughout having customers achieve
value and Return on Investment (ROI), cultivating internal champions, and
driving strategic expansion (horizontal and vertical) — see
[Expansion Deals](https://flowfuse.com/handbook/sales/hubspot/#expansion-deals) for when a CSM
owns an expansion deal directly versus when the AE does. CSMs are also the primary
FlowFuse contact that can establish and accelerate the pace of replacing or
augmenting legacy MES/SCADA systems with our product. In turn resulting in
higher net revenue retention (NRR) rates, and the development of strong customer
advocacy that will further fuel FlowFuse's growth.

## Customer Success Methodology

The basic principal of CS is to help customers succeed in their goals by getting
value from our services. The assumption is, where customers get value they are
likely to consciously recognize that value, be open to gaining more value, and
recommending FlowFuse to potential customers. This should in turn result in
customers remaining with FlowFuse for longer, delivering greater revenue, and
encouraging more of their professional and personal networks to join FlowFuse.

FlowFuse has a diverse customer-base. When devising a strategy to deliver CS it
is important to recognise the key cohorts within our customers. They are grouped
as follows:

<table>
<thead>
  <tr>
    <th>
      Cohort
    </th>
    
    <th>
      Key Traits
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Trial
    </td>
    
    <td>
      Not paying for services
    </td>
  </tr>
  
  <tr>
    <td>
      Enterprise
    </td>
    
    <td>
      Large scale applications, extensive use of FlowFuse's features
    </td>
  </tr>
</tbody>
</table>

You can view our current customer-base and their cohorts in
[this report](https://main.flowforge.cloud/ui/#!/7?socketid=reLw4efoWf45RfOsAACH){rel="nofollow}.

CS activity is planned to manage each of the cohorts with appropriate support &
communications. The support and communications will be in some cases fully
automated and in others will involve individual actions by our CS team, such as
holding regular review meetings with customers.

The key goal of CS is to migrate customers from the trial status, down the table
of cohorts above, and where appropriate onto being an Enterprise customer. It is
however important to consider that some customers would not benefit from our
broadest offerings of services. Appropriate resources should be put into
customers who have found lasting value further up the cohorts table.

To ensure a smooth onboarding experience and long-term success for our customers, we follow a structured [Customer Success Playbook](https://docs.google.com/document/d/1LqttB5AWueJfahdCciqloS4MSRhDZQRVHjla5xR4toU/edit?tab=t.0#heading=h.rwalcx5xuqez) for our Enterprise customers. This playbook outlines key activities, engagement points, and best practices that guide our Customer Success team in supporting each customer’s goals throughout their journey with FlowFuse.

## Playbooks

- [Onboarding Playbook](https://docs.google.com/document/d/1yxO53QHwBChNAoERLlB0kGRCNdPJzzHV9X0aLZKX8HU/edit?tab=t.0)
- [CS health score](https://docs.google.com/document/d/1zdbhuljqM9AU5ok9Mq24xOiD7-YUHJunO3NNYLcdtZM/edit?tab=t.0)
- [Churn Playbook](https://docs.google.com/document/d/1jrtTNEFgiY3NTHMBMm67y2P1Pm3qeIsxy8mckOEg9s4/)
- [Expansion & Growth](https://docs.google.com/document/d/1MPgtKuI3pSD5yIgWaSfywxP8YrqAdFjgmfLPB7V9sGE/edit?tab=t.0)
- [Meeting structures](https://docs.google.com/document/d/1_s9JW-cD9yuRKS1Ztcc29wtxGIrdmhKjwZyoDIkkMRE/edit?tab=t.5xzj4a2p6zxn)

## Customer Success Tools

### Data Sources

To drive CS, we need to utilise data across various platforms to understand what
our customers need from us to succeed. the main platforms we use are as follows:

<table>
<thead>
  <tr>
    <th>
      Platform
    </th>
    
    <th>
      Key Data
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      FlowFuse Cloud's Database
    </td>
    
    <td>
      Current usage of the platform and uptake of features
    </td>
  </tr>
  
  <tr>
    <td>
      Stripe
    </td>
    
    <td>
      Expenditure
    </td>
  </tr>
  
  <tr>
    <td>
      HubSpot
    </td>
    
    <td>
      Interaction with support and marketing content on our website and in emails
    </td>
  </tr>
  
  <tr>
    <td>
      GitHub
    </td>
    
    <td>
      Record of upcoming and shipped features
    </td>
  </tr>
</tbody>
</table>

### Useful Customer Data

- [Team, User, Instances & Devices Growth](https://main.flowforge.cloud/ui/#!/0?socketid=LPUnOyHnjGM_GqrnAAAd)
- [Customer Cohorts](https://main.flowforge.cloud/ui/#!/1?socketid=LPUnOyHnjGM_GqrnAAAd)
- [Device Agent Adoption](https://main.flowforge.cloud/ui/#!/2?socketid=LPUnOyHnjGM_GqrnAAAd)
- [User Audit Interactions](https://main.flowforge.cloud/ui/#!/4?socketid=zuEy1h2ZhTjyhCnuAABB)

### Communication

To deliver automated and manual communication with customers, we use HubSpot
CRM. HubSpot allows us to collaborate as a team. This is vital when manually
communicating with customers as well as operating automated email campaigns
based on a customer's current cohort and interaction with their account.

We have built an integration in Node-RED which can extract data from our
platforms then append it to a customer's record in HubSpot. The integration as
well as any other CS resources built in Node-RED are hosted on FlowFuse Cloud
and can be
[accessed in this application](https://main.flowforge.cloud/){rel="nofollow}.

## Shipped Feature Updates

Customer success contacts FlowFuse customers and prospective customers (anyone we have had in a sales cycle who has requested a feature) when a requested feature is shipped. To facilitate this, there is a view in the Development board on GitHub called ["CS View"](https://github.com/orgs/FlowFuse/projects/1/views/61). It filters to all issues marked Done by the Engineering team, and those with the label Sales Request or Customer Request. The Customer Success Manager will review this board upon each release and contact customers or prospects who requested a feature to inform them that it has shipped, and invite a conversation or feedback.

All team members are asked to identify customer and prospect requests in the following way:

- On a GitHub issue, use the label Sales Request or Customer Request, as appropriate. (A request is a Sales Request when a member of the Sales team learns that a prospect is interested in a feature. It is a Customer Request when an existing customer makes a request. An issue can be both a Customer Request and a Sales Request.)
- Customer-specific context (which deal or account the request is tied to) does not go on the public issue. Mention the request on the deal's representative issue inside FlowFuse/product, and if a public issue already exists for the same request, reference that existing one from the deal issue rather than opening a new one. See [Deal Management](https://flowfuse.com/handbook/sales/hubspot#deal-management). Sales and Product share responsibility for maintaining this link, including for past requests, so any feature request can be traced back to the deals it pertains to.

### HubSpot Properties

For FlowFuse Cloud customers, we add various useful data to our CRM records to
help us better understand who each customer is and how they are using FlowFuse.
They are as follows:

<table>
<thead>
  <tr>
    <th>
      Field name
    </th>
    
    <th>
      Description
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      FFC-Tier
    </td>
    
    <td>
      This links each contact on HubSpot to the tier their team is currently associated with. Where a contact is in more than one team with different tiers we will show the tier which is expected to deliver the highest ARR. You can view the current contacts by tier in <a href="https://app-eu1.hubspot.com/reports-list/26586079/182668969/" rel="nofollow">
        this report
      </a>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      FFC-Actions
    </td>
    
    <td>
      This shows actions which have been taken by someone on a team this contact is on. To see a full list of available actions view <a href="https://app-eu1.hubspot.com/reports-list/26586079/182831966/" rel="nofollow">
        this report
      </a>
      
       in HubSpot
    </td>
  </tr>
  
  <tr>
    <td>
      FFC-Usage
    </td>
    
    <td>
      This field shows a contact's answer to how they are planning to use FlowFuse Cloud, you can view the options and current data on <a href="https://app-eu1.hubspot.com/reports-list/26586079/182851924/" rel="nofollow">
        this report
      </a>
      
      .
    </td>
  </tr>
  
  <tr>
    <td>
      FFC-Events (deprecated)
    </td>
    
    <td>
      This legacy field showed email campaigns which had been triggered to be sent to each contact. For example, after 24 hours if a user had not used out snapshots feature the integration between FlowFuse Cloud and HubSpot would add the relevant tag to this user. HubSpot would in turn send the email to the contact. This way of working is being replaced by FFC-Actions as that field can triggered email campaigns based on action or inaction as well as adding value to our CRM.
    </td>
  </tr>
</tbody>
</table>

## Inbound Support

For FlowFuse customers, there are two ways to get support, through support
tickets or go to the community forum. Where to go when is described below.

<table>
<thead>
  <tr>
    <th>
      Topic
    </th>
    
    <th>
      Support venue
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Billing
    </td>
    
    <td>
      <a href="/support/">
        Support ticket
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      FlowFuse Application
    </td>
    
    <td>
      <a href="/support/">
        Support ticket
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      FlowFuse Feature Requests
    </td>
    
    <td>
      <a href="https://github.com/FlowFuse/flowfuse/issues" rel="nofollow">
        FlowFuse repository
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      Node-RED Application
    </td>
    
    <td>
      <a href="https://discourse.nodered.org/c/vendors/flowfuse/24" rel="nofollow">
        Community Forum
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      Node-RED flows
    </td>
    
    <td>
      <a href="https://discourse.nodered.org/c/vendors/flowfuse/24" rel="nofollow">
        Community Forum
      </a>
    </td>
  </tr>
  
  <tr>
    <td>
      Custom nodes
    </td>
    
    <td>
      <a href="https://discourse.nodered.org/c/vendors/flowfuse/24" rel="nofollow">
        Community Forum
      </a>
    </td>
  </tr>
</tbody>
</table>

If you're not a FlowFuse customer, or in your trial phase, please go to the
[community forum](https://discourse.nodered.org/c/vendors/flowfuse/24).

### Support Tickets

#### HubSpot

We use HubSpot to manage our customer support tickets for the managed FlowFuse
platform. We can give each FlowFuse team member access to HubSpot by assigning
them a seat.

If you wish to be granted access to HubSpot please post in the FlowFuse
[#support-tickets](https://flowfuse.slack.com/archives/C031K13FLDD)
Slack channel.

Whenever a customer raises a new ticket, a message is posted into slack
#support-tickets.

This will allow the whole team visibility of a new ticket, to reply to a ticket
we need to use the Help
[Desk UI in HubSpot](https://app-eu1.hubspot.com/help-desk/26586079/view/233410279/list-view).
Once you reply to a ticket (if nobody in our team has already replied) you will
be assigned as a ticket owner. Once you are a ticket owner you will get alerts
via the HubSpot Slack app each time a customer replies. You are the only person
who gets these alerts so it's important you deal with them in a timely manner.
You can assign the ticket to someone you feel is a more appropriate owner using
the HubSpot interface in the top right corner of the help desk. You may want to
assign a ticket to a team member if you are out of office due to holidays, time
zones etc so that the customer continues to get the support they need.

When replying to a ticket, you can either send a message to a customer via live
chat or an email. Please ensure you check if the customer is still online before
using live chat, that can be checked by looking for a green circle next to their
avatar on each post. If you don't see the green circle you should switch to
emailing the customer.

You can also add comments to a ticket which will only be visible to our team.
This is a great place to add more context for other team members and ask for
help. You can send an alert to a team member by adding @teammembername to your
comments.

When replying to the ticket one should have the intent to always reply with
links to FlowFuse articles or documentation. If these resources are missing,
please start or update where applicable.

Where a conversation needs to happen with regards to a ticket between FlowFuse
team members, we should use the comments feature in the ticket rather than
having a parallel conversation in Slack. This allows anyone who wants to help
with the ticket can see all relevant information in one place.

Where you can help by replying to a customer you should do so rather than asking
the ticket owner to relay messages. Working this way saves time, reduces the
chance of the wrong information being passed to the customer, and shows that our
wider team is invested in tickets which should have a positive impact on
customer satisfaction.

When a ticket is assigned to you please monitor it for a conclusion. If it's
unclear to you if the customer's request was satisfied please ask the customer
to confirm they don't need any further help. Once the customer doesn't need any
more help on the ticket please close it using the info bar on the right side of
the ticket inbox. Look for the 'Ticket status' section and change the drop down
to closed.

#### Scope of Support

FlowFuse customers will only get support for issues relating to the FlowFuse
application or their account & billing. Any questions around Node-RED itself or
their flows should be redirected to the
[FlowFuse Community forum](https://discourse.nodered.org/c/vendors/flowfuse/24).

3rd party nodes are not supported at this time. It is reasonable to point a
customer direct to a repo for a 3rd party node question.

#### SLA

All paying customers get a Standard Support SLA by default. A faster, Enterprise-level SLA can be purchased and negotiated as an upgrade.

- Standard Support (Legacy -- Pro  Tier Support)
  - Support available 24 × 5 (Monday to Friday, UTC-2 timezone)
  - First Response SLA: Next business day (within 24 hours)
  - Support tickets can be submitted at [our Support Form](https://flowfuse.com/support/)
- Enterprise Support (default for all paying customers)
  - Support available 24 × 5 (Monday to Friday, UTC-2 timezone)
  - First Response SLA: 4 hours
  - Support tickets can be submitted at [https://flowfuse.com/support/](https://flowfuse.com/support/)
- Premium Support (purchasable/negotiable upgrade)
  - Support available 24 × 5 (Monday to Friday, UTC-2 timezone)
  - First Response SLA: 2 hours
  - Support tickets can be submitted at [https://flowfuse.com/support/](https://flowfuse.com/support/)

#### Escalation

Where the issue relates to a bug in the FlowFuse application then the person
dealing with the ticket should aim to reproduce that bug and then raise an
appropriate issue in GitHub, The issue should reference the support ticket but
not mention the customer by name. Once raised the issue URL should be added to
the ticket and shared with the customer for visibility. The ticket should not be
closed until the bug is resolved.

## Community Forum

As the Node-RED forums are intended to be vendor neutral, FlowFuse has a
[community forum](https://discourse.nodered.org/c/vendors/flowfuse/24) too.

#### Scope of Support

FlowFuse customers will only get support for issues relating to the FlowFuse
application or their account & billing. Any questions around Node-RED itself or
their flows should be redirected to the
[FlowFuse Community forum](https://discourse.nodered.org/c/vendors/flowfuse/24).

3rd party nodes are not supported at this time. It is reasonable to point a
customer direct to a repo for a 3rd party node question.

## Quarterly Business Review

For all customers that are over $10k ARR, or are manually nominated because of
their growth potential to the company, a quarterly business review is offered to
them and scheduled. FlowFuse offers these meetings each quarterly, hence the
name Quarterly Business Review (QBR). By meeting, FlowFuse can understand,
pro-actively, how the customer is progressing with their adoption.

Record customer calls using Fathom per the [Sales Meetings guide](https://flowfuse.com/handbook/sales/meetings/).

For each meeting, the goals are:

1. Relationship building -- By having a conversation instead of email, we hope
there's more space for in-depth discussion and candor in the conversation.
2. Assess Problem-Value alignment -- Understand if the problem the customer felt
before buying FlowFuse has been mitigated, or what FlowFuse needs to do to
further mitigate this.
3. Issue prevention -- By proactively reviewing progress, potential roadblocks
or challenges can be identified and addressed early, preventing customer
dissatisfaction or churn.
4. Broader feature adoption -- Often customers are paying for a package that
includes more value than they're currently extracting. Help the customer with
adoption and getting more value from the product
5. Data collection -- Provide space and time for the customer to provide
feedback on the product and experience. Allow them to request feature ideas,
or ask for bug fixes.

## Procedure for Handling a Churned Customer

The Customer Success manager is responsible for executing the following steps
when an annually-billed customer chooses not to renew their subscription:

1. **Update Contracted Customer Tracker** Access the
[CS Customer tracking](https://docs.google.com/spreadsheets/d/1n99ROi49GHdmHjYivbwGlKYH28Qh-x0QZUrxiO9ppHg/edit?gid=0#gid=0)
and move the churned customer to the "Churned" tab. Add the churn date and the reason for churning.
2. **Cancel Subscription in HubSpot** Cancel the subscription on their account page in HubSpot, to ensure no further invoices are
sent.
3. **Close Opportunities in HubSpot** In HubSpot, locate any open Growth and
Renewal opportunities related to the churned customer. Move these
opportunities to "Closed Lost" to reflect the customer's decision not to
renew.
4. **Announce Churn in Slack** Post an announcement in the Slack channel
#dept-sales, summarizing the reasons for the churn. Encourage the team to ask
questions or suggest ways to learn from the situation.
5. **Send Customer Acknowledgment and Learning Questions** Send an
acknowledgment email to the churned customer. Include any relevant questions
aimed at understanding their reasons for churn and gathering feedback for
internal improvement.

## Notifying Customers of Downtime for FlowFuse Cloud Kubernetes Migrations

Occasionally, we need to restart customer instances of Node-RED on FlowFuse
Cloud to migrate them to a new server at AWS. To manage this, we inform
customers in advance, giving them time to restart their instances. If they don’t
do so within that time, we’ll restart the instances for them. Sometimes, an
instance might not restart properly, so we need to ensure everything works
smoothly and notify the customer with instructions if any issues arise.

Our goal is to minimize the number of customers needing to restart their
instances and reduce how many we need to handle manually. Ideally, the migration
should happen without customers even noticing.

### Steps

1. **Set Up the New Server Early:**<br />


The new server should be ready at least 90 days before the migration
deadline. This ensures any new instances or manual restarts automatically
move to the new server.
2. **Notify Customers 30 Days Before:**<br />


Create a list of instances that need to be migrated 30 days before the
deadline. Send an email to each team, explaining which instances need to be
restarted. Make sure the email is clear, concise, and easy to follow.
3. **Review 7 Days Before Deadline:**<br />


A week before the deadline, review any remaining instances. If a customer is
particularly important or has many instances left to migrate, consider
providing personalized help to ensure a smooth process.

## Handling Requests from Self-Hosted Customers to Enable FlowFuse Assistant

The [FlowFuse Assistant](https://flowfuse.com/docs/user/expert/) is enabled by default for Cloud customers. Self-hosted customers can use it, too, but must request access through support.

When a customer requests access to the FlowFuse Assistant, do the following:

1. Route the request to Engineering
2. Note in the customer's page on HubSpot that the customer is using the FlowFuse Assistant. This will enable Customer Success to discuss the feature with the customer and adds to our holistic understanding of the customer.
3. **Handle Final Restarts on Deadline Day:**<br />


On the deadline day, go through the remaining instances and restart them.
Check that each one comes back online properly, and assist customers with any
issues that come up.

## Customer Success Bonus Structure

The Customer Success team is compensated under a quarterly bonus plan that
rewards the retention and growth of their total portfolio. This is a bonus, not a
commission: it's based on the performance of the whole portfolio, rather than a
percentage of the value of individual deals.

### Bonus Components

Payouts are based on one goal. Note that specific targets are subject to review at the start of each fiscal year or quarter.

- Net Retention Revenue (NRR): Measured against a 115% NRR goal. (100% NRR = 0% payout; 115% NRR = 100% payout).
**Note: overachieving the NRR goal comes with a proportional upside bonus.**

#### NRR Bonus Formula

The NRR portion of the payout is calculated on a linear scale between the baseline and goal:

Variables

- <span className="katex">
<span className="katex-mathml">
<math xmlns="http://www.w3.org/1998/Math/MathML">
<semantics>
<mrow>
<mi>

X

</mi>
</mrow>

<annotation encoding="application/x-tex">

X

</annotation>
</semantics>
</math>
</span>

<span className="katex-html" ariaHidden="true">
<span className="base">
<span className="strut" style="height:0.6833em;">



</span>

<span className="mord,mathnormal" style="margin-right:0.0785em;">

X

</span>
</span>
</span>
</span>

: Achievement (Actual Net Retention Rate)
- <span className="katex">
<span className="katex-mathml">
<math xmlns="http://www.w3.org/1998/Math/MathML">
<semantics>
<mrow>
<mi>

Y

</mi>
</mrow>

<annotation encoding="application/x-tex">

Y

</annotation>
</semantics>
</math>
</span>

<span className="katex-html" ariaHidden="true">
<span className="base">
<span className="strut" style="height:0.6833em;">



</span>

<span className="mord,mathnormal" style="margin-right:0.2222em;">

Y

</span>
</span>
</span>
</span>

: Baseline (The 100% minimum threshold)
- <span className="katex">
<span className="katex-mathml">
<math xmlns="http://www.w3.org/1998/Math/MathML">
<semantics>
<mrow>
<mi>

G

</mi>
</mrow>

<annotation encoding="application/x-tex">

G

</annotation>
</semantics>
</math>
</span>

<span className="katex-html" ariaHidden="true">
<span className="base">
<span className="strut" style="height:0.6833em;">



</span>

<span className="mord,mathnormal">

G

</span>
</span>
</span>
</span>

: Goal (The target NRR for a standard 100% bonus payout)
- <span className="katex">
<span className="katex-mathml">
<math xmlns="http://www.w3.org/1998/Math/MathML">
<semantics>
<mrow>
<msub>
<mi>

B

</mi>

<mtext>

target

</mtext>
</msub>
</mrow>

<annotation encoding="application/x-tex">

B_{\text{target}}

</annotation>
</semantics>
</math>
</span>

<span className="katex-html" ariaHidden="true">
<span className="base">
<span className="strut" style="height:0.9694em;vertical-align:-0.2861em;">



</span>

<span className="mord">
<span className="mord,mathnormal" style="margin-right:0.0502em;">

B

</span>

<span className="msupsub">
<span className="vlist-t,vlist-t2">
<span className="vlist-r">
<span className="vlist" style="height:0.2806em;">
<span style="top:-2.55em;margin-left:-0.0502em;margin-right:0.05em;">
<span className="pstrut" style="height:2.7em;">



</span>

<span className="sizing,reset-size6,size3,mtight">
<span className="mord,mtight">
<span className="mord,text,mtight">
<span className="mord,mtight">

target

</span>
</span>
</span>
</span>
</span>
</span>

<span className="vlist-s">

​

</span>
</span>

<span className="vlist-r">
<span className="vlist" style="height:0.2861em;">
<span>



</span>
</span>
</span>
</span>
</span>
</span>
</span>
</span>
</span>

: Target Bonus (The dollar amount paid if the CSM exactly hits goal <span className="katex">
<span className="katex-mathml">
<math xmlns="http://www.w3.org/1998/Math/MathML">
<semantics>
<mrow>
<mi>

G

</mi>
</mrow>

<annotation encoding="application/x-tex">

G

</annotation>
</semantics>
</math>
</span>

<span className="katex-html" ariaHidden="true">
<span className="base">
<span className="strut" style="height:0.6833em;">



</span>

<span className="mord,mathnormal">

G

</span>
</span>
</span>
</span>

)

**Formula**

<span className="katex-display">
<span className="katex">
<span className="katex-mathml">
<math xmlns="http://www.w3.org/1998/Math/MathML" display="block">
<semantics>
<mrow>
<mtext>

Bonus

</mtext>

<mo>

=

</mo>

<mi>

max

</mi>

<mo>

⁡

</mo>

<mrow>
<mo fence="true">

(

</mo>

<mn>

0

</mn>

<mo separator="true">

,

</mo>

<msub>
<mi>

B

</mi>

<mtext>

target

</mtext>
</msub>

<mo>

×

</mo>

<mfrac>
<mrow>
<mi>

X

</mi>

<mo>

−

</mo>

<mi>

Y

</mi>
</mrow>

<mrow>
<mi>

G

</mi>

<mo>

−

</mo>

<mi>

Y

</mi>
</mrow>
</mfrac>

<mo fence="true">

)

</mo>
</mrow>
</mrow>

<annotation encoding="application/x-tex">

\text{Bonus} = \max \left( 0, B_{\text{target}} \times \frac{X - Y}{G - Y} \right)

</annotation>
</semantics>
</math>
</span>

<span className="katex-html" ariaHidden="true">
<span className="base">
<span className="strut" style="height:0.6833em;">



</span>

<span className="mord,text">
<span className="mord">

Bonus

</span>
</span>

<span className="mspace" style="margin-right:0.2778em;">



</span>

<span className="mrel">

=

</span>

<span className="mspace" style="margin-right:0.2778em;">



</span>
</span>

<span className="base">
<span className="strut" style="height:2.4em;vertical-align:-0.95em;">



</span>

<span className="mop">

max

</span>

<span className="mspace" style="margin-right:0.1667em;">



</span>

<span className="minner">
<span className="mopen,delimcenter" style="top:0em;">
<span className="delimsizing,size3">

(

</span>
</span>

<span className="mord">

0

</span>

<span className="mpunct">

,

</span>

<span className="mspace" style="margin-right:0.1667em;">



</span>

<span className="mord">
<span className="mord,mathnormal" style="margin-right:0.0502em;">

B

</span>

<span className="msupsub">
<span className="vlist-t,vlist-t2">
<span className="vlist-r">
<span className="vlist" style="height:0.2806em;">
<span style="top:-2.55em;margin-left:-0.0502em;margin-right:0.05em;">
<span className="pstrut" style="height:2.7em;">



</span>

<span className="sizing,reset-size6,size3,mtight">
<span className="mord,mtight">
<span className="mord,text,mtight">
<span className="mord,mtight">

target

</span>
</span>
</span>
</span>
</span>
</span>

<span className="vlist-s">

​

</span>
</span>

<span className="vlist-r">
<span className="vlist" style="height:0.2861em;">
<span>



</span>
</span>
</span>
</span>
</span>
</span>

<span className="mspace" style="margin-right:0.2222em;">



</span>

<span className="mbin">

×

</span>

<span className="mspace" style="margin-right:0.2222em;">



</span>

<span className="mord">
<span className="mopen,nulldelimiter">



</span>

<span className="mfrac">
<span className="vlist-t,vlist-t2">
<span className="vlist-r">
<span className="vlist" style="height:1.3603em;">
<span style="top:-2.314em;">
<span className="pstrut" style="height:3em;">



</span>

<span className="mord">
<span className="mord,mathnormal">

G

</span>

<span className="mspace" style="margin-right:0.2222em;">



</span>

<span className="mbin">

−

</span>

<span className="mspace" style="margin-right:0.2222em;">



</span>

<span className="mord,mathnormal" style="margin-right:0.2222em;">

Y

</span>
</span>
</span>

<span style="top:-3.23em;">
<span className="pstrut" style="height:3em;">



</span>

<span className="frac-line" style="border-bottom-width:0.04em;">



</span>
</span>

<span style="top:-3.677em;">
<span className="pstrut" style="height:3em;">



</span>

<span className="mord">
<span className="mord,mathnormal" style="margin-right:0.0785em;">

X

</span>

<span className="mspace" style="margin-right:0.2222em;">



</span>

<span className="mbin">

−

</span>

<span className="mspace" style="margin-right:0.2222em;">



</span>

<span className="mord,mathnormal" style="margin-right:0.2222em;">

Y

</span>
</span>
</span>
</span>

<span className="vlist-s">

​

</span>
</span>

<span className="vlist-r">
<span className="vlist" style="height:0.7693em;">
<span>



</span>
</span>
</span>
</span>
</span>

<span className="mclose,nulldelimiter">



</span>
</span>

<span className="mclose,delimcenter" style="top:0em;">
<span className="delimsizing,size3">

)

</span>
</span>
</span>
</span>
</span>
</span>
</span>

The process and tasks for paying out this bonus, including timelines and
currency, are described in the Operations handbook, under
[Processing the CSM Bonus](https://flowfuse.com/handbook/operations/commission-payment/#processing-the-csm-bonus).

### When Transactions are Credited

Transactions are credited towards the bonus based on the date the transaction is signed, or notice is given, ensuring CSMs are recognized in the quarter the outcome is determined.

<table>
<thead>
  <tr>
    <th>
      Metric
    </th>
    
    <th>
      Credit Date for Bonus
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      Churn
    </td>
    
    <td>
      Notice/Cancellation Date
    </td>
  </tr>
  
  <tr>
    <td>
      Expansion (In-Term)
    </td>
    
    <td>
      Signing Date
    </td>
  </tr>
  
  <tr>
    <td>
      Expansion (Renewal)
    </td>
    
    <td>
      Signing Date
    </td>
  </tr>
  
  <tr>
    <td>
      Renewal
    </td>
    
    <td>
      Signing Date
    </td>
  </tr>
  
  <tr>
    <td>
      Contraction
    </td>
    
    <td>
      Notice Date
    </td>
  </tr>
</tbody>
</table>

**Example: If a renewal is signed in Q4 but the Effective Start Date is in Q1, it counts towards the Q4 bonus.**

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
