A reference software architecture (RSA) enables systematic reuse of domain knowledge and components when developing concrete architectures and systems, leading to reduced development cycles, increased quality, and conceptual integrity. However, creating an RSA is challenging because it requires an initial investment and should ensure adequacy of the RSA for the organization. In this presentation, we report the experiences of creating an RSA for an Argentine R&D company in the domain of ground radar monitoring (GRM) systems. This was a brown-field development: we departed from an existing system for processing telemetry from radars, and we evolved it toward a more general architecture. We aimed to adjust the development estimates for GRM products using the RSA as the baseline. Our architecture-centric approach was driven by the company’s business goals and the corresponding quality attributes for the product family. We captured these quality attributes through a Quality Attribute Workshop, then engineered them into an RSA blueprint following a three-iteration Attribute-Driven Design process. We documented key design decisions and architectural views, and evaluated the RSA using the Architecture Tradeoff Analysis Method. Along this path, the architectural vision defined an iterative and prototype-based development strategy and infused architecture-based techniques into the software division of the company. The resulting RSA successfully articulated the main elements and business rules of the GRM domain via a set of architectural mechanisms and practices.