Failure PatternDecision layer
The Project Echo White-Label Margin Trap
Symptom: Client workspaces still show Project Echo branding because the agency never upgraded past the Free plan, which includes unlimited workspaces but no custom domain or branding removal. Root cause: The Free plan allows unlimited workspaces and unlimited team members, which makes it easy to onboard every client without ever hitting a paywall, so agencies never budget for the Pro plan's $29/mo per workspace.
By InnovaAI ResearchPublished
How do you recognize it?
- •Client workspaces still show Project Echo branding because the agency never upgraded past the Free plan, which includes unlimited workspaces but no custom domain or branding removal.
- •The agency's own domain never appears in the portal URL, so clients share links that read projectecho.app instead of the agency's brand.
- •Retainers priced at $299/mo for the Starter Portal offering start losing money once the $29/mo Pro upgrade is applied to each client workspace.
- •Feedback portals sit empty because the agency configured boards but never routed client feature requests into the public portal from Linear or Slack.
- •Changelog pages go stale within 30 days because no one on the delivery team owns the publish step after the initial setup.
Why does it happen?
- •The Free plan allows unlimited workspaces and unlimited team members, which makes it easy to onboard every client without ever hitting a paywall, so agencies never budget for the Pro plan's $29/mo per workspace.
- •White-label branding removal and custom domains are gated behind Pro at $29/mo, meaning each client workspace carries a recurring cost that was not factored into the $299/mo Starter Portal fee.
- •Agencies treat Project Echo as a one-time setup deliverable (6h setup) rather than an ongoing retainer service, so the 2h/mo maintenance window is never staffed.
- •The MCP Server and Linear/Slack integrations are available on Free, which creates the illusion that the full workflow is free, masking the Pro-only features that clients actually notice (branding, custom domain).
How do you fix it?
- •Audit every client workspace in the Project Echo admin panel and count how many are on Free versus Pro; calculate the true monthly cost at $29/mo per Pro workspace before quoting any new retainer.
- •Upgrade only the client workspaces that appear in client-facing URLs to Pro, and keep internal or pilot workspaces on Free to protect margin.
- •Reprice the Starter Portal offering to include the $29/mo Pro cost as a line item, or bundle it into a higher retainer tier so the agency is not absorbing it.
- •Assign a named delivery owner and a recurring calendar block for the 2h/mo changelog and roadmap maintenance, and connect Linear and Slack so feedback flows into the portal without manual entry.
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)
- Implementation BlueprintProject Echo White-Label Client Portal Rollout (5-7 days)
- Operating ProcedureProject Echo White-Label Client Workspace Handoff (Onboarding)
More for Roadmaps Ops Planning
- Failure PatternsThe Roadmap-as-Deliverable Trap: Why Agencies Stall on Roadmaps & Ops Planning
- Failure PatternsThe Frozen Roadmap Trap: Why Agencies Lose the Priority Conversation in Roadmaps & Ops Planning
- StrategiesThe Roadmap as a Negotiation Instrument: Why Sequencing Discipline Sets Agency Margin
- ConceptsPriority Repricing Ladder