Often when starting a new project in web development participants gain a lot of proprietary knowledge about a new subject, and distribute this knowledge inefficiently.
It has been my experience that when starting a new project, it may benefit the team to start building a glossary. Many companies have their own proprietary language they use internally and this language has no usage or meaning outside of their company. Talking to others about the project, will leave them confused without a knowledge of this vernacular, and leave you scrambling to define obscure terms.
Even if you never show your client the glossary, build it for yourself and anyone else working on the project. If by chance you quit, those who pick up on the project will have a great reference tool.