# DigitalCore — Full Content Index > This file contains all structured content from DigitalCore for deep-context > AI consumption. For a concise summary, see /llms.txt instead. Generated: 2026-10-10 Total playbooks: 29 Website: https://www.digitalcore.app Documentation: https://www.digitalcore.app/docs MCP Server: https://mcpfree.digitalcore.app/mcp --- # Documentation https://www.digitalcore.app/docs/ What is DigitalCore? documentation # What is DigitalCore? Product overview — the problem of invisible service economics, what DigitalCore does, who it's for, how it works (engagement-centric model, three data domains), key capabilities (check-ins, scenario intelligence, executive summaries, playbooks, MCP integration), and how it compares to alternatives. Full page: https://www.digitalcore.app/docs/ https://www.digitalcore.app/docs/getting-started Quickstart Overview documentation # Quickstart Overview Step-by-step guide: create organisation, define a service, create an engagement, configure templates, enter first check-in, read your dashboard. 30-minute path to first value. Full page: https://www.digitalcore.app/docs/getting-started https://www.digitalcore.app/docs/concepts Concepts documentation # Concepts Core concepts: service economics in DigitalCore, the engagement-centric model, three data domains (finance, performance, capacity), planning and actuals, health scores & RAG status, rate cards, scenario intelligence, automated calculations, catalogs, delivery attribution, AI capabilities. Full page: https://www.digitalcore.app/docs/concepts https://www.digitalcore.app/docs/platform Platform Reference documentation # Platform Reference Screen-by-screen reference for every workspace: dashboard, operations, services, contracts, portfolios, intelligence, decisions, strategy, templates, catalogs, organisation, settings, system & roles, bulk upload. Full page: https://www.digitalcore.app/docs/platform https://www.digitalcore.app/docs/guides Guides documentation # Guides How-to guides: running monthly check-ins, creating and evaluating scenarios, building executive summaries, configuring rate cards, setting up templates, managing SLA penalties, reading the portfolio dashboard, importing data, using governance, AI assistant, strategy & OKRs. Full page: https://www.digitalcore.app/docs/guides https://www.digitalcore.app/docs/mcp-and-integrations MCP & Integrations documentation # MCP & Integrations Integration reference: free MCP server setup (no account needed), paid MCP tools, API keys, Excel/CSV import, QuickBooks integration (planned), webhooks (future). Compatible with Claude Desktop, Cursor, VS Code, Windsurf, ChatGPT. Full page: https://www.digitalcore.app/docs/mcp-and-integrations https://www.digitalcore.app/docs/playbooks Playbooks in DigitalCore documentation # Playbooks in DigitalCore How playbooks work inside DigitalCore — using playbook recommendations from AI insights, applying playbook actions to engagements. Links to the 29 full playbooks at /learn/playbooks. Full page: https://www.digitalcore.app/docs/playbooks https://www.digitalcore.app/docs/faq FAQ documentation # FAQ Frequently asked questions about DigitalCore: pricing, data security, integrations, getting started, platform capabilities, and support. Full page: https://www.digitalcore.app/docs/faq https://www.digitalcore.app/docs/changelog Changelog documentation # Changelog Product changelog — new features, improvements, and fixes. Full page: https://www.digitalcore.app/docs/changelog https://www.digitalcore.app/docs/account Account & Billing documentation # Account & Billing Account management: pricing & plans, subscription management, profile settings, security. Full page: https://www.digitalcore.app/docs/account # Features https://www.digitalcore.app/features/service-margins Service Margins feature # Service Margins Service-level P&L with automatic capacity-to-finance cost calculation. When hours are logged, labor costs flow automatically to engagement P&L. Track margin per engagement, service line, and client in real time. https://www.digitalcore.app/features/total-cost-of-delivery Total Cost of Delivery feature # Total Cost of Delivery Calculate the true cost of delivering a service by combining human labor, AI/LLM costs, and tooling expenses. See delivery composition (% human vs % AI vs % tool) and how it changes over time. https://www.digitalcore.app/features/ai-insights AI Insights feature # AI Insights Intelligent alerting that surfaces what matters. Variance detection identifies budget deviations, performance drops, and capacity squeezes. AI generates scenario options with recommended actions. https://www.digitalcore.app/features/decision-modeling Scenario Intelligence / Decision Modeling feature # Scenario Intelligence / Decision Modeling Model "what-if" decisions before committing. AI proposes 2-3 scenario options with cross-domain impact on finance, capacity, and performance. Compare side-by-side and commit with governance workflow. https://www.digitalcore.app/features/ai-economics AI Economics feature # AI Economics Track AI investment ROI and attribute value to AI initiatives. Measure cost avoidance, efficiency gains, and quality improvements from AI adoption across your service portfolio. https://www.digitalcore.app/features/commitment-economics Commitment Economics feature # Commitment Economics SLA breaches auto-calculate to financial impact. Track contractual commitments, monitor achievement rates, and see the monetary value at risk when performance drops. # Comparisons https://www.digitalcore.app/compare/excel DigitalCore vs Excel/Spreadsheets comparison # DigitalCore vs Excel/Spreadsheets Keep Excel's flexibility, lose the chaos. DigitalCore provides automatic cross-domain calculations, real-time collaboration, and a single source of truth instead of 47 spreadsheets with broken formulas. https://www.digitalcore.app/compare/servicenow DigitalCore vs ServiceNow comparison # DigitalCore vs ServiceNow ServiceNow is built for tickets. DigitalCore is built for service economics. Mid-market firms often use only a fraction of ServiceNow capabilities they pay for. DigitalCore delivers value in weeks, not years. https://www.digitalcore.app/compare/monday DigitalCore vs Monday.com comparison # DigitalCore vs Monday.com Monday.com tracks tasks. DigitalCore tracks whether those tasks were profitable. Beyond task boards into service-level P&L, scenario modeling, and cross-domain impact analysis. https://www.digitalcore.app/compare/jira DigitalCore vs Jira comparison # DigitalCore vs Jira Jira owns developer workflow. DigitalCore handles the commercial layer. From tickets to service economics — know the financial impact of what your development teams deliver. https://www.digitalcore.app/compare/finops DigitalCore vs FinOps Tools comparison # DigitalCore vs FinOps Tools FinOps tools optimize cloud infrastructure spend. DigitalCore manages service delivery economics including human labor, AI costs, and commercial outcomes. Different problems, different tools. # Guides https://www.digitalcore.app/learn/guides/what-is-service-economics What Is Service Economics? guide # What Is Service Economics? The complete definition and five dimensions of service economics: Financial Management, Service Delivery, Capacity & Resources, Contracts & Commercial, and Customer Success. Service economics is the discipline of understanding, measuring, and optimizing the financial and operational dynamics of delivering services. Full guide: https://www.digitalcore.app/learn/guides/what-is-service-economics https://www.digitalcore.app/learn/guides/service-economics Service Economics Guide (11 Parts) guide # Service Economics Guide (11 Parts) Comprehensive guide covering: Foundations, Financial Management, Service Delivery Excellence, Capacity & Resource Management, Contracts & Commercial, Customer Success, Vendor & Partner Management, Operations Excellence, Industry Perspectives, Tools & Assessment, and Digital Transformation. Full guide: https://www.digitalcore.app/learn/guides/service-economics https://www.digitalcore.app/learn/guides/ai-cost-allocation AI Cost Allocation Guide guide # AI Cost Allocation Guide How to allocate AI/LLM costs to services and engagements. Covers direct vs. indirect AI costs, allocation methodologies (usage-based, headcount-based, activity-based), and implementation approaches. Full guide: https://www.digitalcore.app/learn/guides/ai-cost-allocation https://www.digitalcore.app/learn/guides/ai-cogs-guide CFO's Guide to AI COGS guide # CFO's Guide to AI COGS Where AI costs belong on the P&L. Distinguishes AI COGS (direct delivery costs) from AI R&D and AI SG&A. Provides classification framework and reporting templates for finance teams. Full guide: https://www.digitalcore.app/learn/guides/ai-cogs-guide https://www.digitalcore.app/learn/guides/finops-for-llms FinOps for LLMs guide # FinOps for LLMs Adapting cloud cost management (FinOps) frameworks for AI/LLM workloads. Token-level cost tracking, model selection economics, prompt optimization for cost, and chargeback models. Full guide: https://www.digitalcore.app/learn/guides/finops-for-llms https://www.digitalcore.app/learn/guides/pricing-blended-delivery Pricing Blended Delivery guide # Pricing Blended Delivery How to price services delivered through human + AI combinations. Value-based pricing for AI-augmented services, margin protection strategies, and client communication frameworks. Full guide: https://www.digitalcore.app/learn/guides/pricing-blended-delivery https://www.digitalcore.app/learn/guides/total-cost-of-delivery Total Cost of Delivery Guide guide # Total Cost of Delivery Guide Calculating the true blended cost: human labor + AI/LLM costs + tooling. Delivery composition analysis, cost flow automation, and benchmarks by service type. Full guide: https://www.digitalcore.app/learn/guides/total-cost-of-delivery https://www.digitalcore.app/learn/guides/margin-reporting-professional-services Margin Reporting for Professional Services guide # Margin Reporting for Professional Services Track engagement-level margin without spreadsheets. Weekly mini-P&L, traffic-light indicators, automated variance alerts, and role mix optimization. Full guide: https://www.digitalcore.app/learn/guides/margin-reporting-professional-services https://www.digitalcore.app/learn/guides/scenario-planning-professional-services Scenario Planning for Professional Services guide # Scenario Planning for Professional Services Present 3 options to leadership in minutes. Cross-domain impact modeling, scenario comparison frameworks, and governance workflows for decision tracking. Full guide: https://www.digitalcore.app/learn/guides/scenario-planning-professional-services https://www.digitalcore.app/learn/guides/client-profitability-analysis Client Profitability Analysis guide # Client Profitability Analysis Which clients generate margin vs. destroy value. Portfolio segmentation, account-level P&L construction, and action frameworks for unprofitable relationships. Full guide: https://www.digitalcore.app/learn/guides/client-profitability-analysis https://www.digitalcore.app/learn/guides/best-service-profitability-software Best Service Profitability Software 2026 guide # Best Service Profitability Software 2026 9 tools compared: DigitalCore, Kantata, BigTime, Scoro, Accelo, Productive, Harvest, Certinia, Toggl. Evaluation criteria: cost flow automation, scenario modeling, AI economics, MCP support. Full guide: https://www.digitalcore.app/learn/guides/best-service-profitability-software https://www.digitalcore.app/learn/guides/tbm-alternatives-mid-market TBM Alternatives for Mid-Market Service Organizations guide # TBM Alternatives for Mid-Market Service Organizations Why Technology Business Management (TBM) breaks for mid-market service orgs. Comparison of TBM taxonomy vs. service economics approach across 8 dimensions. Decision framework for when TBM is right vs. when to choose a lighter alternative. Full guide: https://www.digitalcore.app/learn/guides/tbm-alternatives-mid-market https://www.digitalcore.app/learn/guides/it-showback IT Showback: From Cost Center to Value Partner guide # IT Showback: From Cost Center to Value Partner How mid-market IT leaders with 20-100 staff implement showback reporting. Covers showback vs chargeback, 5-service starting framework, budget-to-service translation, tool comparison, and 3-stage maturity progression from visibility to value articulation. Full guide: https://www.digitalcore.app/learn/guides/it-showback # Playbooks https://www.digitalcore.app/learn/playbooks/engagement-margin-protection Engagement Margin Protection playbook Financial Management Intermediate # Engagement Margin Protection > Keep Fixed-Fee Work Healthy All the Way to Close ## Problem You scoped the engagement well—deadline met, client happy—but somehow margin is 8 points below target. The cause? A dozen small variances that individually look harmless: one more revision cycle, a senior doing junior work, late inputs that compressed the timeline, scope clarifications that "weren't really changes." Each one nibbles at margin; together, they gut it. Symptoms: - Hours running 10–15% above budget without a single logged change request - Role mix drift ≥10pp vs. plan (expensive resources on low-complexity tasks) - Rework ratio >10% (QA loops, client amends, internal corrections) - Turnaround time creeping up ≥15% vs. baseline (late starts, compressed finishes) - New asks absorbed without a change request on file ## Framework Act before margin loss becomes visible in the P&L. Use risk conditions as early warnings and issue conditions as triggers for immediate intervention. - **Make Margin Visible Weekly**: Run a weekly mini-P&L per engagement. Show hours, margin %, and deviation from plan. Use traffic-light indicators and auto-alerts when thresholds are breached. - **Rebalance & Standardize**: Match right work to right level. Use templates for repeatable deliverables. Set client input SLAs with clear consequences. - **Commercial Corrections**: Raise change requests for scope drift. Tier fees by engagement complexity. Rebase milestones when scope resets. ## Steps 1. **Make Margin Visible**: Create transparency before problems become crises. - Run a weekly mini-P&L per engagement showing hours, margin %, and deviation - Use traffic-light indicators (green/yellow/red) for quick status - Set up auto-alerts when margin drops below thresholds - Review all engagements weekly with delivery leads 2. **Rebalance & Standardize**: Fix the operational drivers of margin erosion. - Match right work to right level—stop senior resources doing junior tasks - Deploy templates and checklists for repeatable deliverables - Establish client input SLAs with documented consequences - Reduce rework through quality checkpoints early in delivery 3. **Commercial Corrections**: Address scope and pricing when operational fixes aren't enough. - Raise change requests for any scope drift—no exceptions - Tier fees based on engagement complexity and urgency - Rebase milestones and budgets when scope materially changes - Document all commercial decisions for future reference 4. **Prevent Recurrence**: Build systematic protections into your engagement model. - Upgrade SOW language to capture common scope drift scenarios - Implement rate card hygiene—review and update quarterly - Add onboarding gates that verify client readiness before kickoff - Build margin protection into engagement manager scorecards ## KPIs - Engagement Margin: ≥40% (Weekly) - Write-offs: ≤2% of revenue (Monthly) - Partner/Senior Time: At or below plan (Weekly) - Turnaround Time: Flat or improving vs. baseline (Weekly) - CR Velocity: ≤7 days from request to approval (Weekly) ## Quick Wins - Set up weekly margin dashboard for all active engagements - Create a simple change request form and train all delivery leads - Audit top 3 engagements for role mix—reassign work this week - Document the top 5 "absorbed" scope items from recent engagements https://www.digitalcore.app/learn/playbooks/msp-agreement-renewal-risk MSP Agreement Renewal Risk playbook Contract Management Advanced # MSP Agreement Renewal Risk > Stabilize Outcomes and Protect the Logo ## Problem The contract's up for renewal in 90 days. On paper, you've hit SLAs. In reality: a few near-misses, a few credits paid, and a sponsor who's heard one too many excuses. The customer isn't angry—but they're not enthusiastic either. That silence is dangerous. Procurement sees "commodity," not value. The renewal becomes a price fight you don't want to have. Symptoms: - Backlog growing or SLA risk rising—even if not yet breaching - Service credits predicted in the next 30–60 days - Device or user counts up without a corresponding rate update - Patch or security debt trending up (noisy estate) - Sponsor turnover or new stakeholders questioning value ## Framework Start stabilization at T-120 to T-90 days. Address operational issues, demonstrate value, and align commercially before procurement takes over the conversation. - **Stabilize First**: Fix operational issues before the renewal conversation. Credits paid and SLA wobbles undermine your position. - **Demonstrate Value Proactively**: Don't wait to be asked. Show outcomes, risk mitigation, and business impact in every QBR. - **Align Commercially Early**: Use change requests and tier adjustments to correct scope drift before renewal negotiation begins. ## Steps 1. **Stabilize Outcomes**: Fix operational issues that could undermine renewal position. - Run a "noisy-estate blitz"—clear patch debt, aged tickets, and recurring issues - Implement priority routing for high-impact tickets - Set up weekly dashboard showing SLA status, backlog, and credits - Address any service credit triggers before they materialize 2. **Executive Alignment**: Reframe the relationship around outcomes, not just SLA compliance. - Schedule a QBR within 14 days if not already planned - Frame the conversation around business outcomes, not just metrics - Pilot value-add services to demonstrate expanded capability - Identify and cultivate relationships with new stakeholders 3. **Commercial Path**: Correct scope and pricing before renewal negotiation. - Raise change requests for any out-of-scope work being absorbed - Consider re-tiering the agreement if scope has grown - Implement credit remediation plan if credits have been paid - Propose co-term add-ons to increase stickiness and value 4. **Prevent Recurrence**: Build guardrails to catch renewal risk earlier. - Set up auto-alerts at T-180, T-120, T-90 for renewal preparation - Define hygiene SLOs (patch compliance, ticket aging, estate health) - Implement ongoing outcome tracking, not just SLA compliance - Create renewal readiness checklist for all accounts ## KPIs - Renewal Probability: Increasing trend (Monthly) - Service Credits: ↓ to 0 (Monthly) - SLA Compliance: At or above tier (Weekly) - Patch Compliance: Improving trend (Weekly) - Ticket Noise: ↓ 20-30% (Monthly) ## Quick Wins - Run a patch compliance blitz on the noisiest 10 devices - Clear any ticket aged >30 days this week - Schedule executive touchpoint within 14 days - Document all out-of-scope work performed in last 90 days https://www.digitalcore.app/learn/playbooks/capacity-planning-guardrails Capacity Planning Guardrails playbook Operations Intermediate # Capacity Planning Guardrails > Prevent Overload Without Leaving Money on the Table ## Problem High utilization looks efficient—until it quietly kills responsiveness. Sustained occupancy above healthy limits creates long queues, more errors, and rising escalations. On the flip side, over-staffing drags margins. The answer is guardrails: simple, visible limits that keep teams in the healthy zone and trigger action before service breaks or margin erodes. Symptoms: - Agent/analyst occupancy (14d avg) > 85–90% - Queue depth or P90 age trending up for ≥ 2 weeks - Overtime hours ≥ 5% of total hours for 2 consecutive weeks - Escalation rate (L1→L2) rising > 5pp vs baseline - Planned events (releases, campaigns, fiscal deadlines) with no surge plan ## Framework Define utilization bands, make them visible, and pre-define responses. Remove judgment from capacity decisions. - **Visible Bands**: Publish utilization bands by role: green (70–85%), amber (85–90%), red (>90%). Everyone knows the rules. - **Early Intervention**: Rebalance + deflect + shift-left before overtime starts. Prevention costs less than recovery. - **Time-Boxed Relief**: Burst capacity with clear stop criteria. Temporary fixes must stay temporary. ## Steps 1. **Set Guardrails & Visibility**: Define the rules and make capacity status visible to everyone. - Publish utilization bands by role: green (70–85%), amber (85–90%), red (>90%) - Create daily capacity snapshot: occupancy, queue depth, P90 age, escalations - Set up auto-alerts at thresholds (e.g., amber for 5 days → manager action ticket) - Review capacity status in daily/weekly operations meetings 2. **Rebalance & Deflect**: Use existing resources more effectively before adding capacity. - Implement workload rebalancing: move tickets by skill/priority; load-share across regions - Boost deflection: refresh top KBs; pin portal answers; guided chat triage - Enable shift-left: create L1 runbooks for high-volume escalations; expand L1 permissions - Clear process debt: remove approval bottlenecks that create queuing 3. **Add Temporary Capacity**: When rebalancing isn't enough, activate burst capacity. - Activate vendor burst pool or approved overtime (time-boxed, 2–4 weeks) - Throttle non-urgent intake or negotiate due-date adjustments (contract-permitting) - Run daily 15-minute stand-up: yesterday's aging, today's priorities, blockers, owners - Document the trigger and planned off-ramp for temporary capacity 4. **Fix Root Causes & Right-Size Baseline**: Prevent recurrence by addressing structural issues. - Remove bottlenecks (approvals, rework loops, tool friction) - Automate repetitive steps (password resets, standard provisioning, templated deliverables) - Right-size staffing baseline to keep typical occupancy 80–85% with a surge buffer - Align WFM forecasts with product/marketing/grant calendars ## KPIs - Occupancy by Role: 70–85% (green), 85–90% (amber), >90% (red) (Daily) - SLA Compliance (Critical Queues): At/above tier during amber/red (Daily) - Overtime % of Hours: ≤ 5% sustained (Weekly) - P90 Ticket Age / Queue Depth: Trending flat/down within 2–3 weeks (Weekly) - Escalation Rate: Back to baseline after shift-left (Weekly) ## Quick Wins - Publish current utilization bands to all team leads today - Identify top 3 escalation categories and create L1 runbooks - Review and refresh top 10 KB articles for high-volume requests - Set up auto-alert for utilization > 85% sustained for 5 days https://www.digitalcore.app/learn/playbooks/service-delivery-death-spiral Service Delivery Death Spiral playbook Operations Advanced # Service Delivery Death Spiral > How to Spot It Early and Stop It Cold ## Problem High utilization is often seen as a sign of efficiency. But when teams run at >90% occupancy for weeks, queues grow, response times slow, and SLA breaches start stacking up. Soon you're issuing service credits, margins are eroding, and renewal discussions turn sour. This is the Service Delivery Death Spiral—and once you're in it, it's expensive and time-consuming to recover. Symptoms: - Agent Occupancy (14-day avg) > 90% — sustained overutilization precedes slower responses and rising backlog - Backlog Growth MoM ≥ 30% — demand growing faster than throughput; precursor to SLA breach - Escalation Rate > 25% — signals skill gap or knowledge issue; shifts load to higher-cost tiers ## Framework Act on leading indicators before breaches occur. Use a staged response: deflect and prevent at risk stage, stabilize at early issue, contain and recover when in active crisis. - **Act on Risks, Not Just Issues**: Intervene at backlog growth or occupancy >90% before breaches occur. - **Run Diagnostics, Don't Guess**: Find if the problem is demand, skills, or process debt before choosing a fix. - **Address Root Causes Post-Incident**: Avoid returning to firefighting mode next quarter by fixing structural issues. ## Steps 1. **Prevent & Deflect (Risk Stage)**: Intervene before SLAs are impacted. - Refresh top 10 KBs for spike categories, promote in portal and auto-replies - Introduce temporary self-service deflection campaign - Prepare vendor burst pool contract or short-term staffing plan - Implement preventive staffing or burst pool planning - Shift-left enablement: runbooks + L1 training for top escalated categories 2. **Stabilize & Shift-Left (Risk → Early Issue)**: Build capability to handle more at lower tiers. - Build/run runbooks for top L1 escalations - Pair senior agents with L1 for coaching - Enable L1 access for simple tasks to reduce escalation load - Audit escalation patterns to identify training opportunities 3. **Contain & Recover (Active Issue)**: When you're in the spiral, focus on stabilization. - Activate overtime or vendor burst staffing - Rebalance queues by priority & skill - Pause or gate non-urgent requests if contract allows - Run daily backlog stand-ups to keep focus - Re-prioritize queues: focus on high-impact tickets first - Hold an Executive Business Review (EBR): show mitigations, align expectations 4. **Fix Root Causes (Post-Mortem)**: Prevent the spiral from recurring. - Remove slow approval gates or add auto-approvals - Automate repetitive steps (password resets, provisioning) - Adjust staffing baseline to keep utilization within 80–85% target range - Update forecasting to catch demand spikes earlier ## KPIs - SLA Breach Rate: ↓ 20% over 28d (Weekly) - Backlog Days: ↓ 25% over 28d (Weekly) - CSAT: ↑ +3pp (Monthly) - Service Credits Paid: ↓ 100% (eliminate within next cycle) (Monthly) ## Quick Wins - Run demand analysis: Are ≤3 categories responsible for ≥50% of ticket volume? - Check KB coverage & usage: Are KB articles for top categories being used (<10% adoption)? - Identify escalation patterns: Are >25% of tickets escalated from L1 → L2? - Find process bottlenecks: Are there approvals or automations causing >24h wait times? https://www.digitalcore.app/learn/playbooks/customer-sentiment-drop Customer Sentiment Drop playbook Customer Success Advanced # Customer Sentiment Drop > Recover Trust Before Churn Starts ## Problem CSAT/NPS declines rarely happen in isolation. They're usually lagging signals of rising effort, slow responses, unresolved issues, or poor expectation management. If you wait for renewals or escalations to react, you'll be negotiating from a deficit. This playbook catches sentiment dips early, connects them to operational causes, and delivers a credible recovery plan. Symptoms: - CSAT/NPS trend ↓ for 2 consecutive cycles (or month-over-month) - Customer Effort Score (CES) ↑ or verbatims mention "chasing," "waiting," or "handoffs" - Stakeholder engagement ↓ (missed QBRs/EBRs, fewer logins, reduced feature usage) - SLA near-misses rising (breach forecasts, aging P1/P2s) - Ticket reopens ↑ or "answered-not-resolved" cases piling up ## Framework Don't chase the score—fix the drivers. Focus on response, resolution quality, and effort reduction to earn back trust. - **Fix Drivers, Not Scores**: Don't chase the score—fix response time, resolution quality, and customer effort. - **Own Complex Journeys**: Single-threaded ownership for multi-step requests. Fewer handoffs, clearer updates. - **Make Value Visible**: Dashboards and EBRs that tie your work to their KPIs. Don't make them guess the value. ## Steps 1. **Stabilize the Experience**: Fix the most visible pain points immediately. - Protect first-response time on priority queues; add auto-ack + ETA templates - Close the loop: validation checklists to stop "answered-not-resolved" outcomes - Single-threaded ownership for multi-step requests (one owner, fewer handoffs) - Proactive updates for ongoing issues (cadence set by severity/tier) 2. **Fix the Root Causes**: Address the operational drivers of poor sentiment. - Journey-specific runbooks for the top 3 pain journeys (e.g., outage comms, onboarding, change approvals) - Deflect repetitive questions with updated KB and guided chat flows - Reduce handoffs: empower L1 with permissions/scripts; clarify when to escalate - Quality bar: require a "resolution proof" note (what changed, how verified) 3. **Communicate Value & Plan**: Reframe the narrative from "unreliable" to "in control and improving." - Sentiment recovery dashboard: score trend, top drivers, planned fixes, owners, dates - Executive touchpoints: EBR in 14 days with 30–60–90 plan tied to their KPIs - Outcome storytelling: uptime gained, hours saved, incidents avoided, risk reduced - Tier alignment: if expectations outstrip capability, re-tier SLA or scope to match reality 4. **Institutionalize**: Build always-on sentiment monitoring and response capability. - Always-on listening: combine CSAT/NPS/CES with verbatim theme detection and operational metrics - Alerting: threshold-based alerts for score drops, effort spikes, or "chasing" keywords - QBR hygiene: show progress on the drivers of sentiment, not just the score - Playbook library: keep journey runbooks current; automate stable steps ## KPIs - CSAT/NPS/CES: Trend up over 1–2 cycles (Monthly) - Time to First Response & Resolution: ↓ on priority queues (Weekly) - Reopen Rate: ↓ with validation checklists (Weekly) - Handoffs per Ticket: ↓ via single-threaded ownership (Weekly) - Stakeholder Engagement: ↑ (QBR attendance, feature usage, login frequency) (Monthly) ## Quick Wins - Analyze where effort is highest: time-to-first-response, handoffs, or multi-channel ping-pong - Identify which journeys hurt most: outage response, access requests, billing questions - Check quality vs speed: Are we answering quickly but not resolving? - Review expectation setting: Do SLAs and comms reflect reality? https://www.digitalcore.app/learn/playbooks/fixed-fee-margin-erosion Fixed-Fee Margin Erosion playbook Financial Management Intermediate # Fixed-Fee Margin Erosion > Stop the Silent Drift ## Problem Fixed-fee agreements drift when scope expands, ticket mix shifts to harder work, and time goes uncaptured. Margins erode quietly—until credits, discounts, or churn arrive at renewal. Catch it early and reset both delivery and commercials. Symptoms: - Tickets per endpoint/user ↑ 15–25% QoQ (mix shift to high-effort categories) - Unbilled/administrative time ≥ 8% of agreement hours - Patch/compliance backlog ↑ (reactive incidents growing) - CRs raised below expected despite scope changes (silent creep) ## Framework Pair operational guardrails with commercial hygiene to protect profitability without damaging the relationship. - **See It Early**: Agreement P&L weekly + category mix trends. Don't wait for monthly finance reports. - **Fix the Engine**: Shift-left repeatable work; clear proactive debt. Operational efficiency protects margin. - **Charge for Change**: CRs and tiers keep value and effort aligned. Don't absorb scope growth. ## Steps 1. **Guardrails & Visibility**: Create early warning systems for margin drift. - Weekly agreement P&L: time, margin, credits, category mix, CR status - Trigger CRs automatically when category effort ↑ ≥ 20% for 2–4 weeks - Publish top fixes runbooks and macros to standardize high-volume work - Track unbilled/admin time separately to spot capture gaps 2. **Rebalance & Shift-Left**: Fix operational drivers before they require commercial intervention. - Move repeatable fixes to L1 (access, runbooks, tooling) - Schedule proactive maintenance windows to cut incident inflow - Patch/compliance blitz for noisy estates; close "preventable" tickets - Audit work assignment to ensure right level for right work 3. **Commercial Corrections**: Align pricing with actual scope and complexity. - Raise CR for out-of-scope deltas (new systems, security level, after-hours) - Re-tier the agreement (per-device/user bands; complexity uplift) - Right-size SLAs to environmental reality; align on outcomes vs speed - Document all scope drift for renewal negotiation 4. **Prevent Recurrence**: Build structural protections into agreements and operations. - Add pricing guardrails (auto-review when estate grows X%) - Bake health checks & patch SLOs into scope with evidence reporting - Standardize onboarding checklist to avoid future silent creep - Update agreement templates based on lessons learned ## KPIs - Agreement Gross Margin: ≥ 35–40% (Weekly) - CR Velocity (raise → approve): ≤ 7 days (Weekly) - Reactive Incidents per Endpoint: ↓ 15% (Monthly) - Unbilled/Admin Time: ≤ 5% (Weekly) ## Quick Wins - Run category mix analysis: Which top 3 categories now dominate time? Are they in scope? - Check work hygiene: Is engineer time capture complete? Any "admin" buckets growing? - Review proactive debt: Are patching/health checks slipping (causing reactive spikes)? - Assess tier mismatch: Are gold-tier SLAs running on bronze-tier environments? https://www.digitalcore.app/learn/playbooks/grant-reporting-readiness Grant Reporting Readiness playbook Nonprofit Operations Intermediate # Grant Reporting Readiness > Avoid Compliance Slips and Protect Funding ## Problem Grant outcomes can be strong while reporting falls behind—fragmented data, unclear ownership, or vendor/sub-grantee delays. Missed requirements or late submissions put funding, reputation, and future eligibility at risk. The fix: make reporting a predictable operational rhythm with early warnings and a clear play when risk appears. ## Steps 1. **Readiness Sweep** - Assign an overall owner and section owners (Program, Finance, M&E) with time blocks on the calendar - Run a gap check against the donor template; create a punch-list with due dates and owners - Chase dependencies: standardized request emails to subs/vendors; include template + due date + escalation path - Lock narrative sources (field notes, partner updates) and schedule interviews where needed 2. **Production & QA** - Pre-populate the donor template from source systems (M&E, accounting) - Two-pass QA: (1) compliance checklist, (2) editorial review for clarity and evidence references - Evidence vault: receipts, timesheets, attendance lists, photos, signed partner statements—linked in the report - Variance notes: explain KPI/budget deviations with corrective actions and timelines 3. **Containment & Escalation** - Burst admin capacity (internal or outsourced) to assemble supporting docs - Escalate to subs/vendors per contract; cite turnaround clauses and penalties if applicable - Partial submission + mitigation plan when allowed: what's missing, why, and exact delivery date - Leadership comms to the donor: weekly status until closed 4. **Hardening & Improvement** - Calendarize the next cycle with T-60/T-30/T-14 milestones and auto-reminders - Standardize templates for subs/vendors and embed turnaround language in contracts - Systemize data (M&E and finance exports) and link source-of-truth IDs in the report - Amendment playbook for scope or budget changes—faster approvals next time ## KPIs - On-time submission rate: ≥ 98% - Data completeness at T-14: 100% (all sections, all evidence) - Sub/vendor response time: ≤ 5 business days - Corrective actions open > 30 days: 0 - Donor retention / renewal rate: Trending up ## Quick Wins - Create a T-60/T-30/T-14 milestone calendar with auto-reminders - Build a standardized request template for sub-grantee data - Set up an evidence vault folder structure before next cycle - Document variance explanation templates for common KPI misses https://www.digitalcore.app/learn/playbooks/backlog-spike-containment Backlog Spike Containment playbook Service Desk Operations Intermediate # Backlog Spike Containment > Restore Flow Before SLAs Break ## Problem Release defects, seasonal demand, product changes, or knowledge gaps can flood the queue. If the spike isn't contained quickly, P90 age climbs, SLA risk rises, and service credits follow. Morale dips, customers notice, and recovery costs more than prevention. ## Steps 1. **Prevent & Deflect** - Publish/refresh top 10 KBs for the spike categories; add search synonyms and screenshots - Pin answers in the portal and include links in autoresponders - Route low-value "how-to" to self-service or guided chat flows - Announce a short "Self-Help First" campaign (2 weeks) across channels 2. **Stabilize & Shift-Left** - Create L1 runbooks for top 5 escalated categories (known-good paths, screenshots, access needs) - Pair L2 coaches with L1 for 1–2 weeks; expand L1 permissions for common fixes - Tune routing/rules to keep simple issues at L1; add category-specific macros 3. **Contain & Recover** - Activate burst capacity (vendor pool or overtime) for 2–4 weeks - Rebalance queues by priority & skill; cap non-urgent intake where contracts allow - Run daily backlog stand-ups focused on P1/P2 and oldest-age tickets - Pause/process "nice-to-have" work until SLA risk recedes 4. **Root Cause & Hardening** - Fix slow approvals & handoffs (>24h) or set auto-approval thresholds - Automate repetitive fixes (password resets, provisioning, common menu paths) - Add release gates (KB/Runbook complete before major changes) - Adjust baseline staffing to keep occupancy 80–85% with surge buffer ## KPIs - Backlog days: ↓ 25–35% (28d) - SLA breach rate: ↓ 20% (28d) - P90 ticket age: ↓ 20% (14–28d) - L1 resolution rate: +8–12pp - Service credits paid: ↓ to 0 next cycle ## Quick Wins - Refresh top 10 KB articles for spike categories with screenshots - Add search synonyms to improve KB discoverability - Create L1 macro responses for the top 5 repetitive issues - Set up daily backlog aging report for P1/P2 tickets https://www.digitalcore.app/learn/playbooks/vendor-underperformance-response Vendor Underperformance Response playbook Cross-Industry Advanced # Vendor Underperformance Response > Protect Your SLA Chain ## Problem A single slow vendor (cloud, ISP, SaaS, logistics, creative subcontractor) can cascade into your SLA misses, reopens, and angry stakeholders. Without evidence, escalation, and remedies wired into contracts, you eat the cost—credits, rework, and renewal risk. This playbook makes vendor impact visible, actionable, and recoverable. ## Steps 1. **Evidence & Escalation** - Create a vendor dossier: affected tickets, timestamps, severity, business impact, screenshots/logs - Open OLA escalation: follow ladder (support → duty manager → TAM → exec) with SLAs for updates - Request ETA & mitigation: interim steps, rollback plan, or workaround acknowledgment - Communicate to customers: send risk notice referencing vendor case ID and your mitigation plan 2. **Mitigation & Continuity** - Implement workaround: switch path, roll back version, degrade gracefully (reduced feature set) - Re-route service: alternate provider, cached content, manual process, or temporary policy change - Prioritize queues: fast-track P1/P2 tied to vendor impact; pause non-urgent intake if contracts allow - Increase update cadence: internal every 2–4h; external daily or per clause 3. **Commercial Remedies** - Invoke contractual remedies: credits/penalties, service extensions, or professional services at vendor expense - Cost recovery: attribute credits and rework cost to vendor per pass-through clauses - Amend OLA/contract: tighter response/restore targets, explicit blackout windows, redundancy obligations - Performance plan: vendor CAP (corrective action plan) with milestones and reporting cadence 4. **Hardening & Alternatives** - Vendor scorecard: MTTA/MTTR/OLA compliance, incident rate, maintenance hygiene - Dual-vendor or failover pattern where justified (multi-AZ/region, secondary provider, on-prem fallback) - Change governance: require pre-change notice windows, rollback criteria, and joint testing for critical paths - Runbook library: codify workarounds; add synthetic monitoring for early detection ## KPIs - Vendor-attributed SLA breaches: ↓ to 0 - Vendor case aging vs OLA: Within agreed clocks - Time to vendor escalation resolution: ↓ 25–50% vs prior incidents - Reopen rate (vendor-dependent categories): Baseline or better - Customer SLA compliance: At/above tier despite vendor incidents ## Quick Wins - Create a vendor dossier template for documenting issues - Map out vendor escalation paths (support → TAM → exec) - Review contracts for pass-through credit clauses - Set up vendor performance tracking dashboard https://www.digitalcore.app/learn/playbooks/scope-creep-revision-loops Scope Creep & Revision Loops playbook Creative Agency Intermediate # Scope Creep & Revision Loops > Protect Creative Margins ## Problem Creative teams love to deliver. But when requests multiply without clear boundaries—"one more revision," "quick variant," "tiny scope tweak"—hours balloon, schedules slip, and realization % falls. Senior creatives get overutilized while juniors idle, and the project finishes with discounts or write-offs. Scope creep and revision loops are margin killers you can predict and prevent. ## Steps 1. **Shape Demand** - Enforce revision caps from the SOW (e.g., 2 rounds); any extras convert to a Change Request - Tighten approvals: agreed approver list, 48-hour SLA, and "silence = proceed" for low-risk steps - Clarify brief & asset checklist up front (brand kit, references, must-have outcomes) - Preview standards: mood boards / style tiles early to lock direction sooner 2. **Balance & Standardize** - Rebalance the team: shift repetitive tasks to junior/mid with senior QA gates - Template the work: design systems, component libraries, and reusable layouts - Playbooks & macros: common deliverables (ads, banners, landing sections) with checklists and QA criteria - Batch reviews: group feedback sessions to avoid trickle-in commentary 3. **Commercialize Reality** - Freeze current scope and agree on CR(s) for additions (variants, extra channels, new features) - Introduce priority / rush fees if timelines compress - Rebase timeline with a visible burn chart; confirm trade-offs (scope vs schedule vs budget) - Escalate approvals (exec sponsor) if latency blocks delivery 4. **Finish Strong & Prevent Recurrence** - Close the brief loop: document what drove rework; update the brief template - Tune the SOW: sharpen deliverables, add explicit out-of-scope examples, define CR triggers - Rate card hygiene: specialized work gets specialized rates (motion, 3D, localization) - Portfolio learning: add best examples to the system library; reuse next time ## KPIs - Realization %: ≥ 85–90% - Average revisions per deliverable: ≤ 2.0 - Approval latency (median): ≤ 48 hours - On-time delivery: ≥ 95% - Senior utilization: Healthy band 75–85%; avoid >90% sustained ## Quick Wins - Add explicit revision caps to SOW template (e.g., 2 rounds included) - Create a "change request trigger" checklist for project managers - Set up 48-hour approval SLA with "silence = proceed" clause - Build a component library for common deliverable types https://www.digitalcore.app/learn/playbooks/program-efficiency-tracking Program Efficiency Tracking playbook Nonprofit Operations Intermediate # Program Efficiency Tracking > Prove Impact Without Starving Operations ## Problem Pressure to "keep overhead low" can push nonprofits into under-investing in the very capabilities that ensure outcomes—data collection, vendor management, training, and compliance. The result is fragile delivery, inconsistent evidence, and reactive scrambles at audit or grant renewal. Program efficiency isn't about cutting cost; it's about aligning spend to the work that moves outcomes and proving it with data. ## Steps 1. **Make Efficiency Visible** - Build a program efficiency dashboard: Program vs admin %, Unit cost per outcome/beneficiary, M&E completeness/timeliness, Vendor/sub on-time & quality, Staff/volunteer utilization by role - Set variance flags: auto-alert when any metric moves > 10% from plan for 2 consecutive weeks - Assign ownership: single program operations owner to curate and publish the dashboard 2. **Align Capacity to Demand** - Role rebalance: shift repetitive non-clinical/admin tasks to trained volunteers or junior roles; protect scarce expert time - Cross-train & surge roster: prebrief backup staff/volunteers for predictable peaks (distributions, events, campaigns) - Vendor/sub guardrails: weekly check-in on SLAs; standardize templates and clarify turnaround expectations - M&E enablement: short clinics on data definitions, forms, and "good evidence" examples 3. **Fix Measurement & Controls** - Evidence pack refresh: re-baseline indicators, clean forms, and enforce photo/time/location where applicable - Lightweight controls: threshold-based approvals for spend; pre-approved vendors; simple three-quote rules for larger buys - Budget re-phasing: shift funds toward bottlenecks (transport, supplies, field staff) and away from low-impact activities - Partner remediation: corrective action plans for subs with missed SLAs; consider temporary reallocation of scope 4. **Communicate Value, Not Just Ratios** - Outcome storytelling: show beneficiaries reached, milestones delivered, and unit cost trends with context - Donor brief: explain any admin uptick as an investment (e.g., data system, training, vendor upgrade) tied to better reliability and reach - Next-cycle plan: forecast demand, unit costs, and the ops investments that reduce risk ## KPIs - Program vs admin %: Aligned to plan with rationale for changes - Unit cost per outcome/beneficiary: Flat/↓ with improved reliability - M&E completeness & on-time rate: ≥ 95–100% - Vendor/sub on-time & quality: ≥ 95% - Role utilization (critical roles): 70–85% steady (avoid > 90% sustained) ## Quick Wins - Create a simple efficiency dashboard with 5 key metrics - Set up weekly vendor/sub check-in cadence - Document unit cost calculation methodology - Build M&E "good evidence" examples library for field teams https://www.digitalcore.app/learn/playbooks/process-bottleneck-mapping Process Bottleneck Mapping playbook Cross-Industry Intermediate # Process Bottleneck Mapping > Find the Drag and Free the Flow ## Problem Queues age, SLAs wobble, and teams feel "busy" without finishing more. The culprit is usually a handful of bottlenecks—slow approvals, unclear ownership, vendor waits, missing information, or tool friction—that quietly add hours to every ticket or task. Mapping and eliminating these constraints is the fastest way to cut cycle time, protect SLAs, and reduce cost. ## Steps 1. **Map the Journey (1–2 Days)** - Pick 2–3 top journeys (e.g., incident restore, access request, change approval, design review) - Time-stamp the steps: intake → triage → diagnose → approve → execute → validate → close - Measure three things per step: median wait, error/rework rate, and responsible role/team - Visualize (simple swimlane): highlight steps with long wait or high rework 2. **Remove the Drag (1–3 Weeks)** - Fix intake: require 3–5 decisive fields; add macros/templates; attach auto-captured context/logs - Reduce approvals: collapse low-risk approvals; add auto-approve thresholds and fallback SLAs - Single-threaded ownership: assign one owner end-to-end; others consult, not own - Standardize handoffs: definition of "ready," checklists, status reasons; link artifacts to the ticket - Tooling shortcuts: scripts/remote actions for common steps; pre-built forms for repeatable changes 3. **Bypass & Buffer (Now)** - Fast lane for P1/P2 or high-value work: pre-approved steps, dedicated reviewers, or standing CAB - Vendor escalation pack: linked IDs, timestamps, business impact; invoke OLA ladder - Temporary parallelization: split review/execute where independence exists - Daily 15-min stand-up: yesterday's blockers, today's owners, expected unblocks 4. **Make It Durable** - Quarterly journey reviews: cycle time, handoffs, wait ratio, rework, sentiment - Golden-path runbooks: decision trees with validation steps for each journey - Automation candidates: promote stable steps to bots/scripts; add auto-collection of evidence - Contract hygiene: align SLAs/OLAs to the measured reality; formalize approval SLAs and blackout windows ## KPIs - Cycle time (median & P90) by journey: ↓ 15–30% in 30–60 days - Wait time ratio (wait ÷ total): ↓ to < 50% on key flows - Handoffs per item: ↓ 20–40% with single-threaded ownership - Reopen rate: ↓ via intake and validation checklists - SLA breach rate: ↓ 20% in affected queues ## Quick Wins - Create a swimlane diagram for your top 3 work types - Add auto-approve thresholds for low-risk approvals - Implement single-threaded ownership pilot on one queue - Build a "definition of ready" checklist for intake https://www.digitalcore.app/learn/playbooks/profitability-leak Profitability Leak playbook Cross-Industry Intermediate # Profitability Leak > Stop Scope-Driven Cost Creep Before It Hits the P&L ## Problem Profit doesn't usually fall off a cliff—it leaks. Hours drift into "just a quick request," deliverables expand, senior time covers gaps, and small write-offs become habit. Left alone, this turns into margin erosion, discount pressure, and renewal pain. The fix is a simple system: see the leak early, frame it clearly, and commercialize reality. ## Steps 1. **Make the Leak Visible** - Mini P&L weekly: effort vs plan, margin, write-offs, top categories - Delta pack: before/after snapshots (what changed, effort impact, outcome value) - Guardrails: auto-flag when any category rises ≥ 20% for ≥ 2 weeks 2. **Fix the Engine** - Shift-left & rebalance: move repeatables to junior/mid with runbooks/macros - Deflect noise: KB/self-service for low-value asks; templated responses - Trim process debt: remove approvals > 24h, standardize handoffs - Right work / right level: seniors set direction; juniors execute with QA 3. **Commercialize Reality** - Change Request (CR): document scope adds; tie to outcomes and ROI - Re-tier or re-rate: complexity uplifts, channel/feature add-ons, after-hours rates - Milestone trade-offs: adjust scope/date/budget transparently, with impact chart - Credit remediation plan: if credits applied, attach delivery milestones that earn back trust 4. **Prevent the Next Leak** - SOW hygiene: explicit deliverables, out-of-scope examples, CR triggers - Rate card clarity: specialized tasks (security, motion, compliance) priced accordingly - Onboarding checklist: environment/brief/asset readiness criteria before start - Portfolio learning: add best patterns to templates; auto-alerts on early variance ## KPIs - Engagement/agreement margin: ≥ 35–40% - Realization %: ≥ 85–90% - Write-offs/credits: ≤ 2% (eliminate habitual write-offs) - Senior vs junior mix: Seniors 75–85%; juniors/mids healthy & rising - CR velocity: Raise → approve ≤ 7 days ## Quick Wins - Create a weekly mini P&L dashboard (effort vs plan, margin, categories) - Set up auto-flag when any category rises ≥ 20% for 2 weeks - Document top 5 out-of-scope examples in SOW template - Build a CR template with impact fields https://www.digitalcore.app/learn/playbooks/partner-overutilization Partner Overutilization playbook Professional Services Intermediate # Partner Overutilization > Partners Are Delivering, Not Leading ## Problem Partners are logging billable hours on delivery tasks that should be done by managers, seniors, or staff. Meanwhile, business development, relationship management, and practice leadership stall. The result: flat growth, succession gaps, and burnout—both at the top and in the team waiting for their shot. ## Steps 1. **Make It Visible** - Role-level utilization dashboard: Partners vs Managers vs Seniors vs Staff - Billable vs Non-Billable time split by role (weekly) - Delivery vs. BD time ratio for each partner - Client concentration report (top 10 clients vs rest) 2. **Rebalance Work** - Delegate systematically: identify repeatable tasks for managers/seniors with QA gates - Establish transition SOPs for complex client hand-offs - Standardize tooling/templates so juniors can take on more without partner QA - Block partner calendar: protect 1–2 days/week for BD, strategy, leadership 3. **Fix the Model** - Client conversations: reframe engagement model with named manager leads + partner oversight - Succession planning: accelerate high-performers with formal partner-path - Pricing review: if partner involvement is priced in, re-tier rates to reflect true value - Growth-time KPI: add partner BD hours and pipeline contribution to goal set 4. **Build Leverage Muscle** - Quarterly role-level utilization and BD reviews - Training & upskilling: ensure managers/seniors can cover partner-level tasks - Client onboarding: set expectations early about engagement leads - Recognition: reward partners for effective delegation and pipeline, not just delivery hours ## KPIs - Partner utilization: 40–55% (not higher) - Manager/Senior utilization: 65–75% (leveraged, not bottlenecked) - Partner BD/growth time: ≥ 1–2 days/week protected - Revenue per partner: Growing YoY - Succession readiness: ≥ 1 identified candidate per partner ## Quick Wins - Run a utilization by role report for last 90 days - Block 1 day/week on partner calendars for BD/growth - Identify 3 tasks per partner to delegate immediately - Create a named manager lead for top 10 clients https://www.digitalcore.app/learn/playbooks/device-user-growth Device/User Growth playbook MSP Foundational # Device/User Growth > Invisible Growth, Visible Cost ## Problem Endpoints, users, and licenses expand quietly while per-seat billing stays flat. By the time finance notices, the gap between actual cost and collected revenue is real—and awkward to raise with the client. Margins erode not through negligence, but through normal client growth that no one tracked. ## Steps 1. **Make Growth Visible** - Monthly count snapshot: endpoints, users, mailboxes, licenses (auto-pulled if possible) - Variance flag: alert when any count exceeds baseline by ≥ 5–10% - Client dashboard: show them their own counts in real time - Onboarding trigger: new hire or device addition prompts count update 2. **Align Counts to Contract** - Quarterly reconciliation: match RMM/PSA/license data to billing baseline - True-up clause enforcement: activate contract language for count adjustments - Proactive outreach: notify client before billing adjustment, not after - Tooling cost pass-through: ensure licensing cost scales with revenue 3. **Close the Gap** - Reconciliation report: document actual vs. billed with timestamps - Client meeting: present delta with cost impact and proposed path forward - Catch-up options: retroactive billing, future rate adjustment, or credit offset - Escalation path: if client disputes, involve account lead and contract reference 4. **Prevent Future Drift** - Automated count sync: RMM/PSA → billing system (monthly or more frequent) - Contract language: clear true-up windows and notice periods - Client education: explain why accurate counts matter (service quality, compliance) - Renewal prep: count audit 90 days before renewal to avoid last-minute corrections ## KPIs - Count variance: ≤ 5% from contract baseline - Reconciliation frequency: Monthly or continuous (automated) - True-up lag: ≤ 30 days from count change to billing adjustment - Agreement margin: ≥ 35–40% (not eroded by hidden growth) - Client count visibility: 100% (real-time dashboard or monthly report) ## Quick Wins - Run a device/user count audit this week against contract baseline - Set up a monthly count variance alert (≥ 5% flag) - Add a count reconciliation step to your renewal prep checklist - Share a count dashboard with your top 5 clients https://www.digitalcore.app/learn/playbooks/approval-bottlenecks Approval Bottlenecks playbook Creative Agency Foundational # Approval Bottlenecks > Work Is Ready—Approvals Aren't ## Problem Deliverables sit in review queues while deadlines slip. The team scrambles at the last minute, rework spikes, and the client wonders why things feel "slow." Meanwhile, approval ownership is unclear, feedback loops stretch, and the cost of waiting compounds silently. The bottleneck isn't production—it's the handoff. ## Steps 1. **Make Approval Cycle Visible** - Track approval turnaround: submitted → approved (per deliverable type) - Queue dashboard: items awaiting approval, time in queue, owner - Aging alerts: flag items > 24h in review with escalation prompt - Client-side visibility: share approval queue status so they see the backlog 2. **Tighten the Loop** - Name a single approver per deliverable type (no committee drift) - Set SLA: 24h default, 48h max for complex items - Structured feedback: template with required fields (approve, change, reason) - Batch reviews: schedule approval windows (e.g., daily 10am review slot) 3. **Unblock the Queue** - Escalation path: if approval overdue, auto-notify backup approver or exec sponsor - Fast-track tier: pre-approved templates or low-risk items skip full review - Client call: review backlog together, agree on priority order - Grace period rule: if no response in 48h, assume approval (with documented notice) 4. **Build Approval Discipline** - Approval turnaround in retros: celebrate fast cycles, address slow ones - Contract language: include approval SLAs and consequences for delay - Onboarding: set expectations with new clients about review cadence - Recognition: reward clients and internal approvers who hit SLAs consistently ## KPIs - Approval turnaround: < 24h (default), < 48h (complex) - Queue depth: Flat or declining (not accumulating) - Revision rounds: ≤ 2 per deliverable (average) - Escalations triggered: Declining over time (system working) - On-time delivery: ≥ 90% (not blocked by approvals) ## Quick Wins - Add approval turnaround tracking to your project dashboard this week - Name a single approver for your top 3 deliverable types - Set up an aging alert for items > 24h in review - Create a feedback template with required fields (approve/change/reason) https://www.digitalcore.app/learn/playbooks/creative-resource-imbalance Creative Resource Imbalance playbook Creative Agency Intermediate # Creative Resource Imbalance > Use the Right Level for the Right Work ## Problem When senior creatives carry too much execution work, you get bottlenecks, longer cycles, and shrinking realization. Juniors don't build skills, managers firefight, and delivery dates slip. The fix is intentional work leveling: design the flow so juniors/mids execute repeatables, seniors provide direction and quality, and the studio runs at the right cost and speed. ## Steps 1. **Design the Flow** - Define role lanes: which deliverables each level owns (J/M/S) and the QA checkpoints - Standardize the repeatables: component libraries, templates, typography/spacing tokens, motion rules - Brief template v2: task-level acceptance criteria, reference examples, asset checklist, due date - Batch reviews: set daily/bi-daily windows for senior sign-offs to cut context switching 2. **Route Work to the Right Level** - Auto-routing rules in the work manager: repeatables → junior/mid pods with a named senior QA - Checklists & macros for common deliverables (ad sizes, social variations, email modules) - Design QA gates: pixel checks, accessibility, link tests, file hygiene before senior review - Shadowing → ownership: juniors pair on round 1, then own similar tasks with QA 3. **Contain and Rebalance** - Reassign execution tasks stuck behind seniors to trained junior/mid pods immediately - Scope freeze on non-critical tweaks; extras → Change Requests (CRs) with impact charts - Priority swimlanes: seniors handle concept/direction; juniors/mids clear production backlog - Visible burn chart for stakeholders to reduce drive-by requests 4. **Make It Durable** - Capability matrix & training plan: close micro-skill gaps that block junior ownership - Library upkeep: retire "one-off" patterns; push toward system components - Utilization guardrails: publish healthy bands (Seniors 75–85%, Juniors/Mids 70–85%) and alert on drift - Rate card clarity: specialized tasks (motion, 3D, localization) priced accordingly ## KPIs - Utilization by level: Seniors 75–85%, Juniors/Mids 70–85% - Cycle time (repeatables): ↓ 10–20% after standardization - Revisions per deliverable: ≤ 2.0 with clear standards - Realization %: ≥ 85–90% - On-time milestones: ≥ 95% ## Quick Wins - Define role lanes for top 5 deliverable types this week - Set up daily batch review windows for senior sign-offs - Create a QA checklist for your most common deliverable - Audit senior time allocation for last 2 weeks https://www.digitalcore.app/learn/playbooks/ticket-mix-category-drift Ticket Mix & Category Drift playbook Service Desk Intermediate # Ticket Mix & Category Drift > Rebalance Work Before Cost and SLAs Suffer ## Problem Your queue looks "normal," but underneath it the mix of tickets shifts toward harder, longer cases. Average Handle Time creeps up, L1 escalations rise, experts get swamped, and cost-per-ticket climbs. Because volume stays steady, the signal hides in plain sight—until breaches and credits show up. Detecting category drift early lets you rebalance skills, knowledge, and commercials before it hurts. ## Steps 1. **Make Drift Visible** - Weekly mix report: top categories by volume, AHT, escalations, reopens - Drift alerts: trigger when any category's share or AHT crosses thresholds for 2 consecutive weeks - Publish a "What's New" board for analysts: new patterns, quick fixes, watchouts 2. **Enable Front Line for Drift Categories** - Golden-path runbooks with diagnose → resolve → validate → document steps - KB refresh & search tuning (synonyms, screenshots, short clips) for drift topics - Intake upgrades: require 3–5 decisive fields; add macros to gather them fast - Routing rules: direct drift category tickets to trained L1 pods first 3. **Expert Relief & Containment** - SWAT the backlog: L2/L3 "tiger team" clears oldest-age drift tickets with L1 shadowing (live knowledge transfer) - Time-boxed burst capacity for experts (vendor or OT) with a clear ramp-down plan - Quality guardrails: mandatory validation checklists to prevent reopens 4. **Close the Loop** - Root-cause fixes: patch/vendor ticket, configuration template, or process change - Automation candidates: promote stable runbook steps to scripts/bots - Forecasting: add drift-sensitive signals to WFM and change calendars - Commercial hygiene: if drift is due to scope/complexity growth, prep CR or tier changes ## KPIs - Category share variance (top 3): Stable/expected - AHT (drift categories): Flat/↓ after enablement - L1→L2 escalation (drift): ↓ 20–30% in 30–60 days - Reopen rate (drift): ≤ baseline with validation steps - Expert occupancy (L2/L3): ≤ 85% sustained ## Quick Wins - Run a category mix report comparing this month to last quarter - Set up a drift alert for any category with +15% AHT for 2 weeks - Create a "What's New" board for your analysts - Identify top 3 drift categories and audit their KB articles https://www.digitalcore.app/learn/playbooks/shift-left-acceleration Shift-Left Acceleration playbook Service Desk Intermediate # Shift-Left Acceleration > Resolve More at L1 Without Breaking Quality ## Problem When too many tickets jump from L1 → L2/L3, queues bloat, experts get overloaded, and costs spike. Customers feel the lag, engineers burn out, and leaders pay twice—first in SLA risk, then in credits or discounts. A deliberate shift-left program resolves more at the front line, faster, with lower cost-per-ticket—and frees experts for the work only they can do. ## Steps 1. **Target & Prepare** - Pick 5–10 high-volume escalation categories with clear resolution patterns - Build "Golden Path" runbooks (diagnose → resolve → validate → document); add screenshots & failure branches - Refresh KB and embed decision trees; add search synonyms and short videos/GIFs - Fix intake: require the 3–5 critical fields that L1 needs to succeed (template forms/macros) 2. **Enable L1** - Access enablement: provision safe permissions or Just-In-Time elevation for specific tasks - Tooling shortcuts: one-click scripts, remote actions, and prefilled commands for common fixes - Coaching loops: daily 15-min L2 "bar" for L1 questions on target categories; capture answers back into KB - Routing rules: route matching tickets to enabled L1 skill groups first 3. **Contain & Recover** - Freeze new escalations for enabled categories unless runbook steps are exhausted - SWAT the backlog: L2/L3 pair with L1 to clear aging tickets and transfer know-how live - Quality guardrails: mandatory validation steps + reopen review within 24h 4. **Institutionalize** - Performance reviews by category: FCR, escalation %, AHT, CSAT; refresh runbooks quarterly - Automation candidates: promote stable runbook steps to scripts/bots - Career pathways: certify L1 on categories → create incentives for multi-skill breadth - Forecasting & WFM: reflect shift-left wins in staffing models and training plans ## KPIs - L1→L2 escalation rate (target categories): ↓ 20–40% in 30–60 days - FCR (overall & per category): ↑ 8–12pp on enabled categories - AHT: Flat/↓ after runbook stabilization - Reopen rate: ≤ baseline with guardrails - Expert occupancy (L2/L3): ↓ back into healthy band (≤ 85%) ## Quick Wins - Identify your top 5 escalation categories by volume - Create one golden-path runbook this week for the #1 category - Set up a daily 15-min coaching "bar" between L1 and L2 - Audit L1 permissions for the #1 escalation category https://www.digitalcore.app/learn/playbooks/seasonal-surge-planning Seasonal Surge Planning playbook Cross-Industry Intermediate # Seasonal Surge Planning > Hit Peak Demand Without Burnout ## Problem Tax season. Holiday sales. Product launches. Annual renewals. Even when surges are known in advance, teams slip into firefighting: occupancy blows past 90%, overtime and error rates climb, SLAs wobble, and post-peak backlogs linger for weeks. The fix is a repeatable, data-led surge plan—activated before the curve hits. ## Steps 1. **Prepare** - Lock surge schedule with backups for key skills; brief vendor burst pools - Refresh KB & macros for top surge topics; add search synonyms/pinned answers - Tune chat/IVR triage to fast-path repetitive requests - Freeze risky changes (tooling/process) that could add noise - Set comms cadence (internal huddles + customer status updates) 2. **Operate** - Daily 15-min stand-ups: yesterday's aging, today's priorities, blockers, owners - Priority routing: P1/P2 to best skills; defer non-urgent work if contracts allow - Activate burst capacity: vendor pool or OT with clear stop criteria - Quality guardrails: double-check high-risk categories to avoid reopens 3. **Recover** - Backlog burn-down sprint: oldest-age first, daily targets visible to all - De-escalate staffing: roll off OT/vendors as targets are met - Customer recap: share outcomes and any credits avoided/applied 4. **Harden** - Variance review: forecast vs actual, skills vs demand, vendor performance - Update surge kit: KB/runbooks, macros, triage rules, roster templates - Contract updates: add surge provisions or tiered SLAs for next cycle - Automation candidates: identify top repetitive work to automate before next peak ## KPIs - SLA compliance (critical queues) during peak: ≥ agreed tier - Agent occupancy: ≤ 85–90% with surge buffer - Overtime/burst spend vs plan: ≤ budget - Post-peak backlog clearance time: ≤ 7–10 days - Reopen/error rate: At or below baseline ## Quick Wins - Identify your next predictable surge (season, launch, renewal) - Pull historical data for the last similar surge - Refresh KB articles for top 5 expected topics - Lock your surge roster 4 weeks before peak https://www.digitalcore.app/learn/playbooks/volunteer-capacity-shortfall Volunteer Capacity Shortfall playbook Nonprofit Intermediate # Volunteer Capacity Shortfall > Protect Critical Programs When People Power Drops ## Problem Many nonprofit programs hinge on volunteers for delivery (distributions, events, helplines, tutoring, outreach). When volunteer supply dips—or skills don't match demand—milestones slip, beneficiaries wait, and staff burn overtime to fill the gaps. The fix is a simple cadence: forecast people needs, build a cross-trained surge roster, and wire in partner/vendor fallbacks so service doesn't stall. ## Steps 1. **Forecast & Nudge** - People forecast by role/week: required vs confirmed, with skill tags (driver, interpreter, CPR, etc.) - Auto-nudges: targeted outreach to prior volunteers with "1-click claim" links; include role, location, time, and impact blurb - Cross-train kit: 30–45 min micro-modules to expand eligible volunteers for scarce roles - Incentives & recognition: certificates, letters of service, public thank-yous; align to what your community values 2. **Reduce Friction** - Express onboarding: pre-clear recurring volunteers; streamline background checks; offer virtual orientation - Shift redesign: shorter windows, micro-shifts, or buddy system to reduce commitment barrier - Role clarity: task checklists, safety notes, who-to-call; supervisors spend less time coaching ad hoc - Scheduling UX: mobile-friendly signup, calendar holds, reminders T-72/T-24/T-2 hours 3. **Surge & Safeguard** - Partner bench activation: call pre-vetted community orgs, schools, faith groups; share simple role packs - Paid coverage: temp staffing for safety-critical roles (drivers, med/clinical) within pre-approved budget - Re-sequence & right-size: prioritize highest-impact activities; reschedule noncritical tasks; combine locations if needed - Supervisor protection: cap staff backfill hours; rotate leads; add water/rest and safety pauses 4. **Make Capacity Durable** - Quarterly capacity review: fill rates, no-shows, time-to-fill by role/channel; update forecasts before seasonal peaks - Volunteer lifecycle: welcome → train → first shift buddy → recognition → reactivation cadence - Partner MOUs: OLAs for turnaround, headcount, skills, and documentation - Talent pipeline: internships, service-learning credits, employer volunteer days, and alumni networks ## KPIs - Roster fill rate (critical shifts): ≥ 90–95% - No-show/cancellation rate: ≤ 10% overall; ≤ 5% for critical roles - Time-to-fill (by role): ↓ week over week; watch scarce skills - Supervisor overtime hours: ↓ to sustainable band - Program milestone adherence: ≥ 95% on-time delivery ## Quick Wins - Create a 4-week volunteer forecast by role and shift - Set up auto-nudge outreach to prior volunteers - Build a partner bench list with contact info and pre-clearance status - Streamline your background check and onboarding process https://www.digitalcore.app/learn/playbooks/turnaround-time-lag Turnaround Time Lag playbook Professional Services Intermediate # Turnaround Time Lag > Restore Speed Without Sacrificing Quality ## Problem Turnaround time slips rarely come from a single big miss. It's usually a pile of small frictions—unclear briefs, late client inputs, partner bottlenecks, handoff loops, and tool friction. As cycle time grows, realization % falls (more touches, more rework), deadlines wobble, and clients get nervous. This playbook finds the drag, restores flow, and protects margin—without compromising quality. ## Steps 1. **Map & Measure** - Time-stamp the flow for two high-volume deliverables (e.g., monthly close pack, standard tax file) - Track three numbers per step: median wait, touch time, rework % - Visualize the longest waits and the most reworked steps; pick 3 fixes 2. **Remove the Top Frictions** - Intake upgrade: brief template with acceptance criteria, required documents, and examples - Client input SLA: formats + due dates; "silence = proceed" for low-risk clarifications - Right work / right level: move repeatables to Associates/Mids; add QA checklists for Seniors/Partners - Standardize handoffs: definition of "ready for review," file hygiene, versioning rules - Tooling shortcuts: checklists/macros; pre-validated templates; one-click tie-out scripts 3. **Contain the Active Delays** - Milestone rebase: agree new dates with a visible burn chart and owners - Daily 15-min unblock huddle: yesterday's blockers, today's expected unblocks - Escalation ladder: fast legal/finance reviews; Partner review windows batched, not ad hoc - Scope hygiene: extras → Change Requests (CRs) with impact chart (date/scope/budget trade-off) 4. **Make Speed Durable** - Quarterly journey reviews: cycle time (median/P90), wait ratio, rework, and on-time rate - Golden-path runbooks: decision trees + validation steps for your top 5 deliverables - Capability matrix: close micro-skill gaps that keep work with Partners - Automation candidates: promote stable steps to scripts/bots; reduce manual reconciliations ## KPIs - Turnaround time (median & P90) by deliverable: ↓ 15–30% in 30–60 days - Wait time ratio (wait ÷ total): < 50% - On-time delivery rate: ≥ 95% - Rework ratio: ≤ 5–8% - Realization %: ≥ 90% after stabilizing the flow ## Quick Wins - Time-stamp your most common deliverable workflow this week - Create a client input checklist with required formats and due dates - Set up batch partner review windows - Identify your top 3 rework causes https://www.digitalcore.app/learn/playbooks/renewal-risk-early-warning Renewal Risk Early Warning playbook Cross-Industry Intermediate # Renewal Risk Early Warning > Save the Account Before It's Lost ## Problem Accounts rarely churn "out of the blue." The early signs—SLA wobble, credits, sentiment dips, stakeholder turnover—show up months before renewal. Without a structured early-warning motion, teams scramble late, discount hard, or lose the logo. ## Steps 1. **Stabilize Outcomes** - Publish a weekly recovery dashboard (targets, gaps, owners, dates) - Pull 2–3 quick wins tied to the customer's top outcomes - Pre-align a right-sized SLA tier or scope tweak based on observed reality 2. **Executive Alignment** - Schedule an EBR within 14 days; agree on a 30–60–90 plan - Assign clear owners and checkpoints; share a written timeline - Offer value pilots (automation, deflection, modernization) linked to their KPIs 3. **Commercial Path** - Convert chronic out-of-scope work into Change Requests with outcomes/ROI - Negotiate a credit remediation agreement (credits tied to milestone delivery) - Re-tier SLAs or extend term alongside modernization to de-risk both sides 4. **Close the Loop** - Add the account to a renewal risk watchlist (120/90/60/30-day cadence) - Capture root-cause patterns (vendor OLAs, staffing gaps, process debt) - Update defaults & alerts so the next risk fires earlier with better context ## KPIs - Renewal probability: ↑ (risk-weighted) - Credits paid (60–90d): ↓ to 0 - SLA compliance (30d): At/above agreed tier - Executive sentiment: Neutral → positive (meeting notes / survey) - Outcome KPIs: Movement on the 1–2 metrics they value most ## Quick Wins - Create a renewal risk watchlist with 120/90/60/30-day triggers - Pull a sentiment report for accounts renewing in next 90 days - Identify accounts with credits paid in last 60 days - Schedule EBRs for at-risk accounts within 14 days https://www.digitalcore.app/learn/playbooks/reactive-incident-spike Reactive Incident Spike playbook MSP Intermediate # Reactive Incident Spike > Cut Firefighting by Fixing the Feed ## Problem When reactive incidents spike, technicians get buried, SLAs slip, and escalations multiply. The root causes are usually hygiene debt or config drift—cleared patches, failed backups, weak policies—but the "urgent" flood drowns out time to fix them. ## Steps 1. **Triage & Protect SLAs** - Identify the top 10 noisy CIs/categories; log them in a "spike brief" - Temporarily assign a senior tech to clear the queue and flag patterns - Communicate a realistic SLA expectation window to affected clients 2. **Fix the Feed** - Run a 48-hour hygiene blitz: patch, reboot, reconfigure the noisy subset - Tune or mute monitoring rules generating non-actionable alerts - Deploy self-service or automation for top repeat categories (password reset, print fix, VPN) 3. **Protect Future Bandwidth** - Shift L1-appropriate work back down; protect L2/L3 for project/change - Re-establish proactive hours (20–30% of week) in the roster - Add top offenders to a "watch list" CI group with stricter SLA triggers 4. **Recover Margin** - Log reactive surge effort; convert to CR if client caused the drift - Propose a Managed Hygiene add-on or quarterly config review cadence - Adjust SLA tiers or coverage if underlying estate reality changed ## KPIs - Reactive / proactive ratio: < 50% reactive within 30d - Top 10 CI incident volume: ↓ 40% after blitz - FTRR: ↑ 5pp - MTTA / MTTR: Back to baseline - Overtime hours: ≤ baseline ## Quick Wins - Pull a "top 10 noisy CIs" report for the last 7 days - Identify the 3 categories driving most reactive volume - Check patch compliance rate across the estate - Review monitoring alert volume vs. actionable tickets https://www.digitalcore.app/learn/playbooks/knowledge-base-deflection-boost Knowledge Base Deflection Boost playbook Service Desk Intermediate # Knowledge Base Deflection Boost > Reduce Tickets Without Reducing Service ## Problem Support teams answer the same questions hundreds of times a week while knowledge articles sit unseen in a dusty wiki. Without a targeted deflection motion, self-service rates plateau, agents stay busy with low-value work, and you leave capacity—and cost savings—on the table. ## Steps 1. **Find the Gaps** - Pull a ticket category report (last 30–60d) and rank by volume - Map top 10 categories to existing KB articles; flag missing or stale - Identify top repeat tickets (same user, same issue) as deflection candidates 2. **Build/Refresh Articles** - Draft or refresh 10 articles targeting top categories (keep < 300 words, clear titles) - Include screenshots/GIFs for how-to steps; use consistent formatting - Tag articles for search; add synonyms and common misspellings 3. **Wire to Ticket Journey** - Add suggested articles on the ticket submission form (category-based triggers) - Deploy a chatbot/virtual agent using KB as the answer source - Enable agents to insert KB links in one click; track usage 4. **Close the Feedback Loop** - Track deflection rate, article views, and "was this helpful?" signals weekly - Review tickets still logged on covered topics—refine article or surface earlier - Add KB sprint to monthly cadence: refresh stale, add new top issues ## KPIs - Self-service deflection rate: ↑ 5pp in 30d; 15–25% target - KB article coverage: Top 10 categories = 100% - Ticket volume (covered categories): ↓ 15–20% - "Was this helpful?" positive rate: > 70% - Agent KB link usage: ↑ 20% ## Quick Wins - Pull a "top 10 ticket categories" report for the last 30 days - Audit KB article coverage for those 10 categories - Identify the 3 articles most viewed but lowest rated - Add "suggested articles" to the ticket submission form https://www.digitalcore.app/learn/playbooks/service-credit-explosion Service Credit Explosion playbook Cross-Industry Advanced # Service Credit Explosion > Stop the Bleed and Rebuild Trust ## Problem Service credits start as a safety valve but can become a cash drain and a trust killer. When credits spike, it's rarely just "bad luck"—the SLA structure, operational capacity, or client environment has drifted. Without a structured response, teams pay out, patch up, and repeat. ## Steps 1. **Immediate Stabilization** - Identify the top 3 SLA categories driving credits; assign owners - Surge capacity (overtime, cross-train, escalate) on at-risk work - Communicate a stabilization plan to the client within 48 hours 2. **Fix the Engine** - Run a credit post-mortem: timeline, root causes, and contributing factors - Map breaches to operational gaps (staffing, tools, process, vendor OLAs) - Quantify the cost of credits vs. the cost of fixing the root cause 3. **Cap Exposure** - Propose a credit remediation agreement: milestone delivery tied to credit offsets - Review SLA structure—re-tier if targets don't match environment reality - Convert chronic out-of-scope work into a Change Request or scope amendment 4. **Rebuild the Safety Net** - Add near-breach alerts (7–14 days out) to dashboards and escalation paths - Codify credit caps and SLA exclusions for vendor/OLA-caused delays - Run quarterly SLA reviews to catch drift before it becomes a crisis ## KPIs - Credits paid (30d): ↓ 50%+ in 60 days - SLA compliance (breach rate): At/above agreed threshold - Near-breach forecast accuracy: > 80% true positive - Root-cause coverage: Top 3 drivers identified and addressed - Account margin: Stabilized or recovering ## Quick Wins - Pull a "credits paid by category" report for the last 60 days - Identify the top 3 SLA categories driving credit payouts - Check near-breach forecast for the next 14 days - Review SLA exclusion language for vendor/OLA-caused delays https://www.digitalcore.app/learn/playbooks/fcr-improvement-workflow FCR Improvement Workflow playbook Service Desk Intermediate # FCR Improvement Workflow > Solve More on First Contact ## Problem When customers don't get resolution on first contact, tickets bounce between queues, age increases, and cost-per-ticket climbs. Low FCR (First Contact Resolution) is usually a symptom of missing knowledge, poor intake quality, access gaps, or routing errors. Fixing FCR tightens SLAs, reduces backlog, and frees experts for work only they can do. ## Steps 1. **Target & Design** - Pick top 10 non-FCR categories (volume × fixability × business impact) - Create "Golden Path" runbooks (diagnose → resolve → validate → document) with screenshots and failure branches - Add validation checklists (what must be true before closing) - Tune intake forms to require 3–5 decisive fields per category 2. **Enable Front Line** - Grant safe permissions (or Just-In-Time elevation) for L1 to complete fixes - Tooling shortcuts: one-click scripts, remote actions, pre-filled commands - Knowledge embedding: surface article snippets in the ticket UI; add search synonyms - Daily 15-min coaching bar with L2 for target categories; capture answers back into KB 3. **Contain & Recover** - Route matching tickets to newly enabled L1 pods first - Freeze escalation on enabled categories until runbook steps are exhausted - Reopen review within 24h: fix the missing validation step or update runbook/KB - Backlog SWAT: pair L2/L3 with L1 to clear oldest-age items and transfer know-how live 4. **Institutionalize** - Quarterly category review: FCR, AHT, escalations, reopens → refresh runbooks - Automation candidates: promote stable steps to scripts/bots - Skill matrices & certification: L1 breadth incentives; rotate coaches - Forecasting/WFM: reflect FCR gains in staffing and training plans ## KPIs - FCR (overall & targeted categories): ↑ 8–12pp in 30–60 days - Reopen rate: ↓ to baseline or better - AHT (target categories): Flat/↓ after runbook stabilization - L1→L2 escalations: ↓ 20–40% on enabled categories - CSAT "effort" theme: ↓ in verbatims (lower customer effort) ## Quick Wins - Identify the top 10 categories with lowest FCR - Audit L1 permissions for those categories - Create a golden-path runbook for the #1 non-FCR category - Set up a daily 15-min coaching bar between L1 and L2 https://www.digitalcore.app/learn/playbooks/realization-guardrail Realization % Guardrail playbook Professional Services Intermediate # Realization % Guardrail > Keep Fixed-Fee Work Profitable ## Problem Fixed-fee engagements drift when unseen rework, partner-heavy delivery, and scope creep stack up. Discounts and write-offs become "the cost of keeping the client," and realization % slides a few points each cycle—until the P&L notices. The cure is a simple guardrail system that flags variance early and guides both delivery and commercial corrections. ## Steps 1. **Guardrails & Visibility** - Weekly mini P&L per engagement: planned vs actual hours, realization %, write-offs, role mix - Traffic-light targets: Realization ≥ 90% (green), 85–90% (amber), < 85% (red) - Auto-alerts when partner time on associate-level tasks exceeds a threshold (e.g., > 6 hours/week) 2. **Rebalance & Standardize** - Right work, right level: move repeatable tasks to Mid/Associate; keep Partner for review/advisory - Playbooks & templates: standardized workpapers, checklists, and QA gates for recurring deliverables - Client inputs SLA: define formats/deadlines; use intake checklists to avoid rework 3. **Commercial Corrections** - Change Requests (CRs): convert new asks/complexity changes into priced CRs - Re-tier fixed fees by complexity (entity count, consolidation, regulatory scope) - Milestone renegotiation: adjust sequence/dates to protect quality and realization - Discount discipline: if discounting, tie it to a remediation plan (future scope, process changes) 4. **Prevent Recurrence** - Engagement letter upgrades: explicit deliverables, assumptions, acceptance criteria, and CR triggers - Rate card hygiene: specialist rates (IFRS changes, transaction advisory, complex tax) clearly defined - Onboarding checklist: data readiness, access, and calendar coordination before work begins - Library of exemplars: store best workpapers and memos; reuse on similar clients ## KPIs - Realization %: ≥ 90% (amber 85–90%) - Write-offs/discounts: ≤ 2% - Partner utilization (delivery): ≤ 75–80%; keep room for review/advisory - Turnaround time per deliverable: Flat/down vs prior cycle - CR velocity (raise → approve): ≤ 7 days ## Quick Wins - Create a weekly mini P&L report for top 10 engagements by revenue - Identify engagements with Partner utilization > 85% - Review last quarter's write-offs for pattern analysis - Set up traffic-light alerts for realization thresholds https://www.digitalcore.app/learn/playbooks/donor-retention-risk Donor Retention Risk playbook Nonprofit Intermediate # Donor Retention Risk > Stop Attrition and Grow Lifetime Value ## Problem Most nonprofits pour effort into new donors while quietly losing last year's supporters. Lapsed givers don't complain—they just stop responding. If you don't detect early drift and intervene with the right message and channel, you'll pay more to stand still. This playbook catches retention risk early, aligns actions to donor value and intent, and builds a predictable renewal rhythm. ## Steps 1. **Detect & Prioritize** - Build a retention dashboard with RFM scores (Recency, Frequency, Monetary) and engagement signals - Flag "amber" donors (e.g., 6–9 months since last gift; recurring at risk in 30–60 days) - Tier by value and intent: recurring & mid/major get higher-touch; one-time get automated saves - Define success: 60-day reactivation rate and 90-day recurring save rate by segment 2. **Run the Save Series** - Personalized impact refresh: show what their last gift accomplished; invite them to finish a milestone - Channel fit: email + SMS nudge for digital; phone for mid/major; social retargeting for broad - Friction removal: one-click renewals, prefilled forms, Apple/Google Pay, clear tax receipt language - Recurring save kit: card updater, grace periods, and "resume at a lower amount" option 3. **High-Touch for High-Value** - 1:1 outreach from a donor steward (phone/WhatsApp/LinkedIn) within 7 days - Intent conversation: ask about preferred impact area and cadence; capture notes in CRM - Offer a match window or impact-driven micro-campaign relevant to their history - Honor pauses: allow a 1–3 month pause instead of churn; schedule a warm re-entry 4. **Make It Habit** - Quarterly retention retro: cohort curves, channel lift, creative themes that worked - Lifecycle journey: welcome → impact stories → second gift ask (30–60 days) → recurring upgrade - Event-to-recurring bridge: post-event "keep the momentum" recurring ask with small onramp - Data hygiene: refresh contact details & consent; enrich preferred channel and interests ## KPIs - Donor retention rate (12-month): ↑ to prior-year level and beyond - Recurring save rate (60–90d): ≥ 60–70% of at-risk recurring donors - Reactivation rate (60d): ≥ 10–20% in lapsed cohorts - Average gift: Flat/↑ post-save - Engagement rate (open/click/reply/RSVP): ↑ on save journeys ## Quick Wins - Build an RFM dashboard to flag at-risk donors - Identify recurring donors with cards expiring in 60 days - Pull a list of donors approaching their lapse window - Set up automated card update reminders