Skip to content

Instantly share code, notes, and snippets.

What would you like to do?
<p>{% if customer.clearbit-location == "FR" %}
{% if customer.first_name != blank %} {{ customer.first_name | capitalize }}{% else %}{% endif %},
{% else %}
{% if customer.first_name != blank %}{{ customer.first_name | capitalize }}{% else %}there{% endif %},{% endif %}
{% if customer.account_clearbit-tags contains "SAAS" %}<p>Quick question to start - any chance you’ll be at SaaStr next month? Would be great to meet you there - reply and let me know!</p>{% endif %}
<p>Over the past few years, we’ve seen a new role emerging at within scaling startups - <a href=";utm_medium=email&amp;utm_campaign=opinion&amp;">the growth engineer</a>.</p>
<p>In short, we observe that Head, Director &amp; VP of Growth titles {% if customer.clearbit-employment_title contains "growth" %}, like yourself,{% endif %} are becoming more abundant, but the “growth hacker” is fading away. The “hackers” aren’t rebranded marketers but engineers.</p>
<p>The explosion of SaaS tools (and with it, data silos) together creates a need for a cross-functional, operations role to support go-to-market teams.</p>
<p>These roles are filled by engineers that roll up to the CMO/COO (not CTO) as part of a growth team. Their job is to enable go-to-market teams through “joining the dots” between tools, teams &amp; data, optimizing the business rules that drive growth.</p>
<p>In this post, we’re going to share where growth engineers come from and why they’re here to stay.</p>
<p><strong>Read: <a href=";utm_medium=email&amp;utm_campaign=opinion&amp;">Why 2019 is the year of growth engineering</a></strong></p>
{% if customer.account_salesforce-type contains "Prospect" %}<p>And if you’re curious to try out Hull for your growth engineering at , shoot me a reply too - I can set you up with a 14-day free trial this January.</p>{% endif %}
<p>That’s all for this week - let me know if you have any questions!</p>
<p>Ed Fry<br>
<strong>'Ed of Growth, <a href=""></a></strong><br>
<em>For {% if customer.clearbit-employment_role == "sales" %}people in sales{% elsif customer.clearbit-employment_role == "marketing" %}marketers{% else %}people{% endif %} who like curly brackets }}</em></p>
<p>P.S. Want to see the templated personalization behind this email? <a href="">Checkout this gist.</a></p>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment