-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
cc050cd
commit 26f8bbd
Showing
3 changed files
with
12 additions
and
17 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
## Closing a deal | ||
|
||
Follow the steps below to ensure every new customer is setup for success and quickly as possible following a sale. | ||
|
||
### Steps | ||
|
||
1. Once the order form is signed by the customer, you should move the deal to Closed Won in HubSpot. You do not need to wait for countersignature. | ||
1. Once all parties have signed, download the completed Order Form and Subscritpion Agreement, and upload them to the Legal folder in Google Drive. | ||
1. If the license is self hosted, ask the CEO to generate the key, then include in the onboarding email. | ||
1. If it is a cloud deal, any discounts need to be setup by the CEO in Stripe. Let the CEO know which email to send the invoice to once configured. | ||
1. Send the onboarding email with an introduction to their CSM, and the license key (if self-hosted). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters