To add to what the other user has said, it is used at a number of firms, but primarily in early stages of design. It's actually very solid for actual drafting

To add to what the other user has said, it is used at a number of firms, but primarily in early stages of design. It's actually very solid for actual drafting (Rhino originated out of an AutoCAD plugin), and does freeform surface modeling very well. It's the middle piece, bringing the design into a set of drawings, that is the sticking point, and something that Revit automates very well. It's not that Rhino can't do it, it's that it's a very manual process that requires a lot more steps and structured process than most firms are willing to invest. Also, the kind of work you'd use Rhino for doesn't flow well to other downstream CAD or BIM software that architects typically use. Yes, you can easily export linework, but at that point, you might as well keep it in Rhino. Somewhat unrelated, but Rhino's SDK is really solid and gives a ton of access to the software. It's amazing some of the things that can be done with it, and Rhino as a whole, but at the same time it's producing construction documents that's where the rubber meets the road as far as Architecture is concerned. Source: Former architecture student and Rhino plugin developer