Play 12 Complete Implementation Guide

You need predictive reporting that tells you what's coming, not what already happened. This guide walks you through building a system that forecasts revenue shortfalls, flags utilization drops before they crater profitability, and predicts client churn while you can still act.

No theory. Just the exact steps to select metrics, wire up your data, build dashboards that partners actually use, and configure alerts that trigger action.

Start with metrics that directly impact partner compensation. Everything else is noise.

Step 1: Lock Down Your Core Financial Metrics

Pick three to five metrics maximum. More than that and nobody pays attention.

Revenue metrics:

• Monthly recurring revenue (MRR) by practice area
• Realization rate (billed hours / total hours worked)
• Collection rate (cash received / invoices sent)
• Revenue per lawyer or consultant

Profitability metrics:

• Contribution margin by client (revenue minus direct costs)
• Effective billing rate (total fees / total hours)
• Write-off percentage by partner

Client health metrics:

• Client concentration (percentage of revenue from top 10 clients)
• Average engagement size
• Client tenure

Choose metrics where a 10% swing would trigger a partner meeting. If it wouldn't, drop it.

Step 2: Identify Leading Indicators

Leading indicators move before your core metrics do. They give you time to respond.

For revenue prediction:

• Pipeline value by close date (from your CRM

  CRM

  Click to read the full definition in our AI & Automation Glossary.

  )
• Proposal win rate (last 90 days)
• Average sales cycle length (trending up = trouble)
• New client meetings scheduled

For utilization prediction:

• Scheduled project hours (next 30/60/90 days)
• Bench time by role level
• Project pipeline conversion rate
• Average project duration

For client retention prediction:

• Days since last engagement
• Invoice dispute frequency
• Response time to client requests
• Engagement profitability trend (last 6 months)

For talent risk prediction:

• Overtime hours by employee
• Time since last promotion
• Billable hour variance from target
• PTO accrual levels

Map each leading indicator to a core metric. If you can't draw a direct line, cut it.

Step 3: Validate Correlation Strength

Pull 12-24 months of historical data. Run basic correlation analysis in Excel or Google Sheets.

For each leading indicator, calculate the Pearson correlation coefficient against your core metric. Anything below 0.5 is weak. Drop it or find a better proxy.

Example: If "pipeline value" has a 0.7 correlation with "revenue 60 days later," keep it. If "client satisfaction scores" show 0.3 correlation with "client retention," find a better predictor (like invoice payment speed or engagement frequency).

Your predictive models are only as good as your data feeds. Garbage in, garbage out.

Step 1: Map Every Data Source

Create a spreadsheet with these columns:

• System name
• Data needed
• Update frequency required
• Access method (API

  API

  Click to read the full definition in our AI & Automation Glossary.

  , database, CSV export)
• Owner/contact

Common sources for professional services:

• Practice management system (Clio, PracticePanther, BigTime)
• Accounting software (QuickBooks, Xero, NetSuite)
• CRM

  CRM

  Click to read the full definition in our AI & Automation Glossary.

  (Salesforce, HubSpot, Pipedrive)
• HRIS (BambooHR, Workday, ADP)
• Time tracking (Harvest, Toggl, built-in PMS)

Step 2: Establish API Connections

Use a data integration platform. Don't build custom scripts unless you have a dedicated dev team.

Recommended tools:

• Fivetran (easiest, handles most professional services apps)
• Stitch Data (cheaper, more technical)
• Airbyte (open source, requires setup)

For each connection:

1. Create a read-only API

   API

   Click to read the full definition in our AI & Automation Glossary.

   key in the source system
2. Configure the connector in your integration platform
3. Select only the tables/objects you need (don't sync everything)
4. Set sync frequency (hourly for CRM

   CRM

   Click to read the full definition in our AI & Automation Glossary.

   , daily for accounting, weekly for HRIS)
5. Choose a destination (Snowflake, BigQuery, or Redshift if you're enterprise; Google Sheets or Airtable if you're under 50 people)

Test each connection:

• Verify data appears in destination within expected timeframe
• Check for null values or formatting issues
• Confirm row counts match source system

Step 3: Build Your Data Model

Create a central fact table with one row per time period (day, week, or month).

Required fields:

• Date
• Practice area or department
• Partner/owner
• Client ID (if client-level analysis)

Join in metrics from each source:

• Revenue and costs (from accounting)
• Hours and utilization (from time tracking)
• Pipeline and opportunities (from CRM

  CRM

  Click to read the full definition in our AI & Automation Glossary.

  )
• Headcount and turnover (from HRIS)

Use SQL views or dbt models to calculate derived metrics (realization rate, effective billing rate, etc.) once, not in every dashboard.

Handle missing data:

• For revenue: Carry forward last known value
• For pipeline: Assume zero if no data
• For utilization: Flag as "incomplete data" if hours not submitted

Set up data quality checks. Alert if:

• Row count drops more than 20% day-over-day
• Key fields are null for more than 5% of records
• Numeric values fall outside expected ranges (negative revenue, 200% utilization)

Build for the person who will actually use it. Managing partners don't want drill-downs. Practice leaders do.

Step 1: Choose Your BI Tool

For firms under 25 people: Google Sheets with built-in charts. Seriously. It's free, everyone knows it, and you can share it instantly.

For firms 25-100 people: Metabase (open source, easy setup) or Google Looker Studio (free, connects to everything).

For firms over 100 people: Tableau or Power BI. You'll need someone who knows what they're doing.

Step 2: Build the Executive Summary Dashboard

One page. Six to eight visualizations maximum.

Top row (KPI cards):

• Current month revenue vs. target (with percentage)
• Current utilization rate vs. target
• Projected next quarter revenue (from pipeline)
• Client retention rate (trailing 12 months)

Middle section (trend charts):

• Revenue by month (last 12 months, with forecast for next 3)
• Utilization by practice area (last 6 months)
• Pipeline value by expected close month

Bottom section (alerts):

• List of clients at churn risk (based on your leading indicators)
• List of upcoming project end dates with no follow-on work
• List of staff with utilization below 60% next month

Use red/yellow/green color coding. Red means "act today." Yellow means "watch closely." Green means "on track."

Step 3: Build Practice-Level Dashboards

One dashboard per practice area or department.

Include:

• Revenue and margin trends (monthly, last 12 months)
• Utilization by person (current month and next month forecast)
• Client list with engagement status and next scheduled work
• Pipeline by stage with win probability
• Capacity analysis (available hours vs. scheduled hours, next 90 days)

Add filters for:

• Time period
• Client
• Team member

Step 4: Configure Predictive Models

If you have a data scientist, build custom ML models. If you don't, use simple forecasting.

Simple revenue forecast (works for 80% of firms):

1. Calculate 3-month rolling average revenue
2. Apply seasonal adjustment (compare current month to same month last year)
3. Add weighted pipeline (multiply pipeline value by historical win rate for each stage)
4. Result: Forecasted revenue = (rolling average × seasonal factor) + (pipeline × win rate)

Simple utilization forecast:

1. Sum scheduled project hours by person for next 30/60/90 days
2. Divide by available hours (working days × target billable hours per day)
3. Flag anyone below 70% as "at risk for low utilization"

Simple churn prediction:

Score each client 0-100 based on:

• Days since last invoice (more days = higher risk)
• Invoice payment speed (slower = higher risk)
• Engagement profitability (lower margin = higher risk)
• Engagement frequency (less frequent = higher risk)

Clients scoring above 70 are "high churn risk."

Build these calculations in your data model, not in the dashboard. Dashboards just display the results.

Step 5: Design for Mobile

At least 40% of dashboard views will happen on phones. Test on an actual phone, not just a narrow browser window.

Mobile-friendly design:

• Stack visualizations vertically
• Use large fonts (minimum 14pt)
• Limit charts to one metric each
• Put most critical KPIs at the top

Alerts only work if they trigger action. Configure them to go to the person who can actually do something.

Step 1: Define Alert Thresholds

Be specific. "Revenue is down" is useless. "Revenue is 15% below target with 10 days left in the month" triggers action.

Revenue alerts:

• Current month revenue is more than 10% below target with fewer than 10 days remaining
• Forecasted next quarter revenue is more than 15% below target
• Any single client represents more than 25% of monthly revenue

Utilization alerts:

• Any billable staff member has fewer than 60% scheduled hours for the next 30 days
• Practice area utilization drops below 70% for two consecutive weeks
• Bench time (unscheduled hours) exceeds 20% of total capacity

Client health alerts:

• Any client scores above 70 on churn risk model
• Invoice remains unpaid 45 days past due
• No new engagement in 90 days for clients with historical monthly activity

Pipeline alerts:

• Pipeline value for next quarter is less than 1.5× revenue target
• Win rate drops below 30% for any practice area
• Average sales cycle extends beyond 90 days

Step 2: Set Up Alert Delivery

For managing partners: Daily email digest at 7 AM with critical alerts only (revenue, major client risk).

For practice leaders: Slack message when utilization drops or client churn risk spikes for their team.

For operations: Email when data quality issues are detected or sync failures occur.

Implementation in common tools:

Metabase:

1. Create a question that returns rows only when alert condition is met
2. Click "Set up an alert"
3. Choose frequency and recipients
4. Test by temporarily adjusting threshold

Google Looker Studio:

1. Use Google Apps Script to query your data source
2. Check conditions in script
3. Send email via MailApp.sendEmail() if condition is true
4. Set script trigger to run hourly or daily

Tableau:

1. Create a calculated field for alert condition
2. Build a view showing only alert records
3. Subscribe users to the view
4. Set delivery schedule

Step 3: Build Alert Response Workflows

An alert without a workflow is just noise.

For each alert type, document:

• Who receives it
• What action they should take
• Deadline for action
• Escalation path if no action taken

Example workflow for "Client Churn Risk" alert:

1. Practice leader receives Slack alert: "Client XYZ scored 75 on churn risk model"
2. Practice leader reviews last 3 engagements and payment history
3. Within 24 hours: Schedule call with client to discuss upcoming needs
4. Within 1 week: Send proposal for next engagement or schedule quarterly business review
5. If no action taken in 1 week: Alert escalates to managing partner

Example workflow for "Low Utilization" alert:

1. Practice leader receives alert: "John Smith has 45% scheduled hours next month"
2. Practice leader reviews current project assignments
3. Within 48 hours: Assign to new project, move to business development activities, or schedule training
4. Update capacity planning system with new assignment
5. If utilization remains below 60% for 2 consecutive weeks: Escalate to operations director

Document these workflows in your firm's operations manual. Review quarterly and update based on what actually works.

Step 4: Monitor Alert Effectiveness

Track two metrics for each alert:

• False positive rate (alerts that didn't require action)
• Response time (hours from alert to action taken)

If false positive rate exceeds 30%, tighten your thresholds. If response time exceeds your target, simplify the workflow or escalate sooner.

Review alert performance monthly. Kill alerts that nobody acts on.

Predictive reporting works when you focus on metrics that drive partner decisions, connect clean data sources, build dashboards people actually open, and configure alerts that trigger real action. Start with revenue forecasting and utilization prediction. Add complexity only after those are working.

Most firms fail because they build dashboards nobody uses. Avoid that by involving end users in every step, starting with metric selection. If a partner wouldn't change their behavior based on the insight, don't build it.