Hey, I'm Cam. I build systems, businesses, and weird ideas.

I was around eight when I took the robot apart.

It was a toy. It walked, which at the time seemed like the whole point of it. I wanted to know why it walked. So I opened it up and looked.

That's the part that stuck. Not the robot. The question.

Tron was the first movie that made me look at the world differently. It showed me that inside every system there's a world of light, logic, and possibility. I was already the kid taking things apart, and here was a movie telling me the inside was worth seeing.

Birthdays at Nickelcade, surrounded by neon lights and arcade energy. Journey, Depeche Mode, Chicago. That was the sound underneath everything.

And the 80s built things to last. No planned obsolescence. No shortcuts. I didn't have words for that then. I just knew those machines felt built on purpose.

I've spent eleven years learning how people decide, trust, hesitate, and buy, starting in customer-facing work when I was sixteen.

Sales taught me it's fine to fall on your face. No's don't mean no. They get you to the next yes. The bigger lesson took longer, and I still repeat it to myself: some days you gotta sit in the shit. Growth doesn't come from comfort.

But the thing I kept noticing had almost nothing to do with selling.

The tools were fine. Every one of them was capable and well built and did what it said on the box. What wasn't connected was everything between them. So every new deal started back at the drawing board. Somebody rebuilding context that already existed somewhere else. Pulling information out of one system by hand to get it into another. Reconnecting pieces that had been connected last week, by a different person, for a different deal.

The software wasn't the problem. The space between the software was the problem. And there was always a person standing in that space, holding both ends.

I kept bringing it up. I'd show up prepared. Build a demonstration nobody asked for. Put together a small tool to show what I meant. Try to explain why a different approach would hold up better.

Mostly it didn't land. The preparation didn't register. The approach was different enough that it read as a detour.

For years I thought the way I think was the problem.

Then it got specific.

In 2025 I was the back office for two financial advisers. Both of them. One person.

Investment paperwork. Insurance paperwork. Underwriting. Financial plans. Past-due premiums I had to call and collect on. Pipeline. Knowing which decisions needed an adviser and which ones didn't. Two calendars.

None of it was hard on its own. What was hard was that I was the only place all of it connected. The business ran because I remembered how the pieces fit together.

Then I sent a financial plan to the wrong client.

Moving too fast, not paying attention, didn't check the recipient before it went out. That one's mine. But I had also become the only safeguard in a process that needed more than one, and nobody had noticed that — including me.

I could see the shape of the fix. I couldn't build it. Financial services is regulated for good reasons and the constraints were real; you don't casually redesign a workflow with compliance sitting on top of it. So I understood the problem and had no way to touch it.

I was still inside the system.

What I did see clearly: the advisers who grew got out from under their own operation. The ones who stalled got buried in it. That had nothing to do with how good they were at the actual job.

What moved my thinking wasn't a realization. It was conversations, over a long stretch, with people doing my job on bigger teams.

They weren't better at it than I was. They had somebody who handled paperwork and only paperwork. Somebody whose entire job was scheduling. A person to hand a thing to when it left their lane. Nobody was carrying the whole shape of it in their head, because nobody had to.

The difference wasn't the people. It was that the work had somewhere to go.

So the question changed. Not why is this so heavy — that one I already knew the answer to. The new one was whether technology could do some of what a bigger team does. Not replace anybody. Just hold the parts that shouldn't have to live in one person's memory.

Around December 2025 I was working part time, in the middle of a transition, trying to build a path toward work that actually fit.

What I wanted was specific. Operations. Enablement. Training. Systems. Technology pointed at how people actually work instead of at how a demo works.

I want to be clear about something, because the easy version of this story is wrong. I wasn't trying to escape a job. I like my job and I like the company I work for. This was never an exit. It was about fit.

Money was part of it. I'm not going to pretend it wasn't. It just wasn't the reason.

The reason was ownership, and I don't mean control. I wanted to be responsible for something. Something that would keep working when I wasn't in the room, and that could reach more people than I can one at a time.

So I started building. Not because anything had happened to me. Because that was already the direction I was headed.

Then in April I applied for an internal role and didn't get it.

The role wasn't about AI. It was about helping people get back into the workforce — people who'd been out a while and were trying to come back. Teaching. Sitting with somebody while their confidence rebuilt. Taking something complicated and making it usable for a person who needs it to be usable.

I was more upset than I expected to be. Butt hurt, honestly. A little sad, because I really did like the job and I liked what that job would have been.

And it landed on something older. Overlooked again — not by anyone in particular. Just the same pattern I'd been walking into for years. Prepared, and it doesn't register. A different approach, and it reads as the wrong one.

The thing I spent years trying to fix became the thing I learned to use.

I don't think of myself as an AI person. AI is the current tool for a question I've been asking since I was eight. What I actually care about is the space between technology and people — building the thing around how a person really works, and helping somebody trust it enough to use it. A system nobody understands or trusts isn't a system. It's just more work.

Nobody should have to be the glue.

I was the glue, for two people, for a while, and the business worked because I was there holding it. That isn't a compliment to me. It's a design flaw.