Loading
CASE STUDY · MSP MARGIN AUDIT

MSP Diagnostic Tool · Functional MVP · Deployment Pending

MSP Margin Audit

A focused Rails diagnostic that estimates operational leakage from unbilled cloud seats, technician administration and manual dispatch—then models the hours and value automation could potentially reclaim.

My Role Product strategy, diagnostic model, UX and Rails development
Product Model Focused MSP planning tool with saved reports and scorecards
Core Stack Ruby on Rails, PostgreSQL, server-rendered reporting, PDF and email delivery
Current Stage Functional MVP complete; public deployment pending

The Product

The Problem

Operational leakage is easy to feel and difficult to quantify.

MSP leaders often know that technicians spend too much time on administration, dispatch requires repeated manual effort and cloud seats occasionally escape billing. The harder question is what those leaks may be costing each month.

MSP Margin Audit turns a small set of operating assumptions into a transparent planning estimate. The purpose is not to replace an accounting review. It is to create a useful starting point for prioritising workflow improvements.

MSP Margin Audit calculator showing MSP operating inputs and automation investment assumptions
The calculator collects a focused set of operating assumptions and shows the core planning results immediately. No signup is required before the estimate is displayed.

Diagnostic Model

From Assumptions to Planning Estimate

The model keeps each source of leakage visible.

The calculator uses deterministic arithmetic rather than AI. Each result follows directly from the values entered, making the estimate easy to explain, review and challenge.

01

License Leakage

Estimate recurring loss from cloud seats that are active but not billed.

02

Technician Administration

Convert repeated non-billable administration time into a monthly labor estimate.

03

Manual Dispatch

Quantify recurring effort spent reviewing, assigning and routing service work.

04

Monthly & Annual Loss

Combine the three operating areas into a clear planning total.

05

Potential Recovery

Apply the user’s recovery assumption to estimate hours and value that may be reclaimed.

06

ROI & Payback

Compare potential reclaimed value with implementation and ongoing automation assumptions.

What the Tool Evaluates

01 · LICENSE CONTROL

Unbilled Cloud Seats

Estimates recurring revenue leakage when active cloud subscriptions are not reflected in client billing.

  • Unbilled seat count
  • Monthly value per seat
  • Monthly and annual licensing leakage

02 · TECHNICIAN TIME

Administrative Overhead

Converts recurring technician administration into a labor-cost estimate using the operating assumptions entered.

  • Administrative hours
  • Loaded hourly cost
  • Potential time recovered

03 · SERVICE COORDINATION

Manual Dispatch Effort

Quantifies the time spent manually reviewing, prioritising, assigning and routing incoming service work.

  • Dispatch hours
  • Labor value consumed
  • Potential automation opportunity

04 · INVESTMENT VIEW

Recovery, ROI & Payback

Models how much value may be reclaimed and compares it with the assumed cost of implementation and maintenance.

  • Potential monthly value reclaimed
  • Estimated ROI
  • Estimated payback period
Monthly Loss

Estimated operational leakage

The combined monthly impact of the three diagnostic areas.

Annual Loss

Twelve-month planning exposure

A simple annualised view for budgeting and prioritisation.

Wasted Hours

Recurring labor consumed

Administrative and dispatch effort expressed as time.

Hours Reclaimed

Potential capacity returned

Estimated recoverable time based on the selected assumption.

Value Reclaimed

Potential monthly benefit

The labor and licensing value the model suggests may be recoverable.

ROI & Payback

Implementation planning view

Estimated return and time to recover the assumed automation investment.

Report Workflow

01 · Calculate

See results immediately.

The diagnostic returns a planning estimate as soon as the operating assumptions are submitted.

02 · Save

Create a durable report.

A saved scorecard receives an opaque token rather than exposing a predictable record identifier.

03 · Share

Deliver the scorecard.

The report can be delivered by email for internal follow-up or a prospect conversation.

04 · Export

Download a PDF.

A portable scorecard keeps the assumptions, results and planning caveats together.

Product Architecture

A Focused Rails Product

Calculation, reporting and privacy have separate responsibilities.

The application keeps business rules inside deterministic calculation logic, validates the submitted assumptions and preserves saved reports for later review. Report delivery is part of the product, not an afterthought.

01

Validated Input Model

Form-level validation keeps incomplete or unrealistic submissions from producing misleading output.

Input
02

Deterministic Calculation Service

Centralized formulas calculate leakage, recovered capacity, value, ROI and payback.

Domain
03

Saved Report Snapshot

The report preserves the submitted assumptions and resulting scorecard for later review.

Data
04

Opaque Report Tokens

Non-sequential public identifiers reduce predictable report discovery.

Privacy
05

Email & PDF Delivery

Saved scorecards can be delivered and exported without changing the underlying calculation.

Output
06

Edge-Case QA

Validation covers zero values, unusual inputs and private-report behavior.

Quality

Product Boundaries

Focused MVP Scope

The tool deliberately evaluates three operating areas.

MSP Margin Audit currently focuses on unbilled cloud seats, technician administration and manual dispatch. Keeping the scope narrow makes the model understandable and keeps every output tied to a visible input.

Key Product Decisions

Decision 01

Keep the model deterministic.

The diagnostic uses visible arithmetic rather than AI, making each estimate easier to explain and challenge.

Decision 02

Present value before collecting a lead.

The calculator is designed to show the result first. Saving, emailing or discussing the scorecard follows the useful output.

Decision 03

Use planning language responsibly.

Results are framed as estimates based on supplied assumptions, not as guaranteed savings or verified financial findings.

My Role & Engineering Approach

End-to-End Ownership

I turned an MSP sales conversation into a working diagnostic product.

The tool connects the Hammer Flow service model with a practical way to discuss operational waste. I defined the scope, calculation model, report experience, Rails implementation, privacy boundary and edge-case QA.

  • 01 Product problem, audience and MVP boundary
  • 02 Leakage, recovery, ROI and payback formulas
  • 03 Rails form, calculation and report workflow
  • 04 Saved reports, PDF output and email delivery
  • 05 Edge-case QA and private-report protection

Technology

A conventional Rails stack built for clarity.

The product keeps the model understandable, testable and easy to deploy alongside the broader Hammer Flow work.

Ruby on Rails PostgreSQL Server-Rendered HTML Form Objects PDF Reports Email Delivery Tokenized Reports Automated Tests

Hammer Flow Relationship

A diagnostic tool—not an HF-numbered automation.

MSP Margin Audit helps identify and quantify a potential improvement area. The 15 Hammer Flow workflows remain separate reference implementations for specific MSP operating processes.

MVP Readiness

Calculator Functional
Saved Reports Implemented
Scorecard Delivery PDF & email
Quality Work Edge-case QA complete

Current Stage

Functional MVP · Deployment Pending

The useful product path is complete.

The calculation workflow, immediate result, saved scorecard, PDF output, email delivery, private-report protections and edge-case QA are implemented. Public hosting remains the next release step.

Diagnostic ModelComplete
Saved ScorecardsComplete
PDF & EmailComplete
Public DeploymentPending

Intended Use

Start an evidence-based automation conversation.

The scorecard gives an MSP owner or service leader a clearer starting point for deciding which operating leak deserves deeper investigation and workflow design.

Deployment Pending

Rails Development · MSP Operations · Diagnostic Products

MSP Margin Audit turns an operational problem into a focused, explainable product.

Review the complete Hammer Flow automation portfolio, explore the rest of my tools or start a conversation about practical MSP workflow improvement.

© 2026 Cary Wood. Building software, tools and digital systems.

+
+