We have the same model as you at the company I co-founded. The only valid worry that comes to my mind is a 50-50 split with no person designated as the boss. But you already have that part sorted.
At least amongst Bay Area startups at your stage, a 50/50 split is common. It has its advocates (YC amongst them) and detractors.
Given how common this is, it's peculiar that this VC is bringing this up so early in the lifetime of the company. CEOs often get different refresher packages as the company grows and assembles a board, but you're not at that stage yet.
If your co-founder is happy with the current arrangement then he can just tell the VC no thanks and everyone can move on. It's your company, not your VC's.
More generally, the most troublesome part of all this is that, at your early stage, every minute spent talking about this is a minute not spent on your product and customers.
Each integration is supported as both a source and a destination. So you can have two one-way syncs set up between systems A and B, thus moving data in two directions.
Each sync in Polytomic is one-way so we're not forced to deal with collisions all the time.
But you can, on a per-field basis within a sync config, declare that field not to be synced if the destination system already has a value in the corresponding field.
This setting is a proxy for deciding where your source of truth is for each field if you are indeed setting up two-way syncs.
Most customers are pulling data into their data warehouse, then syncing from queries that generate other values back into other systems. This issue doesn't come up there. But customers of ours doing two-way syncs between, say, HubSpot and Airtable or such do need to decide where the source of truth is for each field.
[email protected]
www.linkedin.com/in/ghalibs www.twitter.com/ghalib