Radix

Advisory through Scale Data, July to August 2025. CTO, 1 September to 3 December 2025.

I joined Radix through Scale Data to assess engineering delivery and the opportunity for AI in its products. That advisory engagement developed into the CTO role, with responsibility across engineering and product. To make a credible delivery plan, I needed to understand how the applications fit together and what the teams could take on while supporting them.

.NET Framework, SQL Server, React, AWS. Adjacent products on Angular and Azure.

What the company sells

Radix Analytics lets property owners and operators compare rents, occupancy, leasing, and availability. Radix Underwriting, formerly redIQ, helps investors, brokers, and lenders turn property financials into valuations and investment scenarios. RealRents provides search and listings for renters, with its public data also feeding Analytics. The assessment covered that estate; redIQ is the example below because its frontend and financial logic made the architectural choices particularly clear.

Mapping redIQ

I used Claude Code to investigate about 90 code repositories and hundreds of database tables, then checked its findings through extensive direct code review. For redIQ, that meant tracing financial-modeling logic through stored procedures, views, application controllers, and a custom messaging layer. Reading those connections mattered because a proposed change to the frontend could otherwise leave the same dependencies in place underneath it.

The financial logic was concentrated enough to keep at first. Much of the unnecessary coupling sat between it and a new React frontend talking to legacy .NET presentation and controller layers. I designed an incremental split: explicit backend APIs, financial logic left in the database behind domain-oriented interfaces. Individual capabilities could be refactored later through those boundaries. That was a way to simplify the application without an immediate rewrite of the underwriting logic, and without committing to a distributed architecture a simpler backend might have made unnecessary.

An architecture proposal is incomplete until it explains how the organization can get from the existing system to the proposed one while continuing to serve customers. The target diagram may be elegant, but the route depends on business rules, dependencies, and people whose knowledge is often concentrated in the parts everyone most wants to replace. I would want the proposal to show where that knowledge is preserved and how the engineers can verify each change.

Product roadmap and cloud migration

The underwriting work was designed around AWS, while adjacent products and data still depended on Azure. I put replication and migration into the product roadmap so Azure-to-AWS consolidation could follow the replacement of those capabilities. This let the plan account for the engineers needed by both efforts, instead of treating the cloud migration as work outside their existing commitments.

Engineering roles and capacity

I worked with about 25 engineers in Kosovo and a three-to-four-person platform team in Scottsdale. I traveled to Kosovo to check the assessment against the people who had to implement it. I reorganized teams into delivery pods, set a roles-and-responsibilities framework covering engineering, analytics, and science, and simplified titles and pay bands. I hired a principal architect in Germany to work closely with the Kosovo organization.

I led multi-day planning sessions in Kosovo to build a two-year roadmap by quarter and epic: effort, dependencies, staffing, leave, critical-person risk, and what hiring or attrition would do to delivery. I brought that plan into 2026 executive budgeting so the consequences of scope and staffing were visible.

By the end of the engagement, the teams had an agreed architecture, a capacity-based roadmap, and a principal architect to lead the technical work. Modernization was underway, and implementation continued after I left; the replatforming and cloud consolidation were not finished during my tenure.

A plan that schedules the same people against product delivery and migration as though each has their full attention is making a promise they cannot keep. It is the leadership team's responsibility to resolve that conflict before treating it as a delivery failure. The engineers need room to disagree with the plan without that disagreement being read as a lack of ambition.

Who did what

I led the architectural assessment and worked with the engineering and product leads on the delivery plan. I also recruited the principal architect to work with the Kosovo organization, whose engineers wrote the production code and continued the implementation.