One CRM Operator Bottlenecks Email
Jay Oram, head of dev at ActionRocket, on intra-agency collaboration on email
The bottleneck in email is usually not raw HTML skill, it is that one overextended operator owns both message logic and the light code edits needed to ship campaigns. In most companies, the person inside Braze, Salesforce, or Klaviyo is also handling segmentation, timing, and channel orchestration, so custom coding becomes a small side task. That is why brands often buy finished templates, component systems, or agency support instead of hiring a full-time specialist.
-
ActionRocket sees most client teams with one CRM person who can tweak email HTML but usually cannot build a full template from scratch. Even larger brands often outsource the base template so the in-house team can keep running daily and weekly campaigns.
-
The workflow split is real across the market. Figma’s marketing ops team writes marketing emails in Parcel, while product and engineering use Litmus only for transactional testing. Different email jobs sit with different owners, not one deep bench of email developers.
-
This is why tools separate into creation versus testing. Parcel is used like an email IDE for the few people actually editing code, while Litmus is often bought because the company already needs previews, QA, and broader marketer access.
The market is heading toward software and service that lets a CRM generalist do 80% of the work safely, then pull in specialists for the hard 20%. That favors reusable component libraries, direct ESP integrations, and agencies that productize advanced email builds into templates ordinary lifecycle teams can operate.