Fragmented systems
Your data is scattered across Jira, GitHub, Slack, drives, and a graveyard of spreadsheets. There is no single source of truth — and everyone on the team already knows it.
Most AI initiatives stall in the same place: tangled data, undocumented workflows, and dashboards nobody trusts. We fix that layer first — then build AI systems your teams actually use.
Your data is scattered across Jira, GitHub, Slack, drives, and a graveyard of spreadsheets. There is no single source of truth — and everyone on the team already knows it.
AI built on noisy data produces noisy answers. Teams stop trusting the system. Then they stop using it.
Dashboards report what already happened. Nobody can answer why — let alone what to do next.
AI doesn't fix this. It amplifies it.
Brilliant engineers ship technically impressive systems that nobody adopts. Not because the tech is wrong — because nobody mapped how the work actually gets done, and nobody brought the people along.
AI doesn't replace process design. It depends on it. And no model — however capable — fixes a workflow that nobody documented, owned, or agreed on.
That's the layer we live in. People and process, sitting between the engineering team and the business — and we'll be doing this work for decades.
We integrate, standardize, and clean the data underneath your business — so AI has something solid to stand on.
Internal copilots, automated triage, decision support. We wire AI into the work people actually do — not the work the slide deck describes.
The layer most AI work skips. We map real workflows, harmonize them across teams, and train the humans who'll use the system — because nothing else matters if nobody adopts it.
We audit your data, workflows, and AI readiness. We surface what's broken — and what's leverageable. Honest, not flattering.
We integrate sources, harmonize processes across teams, and ship the systems that run on top of them — alongside the people who'll use them. Engineering with the business, not at it.
We integrate into the real workflow and train your teams. Demos don't count. Usage does.
I'm a researcher and educator. For more than a decade, I've studied the layer this site is built around — the human side of how software, data, and AI work actually succeed or fail inside organizations.
My research explores how to curate data from heterogeneous sources and integrate it in ways that are both insightful and traceable — work that sits at the intersection of Software Engineering and Computer-Supported Cooperative Work. Over 150 publications. Leadership at the field's major conferences. A PhD from the University of São Paulo, a visiting year at UC Irvine, and an academic home at Northern Arizona University.
The gap I document in research is the same gap I keep watching organizations stumble into. Brilliant engineers, real business problems, and almost no one minding the process and the people in between. The technology gets the spotlight. The unglamorous middle is where the work actually lives or dies.
DataTruth AI grew out of that observation. I led an NSF I-Corps team through structured customer discovery — engineering managers, consultants, CTOs — and the same pattern surfaced again and again: brilliant teams stuck doing janitorial work on their own data, insights that never reach decisions, dashboards nobody trusts.
That's the work I do here. Senior-led engagements from someone who has spent a career on the human side of building things — and refuses to leave it to chance.
A focused diagnostic of your data, workflows, and AI readiness.
End-to-end delivery of a working system, integrated into how your teams already work.
Senior support for the people inside your organization doing this work.
You leave with a roadmap, working prototypes, and a short list of things you should stop doing.