Finn's track
The role arc, roadmap, and self-study — kept inside Demand Desk so there's one destination, no parallel surface to drift. The hub owns the pull; Finn owns the action layer.
Role arc
Channel operator
Runs the channels by hand — pulls numbers, posts, formats. The starting point.
AI-augmented marketer
Stops wrestling data — intel is provided in the hub. Spends time on the action layer: content, landing pages, experiments. Requests automations as she finds the need.
Growth engineer
Owns and extends the automations themselves — identifies a gap, proposes the capability, and increasingly builds it. Autonomy compounds.
Roadmap
Operate the action layer on provided intel
Use the three lanes' so-what/now-what to decide what to make next, instead of pulling SEO and channel exports by hand.
Run the first repurposing capability
Maven webinar (Jun 23) → LinkedIn + newsletter + shorts, via the content-repurposing skill. First time she drives a capability end-to-end.
Own the SEO content-gap → draft loop
Once Gregor gates the Ahrefs pull, Finn runs the gap → draft cadence weekly and owns the editorial calendar off it.
Propose her first net-new capability
Identify a manual step worth automating, write the registry entry, and spec it with Anna — the operator → engineer hinge.
Wire a lane she relies on
Move from requesting automations to helping build one — likely landing-page generation or the Webflow upload, alongside Anna.
Self-study & the marketing repo
Marketing repo
RepoSource of truth for lane configs, the registry, and Finn's agent — the hub reads from here.
gtm/Compete Lens
DocHow the competitive feed is produced — read it to understand what the SEO lane surfaces.
gtm/compete-lens/README.mdLinkedIn raw-content skill
SkillHow voice-true content briefs get produced for Ves to draft + schedule.
Metric-tree thinking
DocWhy every lane ladders to QILs and nothing is shown as a vanity number.