Hi, I'm Dillon.
I spent years building dashboards before I admitted that most of them go unread.
Not because they were bad. Because asking a person to stop what they're doing, find the right report, work out which filter to change and then interpret a chart is a lot to ask. Most people quietly go back to emailing someone who knows.
Why I started Farrar Analytics
Put a natural language layer over enterprise data and something specific happens: people who had never once opened a report start asking questions. Not analysts. Salespeople, operations managers, owners. The barrier was never curiosity. It was the interface.
I watched that play out at enterprise scale and it struck me as unfair that it needed an enterprise budget. The underlying technology doesn't care how big you are. A thirty-person company has the same right to ask its own data a question as a thirty-thousand-person one, and the answer should take seconds either way.
So I started Farrar Analytics to bring it to everyone else. Any team, any size, asking their data a question and getting a real answer back.
Background
Ten-plus years working on data and analytics inside large enterprises: the reporting pipelines, the integrations, the rollouts, and latterly AI integration and MCP work.
- Enterprise data architecture. The patterns large companies use to keep data connected, governed and trustworthy, applied at a size that actually fits your business
- AI integration and MCP. Connecting language models to real business systems so answers come from your data rather than from a guess
- Org-wide rollouts. The part most projects underestimate: access rules, onboarding, and getting people to actually use the thing
- The reporting era. Power BI, Looker Studio, SQL Server and the rest. Still useful, and still what I reach for when a dashboard genuinely is the right answer
Farrar Analytics LLC is my own independent company. The businesses above are where I've worked over my career; none of them are affiliated with or endorse this one.
How I work
You're hiring one person, and you should know what that means in practice before you do.
-
You get a fixed quote, and the assumptions behind it
Every quote lists what it assumes about your systems. If reality turns out differently, we price that change before I do the work, not after, on an invoice.
-
Your data stays in your infrastructure
I connect to what you already run. Nothing gets copied into a platform of mine, and nothing is fed into third-party AI training.
-
You aren't locked to me
The connections, access rules and configuration live in your environment and are documented for your team. If you want to take it in-house or hand it to someone else, you can.
-
I'll tell you when it isn't worth doing
Sometimes the honest answer is that a dashboard is fine, or that your data isn't ready yet. You'll hear that on the first call rather than three weeks into a project.
Based in the Treasure Valley
I'm in Nampa and work with businesses across Boise, Meridian, Eagle, Caldwell, Garden City, Star and Kuna. In person when that's useful, remotely when it isn't. Plenty of the work happens over a screen share, but there's something to be said for being able to sit down with the person whose reports you're replacing.
Call (208) 391-3599 or email dillon.farrar@farraranalytics.com.