How we reach companies that can benefit from FlowFuse.
-| [Customer Success](/handbook/customer/customer-success/)Happy customers is what makes FlowFuse a sustainable business.
+| [Marketing](/handbook/marketing/)How we reach companies that can benefit from FlowFuse.
+| [Customer Success](/handbook/sales/customer-success/)Happy customers is what makes FlowFuse a sustainable business.
| | ### About the Handbook diff --git a/src/handbook/customer/marketing/blog.md b/src/handbook/marketing/blog.md similarity index 93% rename from src/handbook/customer/marketing/blog.md rename to src/handbook/marketing/blog.md index c85b126907..c1da795d95 100644 --- a/src/handbook/customer/marketing/blog.md +++ b/src/handbook/marketing/blog.md @@ -7,10 +7,10 @@ meta: ## Blogging Process -Content creation and blogging are effective ways to communicate with our community and are tied to our SEO performance and our [Social Media Strategy](/handbook/customer/marketing/social-media/#strategy-for-increasing-reach). The process for publishing a blog is as follows: +Content creation and blogging are effective ways to communicate with our community and are tied to our SEO performance and our [Social Media Strategy](/handbook/marketing/social-media/#strategy-for-increasing-reach). The process for publishing a blog is as follows: 1. Create an initial issue or tie your blog to one of your scheduled issues [here](https://github.com/orgs/FlowFuse/projects/21/views/1). -2. Issues should be assigned a date, which should be posted here in this [Github projects](https://github.com/orgs/FlowFuse/projects/21/views/1). The target date for review should be at least three working days before the planned posting date on social media. Check the [social media planning and posting section](/handbook/customer/marketing/social-media/#planning-and-posting). +2. Issues should be assigned a date, which should be posted here in this [Github projects](https://github.com/orgs/FlowFuse/projects/21/views/1). The target date for review should be at least three working days before the planned posting date on social media. Check the [social media planning and posting section](/handbook/marketing/social-media/#planning-and-posting). 3. Create a PR requests with your Blog Content. 4. Assign yourself as an Assignee. 5. Convert to Draft @@ -21,7 +21,7 @@ Content creation and blogging are effective ways to communicate with our communi 8. Content will be reviewed first. 9. SEO will be reviewed second. 10. When both reviews are done, the Author or SEO reviewer can merge. In the event of an external author, SEO/content review will merge. -11. Once merged, SEO Reviewer will promote on FlowFuse Social channels. Check the [social media planning and posting section](/handbook/customer/marketing/social-media/#planning-and-posting) for guidance and considerations. +11. Once merged, SEO Reviewer will promote on FlowFuse Social channels. Check the [social media planning and posting section](/handbook/marketing/social-media/#planning-and-posting) for guidance and considerations. ## Blog CMS @@ -96,7 +96,7 @@ You can also add your own custom tags. While these won't create a new page with #### Meta Keywords -Additionally, the tags you assign to your content will also be used as [meta keywords](/handbook/customer/marketing/website/#meta-keywords) for each article, alongside the [default keywords](/handbook/customer/marketing/website#default-keywords). +Additionally, the tags you assign to your content will also be used as [meta keywords](/handbook/marketing/website/#meta-keywords) for each article, alongside the [default keywords](/handbook/marketing/website#default-keywords). ### Adding Images diff --git a/src/handbook/customer/marketing/brand-voice.md b/src/handbook/marketing/brand-voice.md similarity index 96% rename from src/handbook/customer/marketing/brand-voice.md rename to src/handbook/marketing/brand-voice.md index 21c37fb2a2..a92a547788 100644 --- a/src/handbook/customer/marketing/brand-voice.md +++ b/src/handbook/marketing/brand-voice.md @@ -116,7 +116,7 @@ Tone should be: **Example:** > Hey, good question! I’ve seen a similar issue when deploying on Docker — it might be worth checking your volume permissions. Let me know if that helps or if you want to try another approach. -For broader principles on interacting with the community as a FlowFuse team member, see our [Community Guidelines](/handbook/customer/marketing/community/community-guidelines.md). +For broader principles on interacting with the community as a FlowFuse team member, see our [Community Guidelines](/handbook/marketing/community/community-guidelines.md). ### Commenting on third-party content (e.g. posts by others) diff --git a/src/handbook/customer/marketing/community/community-guidelines.md b/src/handbook/marketing/community/community-guidelines.md similarity index 100% rename from src/handbook/customer/marketing/community/community-guidelines.md rename to src/handbook/marketing/community/community-guidelines.md diff --git a/src/handbook/customer/marketing/community/event-and-webinars.md b/src/handbook/marketing/community/event-and-webinars.md similarity index 100% rename from src/handbook/customer/marketing/community/event-and-webinars.md rename to src/handbook/marketing/community/event-and-webinars.md diff --git a/src/handbook/customer/marketing/community/forums-and-support.md b/src/handbook/marketing/community/forums-and-support.md similarity index 100% rename from src/handbook/customer/marketing/community/forums-and-support.md rename to src/handbook/marketing/community/forums-and-support.md diff --git a/src/handbook/customer/marketing/community/index.md b/src/handbook/marketing/community/index.md similarity index 100% rename from src/handbook/customer/marketing/community/index.md rename to src/handbook/marketing/community/index.md diff --git a/src/handbook/customer/marketing/customer-stories.md b/src/handbook/marketing/customer-stories.md similarity index 100% rename from src/handbook/customer/marketing/customer-stories.md rename to src/handbook/marketing/customer-stories.md diff --git a/src/handbook/customer/flowfuseforeducation.md b/src/handbook/marketing/education.md similarity index 100% rename from src/handbook/customer/flowfuseforeducation.md rename to src/handbook/marketing/education.md diff --git a/src/handbook/customer/marketing/email.md b/src/handbook/marketing/email.md similarity index 100% rename from src/handbook/customer/marketing/email.md rename to src/handbook/marketing/email.md diff --git a/src/handbook/customer/marketing/how-we-work.md b/src/handbook/marketing/how-we-work.md similarity index 100% rename from src/handbook/customer/marketing/how-we-work.md rename to src/handbook/marketing/how-we-work.md diff --git a/src/handbook/customer/marketing/images/blog-article.png b/src/handbook/marketing/images/blog-article.png similarity index 100% rename from src/handbook/customer/marketing/images/blog-article.png rename to src/handbook/marketing/images/blog-article.png diff --git a/src/handbook/customer/marketing/images/blog-index.png b/src/handbook/marketing/images/blog-index.png similarity index 100% rename from src/handbook/customer/marketing/images/blog-index.png rename to src/handbook/marketing/images/blog-index.png diff --git a/src/handbook/customer/marketing/images/story-index.png b/src/handbook/marketing/images/story-index.png similarity index 100% rename from src/handbook/customer/marketing/images/story-index.png rename to src/handbook/marketing/images/story-index.png diff --git a/src/handbook/customer/marketing/images/story-page.png b/src/handbook/marketing/images/story-page.png similarity index 100% rename from src/handbook/customer/marketing/images/story-page.png rename to src/handbook/marketing/images/story-page.png diff --git a/src/handbook/customer/marketing/images/video-framing.png b/src/handbook/marketing/images/video-framing.png similarity index 100% rename from src/handbook/customer/marketing/images/video-framing.png rename to src/handbook/marketing/images/video-framing.png diff --git a/src/handbook/customer/marketing/index.md b/src/handbook/marketing/index.md similarity index 64% rename from src/handbook/customer/marketing/index.md rename to src/handbook/marketing/index.md index 66b269807c..a2c3788f35 100644 --- a/src/handbook/customer/marketing/index.md +++ b/src/handbook/marketing/index.md @@ -1,33 +1,42 @@ --- navTitle: Marketing -navGroup: Customer Department +navGroup: Marketing department --- -# Marketing +# Marketing department -## What we all do +## What we do We're the team that promotes our company and product of FlowFuse to the core audience of FlowFuse. This includes: 1. Generating brand awareness. 1. Publishing high-quality content such as blog posts, video, and infographics. 1. Engaging with the Node-RED and nascent FlowFuse communities -1. Event planning, such as [trade shows](/handbook/customer/marketing/tradeshow/) +1. Event planning, such as [trade shows](/handbook/marketing/tradeshow/) 1. Growth hacking; always be innovating when finding the audience and engaging with them in a cost effective way. The ultimate goal for the department is to generate sales pipeline for the sales team or sign ups for [FlowFuse Cloud](https://app.flowfuse.com). +## Team + +| Role | Contributors | +|------|--------------| +| GTM | [Michael](https://www.linkedin.com/in/michaelbdavis/) [@MichaelBDavis](https://github.com/MichaelBDavis) | +| Marketing Manager, Website & Social Media | [Yndira](https://www.linkedin.com/in/yndira-escobar-es/) [@Yndira-E](https://github.com/Yndira-E) | +| Technical Writer | [Sumit](https://in.linkedin.com/in/shindesumit84) [@sumitshinde-88](https://github.com/sumitshinde-84) | + ## Contact us -Questions can be asked in the [#dept-customer](https://flowforgeworkspace.slack.com/archives/C05GYH95NJZ). +Questions can be asked in the [#dept-marketing](https://flowforgeworkspace.slack.com/archives/C05GYH95NJZ). + +## Further Reading | | | |:----|:----| | [Blog](./blog.md) | How to write new content for the FlowFuse Blog | | [Social Media](./social-media.md) | Our online presence and how we engage with our community on various platforms | -| [Hubspot](/handbook/customer/hubspot/) | How we use our CRM | | [Trade shows](./tradeshow.md) | How to get the most out of visiting a trade fair | | [Videos](./videos.md) | To produce quality content in video, follow these guidelines | | [Website](./website.md) | How to contribute to the FlowFuse marketing website | diff --git a/src/handbook/customer/marketing/leads.md b/src/handbook/marketing/leads.md similarity index 100% rename from src/handbook/customer/marketing/leads.md rename to src/handbook/marketing/leads.md diff --git a/src/handbook/customer/marketing/messaging.md b/src/handbook/marketing/messaging.md similarity index 98% rename from src/handbook/customer/marketing/messaging.md rename to src/handbook/marketing/messaging.md index 2b94b7b221..c567b42810 100644 --- a/src/handbook/customer/marketing/messaging.md +++ b/src/handbook/marketing/messaging.md @@ -16,7 +16,7 @@ consistent the company can learn faster and have a structured approach to these iterations. For guidance on how to express our brand in writing and communication style, see -[Brand Personality, Tone of Voice & Character](/handbook/customer/marketing/brand-voice/) +[Brand Personality, Tone of Voice & Character](/handbook/marketing/brand-voice/) Please also read the [Company Mission](/handbook/company/strategy/#flowfuse%27s-mission) before diff --git a/src/handbook/customer/marketing/social-media.md b/src/handbook/marketing/social-media.md similarity index 94% rename from src/handbook/customer/marketing/social-media.md rename to src/handbook/marketing/social-media.md index 9e3f768816..8633fc832b 100644 --- a/src/handbook/customer/marketing/social-media.md +++ b/src/handbook/marketing/social-media.md @@ -81,7 +81,7 @@ Each content type has channels which are appropriate, this table sets out which - Descriptive text: - Align with post purpose and audience goals. - - Must reflect our [Brand Voice](/handbook/customer/marketing/brand-voice/). + - Must reflect our [Brand Voice](/handbook/marketing/brand-voice/). - Think about relevance to the audience. - Emoji - Only one CTA @@ -94,8 +94,8 @@ Each content type has channels which are appropriate, this table sets out which For Reddit, Node-RED Slack, and Node-RED Discourse: -- Follow the tone and behaviour defined in our [Community Guidelines](/handbook/customer/marketing/community/community-guidelines/). -- Use your own voice, you're talking from a personal account after all, but also remember that you represent the brand and company values. Blend your tone with our [Brand Voice](/handbook/customer/marketing/brand-voice/#participating-in-community-spaces-(e.g.-node-red-forum%2C-github%2C-discord)). +- Follow the tone and behaviour defined in our [Community Guidelines](/handbook/marketing/community/community-guidelines/). +- Use your own voice, you're talking from a personal account after all, but also remember that you represent the brand and company values. Blend your tone with our [Brand Voice](/handbook/marketing/brand-voice/#participating-in-community-spaces-(e.g.-node-red-forum%2C-github%2C-discord)). - Copy should remain informal, honest, and useful — without sounding like a sales pitch. Keep it factual. Keep it human. diff --git a/src/handbook/customer/marketing/tradeshow.md b/src/handbook/marketing/tradeshow.md similarity index 99% rename from src/handbook/customer/marketing/tradeshow.md rename to src/handbook/marketing/tradeshow.md index c167e583d3..b14e9b58de 100644 --- a/src/handbook/customer/marketing/tradeshow.md +++ b/src/handbook/marketing/tradeshow.md @@ -86,7 +86,7 @@ Alongside sales and the CTO, define the booth messaging considering the demo and #### Two months before the event -Choose the giveaways that align better with the messaging, audience, storage space, budget and that might be useful on a day to day basis. Remember to consider the weight when deciding the amount of items, specially if a team member will be bringing those items as part of their luggage. Check the [logistics](/handbook/customer/marketing/tradeshow/#logistics) section to decide when to order the items. +Choose the giveaways that align better with the messaging, audience, storage space, budget and that might be useful on a day to day basis. Remember to consider the weight when deciding the amount of items, specially if a team member will be bringing those items as part of their luggage. Check the [logistics](/handbook/marketing/tradeshow/#logistics) section to decide when to order the items. The on-site team should have some branded attire and business cards, don't forget to include those in the artwork requests and the orders alonside the giveaways. @@ -173,4 +173,4 @@ Your phone is kept in your pocket at all times. Go through the business cards you collected and reach out to _each and everyone_ of them. Thank them for the conversation and ask if there's any questions -outstanding you can help them with. Consider adding these contacts to [HubSpot](/handbook/customer/hubspot/). +outstanding you can help them with. Consider adding these contacts to [HubSpot](/handbook/sales/hubspot/). diff --git a/src/handbook/customer/marketing/videos.md b/src/handbook/marketing/videos.md similarity index 100% rename from src/handbook/customer/marketing/videos.md rename to src/handbook/marketing/videos.md diff --git a/src/handbook/customer/marketing/webinars.md b/src/handbook/marketing/webinars.md similarity index 100% rename from src/handbook/customer/marketing/webinars.md rename to src/handbook/marketing/webinars.md diff --git a/src/handbook/customer/marketing/website.md b/src/handbook/marketing/website.md similarity index 95% rename from src/handbook/customer/marketing/website.md rename to src/handbook/marketing/website.md index 318d37fa91..bbd000f7fb 100644 --- a/src/handbook/customer/marketing/website.md +++ b/src/handbook/marketing/website.md @@ -81,7 +81,7 @@ When adding meta keywords to the website pages, a specific priority order is fol 2. **Keywords:** If no `meta.keywords` are found, the `keywords` specified in the front matter of the webpage are used. -3. [**Tags:**](/handbook/customer/marketing/blog/#tags) If neither `meta.keywords` nor `keywords` are assigned, the `tags` assigned to the content are included as meta keywords. These tags are used to categorize the content and provide relevant context. +3. [**Tags:**](/handbook/marketing/blog/#tags) If neither `meta.keywords` nor `keywords` are assigned, the `tags` assigned to the content are included as meta keywords. These tags are used to categorize the content and provide relevant context. 4. **Default Keywords:** These are always included and provide general information about the website's content. They can be appended to the keywords obtained from previous points, or, if neither of the previous conditions are met, the default keywords are used as a fallback option. diff --git a/src/handbook/operations/commission-payment.md b/src/handbook/operations/commission-payment.md index 7d1233b31c..91fe06f71f 100644 --- a/src/handbook/operations/commission-payment.md +++ b/src/handbook/operations/commission-payment.md @@ -17,7 +17,7 @@ next steps to process the commission calculations and setup for payment. Note: all sales commissions are advances under the assumption customers pay the invoice. FlowFuse might withhold commission payments or claw back payments if -payments aren't made within 60 days after the [deal was closed](https://flowfuse.com/handbook/customer/sales/engagements/#closing-a-deal). +payments aren't made within 60 days after the [deal was closed](https://flowfuse.com/handbook/sales/engagements/#closing-a-deal). ### Calculating Team Commissions diff --git a/src/handbook/customer/customer-success.md b/src/handbook/sales/customer-success.md similarity index 99% rename from src/handbook/customer/customer-success.md rename to src/handbook/sales/customer-success.md index 72eb33405e..76bd3c053c 100644 --- a/src/handbook/customer/customer-success.md +++ b/src/handbook/sales/customer-success.md @@ -22,7 +22,7 @@ is before a deal closes and is signed. From the moment an AE commits to a deal onboarding starts for CSM. To understand what their high-level goals are with our product, and what the company as vendor can provide soon to a new customer. The AE will -[close the deal](/handbook/customer/sales/engagements/#closing-a-deal), at which +[close the deal](/handbook/sales/engagements/#closing-a-deal), at which point CSM takes over. Onwards, CSM is responsible for the full customer lifecycle, from establishing diff --git a/src/handbook/customer/sales/dashboard-v2.md b/src/handbook/sales/dashboard-v2.md similarity index 100% rename from src/handbook/customer/sales/dashboard-v2.md rename to src/handbook/sales/dashboard-v2.md diff --git a/src/handbook/customer/sales/engagements.md b/src/handbook/sales/engagements.md similarity index 98% rename from src/handbook/customer/sales/engagements.md rename to src/handbook/sales/engagements.md index 0a5c173322..cb872f4abb 100644 --- a/src/handbook/customer/sales/engagements.md +++ b/src/handbook/sales/engagements.md @@ -34,7 +34,7 @@ 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. 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](/handbook/customer/sales/engagements/#what-to-quote) +4. Add Line Items per [the instructions](/handbook/sales/engagements/#what-to-quote) * Select the appropriate Plan that is being quoted * For each line item, except Professional Services, check the Billing frequence to `Annual` and if the terms **ensure automatic renewal* * Adjust fields for Term and discount/fee/tax as needed. diff --git a/src/handbook/customer/hubspot.md b/src/handbook/sales/hubspot.md similarity index 100% rename from src/handbook/customer/hubspot.md rename to src/handbook/sales/hubspot.md diff --git a/src/handbook/customer/sales/index.md b/src/handbook/sales/index.md similarity index 57% rename from src/handbook/customer/sales/index.md rename to src/handbook/sales/index.md index 113b2bdfbb..5022522dbe 100644 --- a/src/handbook/customer/sales/index.md +++ b/src/handbook/sales/index.md @@ -1,14 +1,14 @@ --- navTitle: Sales -navGroup: Customer department +navGroup: Sales department --- -# Sales +# Sales department ## What we do -The Sales department is responsible for new customer acquisition and existing -customer expansion. This includes: +The Sales department is responsible for new customer acquisition, existing +customer expansion, and customer success. This includes: 1. Prospecting and outreach for new business. 1. Conducting introductory calls to determine use-case and fit. 1. Giving customized product demonstrations to potential customers. @@ -17,7 +17,21 @@ customer expansion. This includes: 1. Working with external procurement teams. 1. Navigating subscription agreement terms. 1. Finalizing contracts and billing details. -1. Introducing new customers to their Customer Success Manager. +1. Customer success management and support. +1. Customer onboarding and training. + +## Team + +| Role | Contributors | +|------|--------------| +| CEO | [ZJ](https://www.linkedin.com/in/zegerjan/) [@ZJvandeWeg](https://github.com/ZJvandeWeg) | +| GTM | [Michael](https://www.linkedin.com/in/michaelbdavis/) [@MichaelBDavis](https://github.com/MichaelBDavis) | +| Sales | [Omar](https://ca.linkedin.com/in/omarazizahmed?trk=public_post_feed-actor-name) [@omarazizahmed](https://github.com/omarazizahmed) | +| CSM | [Esmé](https://nl.linkedin.com/in/esméwieringa) [@Esmewieringa](https://github.com/Esmewieringa) | + +## Contact us + +Questions can be asked in the [#dept-sales](https://flowforgeworkspace.slack.com/archives/C05GYH95NJZ). ## How we work @@ -29,3 +43,4 @@ customer expansion. This includes: - [Customer Licenses (internal)](https://docs.google.com/spreadsheets/d/1wM_o8IWjjkwi-WMRueKfS-lrmkQYzV83xm4BIzZNAO0/edit#gid=0) - [Ideal Customer Profile](https://docs.google.com/document/d/1krMIUJvosw8xUQog_iq_FEvI9R5WEo9ZyWUCdTb9XnQ/edit#heading=h.3rr2wuny55dl) - [Sales Regions](./regions.md) + - [Customer Success](./customer-success.md) diff --git a/src/handbook/customer/sales/legal.md b/src/handbook/sales/legal.md similarity index 98% rename from src/handbook/customer/sales/legal.md rename to src/handbook/sales/legal.md index 457f25b1ad..aa6bf5f5d1 100644 --- a/src/handbook/customer/sales/legal.md +++ b/src/handbook/sales/legal.md @@ -11,7 +11,7 @@ FlowFuse uses Hubspot for generating quotes, and requesting the signatures on th ## Subscription agreement -For self-managed licenses FlowFuse has a standard [subscription agreement template](/handbook/customer/sales/subscription-agreement-1.5/). +For self-managed licenses FlowFuse has a standard [subscription agreement template](/handbook/sales/subscription-agreement-1.5/). When a customer sends over their Standard terms before signing the subscription agreement, we have a [standard response overview](https://docs.google.com/document/d/1US_eixmRtzzFHybl3l9woP0isrwvK2_t7nPXoKYiuq4/edit?tab=t.0#heading=h.w8522tz1d0cr). ## Professional Services agreement diff --git a/src/handbook/customer/sales/meetings/demo.md b/src/handbook/sales/meetings/demo.md similarity index 100% rename from src/handbook/customer/sales/meetings/demo.md rename to src/handbook/sales/meetings/demo.md diff --git a/src/handbook/customer/sales/meetings/discovery.md b/src/handbook/sales/meetings/discovery.md similarity index 100% rename from src/handbook/customer/sales/meetings/discovery.md rename to src/handbook/sales/meetings/discovery.md diff --git a/src/handbook/customer/sales/meetings/index.md b/src/handbook/sales/meetings/index.md similarity index 94% rename from src/handbook/customer/sales/meetings/index.md rename to src/handbook/sales/meetings/index.md index 510169000c..adbc2e22cf 100644 --- a/src/handbook/customer/sales/meetings/index.md +++ b/src/handbook/sales/meetings/index.md @@ -24,12 +24,12 @@ and sync up what the goals are for the meeting. The number of times FlowFuse will meet with a customer depends mostly on the customer. However, in all cases FlowFuse would like to have an initial -[Discovery Call](/handbook/customer/sales/meetings/discovery/). +[Discovery Call](/handbook/sales/meetings/discovery/). -A discovery call is generally followed by a [Demo](/handbook/customer/sales/meetings/demo/). +A discovery call is generally followed by a [Demo](/handbook/sales/meetings/demo/). To validate the solution to the problem the customer is experiencing, FlowFuse will -aid in a [POC](/handbook/customer/sales/meetings/poc/). +aid in a [POC](/handbook/sales/meetings/poc/). ## Using Fathom Notetaker diff --git a/src/handbook/customer/sales/meetings/poc.md b/src/handbook/sales/meetings/poc.md similarity index 95% rename from src/handbook/customer/sales/meetings/poc.md rename to src/handbook/sales/meetings/poc.md index a17b3d08aa..8567efdcc3 100644 --- a/src/handbook/customer/sales/meetings/poc.md +++ b/src/handbook/sales/meetings/poc.md @@ -14,7 +14,7 @@ To extend the trial period, including if a trial has expired already, use the 'E ### Self-hosted trial -If a self-hosted trial is desired, you need to [generate a license key](/handbook/customer/sales/meetings/poc/#generating-a-license) to unlock paid-for features. +If a self-hosted trial is desired, you need to [generate a license key](/handbook/sales/meetings/poc/#generating-a-license) to unlock paid-for features. Every self-hosted POC call should have an engineer present. ### POC Criteria diff --git a/src/handbook/customer/sales/partnerships.md b/src/handbook/sales/partnerships.md similarity index 100% rename from src/handbook/customer/sales/partnerships.md rename to src/handbook/sales/partnerships.md diff --git a/src/handbook/customer/sales/professional-services.md b/src/handbook/sales/professional-services.md similarity index 100% rename from src/handbook/customer/sales/professional-services.md rename to src/handbook/sales/professional-services.md diff --git a/src/handbook/customer/sales/regions.md b/src/handbook/sales/regions.md similarity index 100% rename from src/handbook/customer/sales/regions.md rename to src/handbook/sales/regions.md diff --git a/src/handbook/customer/sales/subscription-agreement-1.4.njk b/src/handbook/sales/subscription-agreement-1.4.njk similarity index 100% rename from src/handbook/customer/sales/subscription-agreement-1.4.njk rename to src/handbook/sales/subscription-agreement-1.4.njk diff --git a/src/handbook/customer/sales/subscription-agreement-1.5.njk b/src/handbook/sales/subscription-agreement-1.5.njk similarity index 100% rename from src/handbook/customer/sales/subscription-agreement-1.5.njk rename to src/handbook/sales/subscription-agreement-1.5.njk