Client to ArchitectYou may not know what an architect does, what a client achieves with an architect, how much it costs; this page gives some insight through the work this architectural practice undertakes.
What an architect doesn't doAn architect is not a building designer, or a draughtsperson. The architect's purpose in life is not to draw plans or detail construction of buildings to the builder's ease or normal habits.
InsteadThe architect's job is to provide the technical expertise to give a physical form to the client's aspirations, hopes, ambitions.
From this Home Page you will already have gathered that the architectural practice of Emilis Prelgauskas focusses on the environmental responsibilities of buildings; and is most applicable to clients who value fulfilling their responsibilities in their own habitat.
Clients to this architectural practice chiefly are looking to:-
Thus these developments have very attractive payback financial aspects which save the capital cost of their environmental features many times over in the life cycle of the building.
Other pages describe the design philosphies, technologies and some of the completed projects of this practice.
Best practiceAs a result the architect's work may result in a building which does things differently to usual builder practice, with particular gains for the client in mind.
ProcessTo achieve this the architect:-
Clients choose to buy the expertise of the architect in those areas where they have the need.
Paying the architectThe foregoing demonstrates why the architect is not paid in relation to the quantity of drawings produced or the hours of work. Much that is being bought are the architect's training, skills and detailed knowledge, particularly where best practice matters are involved.
In effect, the client buys a clear chunk of the architect's time so that he can concentrate on the client's particular issues and priorities. In this way solutions embodying the features of value to the client are achieved.
For example, in the sketch phase, there are the widely divergent inputs of client brief, site practicailities, construction practicalities, regulatory requirements and environmental issues and technologies to meld together. That is not a technical task, it involves intuitive leaps reminiscent of pulling together a monster 1000 piece zigsaw puzzle. Only here the pieces are not all the same size or shape, as these are composed of mixed priorities, mixed emotion response and purely technical issues, some ephemeral, some tightly precise.
From the above it becomes clear that visible solutions sometimes aggregate swiftly, sometimes only with difficulty after 'writers block' or difficult gestation. It would be unreasonable for an architect to work on a variety of clients' projects and to charge each against possibly open ended work hours; since the solution in each case in part depends on the completeness of the client's brief as well as the architect's previous exposure to such issues and situations.
Thus an assessment of the complexity of each client's job in each task is made at the beginning and forms the basis of fee submissions.