Item: Litmus
Rating: 8
Author: Alan Bradford

Use Cases and Deployment Scope

We use Litmus as the final QA and approval tool for final emails. These emails require stakeholder sign off for content, creative and content sign off and technical sign off. This occurs after emails are fully code complete by our agency partners. Any suggested changes are tracked, checked off, and logged before send the email to production.

Pros and Cons

Rendering completed HTML in a variety of key formats
granular feedback suggestions
builder tools to troubleshoot in detail

Direct interactions with ESP like Marketo (rather than sending email)

Return on Investment

Reduced back and forth on small edits. one round, multiple people
No more need to "send the email to myself" to test rendering in Outlook
Ability to export completed html into a portable format

Collaboration with Litmus

Having precise pointers for feedback is key. Sometimes describing exactly what or where the change is can be tough, and Litmus reduces the "is this what you meant" back and forth. Additionally where commenting back and forth, tracking the conversation across multiple commenters is great.

Key Insights

Do you think Litmus delivers good value for the price?

Yes

Are you happy with Litmus's feature set?

Yes

Did Litmus live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Litmus go as expected?

I wasn't involved with the implementation phase

Would you buy Litmus again?

Yes

Other Software Used

Adobe Marketo Engage, Slack, Webex Meetings

Likelihood to Recommend

Where ESPs and Marketing Automation platforms are excellently placed for deployment and programming, their internal build tools are often lacking. They are unable to keep pace due to large numbers of dependent systems. Litmus is smaller and more nimble, able to add features at a quicker pace. It can specialize in that rendered review space.

Litmus Email review

Overall Satisfaction with Litmus