About - Daniel Im
My career started in quota-carrying sales roles at Xerox, then as an early SDR hire at several startups including Spectrust and Arkose Labs. Working inside those organizations gave me direct exposure to how operational systems - or the lack of them - affect what revenue teams can actually execute on a daily basis.
While leading SDR teams at YuJa, I started building internal frameworks to address gaps in CRM structure, reporting visibility, and workflow coordination. What began as solving immediate operational problems evolved into a systematic approach to revenue infrastructure - one that I now pursue full-time through Revenue Operations and Sales Operations work.
Ownership & clarity before automation
Most RevOps problems trace back to unclear responsibility or inconsistent definitions in the CRM. I focus on making sure the data model, ownership rules, and process expectations are solid before building anything on top of them. Automation built on an unclear foundation just makes the problems faster.
Reduce friction for the people doing the work
If a process requires too many manual steps, it will eventually get bypassed. I prefer building systems that guide the correct behavior automatically - routing logic, validation rules, structured fields, and automation that removes repetitive administrative work rather than adding to it.
Build for scale, not just the immediate problem
I treat RevOps systems as infrastructure. One-off fixes create technical debt. I try to build repeatable frameworks that hold up as teams and products grow - governance models, segmentation rules, and reporting structures that don't need to be rebuilt every quarter.