LKMail

Labels

CRM & Email Marketing Manager β€” CV

Inbox
LK
Laurence Kellett <hello@laurencekellett.co.uk> to me Β· Longridge, Preston Β· UK

Laurence Kellett

CRM & Email Marketing Manager

Longridge, Preston Β· UK hello@laurencekellett.co.uk 07700000909 linkedin.com/in/laurencekellett English Β· conversational Spanish

I have over a decade in B2B/B2C marketing, specialising in CRM, Lifecycle Strategy, and Multi-Channel Campaign Management β€” email, SMS, WhatsApp, webinars, and beyond β€” with a consistent focus on lead nurture, retention, engagement, revenue driving & re-engagement.

I untangle operational knots, build the systems & workflows that others rely on and still care about what lands in the inbox. I’ve consolidated complex systems down into manageable tools, delivered huge email suite overhauls a full quarter early, and built frameworks & ways-of-working using AI that have fundamentally changed the pace at which I, and my company, can work.

I pride myself on being highly organised, endlessly curious, having an eye for clean design, and being tuned into the logic-leap between good data and great decisions. A sentence on me: exercise mad, 20+ years in a brass band, a nearly 10-year Duolingo streak, a passion for craft ale, thousands of photos posted on my personal website, and a 2:57 Manchester Marathon.

Driven by brilliant customer experiences Data-informed, but never data-only AI-forward β€” building smarter workflows, not just faster ones

CRM & Email Marketing Manager

Higher Ed Partners

Oct 2023 – Present

Email engagement

+12ppOpen rate
+104%Click-through rate
+112%Click-to-open
βˆ’3.1ppBounce rate

Enrolment funnel

+7.5ppLead-to-contact
28%Faster lead-to-enrolled50 β†’ 36 days
+0.9ppApplications started
+1.8ppApplications submitted
  • Own CRM & lifecycle strategy for 12+ partners across multiple countries and languages β€” 400k+ prospects, 70+ concurrent programmes, and 1,400+ emails.
  • Led the Salesforce replatform for 12 partners (including multi-lingual), producing company-wide technical documentation used from call-centre to director level.
  • Consolidated 220+ engagement programmes to 20 β€” cutting complexity and cost without losing functionality, with documentation adopted across the business.
  • Built hyper-personalised journeys at scale β€” tailoring content, timing, and messaging by partner, programme, country, and lifecycle stage, which is what drove the engagement and funnel gains.
  • Unlocked WhatsApp as a CRM channel β€” taking ownership of template strategy, compliance, and comms framework from scratch, integrating it alongside email and SMS across full lifecycle programmes.
  • Overhauled 400+ emails and restyled 1,000+ templates across 12 partners β€” refreshing lead nurture, RFI programmes, and agent-facing layouts; lead nurture delivered a full quarter ahead of schedule.
  • Built and launched survey and testimonial programmes β€” 700+ student responses and 200+ consented testimonials, surfaced in a bespoke auto-updating analysis dashboard and used directly to shape product and marketing strategy.
  • Managed, trained, and developed a LATAM-based CRM Executive β€” setting clear KPIs and performance tracking that freed up strategic bandwidth and increased execution speed across CRM and campaigns.
  • Designed bespoke internal tools from scratch β€” a live CRM Stage Viewer and Survey Reporting Workbook, built using APIs, Claude Code, and automated pipelines; replacing manual processes and making real-time data accessible across the business.
  • Embedded AI into daily CRM practice β€” custom workflows, prompt frameworks, and functional tools that compress multi-day tasks into single sessions and moved Q4 deliverables into Q1.

Case studies β€” the problem, what I did, what happened, and what I learned

Lead Nurture 2.0 Rebuilding the emails that turn enquiries into students
The problem

About 100,000 people who had enquired were getting our follow-up emails. Over time the setup had been copied again and again, so every partner had its own copy of every list and every email flow. Deadline emails often pulled from fields that were empty, and nothing was joined up with our phone calls or texts. When we went through the journey as if we were a student, some partners sent nothing after the first ‘thanks for your enquiry’ email, and others called five times in two weeks.

What I did

I ran it from start to finish, in three stages.

  • New emails. Three general emails and two deadline emails for each stage: when we were still trying to reach someone, when they had not started an application, and when they had started but not finished. A deadline email always comes before a general one.
  • A map of every message a student gets, built from that walk-through, then a check of every adviser email template, partner by partner, for consistency, the rules and layout.
  • A simpler setup underneath. Three shared lists that pull from the most reliable data in the CRM, feeding three email flows that split by partner, instead of a separate flow for every partner.
  • A careful launch. One partner first, the others added once each was checked, and the old emails switched off in the same order.
What happened
Enquiry to enrolment: the four months before launch against the four months after, all partners
BeforeAfter
Enquiry to successful contact67.1%74.7% +7.5 pts
Enquiry to enrolled50 days36 days 28% faster
Applications started43.0%43.9% +0.9 pts
Applications submitted21.2%23.0% +1.8 pts
Email results: 199,168 emails compared, old against new
OldNew
Delivered94.9%98.8%
Hard bounces (address doesn’t work)4.30%0.57%
Opened48.7%56.5%
Clicked1.68%3.01%

The biggest gain came where we split one group of people into two, based on what they actually wanted. Clicks at that stage went from 1.21% to 3.85%, and bounces fell from 5.37% to 0.49%. Some old emails bounced for 15–24% of the people they went to. No new email goes above 5.5%, and nearly all are under 1%.

What I learned

These numbers compare the four months before with the four months after. It was not a controlled test, and other work was happening at the same time, so they show which way things moved, not proof that this alone caused it. Two results went the wrong way, and they taught me the most:

  • The first email in the journey gets opened six points less than the old one. Most likely because it now reaches people who have only just enquired, not people who had been on our lists for months. I have not proved that yet.
  • Emails written as ‘I’ instead of ‘we’ lost 11.3 points of opens in a test of 3,700 emails, with five of the eight clearly worse. I advised against using them, and redesigned the test to keep the subject line the same, so we can see the effect of the writing style on its own.
220 programmes down to 20 One setup for all twelve partners, changed in one place
The problem

The old setup treated every partner as if it were a separate company. Each email journey was built once for every partner, each with its own lists of who gets it, who is left out and who is checked. That came to about 220 email flows, and far more lists. Changing one line of text or a send time meant doing it up to twelve times, with no easy way to check every copy had been done. The deadline emails also relied on data that was often missing, so the most important emails could fail without anyone noticing.

What I did

Three things.

  • Rebuilt the lists so they pull from the data the CRM actually keeps up to date, based on where each student is in their course. One list now works for every partner.
  • One email flow per journey, which splits by partner. The rules, the timing and who is left out are set once; only the partner’s own wording sits on each branch.
  • A careful switchover. One partner first, the old flows switched off in stages, and a label on everything new, so old and new can be told apart with a filter instead of by hand.
What happened
What changed
BeforeAfter
Email flowsabout 220, one per partner per journeyabout 20, one per journey
Payment-deadline journey45 parts across nine partners3 parts
Main follow-up flowsone per partner per stage3
Deadline remindersone per partner per type of deadline5
Reporting on one journey92 items sorted by handone filter
Delivered94.9%98.8%
Hard bounces4.30%0.57%
Deadline emailssometimes failed without anyone knowingsent reliably, before the deadline
What I learned

To be fair about it: the better delivery and bounce numbers come as much from rebuilding the lists on up-to-date data as from cutting the number of flows, and the time saved is written down rather than measured. The real win is the habit. Change the wording once and all twelve partners get it, and adding a new partner means adding a branch, not building everything again.

Making WhatsApp work at scale From 200-message batches to all twelve partners
The problem

We had WhatsApp, but could not use it properly. We could only send about 200 messages at a time. Message templates were tied to each partner’s own phone number, so every change had to be made twelve times. Once WhatsApp approves a template you cannot edit it: you have to delete it, build it again, and wait 30 days to reuse the name. We had ended up with 36 live templates, none for the deadline messages students needed, no access to the messaging platform for the marketing team, and no figures to measure anything against.

What I did
  • Removed the 200-message limit. I led the marketing side of a project to send in bulk from Salesforce, including testing it and checking it worked once live, and set up campaigns for each of the twelve partners with four deadline campaigns each, so sends across partners are planned, not made up on the day.
  • Cut the planned 35 templates down to 30, combined the deadline messages we needed, and made the tone and sign-off the same throughout.
  • Built 360 templates by hand: 30 for each of the twelve partner accounts. I wrote a small browser tool that fills in each partner’s name and number in the order the WhatsApp form asks for them.
  • Agreed a process with IT. No quick one-off edits: changes are requested, reviewed and signed off by marketing. Plus a repeatable way to measure results using WhatsApp’s own stats.
What happened

WhatsApp can now reach all twelve partners at scale, with a message ready for every step from enquiry to enrolment.

  • The 200-message limit is gone. Bulk sends run through Salesforce, with campaigns set up for each partner, so sending to several partners is planned instead of squeezed into batches of 200.
  • Every step has a template. The deadline messages did not exist before. They do now, on all twelve numbers, alongside the enquiry and on-course messages.
  • 30 templates live, built 360 times by hand with a tool written for the job.
  • A clear way to add new messages. Because the process with IT is agreed, a new message is a simple request, not a rebuild.
What I learned

Measuring WhatsApp properly for the first time showed three things worth acting on:

  • Low clicks were mostly a measuring problem. Every message asked people to type a reply, and WhatsApp does not count a typed reply as a click. So we did not really know how many people responded, and adding tap-to-reply buttons became the most useful next change.
  • Messages that did not arrive were down to old phone numbers in the CRM, mostly at three partners. A data problem, not a WhatsApp problem.
  • The same five templates did badly at partners with nothing in common, which means the problem was the wording, not the audience. That is what the rewrite went after.

Each of these gives a clear next step with a reason behind it, not a guess. That is the other benefit of running the channel properly.

Student Voice From no student feedback to live data
The problem

We had no proper way of hearing from the students we recruited. Nothing told us, across partners, whether a module met expectations or how happy students were when they finished. Testimonials came in at five to eight a quarter, from wherever we could find them. Talks with partners about quality relied on stories, there was no early warning that students might drop out, and reports, when there were any, were slides built by hand from small spreadsheets and already out of date.

What I did

Four surveys at different points in a student’s course, and the reporting to make them useful.

  • Mid-module survey: sent when students are most likely to drop out, asking if the module met their expectations and what would help.
  • End-of-course survey: how happy students are when they finish.
  • Testimonial request: sent automatically, asking for permission to publish and a score out of 10, so a quote can be used without going back to ask.
  • Non-starter survey: the newest, sent to people who enquired or applied but did not enrol, asking why and what would have changed their mind.
  • The reporting: a live workbook anyone can open, which always shows the latest data; a tool that reads the survey exports, groups comments by topic and matches each course to its subject area; and an automatic update so nobody has to do it by hand. We also agreed some ground rules, such as quoting students instead of averaging small numbers.
What happened
The programme
BeforeLatest
Mid-module responsesnone524, across all twelve partners
End-of-course responsesnone288
Testimonialsa few, 5–8 a quarter186: 160 with permission, 103 scored 8–10
Reportingthe odd hand-made slide decklive workbook, updates itself
How the survey emails did
OpenedReplies per 100 sent
Mid-module74%6.3
End of course79%12.4
Testimonial64%2.4

Overall, 76% of students rate their module well, and 82% rate their whole course well.

What I learned

None of this was known before:

  • Module two is where it dips: 3.74, against 4.20 and 4.26 for the modules either side. That tells us exactly when students need more support.
  • Two subject areas score well below the rest. That is a conversation about the courses, not the marketing.
  • Almost every testimonial comes from one email: 72 of 74 last year. Over a hundred students who gave five stars at the end were never asked for one.

That bank of testimonials, with permission to use them, is also what made subject-specific testimonials in Lead Nurture 2.0 possible.

Senior Marketing Executive

Parkingeye

Jul 2020 – Oct 2023 Β· 3y 4m
0β†’500kDatabase builtBrand launched from zero
5Brands managed
4CountriesUK, DE, AT, DK
YoYConsistent growthEvery year of tenure
  • Owned and continuously improved the CRM, CMS, email marketing & customer journey strategy across the UK and sister brands in Germany, Austria & Denmark.
  • Launched a competitor charging brand from zero β€” handling CRM installation, website, marketing, branding, and global stakeholder liaison, scaling the database from 0 to 500k.
  • Drove improvements & efficiencies across 5 brands in 4 countries, delivering consistent YoY growth throughout.

Earlier experience

Email Marketing Executive  Β· INPD
Aug 2019 – Jul 2020 Β· 12m
Senior Marketing Executive  Β· Direct365
May 2013 – Aug 2019 Β· 6y 4m
SEO Outreach Specialist  Β· Custard Media Solutions
Jul 2012 – Apr 2013 Β· 10m

I believe the things you do outside of work say just as much as your CV does. Outside of it, you'll likely find me with my wife, my dog, or deep into one of the hobbies below β€” they reflect the same discipline, curiosity, and focus I bring to work every day.

Most of what I build can’t be linked to: the work tools sit behind company sign-in on live data, and the emails went to real students. These are rebuilds with the names and numbers replaced, and they work. Open one and use it.

At work β€” the internal tools, a test readout and three email builds

CRM Stage Viewer The internal tool, rebuilt as a working mockup

Every engagement series for every partner on one screen: the comms plan and its suppressions, the branching flow, the whole student journey as a swimlane timeline, every send in one filterable table, the term dates the deadline sends read from, and a searchable glossary. I built it because nobody could see the estate at once.

Interface mockup with placeholder partner codes and content Β· the real one is behind company SSO Β· the tabs, timeline filters, glossary search and dark mode all work.
Survey Reporting Workbook CSV in, live dashboard out

Survey exports used to become a week of pivot tables. Now an editor takes the exports, cleans them, detects the themes and maps each programme to its vertical, and publishes a workbook anyone in the business can open: a summary across all the surveys with a partner scorecard and send-to-completion funnel, then each survey in depth, with the questions asked, the score distribution, partners ranked against a concern threshold, the free text grouped by what it is about, and actions split between what we own and what goes to a partner. 700+ responses and 200+ consented testimonials so far.

Interface mockup of the workbook as it stands, with invented partner codes, comments and figures Β· the real one runs on live responses behind SSO Β· try each survey tab, the chart toggles, the funnel picker, the sortable tables and the response search.
Task manager The 1,800+ records the CRM roadmap runs on

No off-the-shelf board coped with twelve partners, so I built my own, on top of Notion. It has grown into where the working day is run from: a Today view that plans the day around the meetings in it, tasks as a list, board or calendar, meetings with their notes filed, projects that flag when their status has drifted, a ledger of A/B tests with their read-outs booked, and the weekly log. Jira work comes in as tasks and personal reminders sync from my phone.

Interface mockup of the app as it stands, with invented partner codes, projects, tasks and test figures Β· try Today, the list, board and calendar, tick a task off, and file the week.
A/B test: stylised vs. plaintext Same audience, same subject line, built two ways

A test I run every intake. The full branded build against the same content typed out as if an adviser had written it. Plaintext won on replies, which is the number that mattered; the rule it produced is about which stage of the journey gets which.

Both variants as they were built, side by side Β· switch between them at the top Β· partner name, links and adviser details removed, and the figures are illustrative.
Post-event nurture email Enquiry to application, in five steps

Sent after an exhibition to people who had given their details in person and nothing else. It answers what happens next? before they have to ask: a five-step ladder with the first step ticked, and the two dates that decide whether they act this month or next.

Built in Marketing Cloud Account Engagement Β· partner name, links, adviser name and ranking citations removed Β· the header resolves per partner at send time.
Support hours email Reply, call or WhatsApp

Part of opening WhatsApp as a CRM channel: the send that tells an enquirer the channel exists and shows what tapping it does. The WhatsApp panel is drawn in HTML rather than an image, so it survives image blocking.

Built in Marketing Cloud Account Engagement Β· partner name, phone number and links replaced with placeholders.
Mid-module survey email One tap to answer

Timed to land where drop-off risk is highest. The five buttons are five links, with the score carried in the query string, so answering costs one tap and the form opens already knowing the answer.

Built in Marketing Cloud Account Engagement Β· partner name, form URL and merge fields removed.

Outside work β€” built for my own use

IPA Okay dashboard A dashboard for my beer blog

Every beer I have reviewed on IPA Okay, with styles, breweries, ratings out of 100 and filters. No client and no deadline.

Interface mockup with placeholder data Β· the filters work.
Open the real dashboard →
The Abstract Diary Every day as one generated picture

Part of the tools app I built for myself, which also runs my diary, finances and the beer blog’s publishing. Each day of the diary becomes a square picture, drawn from what the day recorded. The temperature sets the circle, the words written fill the ink dashes, runs and rides become threads, spending becomes green squares, and people, weather and the date each have their own mark. The same day always draws the same picture, and one goes out to Instagram each day.

The real painter from the app, given invented days Β· placeholder people, made-up weather and spending, stand-in routes Β· try Make up a day, the seven-day strip and Months.
See every day on my website →
Laurence-Kellett-CV.pdfGenerated from this page, so it is never out of date Laurence-Kellett-Cover-Letter.pdfOne page, if you want the why as well as the what
Reply Forward