DataCrest Systems
A data and analytics practice in Huntersville, working with organizations across the Charlotte region.
Why limitations go on the artefact
DataCrest Systems was founded to build reporting and data infrastructure for organizations that needed to trust what they were looking at.
Our analysts had all written careful methodology sections, and had all later watched a single chart from that work appear in a board pack with none of it attached. The qualifications had been written. They had simply not travelled.
The problem is structural rather than careless. A visual is portable and a document is not, so any caveat that lives outside the visual will eventually be separated from it.
So the limitation goes on the tile. Source, period, and exclusions are part of the deliverable itself, and they are written to be read by someone who has never seen the underlying analysis.
What every client can expect
Limitations on the artefact
Source, period, and exclusions appear on the tile, not in a linked appendix.
Insufficiency reported
Where your records cannot answer the question, that is the finding we deliver.
Assumptions stated
Every model sets out its assumptions in language a non-analyst can evaluate.
Maintainable handover
Documentation and training so your team can extend the work without us.
Your infrastructure
Warehouses and pipelines are built in your accounts and remain under your control.
No proxy dressed as an answer
We will not substitute a weak indicator for a measure we cannot produce.
Who you will work with
Caleb Sterling
Data Analyst
Builds client reporting and sets the limitation-statement standard applied to every deliverable.
Managing Director
Leadership
Founded the practice and reviews every dashboard before it is released to a client.
Head of Data Engineering
Engineering
Thirteen years in warehousing and pipeline work across retail and distribution.