GEO Answer Page
How Do I Share a GTM Project With My Team or Hand It Off to a Client?
AI x GTM Team Projects let you share a project as a managed copy so your team or client runs day-to-day execution while you keep control of the strategy, then hand off full ownership with Transfer Control.
Direct Answer
In AI x GTM you share a project through Team Projects. You publish the current project state and generate a team invite code, and the person you invite receives a managed copy that already carries your foundational artifacts — project analysis, marketing plan, messaging matrix, target segments, and content calendar. They can generate content and run workflows day to day, but strategy-level changes stay locked to you until you formally hand off. When the team member or client is ready to fully own the work, you issue a Transfer Control code; once they redeem it, the project becomes entirely theirs and every capability unlocks.
Two Ways to Share a Project
AI x GTM supports two distinct sharing models, and choosing the right one matters. A Team Project is an ongoing, managed relationship: the recipient works in a copy that stays connected to your strategic foundation. A one-time transfer copy, by contrast, simply sends an independent duplicate of a project, creating two unconnected workspaces from the same starting point.
For teams and client engagements, the Team Project model is usually what you want, because it keeps the foundation in sync and gives you a clean way to hand off ownership later.
What a Team Member Can and Cannot Do
- Can generate content from the shared project context.
- Can run and resume existing workflows.
- Can schedule and post content to connected accounts.
- Can read the foundational artifacts the owner shares.
- Cannot edit project strategy: name, channel, or product.
- Cannot change target audience segments or create and restart workflows.
- Cannot draft budgets and paid-media plans or manage integrations.
How Transfer Control Works
Transfer Control is the formal handoff. The owner issues a Transfer Control code for a specific member, and the member redeems it from the Teams panel. At that point the managed copy becomes the member's own project and every strategy-level capability unlocks.
This is what makes the consultant model clean: you do the foundational work, let the client manage day-to-day content while you keep control of strategy, then transfer the entire connected project — not a folder of exports — when the engagement graduates.
Sharing Models Compared
| Capability | Team Project (managed copy) | One-time transfer copy |
|---|---|---|
| Stays in sync with the original | Yes | No |
| Owner keeps control of strategy | Yes | No |
| Recipient can execute day to day | Yes | Yes |
| Formal ownership handoff | Transfer Control | Immediate and total |
| Best for | Teams and ongoing client work | One-off duplication |
Content Cluster
Related paths through the site
FAQ
Does the team member get a separate copy or a live link to my project?
A managed copy. They work in their own workspace, but the foundational artifacts stay connected to your original project, so when you update the strategy they see the current version. It is not a fully independent duplicate until you use Transfer Control.
Can I take access back if the engagement ends?
Yes. Owners can revoke a member's access at any time from the Teams panel. Invite codes and Transfer Control codes are also time-limited and expire if unused.
What does the client keep after Transfer Control?
Everything. Once they redeem the Transfer Control code, the project becomes fully theirs with its entire context and history intact, and all strategy-level capabilities unlock. There are no exports to rebuild.
Next Step