13 KiB
This page describes the Fleet Champions Community and associated processes
Fleet champions deck Fleet champions list
Types of championship that a Fleet customer can help with
- Logo usage on our website
- Customer testimonials
- Press interview
- Press quote
- Peer review - Gartner
- Peer review - G2
- Presenter on a webinar
- Present in a conference
- Public case study
Process to enable customer participation in press interview
Process to present at an industry conference
Process to present in a webinar
Process to publish a public case study
- Gather all information you can pull from Momentum and take this with you to your meeting with the CSM.
- Interview CSM, and have them go through all the information collected, and anything else they feel is important to the case study.
- Write a draft case study
- Send to CSM and have them edit it to their approval.
- Get approved by CSM
- Get CSM to connect you with their point of contact for the customer.
- Review with the customer, and make edits and changes where needed.
- Finalize case study.
- Publish case study to Fleet's customer page.
Process to publish an anonymous case study
Follow this process to publish a case study without identifying the customer. Anonymous case studies help share real outcomes while protecting the customer’s identity.
-
Gather customer information using Momentum
Run the following prompt in Momentum through the company's #acc Slack channel:
“@ Momentum based on all the previous call recordings and meeting notes, answer what's possible from this list of questions to the best of your ability:.”
Include these questions:
- What’s your company’s name?
- What industry does your company operate in? Approximately how many endpoints (Mac, Windows, Linux, etc.) do you currently manage?
- What was the primary frustration or limitation with your previous tool (e.g., Jamf, Intune, Kandji) that led you to look for a change?
- Before Fleet, were there "blind spots" in your infrastructure (like Linux servers or remote laptops) that you couldn't see or manage effectively?
- What were the top 3 requirements Fleet had to meet during your evaluation (e.g., On-premise hosting, GitOps workflows, osquery integration)?
- How does Fleet’s open-source nature or transparency impact your confidence in the security of your device management stack? Fleet emphasizes "transparency" for end-users.
- How has this affected the trust or relationship between your IT team and your employees?
- How long did it take to migrate your fleet? What was the impact on your end-users during that transition?
- Can you estimate the savings in licensing costs or the percentage reduction since consolidating to Fleet?
- Can you share a specific example of something you’ve automated with Fleet’s API that was difficult before?
- How has real-time visibility changed your response time to new vulnerabilities or compliance audits?
- If you were speaking to a CIO at a peer company, what is the single biggest reason you would tell them to switch to Fleet?
- How does having Fleet in place allow your team to be more effective moving forward?
- How important was it to manage macOS, Windows, and Linux from a single binary/API rather than maintaining three separate silos?
- Fleet allows you to stream telemetry directly to your own data tools.
- How has having direct/instant access to your device data changed how your security team monitors for threats?
- Did the choice between Fleet Cloud and self-hosting influence your decision, and why was that control important for your compliance or security needs?
-
Gather information in the Momentum Google Doc
Copy and paste the answers into one of the following Google Docs 2026 case study doc 1 of 2 or 2026 case study doc 2 of 2, where the rest of the marketing team can have access to the information.
Make sure the information is laid out in a question-and-answer format.
-
Review the responses
Confirm which questions Momentum answered, and document any questions that were not answered.
-
Draft the case study
Create the case study using Fleet's writing guidelines and previously published case studies, which can be found on the customers page for reference.
Remove any information that could identify the customer, including:
- Company name
- Unique internal tools or processes
- Specific geographic identifiers
- Any other identifiable details
-
Validate the information
Send the answers and the draft of the case study to the CSM assigned to the account, and have them review the information and case study in 48 hours.
The CSM will confirm that the information is accurate and safe to publish anonymously. If information needs to be edited or changed, it is up to the CMS to make those changes in the case study.
CSMs will have 48 hours to inform the marketing team of any changes that need to be made or whether it can be published. If no answer has been given by the CSM within this time, marketing will act as though the case study is good to be published as is.
-
Publish the case study
Add the case study to the website through create a PR in the articles folder on GitHub.
Use the customer's GitHub code name listed in the Fleet Champions Community spreadsheet in the branch name. This spreadsheet is the source of truth.
Make sure you include the metatag for the case study on the Customers page, so a tile is created and shows up on the customer reference page.
Make sure your meta description for the case study stays within 150 words or fewer, and gives an overview of what the case study is about.
-
Update Fleet Champions Community spreadsheet
Once the case study is live on the website, add the link to column N in the Fleet Champions Community spreadsheet, along with the title.
Identify in column M if the case study is anonymous or public
Once published, post about the new case study in the #help-marketing slack channel.
-
Add the case study to the marketing assets page
Add the new case study to the marketing assets page under the social proof section in the handbook.
Add the case study to the correct Anonymous stories industry table.
Include the following information in the table:
- The description of the story.
- The devices that are managed: macOS, Windows, Linux.
- The date the case study was published.
Process to publish customer testimonials on the website
Spontaneous, nice things that customers say about Fleet in:
- Conversations
- Official meetings
- Slack
- Social media posts
- Anywhere else
... should be captured for posterity in the testimonials.yml file
Steps:
- Copy the good parts of the text or post and the information about the person being quoted.
- Open the testimonials.yml file.
- Scroll to the bottom of the
YAMLfile and add a new block, e.g,
-
quote: Fleet made the process of migrating fast, easy, and simple.
quoteAuthorName: John O'Nolan
quoteAuthorJobTitle: Founder & CEO
quoteLinkUrl: https://www.linkedin.com/in/johnonolan/
quoteAuthorProfileImageFilename: testimonial-author-john-o'nolan-100x100@2x.png
productCategories: [Device management]
-
Add the quote in the
quotefield and fill in all information. All fields are required. -
The
productCategoriesfield should only be populated with one of the following:
Observability
Software management
Device management
- See the top of the testimonials.yml file for this formatting information if this explanation is unclear.
- If the testimonial is being added for immediate use on the website, adding the the new text block with the correct fields is sufficient.
- If the testimonial is being saved in the
testimonials.ymlfile but not published the block just added should be commented out so that the text is not processed by the website build. Your block should look like this:
# -
# quote: Fleet made the process of migrating fast, easy, and simple.
# quoteAuthorName: John O'Nolan
# quoteAuthorJobTitle: Founder & CEO
# quoteLinkUrl: https://www.linkedin.com/in/johnonolan/
# quoteAuthorProfileImageFilename: testimonial-author-john-o'nolan-100x100@2x.png
# productCategories: [Device management]
- There should be a Marketing ritual for processing the commented out spontaneous testimonials at some reasonable interval (quarterly, monthly, etc.) that is either captured here or in another spot in the Marketing handbook.
Process to publish logo on website
Follow this process to add a customer’s logo to the website. Only publish logos that are approved in the contract.
-
Create an issue after the contract is signed
Once the contract is signed, the Content Specialist will create an issue on the marketing board. This is so marketing can keep track of it's process.
The Content Specialist will then add the issue to the finance board, and assign it to Deal Desk.
-
Confirm logo approval
The Deal Desk reviews the contract and confirms whether we can use the customer’s logo on the website.
-
Update the Fleet Champions Community spreadsheet
Once approved, the Content Specialist marks the customer as “yes” for logo usage (found in column K) in the Fleet Champions Community spreadsheet.
-
Assign to design
The Content Specialist will assign the issue to the Head of Design to add the logo to the website.
Process to publish quote on peer review site such as Gartner Peer Review or G2
Follow this process to collect a quote on a peer review site such as Gartner Peer Insights or G2. These reviews help potential customers hear directly from other IT teams using Fleet.
Process
-
Coordinate with the CSM
Reach out to the customer success manager (CSM) who owns the account.
Ask them to schedule a 30 minute meeting with the customer.
The meeting should include the Content Specialist and the CMO if they have not yet met the customer.
-
Introduce the purpose of the meeting
During the meeting, spend the first 5–10 minutes introducing the goal.
Explain what the Fleet Champions Community is and how customer feedback helps others evaluating device management tools.
-
Explain the peer review program
Show the slide that explains peer reviews.
Explain that the goal is to collect honest feedback from real Fleet users on trusted review platforms.
-
Encourage multiple reviewers
Let the customer know that more than one person from their company can submit a review.
Explain that completing the review typically takes less than 5–10 minutes.
-
Share the review link
Send the Endpoint Management Tool review link during the meeting:
Make sure the customer uses the Endpoint Management Tool link, not the vulnerability assessment link.
After the meeting, send the same link again in a direct follow-up message to the person you spoke with.