CBASCo

What kind of problems does CBASCo take on?

Hard ones. We're looking for projects where the domain is complex, the stakes are real, and the problem genuinely needs to be solved. That could be a greenfield system for an industry that's never had good software, a legacy platform that's failing under its own weight, or an integration challenge that three other teams have already failed at. If it's important and difficult, we're interested.

What don't you do?

We don't build marketing websites, generic web apps, mobile games, or simple CRUD tools. We don't do hardware, networking, or IT support. We're not the right fit for projects where the main driver is speed-to-market at the lowest cost. We're solution architects — we take on work that requires deep understanding of a domain and careful system design.

What industries have you worked in?

Over four decades: petroleum and energy, manufacturing, financial services, healthcare, retail and POS, education, CPQ and complex pricing, credit card processing, and more. The actual list is longer than that. We learn new domains quickly because we've learned so many — the patterns transfer.

How big is CBASCo?

We're a small, highly engaged team of engineers. That's deliberate. We don't scale by adding headcount — we scale by bringing deep experience to every engagement. When we take on a project, you get senior architectural thinking from day one, not a junior developer reading the documentation for the first time.

Can you fix something someone else built?

Yes, and we've done it many times. Abandoned projects, poor architecture, systems that were "almost done" years ago. We assess what exists, determine whether it's worth salvaging or needs to be rebuilt, and give you an honest answer. Sometimes the hardest thing to hear is that the right move is to start over — but if that's the case, we'll explain why.

What does an engagement look like?

It starts with a conversation about the problem. Not a sales call — an actual technical conversation about what you're trying to solve, what you've tried, and what's at stake. If we're the right fit, we'll propose how to approach it. Engagements can be fixed-scope projects, ongoing retainers, or consulting arrangements — whatever the problem requires.

What technology do you use?

Whatever the problem calls for. Our deepest experience is in the Microsoft ecosystem — .NET, SQL Server, C# — but we build across platforms: web, desktop, mobile, APIs, database systems, automation frameworks. We choose technology based on what's right for the problem, not what's trending.

How selective are you really?

Very. We'd rather do fewer projects well than spread ourselves thin. If we take something on, it gets our full attention and the full weight of our experience. If we don't think we're the right fit, we'll tell you — and if we can point you in a better direction, we will.