VRV Pages Document Suite - Quick Reference

📋 Complete Document Inventory

Core Legal Documents (3)

1. MSA.md - Master Services Agreement (10-14 pages)
   • Legal framework signed once per client
   • Evergreen, covers all future projects
   • 50+ variables, comprehensive legal terms
   • Two IP ownership options (A: Full Ownership, B: Managed Services)
2. MINI_SOW.md - Mini Statement of Work (2-5 pages)
   • For projects under $10,000
   • 35 variables, ~15-30 minutes to fill
   • References MSA for legal terms
   • Includes ownership option selection
3. SOW_STREAMLINED.md - Full Statement of Work (15-18 pages)
   • For projects over $10,000
   • 75+ variables, ~45-90 minutes to fill
   • Detailed specifications, QA standards
   • References MSA for legal terms

Support Documents (7)

1. MSA_VARIABLES.md - Complete MSA variable reference
2. MINI_SOW_VARIABLES.md - Mini-SOW variable reference
3. SOW_VARIABLES.md - Full SOW variable reference
4. SOW_COMPARISON.md - Decision guide (Mini vs Full)
5. AUTOMATION_GUIDE.md - How to automate document generation
6. DOCUMENT_SUITE_GUIDE.md - Complete system overview
7. ACCESS_CHECKLIST.md - Client access requirements

Legacy Documents (3)

1. CONTRACT.md - Standalone contract (backup option)
2. CLIENT_INTAKE.md - Client intake form
3. README.md - Templates overview

🚀 Quick Start Workflows

New Client, Small Project (< $10K)

# 1. Generate MSA + Mini-SOW
./scripts/vrv_manager.sh document msa "Client Name" "Master Services Agreement"
./scripts/vrv_manager.sh document mini-sow "Client Name" "Project Name"

# 2. Edit filled templates in Admin/Clients/[Client Name]/
# 3. Replace  with real values
# 4. Select IP Option (A or B)
# 5. Generate PDFs
# 6. Send for signature (both MSA + Mini-SOW)

Documents Created:

• MSA_client_name_2025-01-15.md (Exhibit A)
• MINI_SOW_client_name_2025-01-15.md (main document)

Time: 30-45 minutes total

Existing Client, New Project

# 1. Generate Mini-SOW only (MSA already signed)
./scripts/vrv_manager.sh document mini-sow "Client Name" "New Project Name"

# 2. Edit filled template
# 3. Ensure MSA reference is correct (version & date)
# 4. Select same IP option as existing projects (usually)
# 5. Generate PDF
# 6. Send for signature (SOW only)

Documents Created:

• MINI_SOW_client_name_2025-02-01.md (references existing MSA)

Time: 15-20 minutes

Enterprise Client (> $50K)

# 1. Generate MSA + Full SOW
./scripts/vrv_manager.sh document msa "Client Name" "Master Services Agreement"
./scripts/vrv_manager.sh document sow "Client Name" "Project Name"

# 2. Customize MSA terms (may negotiate):
#    - Payment terms (Net 30)
#    - Review days (7-10)
#    - Liability caps (custom)
# 3. Fill comprehensive SOW details
# 4. Send to client's legal team
# 5. Negotiate and revise
# 6. Regenerate with final terms
# 7. Execute via DocuSign

Timeline: 1-4 weeks (includes legal review)

🎯 Decision Tree

Which SOW Template?

Project Budget?
├─ < $10,000 → MINI_SOW.md
└─ > $10,000 → SOW_STREAMLINED.md (or full SOW.md)

Project Complexity?
├─ Simple (3-5 pages) → MINI_SOW.md
└─ Complex (CMS, integrations, custom features) → SOW_STREAMLINED.md

Which IP Ownership Option?

Does client have technical staff?
├─ Yes → Recommend Option A (Full Ownership)
│   └─ Client can self-manage hosting/updates
└─ No → Recommend Option B (Managed Services)
    └─ VRV handles everything, recurring revenue

Client wants control?
├─ Yes → Option A (+ $2K-$5K one-time fee)
└─ Prefers hassle-free → Option B (+ $150-$500/month)

Project value?
├─ < $10K → Option A (managed services not cost-effective)
├─ $10K-$30K → Either option works
└─ > $30K → Option B attractive (recurring revenue, long relationship)

📊 Variable Quick Reference

Must-Fill Variables (All Documents)

IP Ownership Variables

Default Terms (Rarely Change)

🔧 Tool Commands

vrv_manager.sh Usage

# Initialize new client project
./scripts/vrv_manager.sh init "Client Name" "Project Title"

# Generate MSA (first engagement)
./scripts/vrv_manager.sh document msa "Client Name"

# Generate Mini-SOW
./scripts/vrv_manager.sh document mini-sow "Client Name" "Project Name"

# Generate Full SOW
./scripts/vrv_manager.sh document sow "Client Name" "Project Name"

# Generate other documents
./scripts/vrv_manager.sh document intake "Client Name"
./scripts/vrv_manager.sh document contract "Client Name"

# Generate milestone
./scripts/vrv_manager.sh milestone 1 "Discovery" "Requirements gathering"

# Generate PDF from markdown
./scripts/vrv_manager.sh pdf docs/SOW.md "Statement of Work"

# Create client handoff package
./scripts/vrv_manager.sh handoff ~/Desktop/client-delivery

PDF Generation (Manual)

# Using WeasyPrint (recommended)
weasyprint input.md output.pdf --stylesheet assets/pdf-style.css

# Using Pandoc
pandoc input.md -o output.pdf --pdf-engine=weasyprint --css=assets/pdf-style.css

# Using wkhtmltopdf
wkhtmltopdf --page-size Letter input.html output.pdf

📁 File Organization

Where Things Live

VRV_Pages/
├── VRV-Tools/
│   ├── templates/           ← SOURCE OF TRUTH (13 templates)
│   │   ├── MSA.md
│   │   ├── MINI_SOW.md
│   │   ├── SOW_STREAMLINED.md
│   │   ├── *_VARIABLES.md   (variable references)
│   │   └── *_GUIDE.md       (documentation)
│   ├── scripts/
│   │   └── vrv_manager.sh   (CLI tool)
│   └── assets/
│       └── pdf-style.css    (PDF styling)
├── Admin/
│   └── Clients/
│       └── [Client Name]/   ← FILLED DOCUMENTS GO HERE
│           ├── MSA_*.md
│           ├── *_SOW_*.md
│           └── exports/pdf/ (generated PDFs)
├── vrv-client-template/
│   └── templates/           ← Synced from VRV-Tools (14 files)
└── Active_Clients/
    └── vrv-client-*/
        └── templates/       ← Synced from VRV-Tools (14 files)

What Gets Committed to Git

YES (commit):

• All templates in VRV-Tools/templates/
• Variable guides and documentation
• Scripts and automation tools
• CSS styling files

NO (don’t commit):

• Filled documents with client data (Admin/Clients/)
• Generated PDFs (*.pdf)
• Signed contracts (contain PII)
• Client-specific YAML files with sensitive data

✅ Pre-Send Checklist

Before sending documents to client:

Content Review

• All `` replaced (no placeholders)
• Client legal name correct (matches business registration)
• Email/phone/address verified
• Project scope accurate and complete
• Fees and payment schedule correct
• Timeline realistic and agreed upon
• IP ownership option selected (checkbox ✓)

MSA-Specific

• MSA version and date consistent across all docs
• VRV contact information current
• Default terms appropriate (or customized if negotiated)
• Governing state/venue correct

SOW-Specific

• SOW references correct MSA version and date
• First engagement: “MSA attached as Exhibit A” ✓
• Subsequent engagement: “MSA incorporated by reference” ✓
• Deliverables clear and specific
• Milestones have concrete dates
• Out-of-scope items listed

Technical

• PDF generates without errors
• Formatting looks professional
• Tables and lists render correctly
• Signature blocks visible and complete
• Page numbers correct
• No broken formatting

Legal (Enterprise Only)

• Attorney review completed
• Negotiated changes incorporated
• Custom terms properly integrated
• Insurance requirements met
• Data processing terms GDPR/CCPA compliant

🆘 Troubleshooting

”” appears in output

Fix: Variable name misspelled or not in data file

1. Check spelling (case-insensitive)
2. Add to client YAML or defaults
3. Regenerate document

PDF formatting broken

Fix: CSS issue or HTML conversion problem

1. Check pdf-style.css exists
2. Update WeasyPrint: pip install --upgrade weasyprint
3. Test with simpler markdown first
4. Check for special characters breaking HTML

Templates not synced across repos

Fix: Run sync command

cd ~/path/to/VRV_Pages
cp VRV-Tools/templates/*.md vrv-client-template/templates/
cp VRV-Tools/templates/*.md Active_Clients/vrv-client-buckroe/templates/

MSA version mismatch between MSA and SOW

Fix: Always check MSA date when generating SOW

1. Look up client’s signed MSA version/date
2. Update SOW header: and
3. Ensure consistency

🎓 Learning Path

Day 1: Understanding

• Read DOCUMENT_SUITE_GUIDE.md (this file)
• Review MSA.md template
• Review MINI_SOW.md template
• Understand Option A vs Option B

Day 2: Setup

• Update defaults in MSA (contact info, terms)
• Test vrv_manager.sh commands
• Generate sample documents (fake client)
• Review PDF output

Day 3: First Real Client

• Fill MSA with real client data
• Fill Mini-SOW for first project
• Generate PDFs
• Send for signature via DocuSign

Week 2: Automation

• Install Python + WeasyPrint
• Create client YAML files
• Write generation script
• Test automated workflow

Month 2: Optimization

• Track what works, what doesn’t
• Refine templates based on feedback
• Build client library
• Update terms if needed

📈 Success Metrics

You’ll know it’s working when:

✅ Speed: New client docs ready in < 30 minutes
✅ Efficiency: Repeat clients sign in < 24 hours
✅ Clarity: Zero contract disputes
✅ Upsells: Easy Option B → A conversions
✅ Professional: Client feedback is positive
✅ Protection: You feel legally secure

🔗 Key Resources

Primary Templates:

• MSA.md - Master legal framework
• MINI_SOW.md - Small project template
• SOW_STREAMLINED.md - Large project template

Variable References:

• MSA_VARIABLES.md - 50+ MSA variables
• MINI_SOW_VARIABLES.md - 35 Mini-SOW variables
• SOW_VARIABLES.md - 75+ Full SOW variables

Decision Guides:

• SOW_COMPARISON.md - Mini vs Full SOW
• DOCUMENT_SUITE_GUIDE.md - Complete system
• AUTOMATION_GUIDE.md - How to automate

Tools:

• vrv_manager.sh - CLI tool (bash)
• generate_docs.py - Automation script (Python, create this)
• pdf-style.css - Professional PDF styling

💡 Pro Tips

1. Always sign MSA first - Never skip this step, even for small projects
2. Version your MSAs - Track v1.0, v1.1, v2.0 for clarity
3. Grandfather clients - Don’t force existing clients onto new MSA versions
4. Reference by date - “MSA v1.0 dated January 15, 2025” is clearer than just “MSA v1.0”
5. Print-friendly PDFs - pdf-style.css has @media print rules for white backgrounds
6. Automate early - Manual filling gets tedious after 3-5 clients
7. Keep it simple - Don’t over-customize; use defaults
8. Test thoroughly - Generate sample docs before real clients
9. Back up everything - Archive signed contracts for 7+ years
10. Get legal review - For first MSA and any enterprise deals

📞 Quick Help

“Which template do I use?”

• New client → MSA.md + (MINI_SOW.md or SOW_STREAMLINED.md)
• Existing client → (MINI_SOW.md or SOW_STREAMLINED.md) only

“How do I choose Option A vs B?”

• Client wants control → Option A
• Client wants hands-off → Option B
• Budget < $10K → Usually Option A
• Budget > $30K → Consider Option B

“Can I modify templates?”

• Yes, but keep changes in separate files
• Don’t break the `` tokens
• Get legal review for material changes
• Consider if changes should be in standard template

“How often update templates?”

• Review quarterly
• Update when laws change
• Incorporate lessons learned
• Increment version numbers

Last Updated: January 2025
Version: 1.0
Status: Production Ready ✅

🚦 Status: READY TO USE

All 13 templates created, synchronized, and documented.
System ready for real client engagements.

Next Action: Generate your first MSA + Mini-SOW for a test client!