Signature process for agreements where customer kicks off the signature request (#10085)

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
  - For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).

handbook/customers/README.md

@@ -286,6 +286,13 @@ To quickly get help doing a legal review of a prospect subscription agreement, w
 2. Select "Contract signature or legal review"
 3. Follow the instructions in the "Submitting this request" section
 
+If the prospect/customer/partner is originating the request for signature:
+1. Communicate that the Fleet signatory is Mike McNeil, CEO and share his email
+2. Mike will create the github issue mentioned above when he gets request
+3. Mike will forward to business operations for review
+4. Business operations will notify Mike and internal requestor when ready for signature
+5. Mike will sign and close the issue
+
 ## Customer DRI change
 Sometimes there is a change in the champion within the customer's organization.
 1. Get an introduction to the new DRIs including names, roles, contact information.