---
title: "Engagements & Pricing"
description: "Pricing is publicly available at our pricing page. When discussing
pricing with enterprise customers, make a copy of
our internal pricing template deck
to discuss. For per-product commercial conversations, use the relevant
Pricing Decks (Edge, Hub, and Fleet)."
canonical_url: "https://flowfuse.com/handbook/sales/engagements/"
---

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

# Engagements

Pricing is publicly available at [our pricing page](https://flowfuse.com/pricing/). When discussing
pricing with enterprise customers, make a copy of
[our internal pricing template deck](https://docs.google.com/presentation/d/1kaW6aZxpnCaVuQVdVsi0RTulhRMbeqglhZHkzSP-2kM/)
to discuss. For per-product commercial conversations, use the relevant
[Pricing Decks](https://flowfuse.com/handbook/sales/pricing-decks) (Edge, Hub, and Fleet).

For all FlowFuse deals, use the
[Pricing Calculator](https://docs.google.com/spreadsheets/d/1v8Eo8zcdVZZsHxdmqmc03EM1p3QUp0sln14IBpyoo4M/edit?gid=736958252#gid=736958252)
(internal only) for current list prices and quote generation.

For discounts, custom agreements, or any other non-standard terms, follow the
[Deal Approval Process (Deal Desk)](#deal-approval-process-deal-desk).

## Creating a Deal

A deal is opened when an opportunity has achieved the Sales and Buyer Verifiers for a given [Sales Stage](https://docs.google.com/spreadsheets/d/1WKz_ll6bLxkkRlZ4K94Va1laGksHXleo8Pnv0aB08lU/).

To open a deal, be sure to set the correct properties.

1. Deal Type

  - New Business - For new customers or departments
  - Expansions - Upsells that are to be booked in-term
  - Renewal - Changes to the subscription effective on renewal date

For the full rules on when to create each deal type, who owns it, and how to
set its amount fields, see [Deal Management](https://flowfuse.com/handbook/sales/hubspot/#deal-management).

## Generating a Quote

Clearly written, easy to understand quotes are crucial for customers to
understand what they are purchasing and how much it costs. To create a quote,
combine the (1) product plan and (2) other purchased items according to the
following guide.

### What to Quote

When preparing a quote, include the product, quantities, and any required add-ons, if applicable. Always choose the matching product quote template — Edge, Hub, or Fleet — which pre-fills the correct features and terms onto the quote.

Use the internal pricing calculator linked above to configure each product sale, including the correct quantities and add-ons.

### Quote Naming Convention

Every quote is named the same way, so that quotes are identifiable at a glance
in HubSpot and stay identifiable once the signed copy is filed in Drive
alongside purchase orders and agreements:

`Quote - [Company] - [Order Type] - [Product] - [Year] - v##`

For example: `Quote - Acme Corp - Renewal - Hub - 2026 - v01`

- **Company** - the company name exactly as it appears on the HubSpot Company
record. This is internal identification only; the contracting legal entity is
set in the Buyer Information section of the quote itself.
- **Order Type** - `New Business`, `Expansion`, or `Renewal`, matching the
deal's [Deal Type](#creating-a-deal). Use `Amendment` for a change to an
already-executed contract; it is a document type only and has no
corresponding Deal Type.
- **Product** - `Edge`, `Hub`, or `Fleet`, matching the Quote Template selected
in [Creating a Quote](#creating-a-quote). For more than one product, join them
with a slash (`Edge/Hub`, `Edge/Fleet`). Use `Services` for a Professional
Services-only quote.
- **Year** - the year the subscription term starts, not the year the quote is
written. A renewal quoted in December 2026 for a term starting January 2027 is
`2027`.
- **v##** - the version, starting at `v01`. Increment it for each quote created
for the same transaction. Never reuse a number, including for a quote that was
voided.

Do not put the HubSpot record ID or the execution status in the name. HubSpot
tracks both, and the Company Quote Reference Number printed on the quote is the
identifier customers cite on a purchase order (see
[Closing a deal](#closing-a-deal)).

### Creating a Quote

Follow these steps to create a quote.

1. In HubSpot, open the relevant Deal. In the Quotes area, click Add to begin a
new quote.
  - Ensure the Deal Type is set up, "Expension" is an in-term upsel
  - Name the quote per the [Quote Naming Convention](#quote-naming-convention)
  - Ensure the Deal Type is set up, "Expansion" is an in-term upsell
2. Fill in the Buyer Information section. This will pre-fill with the
information from the contact in the Deal.
3. The default Quote creator will be you. Change this if necessary.
4. Add Line Items per
[the instructions](https://flowfuse.com/handbook/sales/engagements/#what-to-quote)
  - Select the appropriate Plan that is being quoted
  - For each line item, except Professional Services, check the Billing
  frequency to `Annual` and if the terms **ensure automatic renewal*
  - Adjust fields for Term and discount/fee/tax as needed.
  - Add Add-on line items for purchases that exceed features that are included
  with the Plan.
  - Enterprise Support line item should automatically be added to the Quote once you create it. There is an active HubSpot workflow supporting this automation.
  
    - Enterprise Support line item can be removed and replaced by a higher tier Premium Level Support for upsell purposes.
5. Set Signature and Payment settings as needed. Ensure a countersignature is
required from either the CEO or Head of GTM.
6. In the Template and Details section, choose the appropriate Quote Template
from the dropdown menu. Always use one of the three product templates that
correspond to our pricing packages:
  - **Edge**
  - **Hub**
  - **Fleet**<br />

Choosing the correct Quote Template is important because it will pre-fill the
correct plan features onto the quote. You can include additional Comments to
Buyer or Purchase Terms here. They will not overwrite the Terms and Comments
included with the Quote Template.
7. Review your Quote, and when everything is correct, click Create to create the
quote attached to the relevant Deal.

## Closing a deal

A deal is considered closed when all the outlined steps below are completed.
Starting the closing process can commence when the customer has legally
committed to purchase our products or services. This commitment must be
evidenced by one of the following:

- **Receipt of a Customer Purchase Order (PO)**: A document issued by the
customer, authorizing the purchase of specified goods or services at a
specified price.
- **Signed Company Quote**: A formal, written quotation provided by our company,
which has been duly signed, indicating their acceptance of the terms and
conditions outlined therein.
- **Note**: In the event a customer does not return a signed Company Quote,
the PO must include the Company Quote Reference Number found in the upper
right corner of the Company Quote (e.g. Reference: 20250820-153746396)

Important Note: Verbal agreements, informal emails, or other non-binding
expressions of interest do not constitute a closed deal. The legal commitment,
as evidenced by a PO or signed quote, is the sole determinant.

### Steps for the AE to complete

1. Verify, again, if the quote has all the right properties set according to
[Generating a Quote](#generating-a-quote) instructions.

  - Verify the Deal amount fields are set correctly per
  [Deal Amount Fields](https://flowfuse.com/handbook/sales/hubspot/#deal-amount-fields).
  - On the HubSpot Deal view, check and update:
  
    - Hosting Environment
    - Contract Start Date
    - Company address
    - Renewal Date
    - Use Case
    - Contract Term (months): the total length of the agreement.
    - Payment Terms: Upfront or Annual Installments. Required whenever
    Contract Term exceeds 12 months.
    - Spiced
  - Under contract management; check the box for MSA if a custom subscription
  agreement is agreed upon.
  - Contract Term and Payment Terms drive multi-year commission tiering
  (see [Sales Compensation Plan](https://flowfuse.com/handbook/sales/commission-plan/), Exhibit
  A, Section 10): multi-year deals must be paid upfront, and get 100%
  commission credit on each of the first three contract years. If these
  fields aren't set at close, payouts default to treating the deal as a
  standard 1-year term, which has caused at least one overpayment.
2. Upload the documents to the Google Drive in the correct directory

  - [Signed quotes and P.O.'s](https://drive.google.com/drive/folders/1Nb3UqFiE56ymgQnyfkDKHMAe6L3akNzQ)
  - If negotiated custom, the
  [Subscription agreement](https://drive.google.com/drive/folders/1h6jBvkJ2oDrBL7jw751RfAzBKkkprKDc)
3. Set up and complete the handover call with the customer, assigned technical contact and the CSM to ensure the start of the onboarding process.

  - Set up meeting agenda
  - Introduce CSM and Technical contact
  - Finalize outstanding action points
4. Move the deal to `Closing` in HubSpots Deal overview, update the close date
to when the customer committed to purchasing.
5. Send the CSM a direct message on slack with the following information:

  - Company Name
  - Key Champion
  - Billing Contact
  - Trial/PoV History: Please specify if they had an active Trial or Proof of Value (PoV) running prior to signing the annual contract.

### Steps for the CSM to complete

1. Check the signed quote for:

  - Start date
  - Renewal date
  - Are line items recurring, or not?
  - Is there a line item for Support?
  - Is an MSA agreed upon, and stored in the Google Drive?
2. Create the
[subscription](https://flowfuse.com/handbook/operations/billing/#creating-a-subscription)
3. If the signed quote is either an upsell or renewal, update the subscription with the line items and new pricing.
4. Provide access to the agreed upon line items

  - *Cloud*
    - Set up a team on FlowFuse Cloud for the customer in the right tier
    - Set the customer team to
    [enter manual billing mode](https://flowfuse.com/handbook/operations/accounts/#internal-teams-and-contracted-revenue)
    - Invite customer as owner to the team
    - Remove own email adress after sign up customer
  - *Self-Managed*
    - Generate a [license key](https://flowfuse.com/handbook/sales/meetings/pov#generating-a-license)
    - Send the license key with the onboarding email to the customer, following
    this
    [HubSpot Template](https://app-eu1.hubspot.com/templates/26586079/edit/135404737?q=welco&page=1).
5. If Professional Services are included, inform the PS team of deal.
6. Add customer to onboarding stage in the CSM tracking document.
7. Set up the meeting structure via the handover call, document customer goals, use case and administration tasks.
8. Move the deal to `Closed Won` stage.
9. Check if a new renewal deal is automatically generated under the correct terms and closing date.
10. Add the following to the deal:

- Hosting Environment
- Contract Start Date
- Company address
- Renewal Date

## Deal Approval Process (Deal Desk)

To ensure consistency and efficiency in our deal cycles, all proposals must follow the established Deal Desk workflow. This process covers the end-to-end journey from initial proposal creation through security review and final legal/contract execution.

### Asana Deal Desk Tasks

Any deal that requires **legal review**, **pricing/discount approval**, or other operational hand-offs must have a task created in the [Deal Desk Asana project](https://app.asana.com/read-only/Deal-Desk/1213818720452348/35b84534fdbe0d38d02d16cf84565538/list). To create a task, submit your request through this [form](https://form.asana.com/?k=hUrD0SJEka-BxHZ5qXAcxQ&d=1213818720452348).

When creating a task, include the following context so reviewers can act without needing to chase down background:

- **Deal / company name** — the customer or prospect this deal is for.
- **Counter-party contacts** — names, titles, and email addresses of the people involved from the customer side (e.g. economic buyer, legal contact, procurement).
- **Deal summary** — ARR, contract length, and any non-standard terms being requested.
- **What is needed** — be explicit: legal redline review, discount approval, MSA exception, etc.
- **Deadline / urgency** — when a decision is needed and why.
- **Link to HubSpot deal** — so reviewers can access the full deal record.

Creating a task ensures nothing gets lost in Slack threads and gives the CEO, Legal, and Finance a single place to review, comment, and approve.

### Overview of the Flow

#### Proposal Stage

Sales reps create proposals and determine if the deal structure (discounts, terms, payment schedules) is standard. Non-standard deals are routed to the CEO via Slack for approval, **and an Asana task must be opened in the Deal Desk project** (see above).

```mermaid
graph TD
    %% Nodes
    Start["Is the deal structure standard?"]
    AcceptProposal["Customer accepts the Proposal 'Agreed in Principle'?"]
    Negotiate["Rep must negotiate with the customer"]
    DealCriteria["Is there a discount?
                Is the term > 1 year?
                Payment terms > Net 30<br />"]
    CEO["Route to CEO for Slack approval"]
    Security["<b>Go to Security Process</b>"]

    %% Connections
    Start -- Yes --> AcceptProposal
    Start -- No --> DealCriteria

    AcceptProposal -- No --> Negotiate
    AcceptProposal -- Yes ----> Security

    Negotiate --> Start

    DealCriteria -- No --> Security
    DealCriteria -- Yes --> CEO

    CEO -- Reject --> Negotiate
    CEO -- Accept --> Security
```

#### Security Review

If a customer requires a security review, the AE coordinates between the
customer's questionnaire and the Engineering team to provide approved answers.

```mermaid
flowchart TD
    %% Nodes
    Start[Sales Rep Reviews Security]
    ReqReview{Requires Security Review?}
    
    %% Happy Path Steps
    ShareQ[Customer Shares Questionnaire]
    SendToEng[AE sends to Eng]
    EngAnswers[Eng sends answers to AE]
    Forward[AE forwards to Customer]
    
    %% Approval Decision
    Accepts{Customer Accepts?}
    Rework[AE reviews notes/Meeting with Engineering]
    
    %% End State
    EndProcess((Go to Contract/Legal))

    %% Connections
    Start --> ReqReview
    
    %% No Review Path
    ReqReview -- No --> EndProcess
    
    %% Review Needed Path
    ReqReview -- Yes --> ShareQ
    ShareQ --> SendToEng
    SendToEng --> EngAnswers
    EngAnswers --> Forward
    Forward --> Accepts
    
    %% Outcome Logic
    Accepts -- Approve --> EndProcess
    
    %% Rejection Loop
    Accepts -- Reject --> Rework
    Rework --> EngAnswers
```

#### Legal & Contract Process

This stage handles the Master Subscription Agreement (MSA).
Depending on whether the customer accepts our standard MSA or requests minor/major
redlines, the contract is routed to Legal (Scale) and/or the CEO for cost and term
approval before final signature. **Any deal entering this stage requires an Asana task in the Deal Desk project** with full counter-party context (see [Asana Deal Desk Tasks](#asana-deal-desk-tasks) above).

```mermaid
flowchart TD
    %% Nodes
    IsStd{Standard MSA?}
    IsRed{Redlines?}
    NonStd[Legal Review + Cost Approval]
    Major[Legal Review - Major/IP]
    CEO[CEO Approval]
    Send[Send to Customer]
    Approved{Customer Approve?}
    Sign((Sign Contract))
    
    %% Non-Standard Path
    IsStd -- No --> NonStd
    NonStd --> CEO

    %% Standard Path
    IsStd -- Yes --> IsRed
    IsRed -- No --> Sign
    
    %% Redline Paths
    IsRed -- "Yes (Minor/Payment)" --> CEO
    IsRed -- "Yes (Major/Liability)" --> Major
    Major --> CEO

    %% Unified Loop
    CEO --> Send
    Send --> Approved
    Approved -- Yes --> Sign
    Approved -- No --> CEO
```

## Sitemap

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