SOLUTION ENGINEERING. REAL-WORLD IMPACT.CLEVELAND, OH · BUILDING EVERYWHERE

Making the
complex
work.

I’m David Gruhin. I connect business, technology, and people to build things that work. And keep working.

THE INTERSECTION IS THE INTERESTING PART.

Different disciplines. One connected perspective.

EXPLORE THE NODES
CURRENTLYCo-Founder & CEO at Hrizn
BUILDER. OPERATOR. RELENTLESSLY CURIOUS.
01 / SELECTED WORK

Less theory.
More making it happen.

Different industries. Different challenges.
The same instinct to figure it out
and build something better.

02 / HOW I WORK

Build aggressively.
Operate deliberately.

I’ve been the person writing the code.
And the person running the business
that depends on it.

That changes the questions you ask.

  1. 01

    Find the real problem.

    Listen to the people doing the work. Question the assumptions. A software problem is often a process problem in disguise.

  2. 02

    Connect the disciplines.

    Bring business context, operational experience, and technical thinking into the same conversation. Design for the whole system.

  3. 03

    Build. Test. Learn.

    Turn the idea into something people can use. Put it in front of them. Let what happens next inform what gets built next.

  4. 04

    Own what comes after.

    A working prototype is the beginning. Think through the permissions, the people, the maintenance, and the day after launch.

03 / THINKING OUT LOUD

A little perspective.
From doing the work.

Notes on AI, operating businesses,
and the space between what’s possible
and what’s actually useful.

THE SERIES BUILDING WITH AI IS EASY. OPERATING IT IS NOT.AUGUST 2026
PART 1

AI Does Not Fix a Broken Operating Model

I argue that dealerships have an operating problem rather than a software shortage. AI can automate a process, but it cannot decide what that process should be or make an inconsistent one consistent.

READ ON LINKEDIN
PART 2

The Dangerous Moment Is When It Works

The riskier case is the experiment that succeeds. I trace how a prototype quietly gains permissions and connected systems until a dealership is running production infrastructure nobody has acknowledged as such.

READ ON LINKEDIN
PART 3

The Real Work Begins After the Prototype Works

Working code is one layer. Ownership, monitoring, permissions, and incident response are the rest. I make the case that "can we connect it" is the wrong question to ask first.

READ ON LINKEDIN
04 / THE PERSON BEHIND THE WORK

An unconventional path.
A consistent curiosity.

I didn’t set out to work in automotive. Restoring pinball machines led to a chance conversation with a dealership owner. That conversation changed the direction of my career.

Before that, I was building digital experiences in publishing. Since then, I’ve run a dealership, co-built automotive businesses, and returned to software as the co-founder of Hrizn.

The thread through all of it? I like understanding how things work—and figuring out how they could work better.

Pinball restorer Live music enthusiast
More of the story on LinkedIn
GOOD WORK IS NEVER A SOLO EFFORT.
With a deep background in software development, David understands data driven decision making and applies it's principles to all aspects of dealership operations.
Matt CopleyLinkedIn recommendation · 2019
His intimate knowledge of technology and digital development has enabled him to help dealerships and dealer groups completely revolutionize their digital retailing.
Liz FarquharLinkedIn recommendation · 2020
Dave possesses the invaluable traits of being a terrific problem solver, extremely reliable, and a clutch performer when a high value project is short on precious time.
Nathan McGowanLinkedIn recommendation · 2016