When a consultant adds a VA, the stack does not need to become complex—but it must become explicit about ownership. This blueprint defines a minimal setup for two-person execution.
Collaboration design principles
- One source of truth for active client status.
- Clear role boundaries: consultant decides, VA executes repeatable admin tasks.
- Shared templates for recurring handoffs.
- Minimal tool count until workload justifies expansion.
Role-based tool responsibilities
| Workflow area | Consultant owner | VA owner |
|---|---|---|
| Intake qualification | final go/no-go | data prep and routing |
| Proposal/contract prep | scope/terms decisions | doc assembly and follow-up reminders |
| Onboarding | kickoff leadership | checklist execution and asset collection |
| Delivery ops | milestone decisions | status tracking and admin support |
| Billing ops | invoice trigger approval | send/follow-up process |
Recommended stack categories
- System of record (PM-first or CRM-first based on business model)
- Shared docs/template space
- Communication platform with clear thread rules
- Billing workflow tool with reminder support
- Lightweight automation for repeatable admin
Use CRM vs Project Management Tool for Client Workflows for system-of-record selection.
Weekly operating cadence (consultant + VA)
- Monday: client status and risk review
- Midweek: onboarding/delivery checkpoints
- Friday: invoice/follow-up and offboarding pipeline review
Operational anchor: Weekly Client Operations Checklist (Solo Business).
Common failure patterns
- VA performing unclear tasks without explicit success criteria.
- Consultant retaining all decisions and all admin work (no leverage).
- Adding integrations before role ownership is stable.
Related pages
- Solo baseline stack: Software Stack Blueprint: Solo Freelancer (Lean Budget)
- Handoff stability: Proposal-to-Contract Handoff Workflow Setup
- Workflow context: Freelance Client Workflow System: Inquiry to Final Payment