SkyMirror Operations & Systems Playbook
Executive Summaryβ
This playbook establishes SkyMirror's operational systems, processes, and infrastructure. It covers dashboards, tools, meeting rhythms, and process documentation for smooth operations at scale across all business units: Software Solutions, AI Applications (CheckMet, Traquiva), and SkyMirror Academy.
Part 1: Company Dashboardβ
1.1 Executive Dashboardβ
Real-Time Metrics Displayβ
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β SKYMIRROR EXECUTIVE DASHBOARD β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ€
β β
β REVENUE CUSTOMERS PRODUCT β
β ββββββββββββββββ ββββββββββββββββ βββββββββββββββββ
β β MRR: β¬15.2K β β Active: 8 β β Uptime: 99.9%ββ
β β β² +12% MoM β β β² +2 this mo β β Users: 1,750 ββ
β ββββββββββββββββ ββββββββββββββββ βββββββββββββββββ
β β
β CASH TEAM PIPELINE β
β ββββββββββββββββ ββββββββββββββββ βββββββββββββββββ
β β β¬1.2M β β 23 FTEs β β β¬450K ββ
β β 18mo runway β β 3 open roles β β 12 deals ββ
β ββββββββββββββββ ββββββββββββββββ βββββββββββββββββ
β β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Dashboard Metrics Definitionsβ
| Metric | Definition | Source | Update Frequency |
|---|---|---|---|
| MRR | Monthly Recurring Revenue | Billing system | Daily |
| ARR | MRR Γ 12 | Calculated | Daily |
| Active Customers | Paying customers with active subscription | CRM | Daily |
| Total Users | Active users on platform | Product analytics | Daily |
| Uptime | System availability % | Monitoring | Real-time |
| Cash Balance | Bank account balance | Banking | Daily |
| Runway | Cash / Monthly Burn | Calculated | Weekly |
| Pipeline | Total value of active opportunities | CRM | Daily |
| Team Size | Full-time equivalent employees | HRIS | Weekly |
| NPS | Net Promoter Score | Survey tool | Monthly |
1.2 Departmental Dashboardsβ
Sales Dashboardβ
| Metric | This Week | MTD | Target | Status |
|---|---|---|---|---|
| New Leads | X | X | X | π’/π‘/π΄ |
| Demos Completed | X | X | X | π’/π‘/π΄ |
| Proposals Sent | X | X | X | π’/π‘/π΄ |
| Deals Closed | X | X | X | π’/π‘/π΄ |
| Revenue Closed | β¬X | β¬X | β¬X | π’/π‘/π΄ |
| Pipeline Value | β¬X | β¬X | β¬X | π’/π‘/π΄ |
| Avg Deal Size | β¬X | β¬X | β¬X | π’/π‘/π΄ |
| Win Rate | X% | X% | X% | π’/π‘/π΄ |
Product Dashboardβ
| Metric | Today | This Week | Target | Status |
|---|---|---|---|---|
| Uptime | X% | X% | 99.9% | π’/π‘/π΄ |
| Response Time | Xms | Xms | <500ms | π’/π‘/π΄ |
| Error Rate | X% | X% | <0.1% | π’/π‘/π΄ |
| DAU | X | X | X | π’/π‘/π΄ |
| Recognition Accuracy | X% | X% | 99% | π’/π‘/π΄ |
| Feature Adoption | X% | X% | 60% | π’/π‘/π΄ |
| Bugs Open | X | X | <20 | π’/π‘/π΄ |
| Sprint Velocity | X | X | X | π’/π‘/π΄ |
Customer Success Dashboardβ
| Metric | This Week | MTD | Target | Status |
|---|---|---|---|---|
| Support Tickets | X | X | <50 | π’/π‘/π΄ |
| Avg Response Time | Xh | Xh | <4h | π’/π‘/π΄ |
| Resolution Time | Xh | Xh | <24h | π’/π‘/π΄ |
| CSAT Score | X | X | 4.5/5 | π’/π‘/π΄ |
| Churn Risk Accounts | X | X | <3 | π’/π‘/π΄ |
| QBRs Completed | X | X | X | π’/π‘/π΄ |
| Expansion Revenue | β¬X | β¬X | β¬X | π’/π‘/π΄ |
Part 2: Tool Stackβ
2.1 Core Toolsβ
| Category | Tool | Purpose | Owner | Cost/Month |
|---|---|---|---|---|
| Communication | Slack | Team messaging | IT | β¬8/user |
| Zoom | Video meetings | IT | β¬15/host | |
| Gmail/Workspace | Email, calendar | IT | β¬12/user | |
| Project Management | Notion | Documentation, wiki | Ops | β¬10/user |
| Linear | Engineering tasks | Eng | β¬8/user | |
| Asana | Cross-team projects | Ops | β¬11/user | |
| CRM & Sales | HubSpot | CRM, marketing | Sales | β¬50/user |
| Apollo | Sales outreach | Sales | β¬50/user | |
| Calendly | Scheduling | Sales | β¬12/user | |
| Finance | QuickBooks | Accounting | Finance | β¬30/mo |
| Stripe | Payments | Finance | 2.9% + β¬0.30 | |
| Expensify | Expenses | Finance | β¬5/user | |
| HR | BambooHR | HRIS | HR | β¬8/user |
| Lever | Recruiting | HR | β¬300/mo | |
| Product | Mixpanel | Analytics | Product | β¬25/mo |
| Hotjar | User feedback | Product | β¬40/mo | |
| Figma | Design | Design | β¬15/user | |
| Engineering | GitHub | Code repository | Eng | β¬4/user |
| AWS | Cloud infrastructure | Eng | Variable | |
| Datadog | Monitoring | Eng | β¬15/host |
2.2 Tool Integration Mapβ
βββββββββββββββ βββββββββββββββ βββββββββββββββ
β HubSpot ββββββΆβ Slack βββββββ Linear β
β (CRM) β β (Comms) β β (Tasks) β
βββββββββββββββ βββββββββββββββ βββββββββββββββ
β β β
βΌ βΌ βΌ
βββββββββββββββ βββββββββββββββ βββββββββββββββ
β QuickBooks β β Notion β β GitHub β
β (Finance) β β (Docs) β β (Code) β
βββββββββββββββ βββββββββββββββ βββββββββββββββ
β β β
βββββββββββββββββββββΌββββββββββββββββββββ
βΌ
βββββββββββββββ
β Dashboard β
β (Metrics) β
βββββββββββββββ
2.3 Tool Ownership & Administrationβ
| Tool | Admin | Backup Admin | Access Levels |
|---|---|---|---|
| Slack | IT Manager | COO | All employees |
| HubSpot | Sales Ops | CMO | Sales, Marketing |
| GitHub | CTO | Lead Dev | Engineering |
| QuickBooks | CFO | Finance Manager | Finance |
| Notion | Ops Manager | COO | All employees |
| AWS | CTO | DevOps Lead | Engineering |
Part 3: Meeting Rhythmβ
3.1 Meeting Calendarβ
Daily Meetingsβ
| Meeting | Time | Duration | Attendees | Purpose |
|---|---|---|---|---|
| Engineering Standup | 9:30 AM | 15 min | Engineering | Daily sync |
| Sales Standup | 10:00 AM | 15 min | Sales | Pipeline review |
Weekly Meetingsβ
| Meeting | Day | Time | Duration | Attendees | Purpose |
|---|---|---|---|---|---|
| Leadership Sync | Monday | 9:00 AM | 60 min | Founders + Leads | Weekly alignment |
| All-Hands | Monday | 4:00 PM | 30 min | All | Company updates |
| Product Review | Tuesday | 2:00 PM | 60 min | Product, Eng, Design | Roadmap review |
| Sales Pipeline | Wednesday | 10:00 AM | 45 min | Sales, CEO | Deal review |
| Customer Success | Thursday | 11:00 AM | 45 min | CS, Product | Customer health |
| Engineering Retro | Friday | 3:00 PM | 60 min | Engineering | Sprint retro |
Monthly Meetingsβ
| Meeting | Week | Duration | Attendees | Purpose |
|---|---|---|---|---|
| Board Prep | Week 4 | 2 hours | Founders | Board meeting prep |
| Monthly Business Review | Week 1 | 2 hours | Leadership | Performance review |
| Town Hall | Week 2 | 1 hour | All | Deep dive topic |
| 1:1s | Ongoing | 30 min | Manager + Report | Individual check-in |
Quarterly Meetingsβ
| Meeting | Duration | Attendees | Purpose |
|---|---|---|---|
| Board Meeting | 3 hours | Board + Founders | Governance |
| OKR Planning | 4 hours | Leadership | Goal setting |
| Strategy Review | Half day | Leadership | Strategic planning |
| Team Offsite | 1-2 days | All | Team building |
3.2 Meeting Templatesβ
Leadership Sync Agendaβ
## Leadership Sync - [Date]
### Attendees
[Names]
### Agenda (60 min)
#### 1. Wins & Celebrations (5 min)
- [Win 1]
- [Win 2]
#### 2. Key Metrics Review (10 min)
| Metric | Actual | Target | Status |
|--------|--------|--------|--------|
| MRR | | | |
| Pipeline | | | |
| Uptime | | | |
#### 3. Department Updates (20 min)
- **Sales:** [Update]
- **Product:** [Update]
- **Engineering:** [Update]
- **Customer Success:** [Update]
- **Operations:** [Update]
#### 4. Blockers & Decisions (15 min)
| Issue | Owner | Decision Needed |
|-------|-------|-----------------|
| | | |
#### 5. Action Items (10 min)
| Action | Owner | Due |
|--------|-------|-----|
| | | |
### Next Meeting: [Date]
All-Hands Agendaβ
## All-Hands - [Date]
### Agenda (30 min)
#### 1. Welcome & Celebrations (5 min)
- New team members
- Anniversaries
- Wins
#### 2. Company Update (10 min)
- Key metrics
- Progress on goals
- Important news
#### 3. Department Spotlight (10 min)
- [Department] deep dive
#### 4. Q&A (5 min)
- Open questions
### Recording: [Link]
### Slides: [Link]
3.3 Meeting Best Practicesβ
Before the Meetingβ
- Clear agenda shared 24 hours in advance
- Pre-read materials distributed
- Right attendees invited
- Technology tested
During the Meetingβ
- Start on time
- Assign note-taker
- Follow agenda
- Capture action items
- End on time
After the Meetingβ
- Notes shared within 24 hours
- Action items assigned with due dates
- Follow-up scheduled if needed
- Recording posted (if applicable)
Part 4: Process Documentationβ
4.1 Core Business Processesβ
Process Inventoryβ
| Process | Owner | Documentation | Last Updated | Status |
|---|---|---|---|---|
| Customer Onboarding | CS Lead | [Link] | [Date] | β Current |
| Sales Qualification | Sales Lead | [Link] | [Date] | β Current |
| Bug Reporting | Eng Lead | [Link] | [Date] | β οΈ Needs Update |
| Expense Approval | CFO | [Link] | [Date] | β Current |
| Hiring Process | HR Lead | [Link] | [Date] | β Current |
| Release Management | CTO | [Link] | [Date] | β οΈ Needs Update |
| Incident Response | CTO | [Link] | [Date] | β Current |
| Customer Escalation | CS Lead | [Link] | [Date] | β Current |
| Contract Review | CFO | [Link] | [Date] | β Current |
| Vendor Onboarding | Ops | [Link] | [Date] | β¬ Not Documented |
4.2 Process Documentation Templateβ
## Process: [Process Name]
### Overview
**Purpose:** [Why this process exists]
**Owner:** [Role responsible]
**Last Updated:** [Date]
**Review Frequency:** [Quarterly/Annually]
### Scope
**Applies to:** [Who uses this process]
**Triggers:** [What initiates this process]
**Outputs:** [What this process produces]
### Process Steps
#### Step 1: [Step Name]
**Owner:** [Role]
**Timeline:** [Duration]
**Tools:** [Systems used]
**Actions:**
1. [Action 1]
2. [Action 2]
3. [Action 3]
**Outputs:**
- [Output 1]
- [Output 2]
#### Step 2: [Step Name]
[Same structure]
### Process Flow Diagram
[Visual flowchart]
### Exceptions
| Scenario | Handling |
|----------|----------|
| [Exception 1] | [How to handle] |
| [Exception 2] | [How to handle] |
### Metrics
| Metric | Target | Current |
|--------|--------|---------|
| [Metric 1] | [Target] | [Actual] |
| [Metric 2] | [Target] | [Actual] |
### Related Documents
- [Document 1]
- [Document 2]
### Change Log
| Date | Change | Author |
|------|--------|--------|
| [Date] | [Change] | [Name] |
4.3 Key Process Documentationβ
Customer Onboarding Processβ
## Process: Customer Onboarding
### Overview
**Purpose:** Ensure new customers successfully implement CheckMet and achieve first value
**Owner:** Customer Success Lead
**Timeline:** 2-4 weeks
**Success Criteria:** Customer actively using product, <5 support tickets
### Process Steps
#### Step 1: Kickoff (Day 1-2)
**Owner:** Customer Success Manager
**Timeline:** 2 days
**Actions:**
1. Send welcome email with onboarding guide
2. Schedule kickoff call
3. Conduct kickoff call:
- Introduce team
- Confirm success criteria
- Review timeline
- Assign customer champion
4. Create customer Slack channel (if applicable)
**Outputs:**
- Kickoff notes documented
- Success plan created
- Timeline confirmed
#### Step 2: Technical Setup (Day 3-7)
**Owner:** Solutions Engineer
**Timeline:** 5 days
**Actions:**
1. Provision customer environment
2. Configure settings per requirements
3. Set up HRIS integration
4. Import employee data
5. Configure access controls
6. Test system functionality
**Outputs:**
- Environment ready
- Integration working
- Test results documented
#### Step 3: Training (Day 8-14)
**Owner:** Customer Success Manager
**Timeline:** 5 days
**Actions:**
1. Schedule admin training
2. Conduct admin training session
3. Provide training materials
4. Schedule end-user training
5. Conduct end-user training
6. Share self-service resources
**Outputs:**
- Admins trained
- Users trained
- Training completion tracked
#### Step 4: Go-Live (Day 15-21)
**Owner:** Customer Success Manager
**Timeline:** 7 days
**Actions:**
1. Confirm go-live readiness
2. Support go-live day
3. Monitor initial usage
4. Address immediate issues
5. Daily check-ins first week
6. Collect initial feedback
**Outputs:**
- System live
- Users active
- Issues resolved
#### Step 5: Handoff (Day 22-28)
**Owner:** Customer Success Manager
**Timeline:** 7 days
**Actions:**
1. Conduct 30-day review
2. Confirm success criteria met
3. Transition to ongoing support
4. Schedule first QBR
5. Request NPS feedback
6. Document lessons learned
**Outputs:**
- Success confirmed
- QBR scheduled
- NPS collected
### Metrics
| Metric | Target | Current |
|--------|--------|---------|
| Time to First Value | <14 days | X days |
| Onboarding Completion | 100% | X% |
| 30-Day Adoption | 80%+ | X% |
| Onboarding NPS | 50+ | X |
| Support Tickets (first 30 days) | <5 | X |
Part 5: Operational Metricsβ
5.1 Operational KPIsβ
| Category | Metric | Definition | Target | Owner |
|---|---|---|---|---|
| Efficiency | Revenue per Employee | Total Revenue / FTE | β¬40K+ | CFO |
| Cost per Customer | Total Costs / Customers | <β¬5K | CFO | |
| Process Cycle Time | Time to complete key processes | Varies | Ops | |
| Quality | First Contact Resolution | % issues resolved first contact | 80%+ | CS |
| Error Rate | Errors / Total transactions | <1% | Ops | |
| Customer Effort Score | Ease of doing business | <3 | CS | |
| Reliability | System Uptime | Available time / Total time | 99.9% | Eng |
| SLA Compliance | % SLAs met | 95%+ | CS | |
| On-Time Delivery | Projects delivered on time | 90%+ | Ops |
5.2 Operational Health Checkβ
## Weekly Operational Health Check
### Date: [Date]
### Reviewer: [Name]
### System Health
| System | Status | Issues | Actions |
|--------|--------|--------|---------|
| CheckMet Platform | π’/π‘/π΄ | | |
| Website | π’/π‘/π΄ | | |
| Email/Calendar | π’/π‘/π΄ | | |
| CRM | π’/π‘/π΄ | | |
| Billing | π’/π‘/π΄ | | |
### Process Health
| Process | Status | Bottlenecks | Actions |
|---------|--------|-------------|---------|
| Customer Onboarding | π’/π‘/π΄ | | |
| Sales Cycle | π’/π‘/π΄ | | |
| Support Response | π’/π‘/π΄ | | |
| Hiring | π’/π‘/π΄ | | |
### Resource Utilization
| Resource | Capacity | Utilization | Status |
|----------|----------|-------------|--------|
| Engineering | X FTE | X% | π’/π‘/π΄ |
| Sales | X FTE | X% | π’/π‘/π΄ |
| CS | X FTE | X% | π’/π‘/π΄ |
### Key Issues
1. [Issue 1] - [Owner] - [Status]
2. [Issue 2] - [Owner] - [Status]
### Actions for Next Week
1. [Action 1] - [Owner]
2. [Action 2] - [Owner]
Part 6: Incident Managementβ
6.1 Incident Severity Levelsβ
| Level | Definition | Response Time | Examples |
|---|---|---|---|
| P0 - Critical | Complete service outage | 15 min | Platform down, data breach |
| P1 - High | Major feature unavailable | 1 hour | Recognition failing, integrations down |
| P2 - Medium | Feature degraded | 4 hours | Slow performance, minor bugs |
| P3 - Low | Minor issue | 24 hours | UI glitches, documentation errors |
6.2 Incident Response Processβ
## Incident Response Playbook
### Phase 1: Detection & Triage (0-15 min)
1. Incident detected (monitoring, customer report, internal)
2. Create incident channel: #incident-[date]-[brief-description]
3. Assign Incident Commander (on-call engineer)
4. Determine severity level
5. Notify stakeholders per severity
### Phase 2: Investigation (15-60 min)
1. Gather initial information
2. Identify affected systems/customers
3. Determine root cause hypothesis
4. Document findings in incident channel
### Phase 3: Mitigation (Ongoing)
1. Implement temporary fix if possible
2. Communicate status to stakeholders
3. Update status page (if customer-facing)
4. Continue investigation
### Phase 4: Resolution
1. Implement permanent fix
2. Verify fix is working
3. Monitor for recurrence
4. Update stakeholders
### Phase 5: Post-Mortem (Within 48 hours)
1. Schedule post-mortem meeting
2. Document timeline
3. Identify root cause
4. Define action items
5. Share learnings
6.3 Post-Mortem Templateβ
## Incident Post-Mortem
### Incident Summary
- **Date:** [Date]
- **Duration:** [X hours/minutes]
- **Severity:** [P0/P1/P2/P3]
- **Incident Commander:** [Name]
- **Customers Affected:** [Number]
### Timeline
| Time | Event |
|------|-------|
| HH:MM | [Event 1] |
| HH:MM | [Event 2] |
| HH:MM | [Event 3] |
### Impact
- **Users affected:** [Number]
- **Revenue impact:** β¬[Amount]
- **Reputation impact:** [Description]
### Root Cause
[Detailed explanation of what caused the incident]
### What Went Well
1. [Item 1]
2. [Item 2]
### What Went Wrong
1. [Item 1]
2. [Item 2]
### Action Items
| Action | Owner | Priority | Due Date | Status |
|--------|-------|----------|----------|--------|
| [Action 1] | [Name] | P1 | [Date] | β¬ |
| [Action 2] | [Name] | P2 | [Date] | β¬ |
### Lessons Learned
1. [Lesson 1]
2. [Lesson 2]
### Prevention Measures
1. [Measure 1]
2. [Measure 2]
Part 7: Vendor Managementβ
7.1 Vendor Inventoryβ
| Vendor | Category | Contract Value | Renewal Date | Owner | Criticality |
|---|---|---|---|---|---|
| AWS | Infrastructure | β¬X/month | [Date] | CTO | Critical |
| HubSpot | CRM | β¬X/month | [Date] | Sales | High |
| Slack | Communication | β¬X/month | [Date] | IT | High |
| [Vendor] | [Category] | β¬X/month | [Date] | [Owner] | [Level] |
7.2 Vendor Evaluation Criteriaβ
| Criteria | Weight | Scoring (1-5) |
|---|---|---|
| Functionality | 25% | Does it meet our needs? |
| Cost | 20% | Is it cost-effective? |
| Integration | 15% | Does it integrate with our stack? |
| Support | 15% | Is support responsive? |
| Security | 15% | Does it meet security requirements? |
| Scalability | 10% | Will it grow with us? |
7.3 Vendor Review Processβ
Annual Review Checklist:
- Review contract terms and pricing
- Assess vendor performance
- Evaluate alternatives
- Negotiate renewal terms
- Update vendor documentation
Part 8: Continuous Improvementβ
8.1 Process Improvement Frameworkβ
Improvement Identificationβ
| Source | Frequency | Owner |
|---|---|---|
| Team retrospectives | Bi-weekly | Team Leads |
| Customer feedback | Ongoing | CS |
| Incident post-mortems | Per incident | Eng |
| Operational reviews | Monthly | Ops |
| Employee suggestions | Ongoing | HR |
Improvement Prioritizationβ
| Factor | Weight | Scoring |
|---|---|---|
| Impact | 40% | How much will it improve? |
| Effort | 30% | How hard to implement? |
| Urgency | 20% | How soon is it needed? |
| Risk | 10% | What could go wrong? |
8.2 Improvement Trackingβ
## Process Improvement Log
| ID | Improvement | Category | Priority | Owner | Status | Impact |
|----|-------------|----------|----------|-------|--------|--------|
| 001 | Automate onboarding emails | CS | High | [Name] | β
Done | -2 hrs/week |
| 002 | Standardize sales proposals | Sales | Medium | [Name] | π In Progress | |
| 003 | Add monitoring alerts | Eng | High | [Name] | β¬ Planned | |
Document Version: 1.0 Last Updated: December 2024 Owner: COO Review Cycle: Quarterly