How We Got Here
It started with a fuel tank
In 1986 I was an engineering student when my dad asked if I could write a BASIC function to calculate fuel volume in a horizontal tank — a problem requiring integral calculus to solve. I could. That was the beginning.
What followed was 16 years of building whatever needed building — contracts, consulting, desktop apps, things that didn't have names yet. No career ladder. No safety net. Just problems needing solved. I learned every technology because I had to. Pediatric care tracking systems. Telemarketing platforms. Point-of-sale for specialty retail. Loan servicing migrations. If someone had a problem and I could solve it, I took the job.
Then Triple E
In 2001, my dad funded a company. My brother handled hardware and operations. I had the vision and built the entire software platform — nearly all of it. Database replication over dialup because SQL Server didn't do it yet. PCI-compliant credit card processing when only the big companies were attempting it. Reverse-engineering COM protocols because we had no other option. Controlling fuel pumps, taking payments, running the IDE live on client sites because that's what it took to get it right.
800+ convenience store locations. The company sold in 2016 for millions.
Enterprise scale
After Triple E, I spent a decade at PACCAR as the technical lead on a 700,000-line application deployed to 2,500+ workstations worldwide. Over eleven years I became whatever the problem required — technical lead, business analyst, Scrum Master, .NET developer, automation builder. I solved things that had been written off as unsolvable.
Then Experlogix, where I architected CPQ systems — configure, price, quote — for complex manufacturing. Led major implementations, wrote conversion tooling, pushed the product further than the documentation said it could go.
And now, CBASCo
Forty years in, I've reached a point where I've seen enough industries, enough architectures, and enough failures to know exactly what matters when building software: understand the domain, design the right solution, and ship it.
CBASCo is a small, highly engaged team of engineers built on that foundation. We're not trying to be an agency. We're not chasing headcount. We take on hard problems — the kind where the domain is complex, the stakes are real, and the thing genuinely needs to exist — and we solve them with the full weight of four decades of architectural experience.
We're selective about the work we take on. If we say yes, you get our full attention.