Case studies

The situations, and how the work meets them

These are the problems clients bring. Each one names the challenge and the engagement that addresses it. Client names and measured results are added only when that client permits them.

Contested Metric Diagnostic

Two official revenues for the same month

Situation

Finance closes on one revenue figure. Sales or operations reports another for the same month. Both extracts refreshed overnight. The board pack cannot pick a side.

Challenge

The jobs are green, so nobody can call it a pipeline failure. The disagreement sits in the level of detail — an order total versus the line items — or in a filter, a copied business rule, or a delete the load did not keep. Close slips while someone reconciles it in a spreadsheet. Commissions or a forecast may already be using the other figure.

How the engagement responds

The diagnostic takes that one metric and the two artifacts. It traces the number from the source system through the warehouse to the report and writes which figure is valid for which decision, with evidence SQL the team can re-run. The rebuild, if they want it, is a separate statement of work.

View this service

Data Engineering & Cloud Platforms

The warehouse is not ready when close starts

Situation

ERP, CRM, files, or an API are supposed to land in Snowflake or AWS before finance starts close. Some days the file is late, a delete never arrives, or the job fails quietly.

Challenge

Analysts backfill by hand. The warehouse bill climbs because models and warehouses were never sized for the actual level of detail. The last engineer who understood the run is gone, and there is no runbook for what to rerun and what not to backfill.

How the engagement responds

The engagement designs the path from those sources into the warehouse, builds the load and the dbt or SQL models with tests, and leaves the repository and a runbook in the client’s cloud and git. The team can operate the job after handoff.

View this service

Analytics & AI-Ready Data

The report and the copilot do not share a number

Situation

Tableau or Power BI shows one revenue. A workbook shows another. A copilot or internal agent answers a leader’s question with a third figure, confidently.

Challenge

Each tool kept its own calculation. Nothing on the warehouse was certified as the version the business agreed to. The pilot looks advanced and still quotes a number nobody will defend.

How the engagement responds

The work writes the metric once, builds the certified mart, and points reporting at that layer. The agent is allowed to quote only after that boundary is written. The chart tool stays. The private calculation does not.

View this service

Governance & Data Quality

An auditor asks where the number came from

Situation

Close is filed from the warehouse. An internal audit, a regulated pack, or a new controller asks for the path from source to the figure. The answer is a diagram in a wiki and a thread in chat.

Challenge

Tests exist and nobody owns the threshold. Lineage is stale. Exceptions were decided in Slack and not written down. The number may be right, and the organization still cannot show it.

How the engagement responds

The engagement puts reconciliation, tests, and a named owner on the paths that land in close. Lineage is something an engineer or an auditor can follow. The exception path is written down. The client keeps the evidence after we leave.

View this service

Partners

The program has a client and no data workstream

Situation

A prime or delivery partner has won the platform work. The program still needs pipelines, models, or a Snowflake or AWS workstream built inside the client’s security boundary.

Challenge

An open request for extra hands does not give the program manager a scope, acceptance criteria, or a handoff. The work drifts into Slack, and the subcontract never becomes something the program can accept.

How the engagement responds

Havilah Technologies LLC takes a named workstream under a written statement of work, in the prime’s repository and cloud. Status and artifacts are what a program manager can file. Expansion is a change order, not silent staff.

View this service

If one of these is live, send it.

Name the metric or the workstream, and the decision that is waiting on it.

Request a fit call