Mowgli Client Workspace Setup (Onboarding)
A sequence with 8 steps: Create the agency workspace in Mowgli, then create a separate workspace for the client account.
By InnovaAI ResearchPublished
What are the steps?
Mowgli Client Workspace Setup (Onboarding)
- 01
Create the agency workspace in Mowgli, then create a separate workspace for the client account
Setup complexity is assessed as medium, so budget a structured onboarding session rather than same-day self-serve. Confirm Mowgli branding stays visible on the canvas: this is an adoption engagement, not a resell-without-rebrand one.
- 02
Assign editing access per person, not per team
Decide which designers, PMs, and client-side reviewers need editing rights versus view-only access on the shared canvas. Real-time collaboration is the core of the Team plan, so seat allocation drives both the retainer margin and who can burn credits.
- 03
Import the client's existing Figma files before generating anything new
Figma import is available on the Free plan, so run it first to prove bidirectional sync on the client's real artifacts. For clients with existing code, test the MCP coding-agent connection (Claude Code, Codex, Cursor) in the same session.
- 04
Run the questionnaire and PRD generation against the client brief
The questionnaire and PRD generation step produces the synchronized product spec that every screen inherits. Lock this before design generation starts; changing the spec later forces regeneration across all screens and consumes credits.
- 05
Generate the full app design from the text description, targeting 30+ screens
Full app design generation covers 30+ screens on the Starter plan. Scope the first client app to a defined screen count up front so the credit-based model does not surprise a fixed-fee retainer.
- 06
Iterate via chat, then build the interactive prototype with real navigation flows
Each chat iteration consumes credits, so batch feedback rounds with the client instead of relaying single comments. The prototype is the stakeholder review artifact; navigation flows must work before it goes to the client.
- 07
Export to Figma and React + Tailwind, then document the spec and screen annotations
Unlimited AI exports and unlimited image exports are Starter-plan features, so export volume is not the constraint. Hand the Figma file and React code to the client's engineering team alongside the product spec and per-screen annotations.
- 08
Set the credit ceiling and review cadence for the retainer
The Team plan at $49/seat/year with shared folders and 12-hour support is the viable tier for small agency retainers. Record the client's monthly credit burn in the workspace so scope creep is visible before it hits the next invoice.
More on Mowgli
- StrategyWhy Mowgli Changes Agency Design-to-Code Economics
- ConceptMowgli Credit Burn Rate
- Evaluation RuleWhen to Adopt Mowgli: Credit-Forecasting Before You Sign a Fixed-Fee App Retainer
- Decision FrameworkMowgli: Buy vs Skip (Design-to-Code Agency Retainers)
- Failure PatternThe Mowgli Credit Burn Trap: Why Agencies Fail With Mowgli on Fixed-Fee Client Retainers
- Implementation BlueprintMowgli Client App Design Sprint (5-7 days)