About Turbo Client Systems

Turbo Client Systems was founded in 2024 by a father-son team: John, a 20+ year Microsoft veteran and an active CISO for multiple companies doing federal contract work, and Charlie, a software engineer with roots in enterprise systems and database architecture. John's Service-Disabled Veteran-Owned Small Business (SDVOSB) certification is real and central to who we are. The team includes extended family too — a cousin handling UI/UX and graphics, occasional help from a longtime friend — small by necessity more than by design; we simply haven't needed to grow past people we already trust.

That practical streak goes back further than 2024. One of our founders got his start in IT at 13, taking an MCSE course his father taught on a U.S. military base in South Korea — he didn't finish the course, but the trajectory was set. After a stretch of college cut short by the 2008 economy and a couple of unrelated jobs, he landed in reporting and business intelligence roles at Universal Orlando and Darden Restaurants: automating manually-built reports, building out executive and partner reporting, and eventually moving into real database work — building a customer trait database, onboarding Microsoft Dynamics, managing Adobe Campaign, and picking up the SQL, ETL/ELT, and data-warehouse experience — including an Oracle-to-Snowflake migration — this team still draws on today.

That's where Turbo Client Systems actually starts. What's now WinDEETS began as a PowerShell script, then a Python prototype, then a full React application running on Electron — built nights and weekends with real dedication and effort while still working full time elsewhere, and largely self-taught, since the background above is data and reporting, not front-end web development.

In June 2025, that work became the full-time job. One of the first decisions was to rip out Electron and rebuild the desktop application on Rust and Tauri, because it was the faster, more modern foundation — even though Electron already worked. The rest of that year went into the commercial infrastructure a real product needs: billing, authentication, a marketing site, Stripe integration. Then we made a different call: give the product away, and charge the organizations that can actually afford it instead. Sunk cost doesn't get to make the decision — the right architecture and the right business model do.

In March 2026, at our first in-person all-hands, we set a new direction: governance, risk, and compliance. The months since have gone into the shared services our applications run on, then into RunDEETS itself — a compliance platform that's been in daily development for several months and is still accelerating. Partway through, we scrapped a fully-built, populated relational database schema in favor of a client-side graph architecture, because it was the right foundation for a product that promises customers we'll never hold their data. Same standard, applied twice: rebuild it when there's a better way, not when it's comfortable.

We're not going to pretend this was fast from day one — it wasn't, and we'd rather say that plainly than fake a smoother history. What changed is what usually changes: a small, closely-held, family-run team spent over a year learning web development, cloud architecture, and compliance frameworks the hard way, and that experience is exactly what's paying off in RunDEETS' pace now. The goal was never to build a typical company — it's to build the kind of place we'd actually want to work: low on hierarchy and busywork, high on autonomy. Here's what needs doing; go do it.