Technical depth
Training in data science and engineering is how I build models, pipelines, and dashboards that can be explained clearly and run again after the handoff.
About
Founder & Principal Analyst
I started Vantyr Point Analytics because I kept seeing the same problem: plenty of data, not enough clarity. Teams have reports, but they still argue about which numbers are right. Others want machine learning before they can trust last month's results.
I work with you directly. We agree on the decision that matters most, build the simplest system that answers it, and document everything so your team can keep moving after the project ends.
For the past four years I have worked at Arizona State University, currently as Assistant Director of Strategic Financial Planning and Integration in EOSS Budget Planning and Analysis. I joined in 2022 as a Data Analysis Specialist supporting finance and HR operations, and my role has grown with the organization.
Day to day, I build the dashboards and analysis leaders use across HR, operations, housing and dining, and the teams that support them. The test is simple: if people do not trust a number, they will not use the report. That shapes how I scope client work. Agreed definitions come first, then the dashboard, and then a model only when there is a real decision behind it.
This is a solo practice by design. You work with the person doing the work: someone who still sits inside a large organization and has to make analysis hold up in front of everyday staff, not just other analysts.
The technical work comes from data science. The recommendations come from economics and from studying how organizations make decisions.
Master of Science
Data Science, Analytics and Engineering
Ira A. Fulton Schools of Engineering, Arizona State University
Master of Business Administration
In progress — expected December 2027
W. P. Carey School of Business, Arizona State University
Bachelor of Science, 2022
Triple major: Data Science, Economics, and Political Science
Arizona State University · Double minor: Philosophy and Communication
Training in data science and engineering is how I build models, pipelines, and dashboards that can be explained clearly and run again after the handoff.
Economics and four years inside university financial planning mean I start with the decision and the budget behind it, not with a chart type or an algorithm.
A recommendation has to hold up in a room of people who stop listening the moment the numbers look shaky. Philosophy and communication training is how I keep the story as rigorous as the math.
We start by naming the decision in plain language. That keeps the build focused — and keeps unused dashboards off your plate.
A model no one uses is not a finished product. A prediction built into daily work, with an owner and a way to measure results, is.
You work with me, not a handoff chain. I will be direct about scope, timeline, and whether a request will actually move the decision — and recommend a better path when it will not.
Every dashboard, model, and document I produce belongs to you, documented as it is built. I am glad to maintain it, and you are never locked in.
A short call is enough to scope a dashboard, a model, or the foundation work that makes either one succeed.