I didn't set out to build a data company. I set out to solve a problem I kept running into — businesses with smart, hardworking people completely stuck behind the tools they were supposed to be using. The spreadsheet that was meant to help had become the thing holding everyone back.
I started as a freelancer. Early jobs: build a dashboard, clean up a report, make this spreadsheet do something useful. I was good at it. But the deeper I got into each project, the more clearly I could see that the dashboard was never the actual problem.
The problem was upstream. It was the broken pipeline feeding the dashboard. The three different spreadsheets that should have been one system. The report that a smart analyst was rebuilding manually every single Monday morning. The decisions being made on numbers that were two weeks out of date.
The moment everything clicked
There was one project — a mid-sized consulting firm — where the team lead spent 12 hours every month producing a client performance report. Twelve hours. Every month. Copy, paste, format, check, reformat, send. She was one of the sharpest people I'd worked with, and the system was consuming her.
I rebuilt that workflow in three weeks. Google Form → Google Sheets → Python script → branded PDF → auto-emailed to clients. What took her 12 hours now took zero. She cried. Genuinely. Not because the automation was clever — because she could finally spend that time on work that actually mattered.
That's when I understood what I was actually building. Not dashboards. Not automations. Not scripts. Time back. Clarity. The ability to make good decisions without having to fight the tools first.
Why I built Datavoris
Datavoris exists because most businesses deserve better data infrastructure than they have — and they don't need a full-time data team to get it. What they need is someone who understands both the technical side and the business side well enough to build something that actually fits how they work.
The name matters to me. Datavoris — data devour. It's the idea that good systems should consume your data problems, not create new ones. Automate the grunt work. Surface the signal. Let the people focus on what only people can do.
What I believe about data work
- The best dashboard is one you don't have to think about — it just tells you what you need to know.
- Automation should be invisible. If a system needs babysitting, it wasn't built right.
- Most "data problems" are actually process problems in disguise.
- Non-technical teams deserve tools they can actually use — not tools that require a technical team to interpret.
- AI is only useful when it's connected to real data and a real workflow. Otherwise it's just impressive-sounding noise.
What I've built
Where I'm taking this
Datavoris is growing into a reusable systems business — not just project-by-project work, but template engines, diagnostic platforms, and AI-powered tooling that any business can run with minimal setup. The goal is to make the kind of infrastructure that used to require a 10-person data team accessible to a 10-person company.
If you're reading this because you've got a data problem — a report that takes too long, a dashboard that doesn't answer the right questions, a system that requires too much manual effort — that's exactly the kind of thing I want to work on.
Tell me what's broken. I'll tell you how to fix it.
Founder, Datavoris · Agra, India