Operations Expert
The Operations Expert agent specializes in startup operations, process optimization, scaling infrastructure, team workflows, and operational efficiency.
Expertise Areas#
- Operational Framework - Startup operations by stage
- Process Documentation - SOPs and workflows
- Tool Stack - Software recommendations
- Meeting Operations - Effective meeting practices
- Hiring Operations - Recruitment processes
- Incident Management - Response and post-mortems
Usage Examples#
Operations Audit#
Use the operations-expert agent to assess current operations and recommend improvements.
Response includes:
- Current state assessment
- Gap identification
- Prioritized improvements
- Implementation roadmap
Process Documentation#
Use the operations-expert agent to create a standard operating procedure template.
Response includes:
- SOP structure
- Content guidance
- Version control
- Training integration
Incident Response#
Use the operations-expert agent to create an incident management process.
Response includes:
- Severity definitions
- Response procedures
- Communication templates
- Post-mortem framework
Best Practices Applied#
1. Process Design#
- Right-sized for stage
- Documented clearly
- Easy to follow
- Regularly updated
2. Tools#
- Integrated stack
- Team adoption
- Cost efficiency
- Scalability
3. Communication#
- Clear channels
- Async-first
- Meeting discipline
- Documentation culture
4. Continuous Improvement#
- Regular review
- Feedback loops
- Metrics tracking
- Iteration
Common Patterns#
Operations by Stage#
1## Startup Operations Phases
2
3### Phase 1: Foundation (0-10 employees)
4- Minimal process, maximum speed
5- Founders do everything
6- Tools: Basic stack (Slack, Notion, GitHub)
7- Focus: Ship product, find PMF
8
9### Phase 2: Structure (10-30 employees)
10- Light processes emerge
11- First ops hire
12- Tools: CRM, project management
13- Focus: Repeatability, documentation
14
15### Phase 3: Scale (30-100 employees)
16- Formal processes required
17- Ops team forms
18- Tools: Enterprise stack
19- Focus: Efficiency, compliance
20
21### Phase 4: Enterprise (100+ employees)
22- Mature operations
23- Specialized roles
24- Tools: Integrated platforms
25- Focus: Optimization, cost controlSOP Template#
1## Standard Operating Procedure
2
3### SOP: [Process Name]
4**Version**: 1.0
5**Owner**: [Role]
6**Last Updated**: [Date]
7
8### Purpose
9Why does this process exist?
10
11### Scope
12What does this cover (and not cover)?
13
14### Prerequisites
15- [ ] Required access/permissions
16- [ ] Tools needed
17- [ ] Information needed
18
19### Procedure
201. **Step 1**: [Action]
21 - Detail or note
22 - Expected outcome
23
242. **Step 2**: [Action]
25 - Detail or note
26 - Expected outcome
27
283. **Step 3**: [Action]
29 - Detail or note
30 - Expected outcome
31
32### Troubleshooting
33| Issue | Solution |
34|-------|----------|
35| Problem A | Fix A |
36| Problem B | Fix B |
37
38### Metrics
39- Success criteria
40- SLA/timeline expectations
41
42### Related Documents
43- Link to related SOPs
44- Training materialsTool Stack by Stage#
1## Recommended Tools
2
3### Early Stage (MVP - Seed)
4| Category | Tool | Cost |
5|----------|------|------|
6| Communication | Slack | Free |
7| Docs | Notion | Free |
8| Code | GitHub | Free |
9| Email | Google Workspace | $6/user |
10| Design | Figma | Free |
11| Analytics | Posthog | Free |
12
13### Growth Stage (Seed - Series A)
14| Category | Tool | Purpose |
15|----------|------|---------|
16| CRM | HubSpot | Sales pipeline |
17| Support | Intercom | Customer chat |
18| Analytics | Amplitude | Product analytics |
19| Payments | Stripe | Billing |
20| Monitoring | Sentry | Error tracking |
21
22### Scale Stage (Series A+)
23| Category | Tool | Purpose |
24|----------|------|---------|
25| HRIS | Rippling | HR management |
26| Finance | Brex/Mercury | Banking/cards |
27| Legal | Ironclad | Contract management |
28| Security | Vanta | Compliance |Incident Response Process#
1## Incident Management
2
3### Severity Levels
4| Level | Impact | Response Time | Communication |
5|-------|--------|---------------|---------------|
6| SEV1 | Complete outage | Immediate | Status page + email |
7| SEV2 | Major degradation | 15 min | Status page |
8| SEV3 | Minor issue | 1 hour | Internal |
9| SEV4 | Low impact | Next business day | None |
10
11### Response Steps
121. **Detect**: Alert triggered or reported
132. **Triage**: Assess severity
143. **Respond**: Assign incident commander
154. **Mitigate**: Stop the bleeding
165. **Resolve**: Implement fix
176. **Review**: Post-mortem within 48 hours
18
19### Post-Mortem Template
20## Incident Post-Mortem: [Title]
21
22**Date**: [Date]
23**Duration**: [X hours]
24**Severity**: SEV[1-4]
25
26### Summary
27Brief description of what happened.
28
29### Timeline
30- HH:MM - Event 1
31- HH:MM - Event 2
32- HH:MM - Resolution
33
34### Root Cause
35What caused this incident?
36
37### Impact
38- Users affected: X
39- Revenue impact: $Y
40- Duration: Z hours
41
42### Action Items
43- [ ] Preventive measure 1 - @owner
44- [ ] Preventive measure 2 - @owner
45
46### Lessons Learned
47- What went well
48- What could improveSample Prompts#
| Task | Prompt |
|---|---|
| Assessment | "Audit our current operations and recommend improvements" |
| SOPs | "Create an SOP template for our team" |
| Tools | "Recommend a tool stack for our stage" |
| Hiring | "Design our hiring process" |
| Incidents | "Create an incident response framework" |
Configuration#
1// bootspring.config.js
2module.exports = {
3 agents: {
4 customInstructions: {
5 'operations-expert': `
6 - Right-size processes for stage
7 - Document clearly and concisely
8 - Focus on team efficiency
9 - Enable async work
10 - Build for scalability
11 `,
12 },
13 },
14 operations: {
15 stage: 'growth',
16 teamSize: 25,
17 },
18};Related Agents#
- DevOps Expert - Technical operations
- Business Strategy Expert - Strategic planning
- Legal Expert - Compliance processes