Service
Contested Metric Diagnostic
We help you settle a number fight: one metric, two disagreeing artifacts, a written ruling, and evidence SQL a controller can re-run — typically in about ten business days.
The work
How we help
When jobs are green and both dashboards refreshed last night, the problem is not “the pipeline failed.” It is grain, a filter, a copied business rule, or CDC that dropped a delete. We follow one metric from the operational document through ingest, fact, mart, and BI until the break is named.
The diagnostic is a scoped SOW. Implementation of the ranked fixes is a separate engineering engagement if you want it.
When this is the engagement
The jobs are green, both dashboards refreshed, and nobody will yield — close, commissions, a branch, or an agent is about to pick a side.
Contracted and invoiced by Havilah Technologies LLC. Delivery in your warehouse and your git.
- 01Take one metric and two artifacts — report, extract, bonus file, or an agent answer — as the intake.
- 02Trace the number from operational document through CDC, warehouse fact, certified mart, and BI calculation.
- 03Issue a written ruling: which number is valid for which decision (close, operations, compensation).
- 04Deliver parameterized evidence SQL your team re-runs.
- 05Rank the fixes with hours and owners, plus a do-not-touch list for bonus formulas, GL maps, and CDC filters.
Typical work
What an engagement looks like
01
Intake
Metric name, two artifacts, and access to warehouse, git, and the workbook.
02
Trace
Document → ingest → fact → mart → BI → downstream (bonus, scorecard, or agent).
03
Ruling
Which figure is valid for which decision, and the break class (source, grain, mapping, CDC, report logic, or copied rule).
04
Handoff
Evidence SQL, ranked changes, and the list of objects that must not be edited without a named approver.
What you receive
Deliverables
- A written ruling: which number is valid for which decision
- Evidence SQL your team re-runs
- Ranked changes with hours and owners
- A do-not-touch list for bonus, GL maps, and CDC filters
Capabilities
In scope
- Trace from operational document through CDC, fact, mart, and BI
- Ruling: which number is valid for close, operations, or compensation
- Parameterized evidence SQL your team re-runs
- Ranked fixes and a do-not-touch list
Method
Trace the number from source to report
01
Operational document
Invoice, job, contract — header vs line.
02
CDC / ingest
Deletes, late arrivals, what the pipeline actually kept.
03
Warehouse fact
Grain. The hop most fights actually live in.
04
Certified mart
The table both sides call source of truth.
05
BI calculation
Joins, filters, table calcs nobody remembers putting in.
06
Downstream
Bonus, branch scorecard, or the agent about to quote it.
- 01Ruling: which number is valid for which decision (close vs ops vs compensation).
- 02Break class: source, grain, mapping, late CDC, report logic, or a copied business rule.
- 03Evidence SQL — parameterized, they re-run.
- 04Ranked changes, hours, and owner.
- 05Do-not-touch list: bonus formulas, GL maps, CDC delete filters unless a named human approves.
Related services
Analytics Architecture & BI
We define and deliver the metric layer so Tableau, Power BI, or Looker reports the warehouse — not a fourth version of revenue.
Data Integrity, Quality & Governance
We put tests, lineage, owners, and reconciliation in place so accuracy holds after delivery — at close, audit, and in regulated programs.
dbt, SQL & Transformation
We build and refactor the dbt and SQL layer that turns landings into certified marts finance and operations can both use.
Discuss Contested Metric Diagnostic.
Contested Metric Diagnostic is contracted under Havilah Technologies LLC. Tell us the stack, the systems, and the outcome.