Senior Lifecycle Marketing Manager
Prime Corporate Services · Salt Lake City, UT · 1 mo ago
On-siteMarketingFull-time
We need to output HTML fragment with sections: About the role? Actually description includes "Description" then "Who We Are", "Why You’ll Love Working Here", "Benefits & Perks", "Requirements" (which includes many sub-sections). We need to use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. The posting includes description of role, responsibilities, requirements, benefits, etc. No explicit Pay or Schedule given, so we should not create those sections unless present. Benefits present: "Benefits & Perks" list. So we create
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. The posting includes description of role, responsibilities, requirements, benefits, etc. No explicit Pay or Schedule given, so we should not create those sections unless present. Benefits present: "Benefits & Perks" list. So we create Benefits
with of items.
We need sections only when posting has real specific content. So we can have:
- About the role
(maybe from description). Could also be "Responsibilities". The description includes responsibilities: own email and SMS ecosystems, architect automations, write copy, build segments, monitor deliverability, partner with design/engineering, etc. So we can put responsibilities under Responsibilities
. Also "Who We Are" could be About the company
but not in list; but we could use "About the role" for role description and maybe "About the company" not required. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. We can map:
- About the role: brief overview of role (the first paragraph maybe).
- Responsibilities: detailed duties.
- Requirements: includes education, experience, etc. Could split into Requirements and Qualifications? But we have both headings. Could put education/experience under Requirements, and maybe skills under Skills. However the posting includes "Requirements" section with sub-bullets: Prospecting Ecosystem, Customer Ecosystem, Platform & Automation, Deliverability, SMS, Testing, Measurement & Compliance, Collaboration, Accountabilities. Those are more responsibilities/duties. Actually those are detailed responsibilities. The "Minimum Education Requirements", "Minimum Experience Requirements", "Required Outside Training", "Physical Requirements" are qualifications. So we could treat:
Responsibilities: the bullet list under "Requirements" heading in the posting (the big list). But that heading is called Requirements in posting, but we need to map to our headings. To avoid confusion, we can treat the posting's "Requirements" as Responsibilities (since they are duties). Then we create a separate "Qualifications" section for education, experience, training, physical requirements. And maybe "Skills" for specific skills like ActiveCampaign, Salesforce, copywriting, HTML/CSS, etc. But we can also put those under Qualifications.
We need to avoid filler. Ensure we preserve all substantive information.
Let's extract content.
First, description paragraph:
"PRIME Corporate Services is seeking a Senior Lifecycle Marketing Manager to own the email and SMS ecosystems that carry our prospects and customers through their entire journey with us. Reporting to the VP of Growth Marketing, this person owns two distinct engines: the prospecting ecosystem that converts leads into booked consultations, and the customer ecosystem that drives onboarding, retention, and expansion across our full service portfolio. Both need to be maintained, measured, and materially improved. This is a hands-on individual contributor role. You will architect the automations, write the copy, build the segments, monitor the deliverability, and read the results. You will partner with Design on creative and Engineering on data integrations, but you own the program end to end. The ideal candidate is equal parts systems thinker and marketer: someone who gets satisfaction from both a clean branching automation and a conversion rate that moves, and who treats inbox placement as an ongoing discipline. There is real room to grow here. You will start with email and SMS, and as those programs mature you will have the opportunity to expand into additional lifecycle channels."
That's about the role.
Next "Who We Are": description of company mission etc. Could be placed under "About the role"? Might be better as separate section but not in allowed headings. Could incorporate into About the role? But we should not invent headings not listed. However we can still include a about company under About the role? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use those for section headings. Likely we should only use those headings. So we need to fit company description somewhere, maybe under About the role as a brief intro. Or we could omit it? But we must preserve ALL substantive information. So we need to include it somewhere. Could put it under About the role as a paragraph.
Next "Why You’ll Love Working Here": bullet points: Impact at scale, Autonomy + Accountability, Collaborative Culture, Modernization Mission. Those are benefits/culture. Could be part of Benefits? Or we could add a section "Benefits" includes both tangible benefits and culture. The posting already has "Benefits & Perks" list. So we can combine.
Next "Benefits & Perks": list items.
Next "Requirements": big list of duties (prospecting ecosystem, customer ecosystem, platform & automation, deliverability, SMS, testing, measurement & compliance, collaboration, accountabilities). Those are responsibilities.
Next "Minimum Education Requirements": Bachelor's degree etc.
Next "Minimum Experience Requirements": 5-8 years etc.
Next "Required Outside Training": ActiveCampaign certification preferred etc.
Next "Physical Requirements": prolonged sitting, lift 25 lbs, access departments, travel <10%.
We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We have no Pay or Schedule info, so omit those sections.
We need to decide what goes where.
Option:
- About the role: include the opening paragraph plus maybe "Who We Are" and "Why You’ll Love Working Here" as cultural description.
- Responsibilities: the big list under "Requirements" heading (prospecting ecosystem, etc.) plus maybe the accountability list? Actually the "Accountabilities" subheading under Requirements includes list of accountabilities. Could be part of responsibilities.
- Requirements: maybe education and experience.
- Qualifications: maybe required outside training and physical requirements.
- Skills: maybe specific skills like ActiveCampaign, Salesforce, copywriting, HTML/CSS, etc. But we could also put those under Qualifications.
But we need to avoid thin sections. Let's think: we could have:
About the role (description + company + why you'll love)
Responsibilities (the detailed duties list)
Qualifications (education, experience, training, physical)
Skills (maybe not needed if we put skills in Qualifications). But we could combine education/experience/training/physical into Qualifications and omit Skills.
But the instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid using other headings, but says use those for section headings. Likely they expect us to use those headings where applicable. So we should try to map content to those headings.
Thus:
- About the role: overview.
- Responsibilities: duties.
- Requirements: maybe minimum education and experience.
- Qualifications: maybe required outside training and physical requirements.
- Skills: maybe specific technical skills (ActiveCampaign, Salesforce, copywriting, HTML/CSS, etc.) but we could also put them under Qualifications.
- Benefits: list.
We need to avoid empty sections.
Let's extract specifics.
**About the role** paragraph: as above.
**Who We Are** paragraph: "Remember when every step of launching your dream felt like a mountain? Debt loomed, the tax code was a cryptic puzzle, and building a rock–solid foundation seemed impossible. PRIME Corporate Services was forged from that very struggle - by entrepreneurs who knew there had to be a better way. We are not just a faceless firm; we are a co-pilot for founders, operators, and business builders navigating the chaos of growth. We help cut through red tape, simplify complex systems, and help entrepreneurs structure their business for long-term financial freedom. From entity structuring to tax strategy to business credit and funding, we don’t just protect businesses - we help to scale them. Our team partners directly with high-growth entrepreneurs and affiliate partners to drive measurable outcomes; more leads, more revenue, and stronger businesses. We deliver expert guidance and exceptional service at every stage of the business journey. Our Mission: We aim to serve, advise, and support entrepreneurs every day."
**Why You’ll Love Working Here** bullet points (as prose): Impact at scale: Your work will shape the experience of thousands of entrepreneurs working with PRIME. Autonomy + Accountability: You’ll be trusted to lead, experiment, and deliver results — no micromanagement, just momentum. Collaborative Culture: You’ll work alongside creative thinkers, engineers, and business leaders who care deeply about customer success and innovation. Modernization Mission: You’ll play a key role in bringing advanced tech, analytics, and discipline to a growing organization — setting the foundation for the next generation of PRIME’s digital ecosystem.
**Benefits & Perks** list:
- Competitive Compensation + performance based bonuses
- Comprehensive Health Coverage - Medical, dental, and vision
- Paid Time Off - Generous PTO, sick days, and paid holidays
- 401k with Company match (we match up to 4%)
- Parental Leave - Paid leave for new parents
- Impact-Driven Culture - Small team, big mission
- Gym Pass - Company sponsored access to local gyms
- Free soda and snacks
- Discounts on Cellular/Wireless bills
- Robust Employee Resource Program with tele-health and more
**Requirements** (the big list) includes:
Prospecting Ecosystem:
- Own the full prospect-to-consultation email and SMS journey, from first touch through booked appointment
- Design and maintain lead nurture sequences segmented by source, service interest, engagement level, and stage
- Build and optimize campaigns that move cold and aging leads back into active conversation
- Partner with Sales leadership on handoff timing, lead routing triggers, and follow-up cadence so marketing and advisor outreach reinforce rather than collide
Customer Ecosystem:
- Own onboarding, activation, education, and retention journeys for existing customers
- Build cross-sell and expansion programs across PRIME's service portfolio, including entity structuring, tax strategy, business credit, and estate planning
- Design renewal, reactivation, and win-back programs, and identify churn signals early enough to act on them
- Own customer feedback and survey programs, including NPS, and route insight back to the business
Platform & Automation:
- Serve as the owner and deepest expert on ActiveCampaign, including automations, branching logic, tagging architecture, segmentation, dynamic content, frequency caps, and global suppression logic
- Maintain a clean, documented, and scalable account structure that does not degrade as programs multiply
- Partner with Engineering to maintain and improve the data flow between ActiveCampaign and Salesforce, defining requirements and validating that data moves correctly in both directions
- Audit and maintain data hygiene: duplicates, decay, tag sprawl, orphaned automations, and stale segments
Deliverability:
- Own inbox placement as a measured discipline, not an assumption
- Manage sending domain and subdomain strategy across transactional, marketing, and cold outbound
- Maintain SPF, DKIM, and DMARC configuration and monitor authentication health
- Monitor bounce rates, spam complaints, blocklist status, engagement decay, and reputation signals; act before problems compound
- Manage domain and IP warming for new sending infrastructure
- Own list hygiene and sunsetting policy for disengaged contacts
SMS:
- Build and own the SMS program end to end, including consent capture, cadence, message design, and opt-out handling
- Ensure every SMS program meets TCPA requirements, including express written consent for promotional
About the role
(maybe from description). Could also be "Responsibilities". The description includes responsibilities: own email and SMS ecosystems, architect automations, write copy, build segments, monitor deliverability, partner with design/engineering, etc. So we can put responsibilities underResponsibilities
. Also "Who We Are" could beAbout the company
but not in list; but we could use "About the role" for role description and maybe "About the company" not required. The instruction says use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should stick to those. We can map: - About the role: brief overview of role (the first paragraph maybe). - Responsibilities: detailed duties. - Requirements: includes education, experience, etc. Could split into Requirements and Qualifications? But we have both headings. Could put education/experience under Requirements, and maybe skills under Skills. However the posting includes "Requirements" section with sub-bullets: Prospecting Ecosystem, Customer Ecosystem, Platform & Automation, Deliverability, SMS, Testing, Measurement & Compliance, Collaboration, Accountabilities. Those are more responsibilities/duties. Actually those are detailed responsibilities. The "Minimum Education Requirements", "Minimum Experience Requirements", "Required Outside Training", "Physical Requirements" are qualifications. So we could treat: Responsibilities: the bullet list under "Requirements" heading in the posting (the big list). But that heading is called Requirements in posting, but we need to map to our headings. To avoid confusion, we can treat the posting's "Requirements" as Responsibilities (since they are duties). Then we create a separate "Qualifications" section for education, experience, training, physical requirements. And maybe "Skills" for specific skills like ActiveCampaign, Salesforce, copywriting, HTML/CSS, etc. But we can also put those under Qualifications. We need to avoid filler. Ensure we preserve all substantive information. Let's extract content. First, description paragraph: "PRIME Corporate Services is seeking a Senior Lifecycle Marketing Manager to own the email and SMS ecosystems that carry our prospects and customers through their entire journey with us. Reporting to the VP of Growth Marketing, this person owns two distinct engines: the prospecting ecosystem that converts leads into booked consultations, and the customer ecosystem that drives onboarding, retention, and expansion across our full service portfolio. Both need to be maintained, measured, and materially improved. This is a hands-on individual contributor role. You will architect the automations, write the copy, build the segments, monitor the deliverability, and read the results. You will partner with Design on creative and Engineering on data integrations, but you own the program end to end. The ideal candidate is equal parts systems thinker and marketer: someone who gets satisfaction from both a clean branching automation and a conversion rate that moves, and who treats inbox placement as an ongoing discipline. There is real room to grow here. You will start with email and SMS, and as those programs mature you will have the opportunity to expand into additional lifecycle channels." That's about the role. Next "Who We Are": description of company mission etc. Could be placed under "About the role"? Might be better as separate section but not in allowed headings. Could incorporate into About the role? But we should not invent headings not listed. However we can still include aabout company under About the role? The instruction: "Use