Tech Second Founders.

I

The Argument

The people closest to the work build the most honest systems.

Not because they are better engineers. Not because AI chose them. Not because they read the right books or attended the right schools.

Because they already know what the system needs to do.

They know it because they have done the work. They have stood the line. They have run the numbers at midnight, lost sleep over a bad health inspection, and felt the exact moment when a tool fails the person using it — because they were the person using it.

That is a different kind of knowledge. It builds different software.

II

My Story

I got my first computer when I was six years old.

Apple II Plus. Then a VIC-20. Then a Commodore 64. I knew DOS like the back of my hand. By the time I was twelve, I was coding in BASIC.

Something happened in those early years that never left me. I moved past being a user — past playing the games and running the programs — into being a creator within that fledgling space. That shift, from consumer to builder, from using the tool to making the tool — that never really left me.

In 1989, when I was a teenager, computers were still genuinely niche. Not mainstream. Not inevitable. Niche.

And I made a choice.

Not a reluctant choice. Not a fearful one. A deliberate one. I looked at two worlds — the kitchen and the computer — and I chose the kitchen. Because I loved it more. Because it fed people. Because the work of cooking, of feeding, of hospitality, felt more alive to me than anything a screen could offer.

So I became a chef.

What I did not do was leave the other world behind.

Graphic design. Web design. Visual Basic in Excel. A 48-page workbook I built over eight years to run my restaurant — every recipe cost, every schedule, every invoice, tracked. The Matrix, we called it. And it was amazing — genuinely powerful. But there are things we can do now that leave Excel behind entirely. The data integration layer of a modern application is something macro-enhanced spreadsheets can never replicate.

The technology never left. It ran alongside the kitchen, quietly, for thirty-five years.

The branch happened in my teens. The two paths ran parallel for three and a half decades.

In 2026, in my fifties, they converged.

III

What Changed

The tools democratized.

What would have cost $500,000 to ideate — let alone prototype — became executable in under eighteen months, by one person, in a real kitchen, while that kitchen was open and serving guests.

I did not learn to code. I have always known how to code.

What I gained was a collaborator — an AI brigade, structured like a professional kitchen, because the only person at the table who knew how to run one was me — that could take thirty-five years of restaurant intelligence and turn it into a platform.

This is not a story about technology democratizing expertise.
This is a story about expertise finally finding its tools.

IV

Who We Are

We are not "non-technical founders."

We are the most technical people in the room. We just speak the language of the work, not the language of Silicon Valley.

A chef who builds restaurant software knows what happens at 4am when the smoker won't hold temperature. A developer who builds restaurant software knows what the API docs say.

Both matter. But only one of them has burned their hand on the answer.

V

The Real Thesis

The people who were always both — who had to choose one lane when they were young — can finally be both.

And they have an unfair advantage over everyone else.

Because they bring something no engineering team can manufacture: the lived intelligence of the work, encoded into every decision.

The financial engine in ChefLife cascades a price change from a vendor invoice to every recipe cost in the system before the chef finishes his coffee. That feature exists because I am the chef. I know what it costs to not have it.

The food safety system logs the temperature of every fridge every ten minutes, flags anomalies, and keeps a regulatory record that holds up under a health inspection. That feature exists because I have stood in front of a health inspector. I know what the stakes are.

No amount of user research produces that.
No amount of market analysis produces that.
Only living the work produces that.

VI

Memphis Fire

I am the Chef-Owner of Memphis Fire Barbeque Company in Winona, Ontario.

Fifteen years. Nearly 900,000 guests. 120+ awards. A Cultural Landmark designation from the Province of Ontario. Multiple appearances on Food Network Canada.

We've always been digital first — as much in-house as possible. Not because I loathe pen and paper. Because data is better. The technologist spirit ran through everything we did, even when the guests never saw it.

Memphis Fire was always a technology company that masqueraded as a BBQ joint.

It was never really about the food. It is a people story that features food.

After You Gotta Eat Here aired on Food Network, we were so busy that we lost touch with our books and our menu costs. We weren't neglecting the business — we were trying to keep the wheels on the ground. Growth hid the drift.

When we finally got systematic about cost management, we retained 2% more gross revenue in year one. Two percent. From gross. That is real money in a restaurant.

Most operators don't have the skill or the time to get there. ChefLife gives them both.