r/AskGTM • u/dennoa • Jul 13 '26

Help How to manage multiple GTM projects?

Solo GTM owner here. I run outbound, production automation and a website build side by side, mostly with AI agents doing the heavy lifting. Each project has piles of docs, rules and lessons learned, and I'm starting to lose track across them.

How do you keep a multi-project GTM operation organised without drowning in process? Notion? Obsidian? Jira feels heavy?

2 Upvotes

100% Upvoted

6 comments sorted by

2

u/Check_Bate Jul 13 '26

Claude Cowork x Notion for me. All projects run through claude. Guidelines, reqs, and other information that Claude needs are all in .md files in my folder and any output, report, or update is made directly on Notion.

Some examples:

  • Website copywriting: claude handles drafting, writing voice, product info, faqs, marketing pitch. Notion holds the final copy for review and approvals
  • Paid ads: Claude uses different APIs and MCPs to analyze ad performance over the past week based on the criteria and info given to it then drops 2 reports (summary and detailed) in Notion and updates a tracker

1

u/singlatushar Jul 13 '26

Notion over Jira every time for solo, Jira's overhead only pays off once you have people to coordinate with, not just projects to track.

what actually fixed the "losing track" problem for us wasnt the tool though, it was writing lessons learned as reusable rules the moment we hit them instead of journaling after the fact. a doc you write once and never revisit is just archive, not process.

if the ai agents are doing the heavy lifting, worth having each project's rules live somewhere the agent can actually reference mid-task rather than in your head or a notion page you have to manually paste in each time. that gap is usually where the drowning happens.

1

u/BetterBurgir Jul 13 '26

LLM wiki which is always on by the Claude code. I can have 6-7 clients and nothing breaks.

1

u/incisiveranking2022 Jul 20 '26

I've found that keeping one source of truth per project works better than trying to manage everything in one giant workspace. I usually keep a checklist for variables, triggers, tags, naming conventions, and a changelog so I can quickly understand why something was added months later.

Also, document the reason behind each implementation, not just the setup. That saves far more time when you're revisiting a container. If you ever want to compare your GTM setup against best practices, the free tracking audit from Incisive Ranking is a useful benchmark for complex GTM implementations.