fleet/handbook/business-operations

Business Operations

Meetings

• At Fleet, meetings start whether you're there or not. Nevertheless, being even a few minutes late can make a big difference and slow your meeting counterparts down. When in doubt, show up a couple of minutes early.
• It's okay to spend the first minute or two of a meeting being present and making small talk. Since we are all remote, it's easy to miss out on hallway chatter and human connections that happen in meatspace. Use this time together during the first minute to say "Hi!" Then you can jump into the topics to be discussed.
• Turning on your camera allows for more complete and intuitive verbal and non-verbal communication. Feel free to leave your camera on or turn it off when joining meetings with new participants you might not be familiar with yet. Turn your camera on when you lead or cohost a meeting.
• In an all-remote company, “face time” matters. Remember: even if someone’s calendar is open, they have other work to do. Limiting (or batching up) internal meetings can enable longer, uninterrupted stretches of deep work.

Internal meeting scheduling

Use the Google Calendar "Find a meeting time" feature to coordinate meetings with Fleet team members. Enter the @fleetdm.com emails for each participant into the "Meet with..." box in Google Calendar, and the calendar availability for each participant will appear in your view. Then, when you select a meeting time, those participants will automatically be invited, and a video conference will be attached to the invite. Please prefer this strategy over negotiating meeting times via chat -- This can save a lot of communication overhead, especially when scheduling with multiple participants. It is important to set your working hours in Google Calendar and block out any personal time/events/PTO, so that team members do not inadvertently schedule a time when you are not available. Many team members use the free tier of reclaim.ai to synchronize personal event times (without event details) into their work calendars. It is also common practice to block out time for focused work.

Modifying an event organized by someone else

To edit an event where someone else at Fleet is the organizer, you can first subscribe to their calendar in Google Calendar and then edit the event on their calendar. Your edits will automatically apply to all attendees.

This works because every Fleetie grants edit access to everyone else at Fleet as part of onboarding.

External meeting scheduling

When scheduling external meetings, provide external participants with a Calendly link to schedule with the relevant internal participants. If you need a Calendly account, reach out to mikermcneil via Slack.

Scheduling a Zoom meeting

We use the Zoom add-on for Google Calendar to schedule Zoom meetings when we create calendar events. To add a Zoom meeting to a calendar event, click the "Add video conferencing" dropdown and select "Zoom Meeting." Google Calendar will automatically add the Zoom meeting details and instructions to join the event. We configure our Zoom meetings to let participants join before the host starts the meeting. We do this to make sure meetings start on time, even if the host isn't there.

Key reviews

Every release cycle, each department leader prepares a key review deck and presents it to the CEO. In this deck, the department will highlight KPI metrics (numbers measuring everyday excellence) and progress of timebound goals for a particular quarter (OKRs). The information for creating this deck is located in the "🌈 Fleet" Google drive using "How to create key review"(internal doc).

TODO: extrapolate "key reviews" to fleetdm.com/handbook/company/why-this-way -- maybe a section on "why measure KPIs and set goals?"

Spending company money

As we continue to expand our company policies, we use GitLab's open expense policy as a guide for company spending. In brief, this means that as a Fleet team member, you may:

• Spend company money like it is your own money.
• Be responsible for what you need to purchase or expense to do your job effectively.
• Feel free to make purchases in the company's interest without asking for permission beforehand (when in doubt, do inform your manager prior to purchase or as soon as possible after the purchase). For more developed thoughts about spending guidelines and limits, please read GitLab's open expense policy.

Attending conferences or company travel

When attending a conference or traveling for Fleet, please make a post in #help-brex on Slack with the following information:

• The start and end dates for your trip.
• The price of your flight (feel free to optimize a direct flight if there is one that is less than double the price of the cheapest non-direct flight).
• The price of your hotel per night (dry cleaning is allowable if the stay is over 3 days).
• The price of the admission fees if attending a conference.
• $100 allowance per day for food and beverage (please use your personal credit card for movies, mini bars, and entertainment, except when entertaining guests who contribute actively in code/community on a quarterly basis, or who are Salesforce contacts on an open, qualified opportunity with a budget of at least $160k+ ΔARR).
• Customer/Partner Facing Events:
  • Gala/Black Tie Events: Tuxedo or Gown Rental, $150-$225 USD per event is reimbursable. (The event must be customer specific and the invitation must state black tie only). The monthly limit on your Brex card will be increased temporarily as necessary to accommodate the increased spending associated with the conference. We highly recommend you order a physical Brex card if you do not have one before attending the conference.

Non-travel purchases that exceed a Brex cardholder's limit

For non-travel purchases that would require an increase in the Brex cardholder's limit, please make a post in #g-business-opeartions) on Slack with the following information:

• The nature of the purchase (i.e. SaaS subscription and what it's used for)
• The cost of the purchase and whether it is a fixed or variable (i.e. use-based) cost.
• Whether it is a one time purchase or a recurring purchase and at what frequency the purchase will re-occur (annually, monthly, etc.)
• If there are more ideal options to pay for the purchase (i.e. bill.com, the Fleet AP Brex card, etc.) that method will be used instead.
• In general, recurring purchases such as subscription services that will continually stretch the spend limit on a cardholder's Brex card should be paid through other means.
• For one time purchases where payment via credit card is the most convenient then the card limit will be temporarily increased to accomodate the purchase.

Reimbursements

We provide all of our team members with Brex cards for making purchases for the company. Fleet will reimburse team members who pay for work-related expenses with their personal funds. Team members can request reimbursement through Gusto if they're in the US or Pilot if they are an international team member. When submitting an expense report, team members need to provide the receipt and a description of the expense. Operations will review the expense and reach out to the team member if they have any questions. The reimbursement will be added to the team member's next payroll when an expense is approved.

Pilot handles reimbursements differently depending on if the international team member is classified as an employee or a contractor. If the reimbursement is for a contractor, Operations will need to add the expense reimbursement to an upcoming recurring payment or schedule the reimbursement as an off-cycle payment. If the reimbursement is for an employee, no other action is needed; Pilot will add the reimbursement to the team member's next payroll.

Benefits

Paid time off

What matters most is your results, which are driven by your focus, your availability to collaborate, and the time and consideration you put into your work. Fleet offers all team members unlimited time off. Whether you're sick, you want to take a trip, you are eager for some time to relax, or you need to get some chores done around the house, any reason is a good reason. For team members working in jurisdictions that require certain mandatory sick leave or PTO policies, Fleet complies to the extent required by law.

Taking time off

When you take any time off, you should follow this process:

• Let your manager and team know as soon as possible (i.e., post a message in your team's Slack channel with when and how long).
• Find someone to cover anything that needs covering while you're out and communicate what they need to take over the responsibilities as well as who to refer to for help (e.g., meetings, planned tasks, unfinished business, important Slack/email threads, anything where someone might be depending on you).
• Mark an all-day "Out of office" event in Google Calendar for the day(s) you're taking off. If you can’t complete the above because you need to take the day off quickly due to an emergency, let your manager know and they will help you complete the handoff. If you ever want to take a day off, and the only thing stopping you is internal (Fleetie-only) meetings, don’t stress. Consider, “Is this a meeting that I can reschedule to another day, or is this a meeting that can go on without me and not interfere with the company’s plans?” Talk to your manager if you’re unsure, but it is perfectly OK to reschedule internal meetings that can wait so that you can take a day off. This process is the same for any days you take off, whether it's a holiday or you just need a break.

Holidays

At Fleet, we have team members with various employment classifications in many different countries worldwide. Fleet is a US company, but we think you should choose the days you want to work and what days you are on holiday, rather than being locked into any particular nation or culture's expectation about when to take time off. When a team member joins Fleet, they pick one of the following holiday schedules:

• Traditional: This is based on the country where you work. Non-US team members should let their managers know the dates of national holidays. Or
• Freestyle: You have no set schedule and start with no holidays. Then you add the days that are holidays to you.

Either way, it's up to you to make sure that your responsibilities are covered, and that your team knows you're out of the office.

New parent leave

Fleet gives new parents six weeks of paid leave. After six weeks, if you don't feel ready to return yet, we'll set up a quick call to discuss and work together to come up with a plan to help you return to work gradually or when you're ready.

Relocating

When Fleeties relocate, there are vendors that need to be notified of the change.

Before relocating, please let the company know in advance by following the directions listed in the relevant issue template ("Moving").

Coworking

Your Brex card may be used for up to $500 USD per month in coworking costs. Please get prior approval by making a custom request to the business operations team.

Performance feedback

At Fleet, performance feedback is a continuous process. We give feedback (particularly negative) as soon as possible. Most feedback will happen during 1:1 meetings, if not sooner.

Compensation changes

Fleet's founders evaluate and update compensation decisions yearly, shortly after the anniversary of a team member's start date.

CEO handbook

The CEO handbook details processes specific to Mike McNeil, CEO of Fleet.

Team member onboarding

Before the start date

Fleet is open source and anyone can contribute at any time. Before a core team member's start date, they are welcome to contribute, but not expected to.

Recommendations for new teammates

Welcome to Fleet!

1. Understand the company
2. Take the time to get trained
3. Get comfortable with the tools
4. Immerse yourself in the world of device management and cybersecurity.

Please see Fleet's "🥽 Recommendations for new teammates".

Role-specific licenses

Certain new team members, especially in go-to-market (GTM) roles, will need paid access to paid tools like Salesforce and LinkedIn Sales Navigator immediately on their first day with the company. The table below can be used to determine which paid licenses they will need, based on their role:

Role	Salesforce CRM	Salesforce "Inbox"	LinkedIn (paid)	Gong (paid)	Zoom (paid)
🐋 AE	✅	✅	✅	✅	✅
🐋 CSM	✅	✅	❌	✅	✅
🐋 SA	✅	✅	❌	❌	❌
🫧 SDR	✅	✅	✅	❌	❌
🐋 Other role	❌	❌	❌	❌	❌
🫧 Other role	❌	❌	❌	❌	❌
Other department	❌	❌	❌	❌	❌

Warning: Do NOT buy LinkedIn Recruiter. Use the cheapest possible LinkedIn tier. The goal is access to profile views and data, not InMail. Fleet does not send InMail.

Training

It's important that every team member at Fleet takes the time to get fully trained and onboarded. When a new team member joins Fleet, we create an onboarding issue for them in the fleetdm/confidential repo using this issue template. We want to make sure that the new team member will be able to complete every task in their issue. To make sure the new team member is successful in their onboarding, we customize their issue by commenting on any tasks they won't need to complete. We believe in taking onboarding and training seriously and that the onboarding template is an essential source of truth and good use of time for every single new hire. If managers see a step that they don't feel is necessary, they should make a pull request to the onboarding template.

Expectations during onboarding:

• Onboarding time (all checkboxes checked) is a KPI for the business operations team. Our goal is 14 days or less.
• The first 3 weekdays (excluding days off) for every new team member at Fleet is reserved for completing onboarding tasks from the checkboxes in their onboarding issue. New team members should not work on anything else during this time, whether or not other tasks are stacking up or assigned. It is OK, expected, and appreciated for new team members to remind their manager and colleagues of this important responsibility.
• Even after the first 3 days, during the rest of their first 2 weeks, completing onboarding tasks on time is a new team member's highest priority.

Sightseeing tour

During their onboarding at Fleet, new team members are asked to schedule a sightseeing tour call with People operations. During this call, the new team member will participate in an interactive tour that includes:

• GitHub issues: the living bloodstream of the company.
• Kanban boards: the bulletin board of quests you can get and how you update status and let folks know things are done.
• Google Calendar: the future.
• Gmail: like any mailbox, full of junk mail, plus some important things, so it is important to check carefully.
• Salesforce: the Rolodex.
• Google Docs: the archives.
• Slack:
  • The "office" (#g-, #general).
  • The walkie talkies (DMs).
  • The watering hole (#oooh-, #random, #news, #help-).

Contributor experience training

During their first week at Fleet, new team members are asked to schedule a contributor experience training call with Mike McNeil. During this call, the new team member will share their screen, and People operations will:

• make sure emails will get seen and responded to quickly.
• make sure Slack messages will get seen and responded to quickly.
• make sure you know where your issues are tracked, which kanban board you use, and what the columns mean.
• make sure you can succeed with submitting a PR with the GitHub web editor, modifying docs or handbook, and working with Markdown.
• talk about Google calendar.
• give you a quick tour of the Fleet Google drive folder.

Directly responsible individuals

Please read "Why direct responsibility?" to learn more about DRIs.

Levels of confidentiality

• Public (share with anyone, anywhere in the world)
• Confidential (share only with team members who've signed an NDA, consulting agreement, or employment agreement)
• Classified (share only with founders of Fleet, business operations, and/or the people involved. e.g., US social security numbers during hiring)

TODO: extrapolate to "why this way" page

Email relays

There are several special email addresses that automatically relay messages to the appropriate people at Fleet. Each email address meets a minimum response time ("Min RT"), expressed in business hours/days, and has a dedicated, directly responsible individual (DRI) who is responsible for reading and replying to emails sent to that address. You can see a list of those email addresses in "Contacting Fleet" (private Google doc).

TODO: extrapolate to "why this way" page

GitHub labels

We use special characters to define different types of GitHub labels. By combining labels, we organize and categorize GitHub issues. This reduces the total number of labels required while maintaining an expressive labeling system. For example, instead of a label called platform-dev-backend, we use #platform :dev ~backend.

Special character	Label type	Examples
#	Noun	#platform, #interface, #agent
:	Verb	:dev, :research, :design
~	Adjective	~blocked, ~frontend, ~backend

TODO: extrapolate to "why this way" page

Tools we use

There are a number of tools that are used throughout Fleet. Some of these tools are used company-wide, while others are department-specific. You can see a list of those tools in "Tools we use" (private Google doc).

Here is an overview of a few of the most important and generally-applicable tools we use at Fleet:

Slack

At Fleet, we do not send internal emails to each other. Instead, we prefer to use Slack to communicate with other folks who work at Fleet. We use threads in Slack as much as possible. Threads help limit noise for other people following the channel and reduce notification overload. We configure our working hours in Slack to make sure everyone knows when they can get in touch with others.

Slack channel prefixes

We have specific channels for various topics, but we also have more general channels for the teams at Fleet. We use these prefixes to organize the Fleet Slack:

• g-: for team/group channels (Note: "g-" is short for "grupo" or "group").
• oooh-: used to discuss and share interesting information about a topic.
• help-: for asking for help on specific topics.
• at or fleet-at: for customer channels.
• 2023-: for temporary channels (Note: specify the relevant year in four digits, like "YYYY-`)

Slack communications and best practices

In consideration of our team, Fleet avoids using global tags in channels (i.e. @here, @channel, etc). 1. What about polls? Good question, Fleeties are asked to post their poll in the channel and @mention the teammates they would like to hear from. 2. Why does this matter? Great question! The Fleet culture is pretty simple: think of others, and remember the company Values.

Zoom

We use Zoom for virtual meetings at Fleet, and it is important that every team member feels comfortable hosting, joining, and scheduling Zoom meetings. By default, Zoom settings are the same for all Fleet team members, but you can change your personal settings on your profile settings page. Settings that have a lock icon next to them have been locked by an administrator and cannot be changed. Zoom administrators can change settings for all team members on the account settings page or for individual accounts on the user management page.

Salesforce

We consider Salesforce to be our Rolodex for customer information.

Here are the steps we take to grant appropriate Salesforce licenses to a new hire:

1. Go to "My Account".
2. View contracts -> pick current contract.
3. Add the desired number of licenses.
4. Sign DocuSign sent to the email.
5. The order will be processed in ~30m.
6. Once the basic license has been added, you can create a new user using the new team member's @fleetdm.com email and assign a license to it.
7. To also assign a user an "Inbox license", go to the "Setup" page and select "User > Permission sets". Find the inbox permission set and assign it to the new team member.

Gong

Capturing video from meetings with customers, prospects, and community members outside the company is an important part of building world-class sales and customer success teams and is a widespread practice across the industry. At Fleet, we use Gong to capture Zoom meetings and share them company-wide. If a team member with a Gong license attends certain meetings, generally those with at least one person from outside of Fleet in attendance.

• While some Fleeties may have a Gong seat that is necessary in their work, the typical use case at Fleet is for employees on the company's sales, customer success, or customer support teams.
• You should be notified anytime you join a recorded call with an audio message announcing "this meeting is being recorded" or "recording in progress." To stop a recording, the host of the call can press "Stop."
• If the call has external participants and is recorded, this call is stored in Gong for future use. To access a recording saved in Gong, visit app.gong.io and sign in with SSO.
• Everyone at Fleet has access, whether they have a Gong seat or not, and you can explore and search through any uploaded call transcripts unless someone marks them as private (though the best practice would be not to record any calls you don't want to be captured). If you ever make a mistake and need to delete something, you can delete the video in Gong or reach out to Nathan Holliday or Mike McNeil for help. They will delete it immediately without watching the video.
• Note that any recording stopped within 60 seconds of the start of the recording is not saved in Gong, and there will be no saved record of it.

Most folks at Fleet should see no difference in their meetings if they aren't interfacing with external parties. Our goal in using Gong and recording calls is to capture insights from sales, customer, and community meetings and improve how we position and sell our product. We never intend to make anyone uncomfortable, and we hope you reach out to our DRI for Gong, Nathan Holliday, or Mike McNeil if you have questions or concerns.

Troubleshooting Gong:

• In order to use Gong, the Zoom call must be hosted by someone with a Fleet email address.
  • You cannot use Gong to record calls hosted by external parties.
• Cloud recording in Zoom has to be turned on and unlocked company wide for Gong to function properly, because of this, there is a chance that some Gong recordings may still save in Zoom's cloud storage even if they aren't uploaded into Gong.
  • To counter this, Nathan Holliday will periodically delete all recordings found in Zoom's storage without viewing them.
• For those with a Gong seat or scheduling a call with someone in attendance that has a Gong seat who does not wish for their Zoom call with an external party to record:
  • A complete list can be found here.
    • 1 on 1, 1:1, confidential, interview, internal and no shadows are some commonly used words that will disable Gong.
  • If you need words added to the list of exlusionary words, please reach out to Nathan Holliday.
• We have excluded anyone with an email domain from @cooley.com or @pilot.com from Gong's recording feature. These are professional services firms working with Fleet on internal matters, and calls with them are considered internal.

If you need help using Gong, please check out Gong Academy at https://academy.gong.io/.

Zapier and DocuSign

We use Zapier to automate how completed DocuSign envelopes are formatted and stored. This process ensures we store signed documents in the correct folder and that filenames are formatted consistently. When the final signature is added to an envelope in DocuSign, it is marked as completed and sent to Zapier, where it goes through these steps:

1. Zapier sends the following information about the DocuSign envelope to our Hydroplane webhook:
   • emailSubject - The subject of the envelope sent by DocuSign. Our DocuSign templates are configured to format the email subject as [type of document] for [signer's name].
   • emailCsv - A comma-separated list of signers' email addresses.
2. The Hydroplane webhook matches the document type to the correct Google Drive folder, orders the list of signers, creates a timestamp, and sends that data back to Zapier as
   • destinationFolderID - The slug for the Google Drive folder where we store this type of document.
   • emailCsv - A sorted list of signers' email addresses.
   • date - The date the document was completed in DocuSign, formatted YYYY-MM-DD.
3. Zapier uses this information to upload the file to the matched Google Drive folder, with the filename formatted as [date] - [emailSubject] - [emailCvs].PDF.
4. Once the file is uploaded, Zapier uses the Slack integration to post in the #peepops channel with the message:

   Now complete with all signatures:
      [email subject]
      link: drive.google.com/[destinationFolderID]
   

Hiring

At Fleet, we collaborate with core team members, consultants, advisors, and outside contributors from the community.

Are you a new fleetie joining the Business Operations team? For Loom recordings demonstrating how to make offers, hire, onboard, and more please see this classified Google Doc.

Hiring a consultant

In addition to core team members, from time to time Fleet hires consultants who may work for only a handful of hours on short projects.

A consultant is someone who we expect to either:

• complete their relationship with the company in less than 6 weeks
• or have a longer-term relationship with the company, but never work more than 10 hours per week.

Consultants:

• do NOT receive company-issued laptops
• do NOT receive Yubikeys
• do NOT get a "Hiring" issue created for them
• do NOT go through training using the contributor onboarding issue.
• do NOT fill any existing open position

Consultants track time using the company's tools and sign Fleet's consulting agreement.

To hire a consultant, submit a custom request to the business operations team.

TODO: replace this w/ issue template (see also commented-out notes in hiring.md for some other steps)

Who ISN'T a consultant?

If a consultant plans to work more than 10 hours per week, or for longer than 6 weeks, they should instead be hired as a core team member.

Core team members:

• are hired for an existing open position
• are hired using Fleet's "Hiring" issue template, including receiving a company-issued laptop and Yubikeys
• must be onboarded (complete the entire, unabridged onboarding process in Fleet's "Onboarding" issue template)
• must be offboarded
• get an email address
• have a manager and a formal place in the company org chart
• are listed in "🧑‍🚀 Fleeties"
• are paid as part of the standard payroll ritual for the place they work and their employment classification.

Consultants aren't required to do any of those things.

Sending a consulting agreement

To hire a non-US consultant, please submit a custom request.

To hire a US-based consultant, send them an agreement using the "Contractor agreement (US)" template in DocuSign. (This template is located in the "¶¶ Classified templates" folder, which is only accessible via certain Docusign accounts in 1Password.)

Note: The Docusign template labeled "Contractor agreement (US)" is actually used for both consultants and core team members in the US who are classified as 1099 contractors or billed corp-to-corp as vendors. You may also sometimes hear this referred to as Fleet's "Consulting agreement". Same thing.

To send a US consulting agreement, you'll need the new consultant's name, the term of the service, a summary of the services provided, and the consultant's fee.

There are some defaults that we use for these agreements:

• Term: Default to one month unless otherwise discussed.
• Services rendered: Copy and paste from the language in this doc
• Work will commence and complete by dates: Start date and end of term date
• Fee: Get from the consultant.
• Hours: Default to 10 hr/week.

Then hit send! After all of the signatures are there, the completed document will automatically be uploaded to the appropriate Google Drive folder, and a Slack message will appear in the #help-classified channel.

Creating a new position

Want to hire? Here's how to open up a new position on the core team:

Use these steps to hire a fleetie, not a consultant.

1. Propose headcount: Add the proposed position to "🧑‍🚀 Fleeties" in an empty row (but using one of the existing IDs. Unsure? Ask for help.) Be sure to include job title, manager, and department. For now, leave the start date blank.
2. Propose job description: Locate one of the existing job descriptions inside the handbook/company/ folder and duplicate it into a new handbook subpage. Use the same style of filename, but based on the new job title. (This filename will determine the URL where candidates can apply.)

• Keep the structure of the document identical. Change only the job title, "Responsibilities", and "Experience".
• In the same pull request, add a link to your new job posting to the bottom of "📖 Company#Open positions" in the handbook.
• State the proposed job title, include the appropriate departmental emoji, and link to the "living" fleetdm.com URL; not the GitHub URL. (This is where the new page will eventually exist, once this pull request is merged. For now, if you were to visit this URL, you'd just see a 404 error. So how can you determine this URL? To understand the pattern, visit other job description pages from the live handbook, and examine their URLs in your browser.)

3. Get it approved and merged: When you submit your proposed job description, the CEO will be automatically tagged for review and get a notification. He will consider where this role fits into Fleet's strategy and decide whether Fleet will open this position at this time. He will review the data carefully to try and catch any simple mistakes, then tentatively budget cash and equity compensation and document this compensation research. He will set a tentative start date (which also indicates this position is no longer just "proposed"; it's now part of the hiring plan.) Then the CEO will start a #hiring-xxxxx-YYYY Slack channel, at-mentioning the original proposer and letting them know their position is approved. (Unless it isn't.)

Why bother with approvals? We avoid cancelling or significantly changing a role after opening it. It hurts candidates too much. Instead, get the position approved first, before you start recruiting and interviewing. This gives you a sounding board and avoids misunderstandings.

Approving a new position

When review is requested on a proposal to open a new position, the CEO will complete the following steps when reviewing the pull request:

1. Consider role and reporting structure: Confirm the new row in "Fleeties" has a manager, job title, and department, that it doesn't have any corrupted spreadsheet formulas or formatting, and that the start date is still blank (so that it is clear to everyone that this position has been proposed, but that it is not confirmed and planned, yet).

2. Read job description: Confirm the job description consists only of changes to "Responsibilities" and "Experience," with an appropriate filename, and that the content looks accurate, is grammatically correct, and is otherwise ready to post in a public job description on fleetdm.com.

3. Budget compensation: Ballpark and document compensation research for the role based on

   • Add screenshot: Scroll to the very bottom of "¶¶ 💌 Compensation decisions (offer math)" and add a new heading for the role, pattern-matching off of the names of other nearby role headings. Then create written documentation of your research for future reference. The easiest way to do this is to take screenshots of the relevant benchmarks in Pave and paste those screenshots under the new heading.
   • Update team database: Update the row in "¶¶ 🥧 Equity plan" using the benchmarked compensation and share count.
     • Salary: Enter the salary: If the role has variable compensation, use the role's OTE (on-target earning estimate) as the budgeted salary amount, and leave a note in the "Notes (¶¶)" cell clarifying the role's bonus or commission structure.
     • Equity: Enter the equity as a number of shares, watching the percentage that is automatically calculated in the next cell. Keep guessing different numbers of shares until you get the derived percentage looking like what you want to see.

4. Decide: Decide whether to approve this role or to consider it a different time. If approving, then:

   • Create Slack channel: Create a private "#hiring-xxxxxx-YYYY" Slack channel (where "xxxxxx" is the job title and YYYY is the current year) for discussion and invite the hiring manager.
   • Publish opening: Approve and merge the pull request. The job posting go live within ≤10 minutes.
   • Reply to requestor: Post a comment on the pull request, being sure to include a direct link to their live job description on fleetdm.com. (This is the URL where candidates can go to read about the job and apply. For example: fleetdm.com/handbook/company/product-designer):

     The new opening is now live!  Candidates can apply at fleetdm.com/handbook/company/railway-conductor.
     

Note: Most columns of the "Equity plan" are updated automatically when "Fleeties" is, based on the unique identifier of each row, like 🧑‍🚀890. (Advisors have their own flavor of unique IDs, such as 🦉755, which are defined in "Advisors and investors".)

Recruiting

Fleet accepts job applications, but the company does not list positions on general purpose job boards. This prevents us being overwhelmed with candidates so we can fulfill our goal of responding promptly to every applicant.

This means that outbound recruiting, 3rd party recruiters, and references from team members are important aspect of the company's hiring strategy. Fleet's CEO is happy to assist with outreach, intros, and recruiting strategy for candidates.

Receiving job applications

Every job description page ends with a "call to action", including a link that candidates can click to apply for the job. Fleet replies to all candidates within 1 business day and always provides either a rejection or decisive next steps; even if the next step is just a promise. For example:

"We are still working our way through applications and still have not been able to review yours yet. We think we will be able to review and give you an update about your application update by Thursday at the latest. I'll let you know as soon as I have news. I'll assume we're both still in the running if I don't hear from you, so please let me know if anything comes up."

When a candidate clicks applies for a job at Fleet, they are taken to a generic Typeform. When they submit their job application, the Typeform triggers a Zapier automation that will posts the submission to g-business-operations in Slack. The candidate's job application answers are then forwarded to the applicable #hiring-xxxxx-202x Slack channel and the hiring manager is @mentioned.

Candidate correspondence email templates

Fleet uses certain email templates when responding to candidates. This helps us live our value of 🔴 empathy and helps the company meet the aspiration of replying to all applications within one business day.

Hiring restrictions

Incompatible former employers

Fleet maintains a list of companies with whom Fleet has do-not-solicit terms that prevents us from making offers to employees of these companies. The list is in the Do Not Solicit tab of the BizOps spreadhseet.

Incompatible locations

Fleet is unable to hire team members in some countries. See this internal document for the list.

Interviewing

We're glad you're interested in joining the team! Here are some of the things you can anticipate throughout this process:

• We will reply by email within one business day from the time when the application arrives.
• You may receive a rejection email (Bummer, consider applying again in the future).
• You may receive an invitation to "book with us." If you've been invited to "book with us," you'll have a Zoom meeting with the hiring team to discuss the next steps.

Hiring a new team member

This section is about hiring a new core team member, or fleetie.

Note: Employment classification isn't what makes someone a fleetie. Some Fleet team members are contractors and others are employees. The distinction between "contractor" and "employee" varies in different geographies, and the appropriate employment classification and agreement for any given team member and the place where they work is determined by CEO during the process of making an offer.

Here are the steps hiring managers follow to get an offer out to a candidate:

1. Add to team database: Update the Fleeties doc to accurately reflect the candidate's:
   • Start date

     Tip: No need to check with the candidate if you haven't already. Just guess. First Mondays tend to make good start dates. When hiring an international employee, Pilot.co recommends starting the hiring process a month before the new employee's start date.

   • First and last name
   • Preferred pronoun _("them", "her", or "him")
   • Country and state where they will be working (Pattern-match from how other rows do it. Please be mindful of spreadsheet formulas.)
   • LinkedIn URL (If the fleetie does not have a LinkedIn account, enter N/A)
   • GitHub username (Every candidate must have a GitHub account in "Fleeties" before the company makes them an offer. If the the candidate does not have a GitHub account, ask them to create one, and make sure it's tracked in "Fleeties".)

     Tip: A revealing live interview question can be to ask a candidate to quickly share their screen, sign up for GitHub, and then hit the "Edit" button on one of the pages in the Fleet handbook to make their first pull request. This should not take more than 5 minutes.

2. Call references: Ask the candidate for at least 2+ references and contact each reference in parallel using the instructions and tips in Fleet's reference check template. Be respectful and keep these calls very short.
3. Schedule CEO interview: Schedule 30m for the CEO to interview the candidate, if they haven't already done so.
   • At Fleet, the CEO interviews every new team member at least once before Fleet extends an offer. (We plan to continue this practice until headcount reaches 100.)
     • No need to check with the CEO first. You can just book the meeting on his calendar.
     • Schedule the meeting directly on the CEO's calendar during a time he and the candidate are both explicitly available according to that calendar. Available means whitespace.
     • Either use Google Calendar directly, or offer to use the CEO's 30m Calendly link. It is up to you, the hiring manager, to get this meeting scheduled and showing up at a time on the CEO's calendar.
   • If this is an engineering position, before the CEO interview, please also be sure that the candidate has already been interviewed by Zach Wasserman. (If not, feel free to include Zach in this final interview.)
   • The personal email the candidate uses for this calendar event is where they will receive their offer or rejection email.
   • Make sure that the agenda doc for the 30m final interview with CEO is in an outline format, located in the "Meeting notes" folder, and contains a discussion point about asking the candidate to verify that 2FA is enabled in their GitHub account.
4. Confirm intent to offer: Compile feedback about the candidate into a single document and share that document with the CEO via Google Drive. This will be interpreted by the CEO as a signal that you are ready for him to make an offer to this candidate.
   • Compile feedback into a single doc: Include feedback from interviews, reference checks, and challenge submissions. Include any other notes you can think of offhand, and embed links to any supporting documents that were impactful in your final decision-making, such as portfolios or challenge submissions.
   • Share this single document with the CEO via email.
     • Share only one, single Google Doc, please; with a short, formulaic name that's easy to understand in an instant from just an email subject line. For example, you could title it:

       Why hire Jane Doe ("Train Conductor") - 2023-03-21

     • When the CEO receives this doc shared doc in his email with the compiled feedback about the candidate, he will understand that to mean that it is time for Fleet to make an offer to the candidate.

Making an offer

After meeting with the candidate for their final interview, the CEO uses the following steps to make an offer:

1. Review decision: The CEO reviews the data and decides whether it still makes sense to make this offer to this person in this role. If not, he lets the manager know. Otherwise, he continues with the offer.
2. Adjust compensation: Re-benchmark salary, adjusting for cost of living where the candidate will do the work.
   • Paste a screenshot from Pave showing the amount of cash and equity in the offer (or write 1-2 sentences about what is being offered to this candidate and why) under the heading for this position in " 💌 Compensation decisions"
   • Update the "🥧 Equity plan" to reflect the offer offer that is about to be sent:
     • Salary (OTE actually offered)
     • Equity (stock options actually offered)
     • "Notes" (include base salary versus commission or bonus plan, if relevant)
     • "Offer sent?" (set this to TRUE)
     • …and make sure the other status columns are set to todo.
3. Prepare the "exit scenarios" spreadsheet: Copy the "Exit scenarios (template)" for the candidate, and rename the copy to e.g. "Exit scenarios for Jane Doe".
   • Edit the candidate's copy of the exit scenarios spreadsheet to include the number of shares they will be offered, and the spreadsheet will update automatically to reflect their approximate ownership percentage.
   • Share the candidate's copy of the spreadsheet with their personal email, granting "Edit" access.

     Note: Don't play with numbers in the exit scenarios spreadsheet. The revision history is visible to the candidate, and they might misunderstand.

4. Prepare offer email: Copy "Offer email (template)" and rename to e.g. "Offer email for Jane Doe". Edit the candidate's copy of the offer email template doc and fill in the missing information:
   • Benefits: If candidate will work outside the US, change the "Benefits" bullet to reflect what will be included through Fleet's international payroll provider, depending on the candidate's location.
   • Equity: Specify the number of shares, then highlight the number of shares with a link to the candidate's personalized copy of the "Exit scenarios" spreadsheet.
   • Other information: Read the offer email very carefully and double-check correctness versus the equity plan, especially in regards to salary, equity, and start date.
5. Send offer: Once both documents are complete, send the offer email:
   • To: The candidate's personal email address (use the email from the CEO interview calendar event)
   • Cc: Zach Wasserman is included as a recipient, but will not participate in the email thread until after the offer is accepted.
   • Subject: "Full time?"
   • Body: (The offer email is copied verbatim from Google Drive into Gmail as the body of the message, formatting and all.)

Steps after an offer is accepted

Once the new team member replies and accepts their offer in writing, either the CEO or Zach Wasserman replies to the candidate. Whoever replies first is responsible for these steps:

1. Verify, track, and reply: Reply to the candidate:
   • Verify the candidate replied with their physical address… or else keep asking. If they did not reply with their physical address, or it's not a usable address, then we are not done. Fleet will reply and ask for it, and no offer should is "accepted" until we've received a physical address.
   • Review and update the team database so that the new team member's row in "🥧 Equity plan" now includes:
     • Physical address (The full street address of the location where work will typically be performed.)
     • Personal email (Use the personal email they're replying from, e.g. @gmail.com)
     • "Offer accepted?" (Set this to TRUE)
     • OTE (salary, expressed as anticipated "on-target" earnings)
     • Equity (stock options)
     • "Notes" (Track base salary here, as well as a very short explanation of commission or bonus structure.)
     • Be sure everything is accurate, one last time!
   • Create a "Hiring" issue for the new team member. (This is what will inform the Business Operations team to get involved. The company will use this issue to keep track of the hiring tasks for the new team member.)
   • Send a reply welcoming the team member to Fleet and letting them know to expect a separate email with next steps for getting the team member's laptop, Yubikeys, and agreement going ASAP so they can start on time. For example:

     \o/  It's official!
     
     Be on the lookout for an email in a separate thread with next steps for quickly signing the paperwork and getting your company laptop and hardware 2FA keys (Yubikeys), which we recommend setting up ASAP.
     
     Thanks, and welcome to the team!
     
     -Mike
     

2. Ask hiring manager to send rejections: Post to the hiring-xxxxx-yyyy Slack channel to let folks know the offer was accepted, and at-mention the hiring manager to ask them to communicate with all other interviewees who are still in the running and let them know that we chose a different person.

   Note: Send rejection emails quickly, within 1 business day. It only gets harder if you wait.

3. Close Slack channel: Then archive and close the channel.

Now what happens? Business Operations will then follow the steps in the "Hiring" issue, which includes reaching out to the new team member within 1 business day from a separate email thread to get additional information as needed, prepare their agreement, add them to the company's payroll system, and get their new laptop and hardware security keys ordered so that everything is ready for them to start on their first day.

Purchasing a company-issued device

Fleet provides laptops for core team members to use while working at Fleet. As soon as an offer is accepted, Nathan Holliday will reach out to the new team member to start this process, and will work with the new team member to get their laptop purchased and shipped to them on time.

Selecting a laptop

Most of the team at Fleet uses 16" MacBook Pros, but team members are free to choose any laptop or operating system that works for them, as long as the price is within reason and supported by our device management solution. (Good news: Since Fleet uses Fleet for device management, every operating system is supported!)

When selecting a new laptop for a team member, optimize their configuration to:

1. have a reasonably large hard drive (at least 512GB hard drive, and if there's any concern go biger)
2. BUT make sure it's still available for delivery or pickup as quickly as possible, and prior to the start date

Play around with build until it ships as quickly as possible. Sometimes small changes lead to much faster ship times. More standard configurations (with fewer customizations) usually ship more quickly. Sometimes MacBook Pros ship more quickly than MacBook Airs, and vice versa. This varies. Remember: Always play around with the build and optimize for something that will ship quickly!

For example, someone in sales, marketing, or business operations might like to use a 14" Macbook Air, whereas someone in engineering, product, or a primarily design role might use a 16" MacBook Pro. Default to a 16" MacBook Pro.

Windows and Linux devices are available upon request for team members in product and engineering. (See Buying other new equipment.)

Buying other new equipment

At Fleet, we spend company money like it's our own money. If you need equipment above and beyond those standard guidelines, you can request new equipment by creating a GitHub issue in fleetdm/fleet and attaching the #g-business-operations. Please include a link to the requested equipment (including any specs), reason for request, and timeline for when the device is needed.

Tracking equipment

When a device has been purchased, it's added to the spreadsheet of company equipment where we keep track of devices and equipment, purchased by Fleet.

When you receive your new their computer, complete the entry by adding a description, model, and serial number to the spreadsheet.

Equity grants

Equity grants for new hires are queued up as part of the hiring process, then grants and consents are batched and processed quarterly.

Doing an equity grant involves:

1. executing a board consent
2. the recipient and CEO signing paperwork about the stock options
3. updating the number of shares for the recipient in the equity plan
4. updating Carta to reflect the grant

For the status of stock option grants, exercises, and all other common stock including advisor, founder, and team member equity ownership, see Fleet's equity plan. For information about investor ownership, see Carta.

Fleet's equity plan is the source of truth, not Carta. Neither are pro formas sent in an email attachment, even if they come from lawyers.

Anyone can make mistakes, and none of us are perfect. Even when we triple check. Small mistakes in share counts can be hard to attribute, and can cause headaches and eat up nights of our CEO's and operations team's time. If you notice what might be a discrepancy between the equity plan and any other secondary source of information, please speak up and let Fleet's CEO know ASAP. Even if you're wrong, your note will be appreciated.

Recurring expenses

Recurring monthly or annual expenses are tracked as recurring, non-personnel expenses in "🧮 The Numbers" (classified Google Sheet), along with their payment source.

Use this spreadsheet as the source of truth. Always make changes to it first before adding or removing a recurring expense. Only track significant expenses. (Other things besides amount can make a payment significant; like it being an individualized expense, for example.)

Individualized expenses

Recurring expenses related to a particular team member, such as coworking fees, are called individualized expenses. These expenses are still considered non-personnel expenses, with a few extra considerations:

• Non-recurring (one-off) expenses such as an Uber ride from the airport are NOT considered "individualized".
• Seat licenses for tools like Salesforce or GitHub are NOT considered "individualized".
• Individualized expenses should include the team member's name explicitly in the name of the expense.
• If multiple team members use the same vendor for an individualized expense (for example, "WeWork"), use a separate row for each individualized expense. (For example: "Coworking, Mungojerry (WeWork)" and "Coworking, Jennyanydots (WeWork)")
• Individualized expenses are always attributed to the "🔦 Business operations" department.
• These expenses are still considered non-personnel expenses, in the same way seat licenses for tools like Salesforce or GitHub are considered non-personnel expenses.

Celebrations

Weekly updates

We like to open about milestones and announcements.

• Every Thursday night, department heads report their KPIs for the week
• Friday nights, Mike McNeil will post a short update in #general. Weekly update principles
• Each department's update is 20-40 words or less.
• Erring on the side of referring to items that are completely done and/or mentioning news that is potentially very exciting to folks throughout the company.

Workiversaries

We're happy you've ventured a trip around the sun with Fleet. Let's celebrate!

• Each Friday, if there are any upcoming workiversaries in the next seven days, Mike McNeil posts about them in #help-classified and tags @mikermcneil to let them know.
• Founders discuss during their 1:1, reviewing performance and the latest compensation benchmarks for this person's role and geography.
• If a compensation change is decided, Mike or Zach posts to Slack in #help-classified with the change to compensation and effective date, if any.
• CEO updates the respective payroll platform (Gusto or Pilot) and equity spreadsheet (internal doc).
• If an additional equity grant is part of this compensation change, the previous equity and new situation is noted in detail in the "Notes" column of the equity plan, and the "Grant started?" column is set back to "todo" to add it to the queue for the next time grants are processed (quarterly).

Tracking hours

Fleet asks US-based hourly contributors to track hours in Gusto, and contributors outside the US to track hours via Pilot.co.

This applies to anyone who gets paid by the hour, including consultants and hourly core team members of any employment classification, inside or outside of the US.

Note: If a contributor uses their own time tracking process or tools, then it is OK to track the extra time spent tracking! Contributors at Fleet are evaluated based on their results, not the number of hours they work.

Informing managers about hours worked

Every Friday at 1:00pm CT, we gather hours worked for anyone who gets paid hourly by Fleet. This includes core team members and consultants, regardless of employment classification, and regardless whether inside or outside of the United States.

• For every hourly core team member in Gusto or Pilot.co, look up their manager (who they report to).
• Consultants don't have a formal reporting structure or manager. Instead, send their hours worked to the CEO, no matter who the consultant is.
• Send each manager a direct message in Slack by copying and pasting the following template:

Here are the hours worked by your direct reports since last Saturday at midnight (YYYY-MM-DD):

• 🧑‍🚀 Alice Bobberson: 21.25
• 🧑‍🚀 Charles David: 3.5

And here are the hours worked by consultants:

• 💁 Bombalurina: 0
• 💁 Jennyanydots: 0
• 💁 Skimbleshanks: 19
• 💁 Grizabella: 0

More info: https://fleetdm.com/handbook/business-operations#informing-managers-about-hours-worked

Departures

Communicating departures

Although it's sad to see you go, Fleet understands that not everything is meant to be forever like open-source is. There are a few steps that we'll need to take to communicate to the team of your departure.

1. Direct team: The CEO will reach out to the departing teammember's direct reports in 1:1 calls.
2. Key stakeholders: The CEO will reach out to his direct reports about the departing teammember's departure.
3. Announcement: Mike McNeil will make an announcement during the "🌈 Weekly Update" post on Friday in the #general channel on Slack.

Adding an advisor

Advisor agreements are sent through DocuSign, using the "Advisor Agreement" template.

• Send the advisor agreement. To send a new advisor agreement, you'll need the new advisor's name and the number of shares they are offered.
• Once you send the agreement, locate an existing empty row and available ID in "Advisors" and enter the new advisor's information.

  Note: Be sure to mark any columns that haven't been completed yet as "TODO"

Finalizing a new advisor

• Update the "Advisors" to show that the agreement has been signed, and ask the new advisor to add us on LinkedIn, Crunchbase, and Angellist.
• Update "Equity plan" to reflect updated status and equity grant for this advisor, and to ensure the advisor's equity is queued up for the next quarterly equity grant ritual.

Security

Security policies are best when they're alive, in context in how an organization operates. Fleeties carry Yubikeys, and change control of policies and access control is driven primarily through GitOps and SSO.

Here are a few different entry points for a tour of Fleet's security policies and best practices:

1. Security policies
2. Human resources security policy
3. Account recovery process
4. Personal mobile devices
5. Hardware security keys
6. More details about internal security processes at Fleet are located on the Security page.

Finance

Monthly accounting

Create a new montly accounting issue for the current month and year named "Closing out YYYY-MM" in GitHub and complete all of the tasks in the issue. (This uses the monthly accounting issue template.

When is the issue created?

We create and close the monthly accounting issue for the previous month within the first 7 days of the following month. For example, the monthly accounting issue to close out the month of January is created promptly in February and closed before the end of the day, Feb 7th.

A convenient trick is to create the issue on the first Friday of the month and close it ASAP.

SLA

The monthly accounting issue should be completed and closed before the 7th of the month.

The close date is tracked each month in KPIs.

Payroll

Many of these processes are automated, but it's vital to check Gusto and Pilot manually for accuracy.

• Salaried fleeties are automated in Gusto and Pilot
• Hourly fleeties and consultants are a manual process in Gusto and Pilot.

Unique payrolls	Action	DRI
Commissions and ramp	"Off-cycle" payroll	Nathan
Sign-on bonus	"Bonus" payroll	Mike McNeil
Performance bonus	"Bonus" payroll	Mike McNeil
Accelerations (quarterly)	"Off-cycle" payroll	Nathan

Add the amount to be paid to the "Gross" line. For Fleet's US contractors, running payroll is a manual process. The steps for doing this are highlighted in this loom, TODO.

1. Time tools
2. Time tracking
3. Review hours
4. Adjust time frame to match current payroll period (the 27th through 26th of the month)
5. Sync hours
6. Run contractor payroll

Commission payroll

TODO: bit more process here. Maybe revops is DRI of commission calculator, creates "2023-03 commission payroll", transfered to Nathan when it's time to run? SLA == payroll run by the 7th, with commission sheet 100% accurate.

• Update commission calculator with new revenue from any deals that are closed/won (have a subscription agreement signed by both parties) and have an effective start date within the previous month.
  • Find detailed notes on this process in Notes - Run commission payroll in Gusto.
• Contact Mike McNeil in Slack and let her know he can run the commission payroll. Use the off-cycle payroll option in Gusto. Be sure to classify the payment as "Commission" in the "other earnings" field and not the generic "Bonus."
• Once commission payroll has been run, update the commission calculator to mark the commission as paid.

Updating a consultant's fee

• Direct message Mike McNeil with hourly rate change information.
• After CEO approval, Mike McNeil will issue a new contractor agreement with the updated fee via DocuSign.

Annual reporting for capital credit line

• Within 60 days of the end of the year:
  • Provide Silicon Valley Bank (SVB) with our balance sheet and profit and loss statement (P&L, sometimes called a cashflow statement) for the past twelve months.
  • Provide SVB with our annual operating budgets and projections (on a quarterly basis) for the coming year.
  • Deliver this as early as possible in case they have questions.

Quarterly Quickbooks Online (QBO) check

• Check to make sure bookkeeping quirks are all accounted for and resolved or in progress toward resolution.
• Check balance sheet and profit and loss statements (P&Ls) in QBO against the monthly workbooks in Google Drive.

Taxes and compliance

From time to time, you may get notices in the mail from the IRS and/or state agencies regarding your company’s withholding and/or unemployment tax accounts. You can resolve many of these notices on your own by verifying and/or updating the settings in your Gusto account. If the notice is regarding an upcoming change to your deposit schedule or unemployment tax rate, Mike McNeil will make the change in Gusto. Including:

• Update your unemployment tax rate.
• Update your federal deposit schedule.
• Update your state deposit schedule. Important Agencies do not send notices to Gusto directly, so it’s important that you read and take action before any listed deadlines or effective dates of requested changes. Notices you should report to Gusto. If you can't resolve the notice on your own, are unsure what the notice is in reference to, or the tax notice has a missing payment or balance owed, follow the steps in the Report and upload a tax notice in Gusto. In Gusto, click How to review your notice to help you understand what kind of notice you received and what additional action you can take to help speed up the time it takes to resolve the issue. For more information about how Fleet and our accounting team work together, check out Fleet - who does what (private doc).

State quarterly payroll and tax filings

Every quarter, payroll and tax filings are due for each state. Gusto can handle these automatically if Third-party authorization (TPA) is enabled. Each state is unique and Gusto has a library of State registration and resources available to review. You will need to grant Third-party authorization (TPA) per state and this should be checked quarterly before the filing due dates to ensure that Gusto can file on time.

CorpNet state registration process

In CorpNet, select "place an order for an existing business" we’ll need to have Foreign Registration and Payroll Tax Registration done.

• You can have CorpNet do this by emailing the account rep "Subject: Fleet Device Management: State - Foreign Registration and Payroll Tax Registration" (this takes about two weeks).
• You can do this between you and CorpNet by selecting "Foreign Qualification," placing the order and emailing the confirmation to the rep for Payroll registration (this is a short turnaround).
• You can do this on your own by visiting the state's "Secretary of State" website and checking that the company name is available. To register online, you'll need the EIN, business address, information about the owners and their percentages, the first date of business, sales within the state, and the business type (usually get an email right away for approval ~24-48 hrs). For more information, check out Fleet - who does what.

Rituals

The following table lists this group's rituals, frequency, and Directly Responsible Individual (DRI).

Ritual	Frequency	Description	DRI
Weekly update reminder	Weekly	Early Friday mornings (US time), a Slack bot posts in the #g-e channel reminding directly responsible individuals for KPIs to add their metrics for the current week in "KPIs" before the end of the day.	N/A
Weekly update	Weekly	On Friday, Mike McNeil updates the KPIs in the "🌈 Weekly updates" spreadsheet and posts a single message recognizing each of the week's on-duty people for each of the on-call rotations, along with any hiring and departure announcements. Mike McNeil posts the company update in the #general channel.	Mike McNeil
AP invoice monitoring	Daily	Look for new accounts payable invoices and make sure that Fleet's suppliers are paid.	Nathanael Holliday
Hours update	Weekly	Screenshots of contractor hours as shown in Gusto are sent via Slack to each contractor's manager with no further action necessary if everything appears normal.	Mike McNeil
Prepare Mike and Sid's 1:1 doc	Bi-weekly	Run through the document preparation GitHub issue for Mike's call with Sid.	Nathanael Holliday
Brex reconciliation	Monthly	Make sure all company-issued credit card transactions include memos.	Nathanael Holliday
Monthly accounting	Monthly	Use the monthly accounting template in GitHub to go through the process of validating Fleet's books.	Nathanael Holliday
Commission payroll	Monthly	Use the commission calculator to determine the commission payroll to be run in Gusto.	Nathanael Holliday
US contractor payroll	Monthly	Sync contractor hours to payments in Gusto and run payroll for the month.	Mike McNeil
550C update	Annually	File California 550C.	Mike McNeil
Workiversaries	Weekly/PRN	Mike McNeil posts in #g-people and tags @mikermcneil about any upcoming workiversaries.	Mike McNeil
Investor and Advisor updates	PRN	Mike McNeil tracks the last contact with investors and coordinates outreach with CEO.	Mike McNeil
CEO inbox sweep	Daily unless OOO	Mike McNeil does a morning sweep of the CEO's inbox to remove spam and grab action items.	Mike McNeil
Recruiting progress checkup	Weekly	Mike McNeil looks in the Fleeties spreadsheet and reports on each open position.	Mike McNeil
Payroll	Monthly before payroll runs	Every month, Mike McNeil audits the payroll platforms for accuracy.	Mike McNeil
Calendar audit	Daily	Daily Mike McNeil audits CEOs calendar and set notes for meetings.	Mike McNeil
TPA verifications	Quarterly	Every quarter before tax filing due dates, Mike McNeil audits state accounts to ensure TPA is set up or renewed.	Mike McNeil
Revenue report	Weekly	At the start of every week, check the Salesforce reports for past due invoices, non-invoiced opportunities, and past due renewals. Report any findings to Mike Mcneil and Alex Mitchell in the #g-sales channel and follow up with customers as necessary to resolve.	Nathanael Holliday
Capital credit reporting	Annually	Within 60 days of the new year, provide financial statements to SVB.	Nathanael Holliday
QBO check	Quarterly	The first month after the previous quarter has closed, make sure that QBO is accurate compared to Fleet's records.	Nathanael Holliday
Business Ops key review	every three weeks	Every release cycle a key review deck is prepared and presented.	Nathanael Holliday
YubiKey adoption	Monthly	Track YubiKey adoption in Google workspace and follow up with those that aren't using it.	Mike McNeil
MDM device enrollment	Quarterly	Provide export of MDM enrolled devices to the ops team.	Luke Heath
Access revalidation	Quarterly	Review critical access groups to make sure they contain only relevant people.	Mike McNeil
Security policy update	Annually	Update security policies and have them approved by the CEO.	Nathanael Holliday
Security notifications check	Daily	Check Slack, Google, Vanta, and Fleet dogfood for security-related notifications.	Nathanael Holliday
Changeset for onboarding issue template	Quarterly	pull up the changeset in the onboarding issue template and send out a link to the diff to all team members by posting in Slack's #general channel.	Mike McNeil
Informing managers about hours worked	Weekly	See handbook entry.	Nathanael Holliday

Kanban

Any Fleet team member can view the 🔦#g-business-operations kanban board (confidential) for this department, including pending tasks in the active sprint and any new requests.

Intake

To make a request of the business operations department, create an issue using one of our issue templates. If you don't see what you need, or you are unsure, create a custom request issue and someone in business operations will reply within 1 business day.

If you're not sure that your request can wait that long, then please ask for urgent help in our group Slack channel: #g-business-operations. Only use this approach or at-mention contributors in business operations directly in urgent situations. Otherwise, create an issue.

Slack channels

These groups maintain the following Slack channels:

Slack channel	DRI
#g-business-operations	Nathan Holliday
#help-onboarding	Mike McNeil
#help-login	Nathan Holliday
#help-manage	Mike McNeil
#help-brex	Nathan Holliday
#help-ceo	Mike McNeil
#help-mission-control (¶¶)	Mike McNeil
#help-classified (¶¶)	Mike McNeil
#help-open-core-ventures (¶¶)	Mike McNeil

Stubs

The following stubs are included only to make links backward compatible.

Open positions

Please see handbook/company#open-positions for a list of open job postings at Fleet.