Skip to content

Commit 92ceed0

Browse files
Merge branch 'main' into moc
2 parents 5239084 + 3b24148 commit 92ceed0

3 files changed

Lines changed: 22 additions & 3 deletions

File tree

.github/workflows/calibreapp-image-actions.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ jobs:
1919
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
2020
- name: Compress Images
2121
id: calibre
22-
uses: calibreapp/image-actions@f32575787d333b0579f0b7d506ff03be63a669d1 # 1.4.1
22+
uses: calibreapp/image-actions@9d037c06280028c110ff61c433ad4dc7d33c3c43 # 1.5.0
2323
with:
2424
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
2525
# For non-Pull Requests, run in compressOnly mode and we'll PR after.

src/handbook/marketing/blog.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,15 @@
11
---
22
meta:
3-
title: Marketing - Blog
3+
title: Blog
44
---
55

66
# Blog
77

88
## Blogging Process
99

10-
Content creation and blogging are effective ways to communicate with our community and are tied to our SEO performance (that we track in this [dedicated dashboard](https://app-eu1.hubspot.com/reports-dashboard/26586079/view/110361885?appliedIlsFilters=JTdCJTIyMTEwMzYxODg1JTIyJTNBJTdCJTIyMC0xJTIyJTNBJTdCJTIyZmlsdGVycyUyMiUzQSU1QiU3QiUyMnByb3BlcnR5TmFtZSUyMiUzQSUyMmNyZWF0ZWRhdGUlMjIlMkMlMjJwcm9wZXJ0eVR5cGUlMjIlM0ElMjJkYXRldGltZSUyMiUyQyUyMm9wZXJhdG9yJTIyJTNBJTIySVNfQkVUV0VFTiUyMiUyQyUyMnZhbHVlJTIyJTNBJTdCJTIycHJvcGVydHlUeXBlJTIyJTNBJTIyZGF0ZXRpbWUtcmFuZ2VkJTIyJTJDJTIyb3BlcmF0b3IlMjIlM0ElMjJJU19CRVRXRUVOJTIyJTJDJTIybG93ZXJCb3VuZFRpbWVzdGFtcCUyMiUzQTE3NTkwMTc2MDAwMDAlMkMlMjJ1cHBlckJvdW5kVGltZXN0YW1wJTIyJTNBMTc2MTUyMzIwMDAwMCU3RCU3RCU1RCUyQyUyMmRhdGFTb3VyY2VOYW1lJTIyJTNBJTIyQ09OVEFDVCUyMiU3RCU3RCU3RA%3D%3D) and our [Social Media Strategy](/handbook/marketing/social-media/#strategy-for-increasing-reach). The process for publishing a blog is as follows:
10+
Content creation and blogging are effective ways to communicate with our community and are tied to our SEO performance (that we track in this [dedicated dashboard](https://app-eu1.hubspot.com/reports-dashboard/26586079/view/110361885) and our [Social Media Strategy](/handbook/marketing/social-media/#strategy-for-increasing-reach) and GEO that we track in this [Google Analytics report](https://analytics.google.com/analytics/web/#/analysis/a221166832p304634214). The process for publishing a blog is as follows:
1111

12+
1. Program your blog post content aligned with the content strategy and schedule it in the Marketing team's [Content Calendar](https://app.asana.com/1/1213818720452348/project/1214069528696432/calendar/1214069573785519).
1213
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).
1314
1. 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).
1415
1. Create an [art request](/handbook/design/art-requests/#creating-an-art-request) for a blog tile to go with your article and share a deadline for when you're planning it to go live. This image will be used not only on the web, but also when the content is promoted on socials.

src/handbook/sales/index.md

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,24 @@ Questions can be asked in the [#dept-sales](https://flowfuse.slack.com/archives/
4848
- [Sales Regions](./regions.md)
4949
- [Customer Success](./customer-success.md)
5050

51+
### Sales tech stack
52+
53+
FlowFuse utilizes a streamlined and integrated tech stack to manage the entire sales process, from initial research to closed-won tracking. Our foundation is built on HubSpot as our primary Customer Relationship Management (CRM) platform, supplemented by specialized tools for enrichment, intelligence, and meeting capture.
54+
55+
Below is the mapping of our core sales capabilities to the specific tools we use:
56+
57+
#### Capability to Tool Mapping
58+
59+
| Capability | Tool | Primary Use Case |
60+
| --- | --- | --- |
61+
| **CRM (Source of Truth)** | **HubSpot** | Managing all customer relationships, pipeline data, and contact records. |
62+
| **Emails, Calls & Sequences** | **HubSpot** | Executing outreach, standardizing email templates, and running automated cadences. |
63+
| **Subscription Tracking** | **HubSpot** | Monitoring customer lifecycles, upgrades, renewals, and ongoing subscriptions. |
64+
| **Call Recording** | **Fathom** | Recording, transcribing, and summarizing customer calls and meetings. |
65+
| **Data Enrichment** | **Clay** | Automatically pulling in missing contact or company data to build robust, targeted lead lists. |
66+
| Account Research & Planning | Claude | Synthesizing account data, conducting deep-dive strategic research, and planning personalized outreach. |
67+
| Account-based Outreach | LinkedIn Sales Navigator | Research and outreach to prospects on LinkedIn. |
68+
5169
### Sales Processes
5270

5371
- [Edge Connect Process](./edge-connect-process.md)

0 commit comments

Comments
 (0)