Strategy questions for using Sugar to allow multiple companies to share resources

[dehuszar]

I have a quick question which I have tried to search for, but I'm not entirely sure how to even describe it in keywords...

I am a single-person web design corporation, I work with a designer and art director who has a similar 1 man corporation. We have discrete projects, but work together on the majority of work. We would like to use Sugar, but are trying to figure out if it makes sense to just use one install in a shared space, or have two separate installs and then somehow tie relevant data together.

Security is an issue in either case. There is tremendous trust between us, but liability is nothing to sneeze at, and business being business, one never knows what the world will look like two years from now.

Has anyone else walked down this road before using Sugar? Any input would be welcome.

[dpuryear]

You can use the Teams feature to keep each other out of some data, no? That said, the SugarCRM admin will still see everything.

Also, what if you guys split up later down the road? Do you each get a copy of the DB?

From a business perspective, I'd do two instances.