10 misconceptions on how to work with an archviz studio
This article is first and foremost addressed to architecture firms, property developers or whatever types of clients we work with on a daily basis (hence why I'm hoping to get it published on architecture media). As in my previous article, the idea is to tackle common misconceptions that undermine the quality of the work we do as collaborators, in order to foster better communication and, down the line, better deliverables. I'd love to get your opinion and experience insight on the topic.

Foreword for archviz audience
This article is first and foremost addressed to architecture firms, property developers or whatever types of clients we work with on a daily basis (hence why I'm hoping to get it published on architecture media). As in my previous article, the idea is to tackle common misconceptions that undermine the quality of the work we do as collaborators, in order to foster better communication and, down the line, better deliverables. I'd love to get your opinion and experience insight on the topic.
Introduction
The more I work with architects and property developers the more I've noticed biases in the way they understand what visualization studio services are actually about. I myself am an architect and can't help to see how similar this situation is to architects trying to explain their role to their own end clients.
It thus becomes all the more curious to me that their frustration doesn't translate in a better understanding of their own contractors.
With this article I'm trying to pinpoint common misconceptions architects tend to have when hiring archviz studios, and clarify what this collaboration is actually about. For the sake of keeping it short, I trimmed the list at the tenth item.