It started with
a better question.

I'm just a regular guy from Northeast Tennessee who has spent most of my adult life working, leading people and solving problems. I've been in management roles since I was 18, served more than two decades in the military, and learned a lot from working with people at every level of an organization.

I've always dreamed big and had a habit of looking at things for what they could be, not just what they are. My mind is always coming up with ideas - sometimes enough that I have to grab my phone and record it, or I'll forget it five minutes later. Because when something doesn't make sense, I want to understand why and whether there's a better way.

Over the years, I've worked with a lot of different software systems and seen companies change platforms hoping to make things better - or sometimes just to save a dollar or two. Sometimes they did. But too often, fixing one problem created another. Features people relied on disappeared, simple processes became complicated, and employees found themselves working around the technology instead of the technology working for them.

Eventually, that got me thinking differently.

Instead of asking which platform was better, I started wondering what I could build if I started with the people actually doing the work.

That's how this began.

There wasn't a grand plan to launch a technology company. There were real problems in front of me, and I started trying to solve them. What began with "I wish our system could do this" eventually became:

"Why don't we build what we actually need?"

There was one obvious problem with that idea: I didn't know how to build software.

I don't come from IT, coding or software development. I have an automotive degree from the early 2000s to work on cars that, in today's society, are considered antiques. But what I do have is years of experience, an understanding of the problems, and a pretty clear picture in my head of what I want things to do.

Technology and AI changed what was possible. They didn't give me the ideas or the experience behind them - they gave me the tools to actually do something with them. I could take technology created by people far more technically skilled than me, put the pieces together, test it against what I knew from the real world, and keep working at it until I had something that actually worked.

I didn't learn how to think like a software company. Technology finally gave me the tools to build like one.

And the more I built, the clearer my philosophy became.

Technology can be incredibly complex underneath, but it shouldn't feel complicated to the person using it. Let's face it, the employee needs tools that make sense and help them do their job. Leadership needs the visibility to understand what's happening and make better decisions.

Complexity belongs in the system. Not in the user's day.

Then I began seeing something I hadn't expected.

The problem I was trying to solve wasn't unique to one company, it was all over. Every business may operate differently, but their employees have to adapt the way they work to fit technology that was never really built around them.

That's when I started seeing the potential for something much bigger.

OutcomePoint grew from a simple idea: start with how people actually work, understand what they're trying to accomplish, and build the technology around that.

And that's really where the name OutcomePoint comes from. Figure out where you're trying to get to, then build a better way to get there.

Listen, I'm not a traditional tech founder. I'm still a regular guy who dreams big, sees potential and believes things can usually be made better.

The difference is, somewhere along the way, I decided to start building what I could see.