It would be nice to not have to enter data multiple times (although people might be in different suites and departments, which could be an extra field you have to fill out each time). Maybe that complicates things on the database side, I don't know.
A feature like that is something that I imagine needs to be decided and thought through very early on in the process.
If you do mass emails to general email boxes or do print pieces to companies with no indication of who it is for, it goes to the receptionist and they throw it in the trash.
The system really needs to essentially force people to make good decisions. One good decision is to stop sending stuff out to addresses with no name attached.
I'm just saying that an address is associated with a person. People have relationships with people, not companies.
Now, it may be an idea to let the user indicate the relationship between contacts. For example, you may be able to indicate that Joe works for Diane or that Diane is in the same division as Steve, but doesn't report to him.
That way when you look at the company, you could see something akin to an org chart.
Like you seem to be alluding, I haven't seen a document that identifies "who exactly is Zurmo for and what exactly does it intend to do."
When you try to appeal to everyone, you appeal to nobody.
Help me understand why you would need multiple addresses for a corporation of agency. What action are you going to take with that address information?
The focus should be on people, not companies. And when you look at a large client, like Linkedin, you should first see
1. the people you know,
2. then see the people others in the system have in their hotlist,
3. then see the people others currently in your firm know,
4. then contacts of users who are no longer in the system knew,
5. and then random people just entered into the system that nobody knows.
Or you should be able to define who you are looking for and see people in that order. It goes back to the concept of reverse social network.