Implementation BlueprintExecution layer

yume Client Onboarding Sprint (5-7 days)

A structured onboarding sprint that configures yume for a client's codebase, sets up agent orchestration, and trains their team on parallel agents and session recovery, enabling them to bill for AI-assisted coding with full visibility. Time: 5-7 days.

By InnovaAI ResearchPublished

Blueprint

yume Client Onboarding Sprint (5-7 days)

A structured onboarding sprint that configures yume for a client's codebase, sets up agent orchestration, and trains their team on parallel agents and session recovery, enabling them to bill for AI-assisted coding with full visibility.

Prerequisites
  • Active Claude subscription or API key for each user
  • yume Pro Monthly ($4/month) or Pro Lifetime ($49) license per seat
  • Client's codebase accessible locally with git initialized
  • Defined agent orchestration strategy (architect, explorer, implementer, guardian) for typical tasks
  • Client stakeholder available for training and feedback sessions
Execution Timeline
  • 1.Download yume and connect it to the Claude CLI using the client's API credentials
  • 2.Run a test session to verify tabs, panes, and window functionality
  • 3.Configure project workspace and git integration for the client's repository
  • 1.Define the agent orchestration strategy: assign architect for planning, explorer for research, implementer for coding, guardian for review
  • 2.Set up parallel agent execution on isolated branches for a sample task
  • 3.Document session setup and prompt templates for reuse
  • 1.Enable live token tracking and show the client how to monitor spend in real time
  • 2.Test session crash recovery using 5-minute snapshots to ensure no work is lost
  • 3.Configure visual diff tracking and rollback per message for code changes
  • 1.Build one AI-assisted coding workflow tailored to the client's core use case
  • 2.Run parallel agents on a real development task and review the output with the client
  • 3.Adjust agent prompts and orchestration based on client feedback
  • 1.Train the client's team on yume's interface, including tabs, panes, and agent controls
  • 2.Provide documentation on session persistence and crash recovery procedures
  • 3.Hand off the configured environment and workflow scripts
  • 1.Conduct a shadow session where the client runs yume with your guidance
  • 2.Troubleshoot any issues with agent orchestration or token tracking
  • 3.Finalize the onboarding documentation and usage guidelines
  • 1.Review token usage data from the sprint to estimate ongoing costs
  • 2.Deliver the final workflow and training materials
  • 3.Schedule a follow-up check-in for one week later
$2,250 per sprint (20 hours setup) plus $4/month per seat for yume Pro5-7 days
ROI Logic

Charging $2,250 for a 20-hour sprint yields an effective hourly rate of $112.50, while the tool cost is only $4 per seat per month or $49 lifetime. Even with 10 seats, the monthly tool cost is $40, leaving a margin of over 98% on the service fee. Agencies can also bundle yume seats into retainers, adding recurring revenue with negligible marginal cost.

Deliverables
  • Configured yume environment with client-specific project context and git integration
  • Agent orchestration playbook defining architect, explorer, implementer, and guardian roles
  • Prompt template library for common development tasks
  • Token usage and cost tracking report from the sprint
  • Client training guide covering session persistence, crash recovery, and rollback
Definition of Done

The client's team can independently run yume with parallel agents, monitor token usage, and recover sessions from crashes, confirmed by a successful shadow session.