The momentum nobody sees
A growth team running multiple initiatives — paid ads, a podcast tour, an influencer push, a content series — is usually best at tracking the work and worst at communicating the outcomes. Weekly results land in a spreadsheet or a Notion doc, the team that’s actually shipping doesn’t see them, and momentum gets quietly lost.
The pieces are there. The workspace already knows which leads and deals came in this week. The CRM is wired to the marketing board through Company, Deal, Lead, and Deal-History entities. The team is on Slack. The missing piece is the rollup that ties them together — and that’s what this example adds.
Initiatives, weekly results, influencer relationships
The Marketing Board lists every active initiative. Each has a detail page tracking weekly results — impressions, leads sourced, deals influenced — alongside threaded comments for context. A separate Influencers list tracks the people involved in influencer initiatives, with per-person detail pages and links back to the deals they contributed to. A Marketing Dashboard page rolls the numbers up so the whole picture is on one screen.
Because the board reads the CRM’s Company / Deal / Lead / Deal-History entities, attribution stops being a spreadsheet question. If a deal came in this week and the contact’s source matches an initiative, the rollup picks it up.
From weekly result to Slack message in one step
- Log this week’s result. Open the initiative’s detail page, capture impressions, leads sourced, deals influenced, and any context. The workspace stores it as a weekly-result entity attached to the initiative.
- The rollup fires automatically. When a weekly result is logged, the workspace posts a Slack message to the configured marketing channel — initiative name, this week’s numbers, a link back to the initiative detail page in the workspace.
- Team sees momentum where they already are. The Slack post is short and structured: the team doesn’t need to open the workspace to know the shape of the week, and if they want depth, the link is right there.
Channel, rollup cadence, attribution rules
- Slack channel — pick a marketing channel for the rollup. One channel per workspace by default; if you need per-initiative routing, extend the rollup function to vary by initiative.
- Rollup cadence — the default posts on every new weekly-result entity. For low-volume teams that’s fine. For high-volume teams (many initiatives, multiple results per week per initiative) a scheduled Friday digest that batches the week’s results reads better.
- Attribution rules — which deals count as “influenced” by a given initiative is a team-specific call. The default reads contact source + deal-history events; tune to your actual attribution model.
- Influencer fields — for influencer initiatives, capture per-person fields (handle, follower count, niche) so the detail page is useful for re-engagement later.
- Message content — short and structured beats prose. Initiative name, the week’s headline numbers, a link back. The Slack message is a pointer, not a report.
The marketing rollup happens in the channel where the team already is. Reading the workspace becomes optional.
Rollup without a maintainer
The work this replaces is small but recurring: someone has to remember to write the Friday recap, paste in the numbers, link back to the board. Predictable enough to automate, fragile enough that it gets dropped when the team is heads-down. Describing it in the workspace spec means the rollup doesn’t have a maintainer: the workspace knows when a weekly result was logged, and the Slack post follows. The spec is what you change when you want a Friday digest instead of a per-result post, when initiatives should route to per-team channels, or when the attribution rule needs to follow your team’s actual definition.