MFid — Software Defined Corporation

MFid · Measured Fidelity

Did you get what you paid for? Here is the number.

Vendors make promises in spec sheets, SLAs, and proposals. Teams make them in roadmaps and OKRs. MFid measures how much of each written promise was actually delivered, rolls the verdicts into one score from 0 to 1, and itemizes exactly where the gaps are.

Request an MFid Engagement Read it in plain English →

Not software-defined networking — the firm’s name means something different.

How the score is built

Collect the promises

Every measurable claim in the contract, the datasheet, the proposal, or the KPI target. What is written down, not what was implied.

Measure what was delivered

Independent measurement over a real window of time that includes your worst day. Not the vendor’s own dashboard.

Compare, promise by promise

Each claim gets a verdict. The verdicts roll into one score, and the report lists exactly where the gaps are and what to fix first.

Four questions, asked of every promise

A claim can miss reality in four distinct ways. Each dimension is scored from 0 to 1 against its own published rubric.

Dependability

Does it hold every time, not just on average?

“Responds in under 200 ms” — measured repeatedly, scored on spread and shortfall.

Efficiency

Does it deliver the number on the sheet, at the cost that was quoted?

“500K IOPS” observed at 340K scores 0.68 on that claim.

Observability

Can you see the gap yourself?

“Audit logs for every admin action” exposed only as a quarterly PDF scores low.

Integrity

Does the design actually serve the stated purpose?

“Zero Trust” running on a perimeter VPN scores low no matter how fast the VPN is.

MFid = (D × E × O × I)^1/4

Geometric mean of the four dimension scores. The weakest dimension caps the result, so one broken promise cannot hide behind ten kept ones.

What clients use it for

Vendor and SLA verification

Score a renewal before you sign it. The itemized gaps become the negotiation, and the score becomes the clause that governs the next term.

KPI performance optimization

Pick the five to ten indicators your workflow actually depends on — latency, availability, cost per unit, turnaround time, error rate — measure each against its target, and remediate in the order the score dictates. The weakest-link math points at the fix with the highest return first.

Platform and purchase decisions

Compare candidates on measured fidelity to their own datasheets rather than on feature checklists. Over-delivery is clipped at 1.00; a vendor that under-promises and over-delivers earns an annotation, not a bonus.

Internal and MSP accountability

Publish a score for your own IT function or for the MSP you pay, as we do for ourselves on the status page. Within our fractional and managed engagements, MFid is the monthly scorecard you hold us to.

We score ourselves first

This website’s own uptime, latency, and reachability are scored with MFid and published live — alongside the promises we make about ourselves that we have not instrumented yet. If our score slips, you see it before we explain it.

See our live MFid score →

Go deeper

Plain English — the whole idea, no formulas. Car people: it is a dyno.
Theory — fidelity, the four dimensions, the math, the limits.
Methodology — evidence tiers, scoring rubrics, version history.
Walkthrough — a real public SLA scored end to end.
Compare — MFid next to SLOs, DORA, and ISO 25010.
Intake — the ten questions that start every engagement.
Manifesto — the ethic: we don’t assert, we calculate.

Bring us a claim. We will tell you the number.

Vendor renewal on your desk, a KPI that keeps missing, a platform decision? Score it before you commit.

Request an MFid Engagement