Marketing & Growth

How to plan a monthly content calendar as Small Marketing Teams

Marketing & GrowthFor Small Marketing Teams3 apps10 steps~20 min to set up

Your three-person team is responsible for every piece of content that touches demand gen, nurture, events, and social — and the monthly content calendar lives in a Notion doc that's already out of date. You're manually checking HubSpot to see which topics drove the most MQLs last quarter, pulling GA4 to see what content actually converted, and cross-referencing your Mailchimp or Customer.io send schedule to avoid cannibalizing email sends with blog drops. By the time you've synthesized all that into a Notion brief, two weeks of the month are gone. There's no system — just a shared doc, a Slack thread, and a standing Thursday meeting where everyone catches up on what slipped.

Build this on Starch → See the apps used

Marketing & GrowthFor Small Marketing Teams3 apps10 steps~20 min to set up

Outcome

What you'll set up

A living content calendar app that pulls HubSpot deal data and GA4 traffic signals into a single view so you can see which topics correlate with pipeline — not just pageviews

A weekly Growth Analyst digest that emails your team every Monday with what content drove signups, what channel mix shifted, and what to prioritize in the next two weeks of the calendar

A lightweight project tracking layer where blog posts, social assets, and email briefs each have an owner, a due date, and a status — captured by typing a sentence instead of filling out a form

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Growth Analyst Project Management Task Manager

Data sources & config

Connect HubSpot as a scheduled-sync provider — Starch syncs your contacts, companies, and deals on a schedule so the calendar always reflects current deal-stage distribution. Connect PostHog via Starch's integration catalog; the Growth Analyst agent queries it live when generating each weekly digest. Connect Mailchimp from Starch's integration catalog for live-query access to campaign send schedules so you can surface email send dates alongside blog and social drops in the same calendar view. Notion syncs on a schedule so existing campaign briefs are readable inside Starch without re-entering anything.

Prompts to copy

Build me a content calendar app that shows this month's planned posts by channel (blog, email, LinkedIn, paid), pulls from HubSpot to tag each piece with the deal stage it targets, and flags anything with no assigned owner or publish date

Set up the Growth Analyst to email me and two teammates every Monday at 8am with: top 3 content pieces by new signups last week, which referral channels moved most, and what topic cluster we should prioritize this week based on conversion trends

Create a task for Jordan to write the April case study draft, priority P1, due April 11th, and tag it under the Q2 Content project

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 Connect HubSpot in Starch — it syncs contacts, deals, and companies on a schedule. Open the Sales Agent CRM app as a reference, then describe your content-focused variation: 'Show me a view of HubSpot deals grouped by the content topic that sourced the contact, with MQL count per topic for the last 90 days.'

2 Connect PostHog from Starch's integration catalog so the Growth Analyst can query traffic and conversion data live each week. If your team uses Amplitude instead, connect it from the catalog the same way — the agent queries it live when it runs.

3 Connect Mailchimp (or Customer.io, or Klaviyo) from Starch's integration catalog. Ask Starch to pull next month's planned email send dates into your calendar view so blog posts and email sends don't stack on the same day.

4 Start the Growth Analyst app from the App Store. Customize the digest prompt to focus on content-specific signals: 'Every Monday, pull last week's signup data from PostHog, identify the top 3 content pieces by assisted conversion, and flag the topic cluster with the biggest week-over-week drop. Email the digest to the whole marketing team.'

5 Build your content calendar app by typing: 'Build me a content calendar for April that shows planned blog posts, LinkedIn posts, and email sends by week. Each row should have: title, channel, target deal stage from HubSpot, assigned writer, publish date, and status. Flag anything with no owner or no publish date in red.'

6 For each piece on the calendar, use the Project Management app to create a task: type 'create a task for [name] to finish the [piece] draft by [date], tag it Q2 Content, priority P1' and Starch creates it with assignment and due date set.

7 Wire a weekly automation: 'Every Friday at 4pm, check the content calendar for any pieces due next week that are still in Draft status, and Slack the assigned writer a reminder with the publish date and any missing fields.' Starch triggers this on schedule — no manual follow-up.

8 At the start of each month, ask Starch: 'Pull the last 60 days of HubSpot deal data and PostHog signup data. Which topic clusters drove the most new MQLs? Suggest 6 blog topics for next month based on that, and add them as draft rows in the content calendar with no owner assigned yet.'

9 Share the calendar app with your CEO or VP before the monthly pipeline review. Because it pulls HubSpot deals in real time, they can see content-to-pipeline attribution without you building a separate slide deck.

10 At the end of each month, prompt Starch: 'Compare this month's planned content calendar against what actually published. How many pieces shipped on time? Which channels had the most slippage? Give me a table I can paste into our retrospective Notion doc.'

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

April 2026 Content Calendar Build — 3-person team, 120-person SaaS company

Sample numbers from a real run

HubSpot MQLs sourced by content (last 60 days)	47
Top topic cluster: 'onboarding automation' — MQLs attributed	19
Planned blog posts for April	8
Posts with no assigned owner at calendar build time	3
Email sends planned — potential conflicts with blog drops	4
Weekly Growth Analyst digest recipients	3

On March 31st, your team runs the month-open routine. You prompt Starch: 'Pull the last 60 days of HubSpot deal data and PostHog signups. Which topic clusters drove the most new MQLs?' Starch surfaces that 'onboarding automation' content drove 19 of your last 47 MQLs — more than any other cluster — while your 'pricing comparison' posts drove only 4 signups despite high traffic. You use that to brief April: 3 onboarding-automation posts, 2 integration how-tos that HubSpot shows are common mid-funnel touchpoints, and pull back on bottom-funnel comparison content that isn't converting. The calendar app populates 8 rows with channel, target deal stage, and writer fields. Three rows come in with no owner — Starch flags them immediately. You type 'create tasks for Jordan to own the two onboarding posts and Sam to own the integration guide, all P1, due by April 14th' and the Project Management app creates all three assignments at once. The following Monday, the Growth Analyst digest lands in your inbox: signups from blog content were up 18% week-over-week, the onboarding category drove 6 of 11 new trial signups, and the digest flags that LinkedIn organic referral dropped 30% — worth investigating before you schedule the April LinkedIn posts. Your Friday automation fires at 4pm: two pieces due the following week are still in Draft. Starch Slacks the writers directly. Neither piece is late.

Measurement

How you'll know it's working

MQLs attributed to content by topic cluster (from HubSpot deal source data)

Content pieces published on schedule vs. planned (calendar adherence rate)

Weekly new signups by content referral channel (from PostHog digest)

Email-to-blog send conflict rate — days where email and blog dropped simultaneously

Time from content brief creation to task assignment (team throughput lag)

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Notion + manual HubSpot exports

Notion is great for the brief itself, but you're still copy-pasting HubSpot data and GA4 numbers into it by hand every month — the calendar is always a snapshot, never live

CoSchedule or Contentful

Purpose-built editorial calendars give you scheduling structure but don't connect to HubSpot deal stages or PostHog conversion data, so you still can't answer 'did this topic drive pipeline' without a separate BI export

Google Sheets + Zapier

Flexible but brittle — every new integration is a separate Zap you have to maintain, and there's no AI layer to synthesize what the data means or suggest what to create next

HubSpot's native content tools

Solid if you're already all-in on HubSpot's CMS, but most three-person teams aren't, and you'd still be missing PostHog or Amplitude signals unless you pay for a BI add-on

On Starch RECOMMENDED

One platform — growth analyst, project management, task manager all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

We use Customer.io, not Mailchimp — can Starch still pull our email send schedule?

Yes. Connect Customer.io from Starch's integration catalog; the agent queries it live when your calendar app runs. Same pattern works for Klaviyo. You describe what you want to see — send dates, campaign names, segment targets — and Starch pulls it into whatever view you've built.

We use Amplitude instead of PostHog. Does the Growth Analyst work with that?

The Growth Analyst starter app is built around PostHog, but you can connect Amplitude from Starch's integration catalog and build a custom digest app on top of it. Tell Starch what signals matter — weekly active users, signup conversion by source, feature adoption by cohort — and it builds the digest around those. You're not locked into PostHog.

Will Starch actually store our historical content performance data, or is it querying live each time?

Honest answer: HubSpot and Notion data syncs on a schedule and lives in Starch's database, so trend comparisons work well. PostHog, Amplitude, and your email platform are queried live when the digest or calendar app runs. Starch is not a data warehouse — it's not designed for archiving years of raw event data. For most content calendar use cases that's fine; for deep historical attribution modeling you'd still want a BI tool.

Can Starch post directly to LinkedIn or schedule posts, or just plan them in the calendar?

Starch can automate LinkedIn through your browser — no API needed — so actions like drafting and posting are reachable via browser automation. For scheduling, the LinkedIn Automation app in the App Store is designed for outreach workflows. If you want to add 'auto-post approved content on publish date' to your calendar workflow, describe it to Starch and it'll build the automation; just know it's running browser automation rather than a native LinkedIn API integration.

We don't have a dedicated project management tool. Is the Starch Project Management app enough for a content workflow?

For a 3-person team managing 8-12 content pieces a month, yes — it covers kanban boards, priority levels, due dates, owner assignment, and AI task creation by prompt. It's not Linear or Asana with all their roadmap features. If you're also running engineering sprints or cross-functional OKR tracking on top of content, you might outgrow it. But for keeping blog posts and email briefs organized with owners and deadlines, it's built for exactly this scale.

How long does it take to set this up?

Connecting HubSpot and Notion (both scheduled-sync providers) takes a few minutes each. Connecting your email platform and PostHog from the integration catalog is similarly fast. Building the content calendar app — describing it in natural language and letting Starch generate it — typically takes one session of 20-30 minutes including iteration. The Growth Analyst weekly digest can be live the same day. You're not configuring a BI pipeline or writing SQL.