Agency Client Projects | Multi-Client Management

Development agencies manage multiple client projects with GitScrum. Create separate projects per client, set viewer access for transparency, and balance team capacity across projects.

4 min read

How to manage client projects for development agencies?

Manage client projects by creating separate GitScrum projects per client, using labels for project priority and type, and monitoring team capacity across all projects. Set client-appropriate visibility (Viewer access for transparency), use Team Standup to track developer allocation, and use Reports to ensure no single client monopolizes resources.

Agency project organization

Level	Purpose	Example
Workspace	Business unit or team	"Development Team"
Project	Per client engagement	"Acme Corp - Web Redesign"
Columns	Workflow stages	Standard or client-specific
Labels	Cross-project categorization	Priority, type, tech stack

Client visibility setup:

Create client project - Named clearly for client

Set up workflow columns - Standard agency process

Add team members - Assign developers as Members

Invite client - Add as Viewer role

Configure what's visible - Public notes only

Set up reports access - Share progress dashboards

Establish update cadence - Weekly summary notes

Balancing multiple clients

Challenge	Solution
Developer spread thin	WIP limits per person
One client dominates	Allocate % per client
Priority conflicts	Clear priority labels
Context switching	Dedicated days per client
Capacity planning	Team Standup visibility

Labels for agency projects

Label	Purpose
client:high-priority	Key account priority
type:retainer	Ongoing retainer work
type:fixed-bid	Fixed scope project
urgent	Needs immediate attention
blocked:client	Waiting on client input
billable	Billable hours
internal	Non-billable work

Multi-client capacity management

CAPACITY ALLOCATION:
┌─────────────────────────────────────────────────────────────┐
│ TEAM OF 8 DEVELOPERS                                        │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│ Client A (Premium): 3 developers, 37.5%                     │
│ Client B (Standard): 2 developers, 25%                      │
│ Client C (Standard): 2 developers, 25%                      │
│ Internal/Support: 1 developer, 12.5%                        │
│                                                             │
│ Use Team Standup to verify allocation matches plan          │
│ Use WIP limits to prevent over-commitment                   │
│                                                             │
└─────────────────────────────────────────────────────────────┘

Client communication with GitScrum

Touchpoint	Method
Real-time status	Client Viewer access
Weekly summary	NoteVault update note
Blocking issues	Email notification
Milestone completion	Task comments
Monthly review	Reports export