I think it’s as ignorant to want to ban kids from social media today as it was ignorant to want to ban my generation from video games 30 years ago. The kids at the time thought the adults were clueless people who did not understand technology. Kids today correctly think the same way about adults who are hysterical about social media.

Each parent can decide the time and age boundaries for their kids. But to think a 14 year old is going to accept being excluded from communication with their friends is just laughable.

(Though, to be a bit pedantic about it, kids don't use Facebook.)

1. You control whether your child has a phone and how much they are allowed to use it (Apple provides all sorts of controls for parents).

2. Every child in the school is not an addict. This is (for lack of a better term) a boomer view of the world.

The answer may sound glib but I don't mean it as such: don't have an unlimited plan and migrate existing customers off it.

You two can easily tell him no thanks and move on.

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.

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.

Meaning, sometimes people set up one-way syncs only. Our syncs don't have to be two-way.

Haha! I’ve been in this market for over ten years now. The term ‘CDP’ is notoriously ill-defined.

More generally, we move data in all directions, rETL is just one part amongst many others.

QuickBooks Online. All the applications we support are cloud versions.

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.

Our clients come in multiple languages. You can see the list here: https://apidocs.polytomic.com/guides/native-clients.

You can see here for sample code: https://apidocs.polytomic.com/guides/code-examples/overview.

The full API reference is here: https://apidocs.polytomic.com/api-reference.