Product Designer
I learned that cost, quality, and scalability are decided at the drawing board — long before production begins.
Tom Bassinger · How I Think
For thirty-five years I kept asking the same question.
Why do companies that grow faster often struggle harder? That question changed how I see every business — and it's where Operating Architecture™ began.
Executive Perspective
A career spent seeing the business from every side.
Over more than 35 years, I have worked across product development, company formation, operations, executive leadership, investment banking, investing, and board governance—advising organizations from startups to the Fortune 500 on how they design, deliver, and finance what they do.
Most careers give you one seat at the table.
Mine kept moving me around it — and every seat showed me something the others couldn't.
The Origin
I didn't start in finance. I started on factory floors and in product development war rooms.
At the University of Rhode Island, I studied under the founders of Design for Manufacturing and Assembly — a discipline built on one beautifully ruthless idea: every component of a product must justify its existence.
Can it be eliminated?
Can it be combined?
Can it be simplified?
I spent years applying that discipline in high-tech product design. Strip the unnecessary complexity out of a product and quality goes up, cost goes down, and it becomes easier to build, service, and scale.
Then one day it hit me. We spend enormous effort designing products. Almost nobody applies that same discipline to the business that delivers them.
The realization
We would never ship a product nobody designed. Most companies run a business nobody designed.
Then Came the Boardrooms
Hundreds of board meetings. The same two elephants in every one.
Elephant No. 1
"How do we grow revenue?"
Debated in every board meeting
Elephant No. 2
"How much cash runway do we have?"
Cash as survival, never as strategy
The question no one asks
"What is the business architecture driving this scorecard?"
That question eventually became more important than the numbers themselves — because the answer kept explaining what the numbers couldn't.
Financial statements don't create performance. They report it. The operating architecture creates it.
Why Clients Engage Me
A perspective built from every side of the business.
The advantage is not experience in any one discipline. It is the ability to connect strategy, operations, finance, capital, and execution—and see how a decision in one part of the business changes the economics of the whole enterprise.
Founder
I've felt what it's like when growth consumes cash faster than it creates it.
Operator
I've untangled the hidden activities, handoffs, and workarounds that quietly consume margin and cash.
Investment Banker
Two decades raising capital taught me how investors evaluate growth, risk, scalability, cash flow, and enterprise value.
Investor
I've watched enterprise value hinge on how efficiently a company converts demand into durable cash flow.
Board Member
I've seen leadership teams discover — too late — that the scorecard was hiding the system beneath it.
The value is not in any one role. It is in seeing how every decision connects across the business.
Working Together
Every engagement starts with the business—not a consulting model.
Some businesses need an experienced advisor at the table. Others need an executive willing to step inside the business, redesign the operating architecture, and help lead execution. The engagement is shaped by what the business needs—not by a predefined consulting package.
The Methodology
Experience led to Operating Architecture™.
This page is how I came to see businesses. The framework page shows what that thinking became — the principles, the five-step conversion model, and the outcomes it's designed to create.
Explore Operating Architecture™