GTM engineers, what's the one tedious task you wish would just disappear? 👋
Dennis T. datalake sounds interesting; not too deep into this whole thing but consider interviewing some claygencies about that. as a small input: i would prefer to dump data once and get a solidified table back. because i need to do that once for a client where we take over because they did it themselves etc. thats what abdul said in the beginning. so its quite punctual. no sure if its a too big problem though. gtm engineers get paid to do it and often times you need to know whats inside this api blockbox. how it works etc. but datalake idea doesnt sound stupid, just need to be money validated.
I thought the same, remains the question if people are willing to pay for that - or building yourself is so cheap, that there is no reason to offer a service 😉
That’s actually a solid idea 👍 most teams I’ve seen end up hacking their own mini “data lake” with BQ or Airtable + Clay API to avoid re-enriching the same people/companies. having a central place to dump + dedupe before enrichment would save a lot of credits + headaches
Exactly Dennis - re-enriching the same people/companies is brutal on credits that’s why I usually set up a ‘master deduped table’ in clay, then only enrich new rows against it saves credits + keeps things clean. Do you already have something like that set up or still running everything raw?
Honestly, the most brutal task is reconciling messy, inconsistent data across multiple tables before any automation will actually run one wrong join or missing field and everything breaks it’s a total time sink even for experienced GTM engineers. what’s the task that drives you crazy? Dennis T.