Project Echo White-Label Client Workspace Handoff (Onboarding)
A handoff with 8 steps: Create the client workspace on the Free plan and confirm the core loop before spending anything.
By InnovaAI ResearchPublished
What are the steps?
Project Echo White-Label Client Workspace Handoff (Onboarding)
- 01
Create the client workspace on the Free plan and confirm the core loop before spending anything
Free includes unlimited workspaces, unlimited boards, unlimited team members, unlimited Feedback, the Feedback Portal, and API & MCP Server access. Run the pilot here so the agency validates the collect, prioritize, announce loop without a vendor line item.
- 02
Upgrade that workspace to Pro at $29/mo when the client signs the retainer
Pro is the only tier that carries Custom domain, Remove branding, Custom user properties, MRR attribution, and Custom SMTP. White-label delivery is impossible below Pro, so the upgrade is the handoff gate, not a nice-to-have.
- 03
Point the client's own domain at the portal and strip Project Echo branding
Set the Custom domain and enable Remove branding in the Pro settings. The client's users should never see the vendor name on the feedback portal or the public changelog.
- 04
Map Custom user properties to the client's account model
Use Custom user properties to tag each submitter with plan tier, MRR band, or segment so the Kanban roadmap can be sorted by revenue weight instead of raw vote count.
- 05
Connect Linear, Notion, and Slack so feedback and roadmap updates stay in the client's existing tools
Route accepted requests into Linear, mirror roadmap state into Notion, and push changelog announcements into Slack. The client team keeps working where they already work.
- 06
Wire the payment integration for MRR attribution
Project Echo connects to Stripe, Lemon Squeezy, Paddle, Chargebee, Recurly, and FastSpring. Once linked, MRR attribution shows which feedback comes from paying accounts, which is the argument for prioritizing it.
- 07
Hand the MCP Server endpoint to the client's AI tooling
Claude and Cursor can read and act on feedback data through the MCP Server. Document the endpoint and access scope in the handoff pack so the client's team can run AI-assisted prioritization without agency involvement.
- 08
Publish the first changelog entry and transfer portal admin rights
Ship one real announcement before handoff so the client sees the changelog working. Then move workspace ownership to the client contact and keep agency access as a collaborator seat.
More on Project Echo
- StrategyWhy Project Echo Turns Roadmap Visibility Into Retainer Margin
- ConceptProject Echo White-Label Margin Threshold
- Evaluation RuleProject Echo Rule: Charge for the Portal Only When the Client Workspace Is White-Labeled
- Decision FrameworkProject Echo: Buy vs Skip (White-Label Client Feedback Portals)
- Failure PatternThe Project Echo White-Label Margin Trap
- Implementation BlueprintProject Echo White-Label Client Portal Rollout (5-7 days)