# Customer marketing sprint > A three lesson sprint that takes you from a post sale journey map to a live adoption campaign and a working advocacy flywheel, with templates at each step. Source: https://saas-marketing.net/courses/saas-customer-marketing-sprint/ Topic: SaaS Customer Marketing Type: course-index Published: 2026-09-11 Last updated: 2026-09-11 Publisher: SaaS Marketing (saas-marketing.net) License: CC BY 4.0. Quote or republish with attribution and a link to https://saas-marketing.net/courses/saas-customer-marketing-sprint/ ## Short answer This customer marketing course is a three week sprint with three lessons and three finished deliverables: a post sale journey map with a trigger table, one live adoption campaign running against a holdout group, and an advocate list synced to your CRM with consent captured. Each lesson takes three to five hours. It assumes you have product event data, email sending rights, and read access to the CRM. ## Key takeaways - The sprint produces three artefacts in three weeks, not a certificate, because unshipped customer marketing plans decay in about a quarter. - Lesson one ends with a trigger table mapping product events to owners, channels and timing, which becomes the campaign backlog. - Every adoption campaign here runs against a holdout so you can report incremental adoption rather than attributed clicks. - Prerequisites are access, not seniority: product events, a sending tool, CRM read rights and one friendly customer success manager. - Customer marketing programs usually die from scope, not ambition, so the sprint caps you at one campaign and one segment. --- Three weeks. Three lessons. Three things that exist afterwards and keep running without you babysitting them. That is the whole promise, and the scope is tight on purpose. Most customer marketing programs do not fail because the person running them lacked ideas. They fail because month one produced a forty slide journey map, month two produced a campaign nobody measured, and month four produced a reorg. This sprint is built the other way around: each lesson ends with something shipped, and nothing carries over. ## Who this sprint is for It is aimed at two people. The first is the company's first customer marketing hire, six weeks in, staring at a Confluence page titled "retention ideas" that three people have added to and nobody owns. The second is a generalist demand or content marketer whose VP just handed them post sale because the board asked about net revenue retention. If you already have a reference desk, a customer advisory board and a person whose job title contains the word advocacy, skip this and read [building a customer advocacy program](/playbooks/customer-advocacy-program/) instead. You are past the starting problem. The sprint also suits customer success managers who keep getting asked to write emails. You will finish knowing which moments deserve a campaign and which deserve a human, which is the split most CS teams get wrong in both directions. New customer marketers usually begin by auditing every existing email. Do not. Half of those emails were built for a product that has since changed, and auditing them puts you in a queue behind engineering. Start from the journey and the triggers, then decide what already exists that maps to one. ## What you build in each lesson Each lesson produces one artefact you can show someone. Not notes. Not a framework. A thing. [Lesson 1: map the post sale journey](/courses/saas-customer-marketing-sprint/01-map-the-post-sale-journey/) is the foundation. You interview four customers, pull the event data, and build the trigger table that becomes your campaign backlog for the next year. Most people find two or three moments they had never noticed, usually around the second admin invite or the first API key. - Lesson two takes one row from that table and ships it. One feature, one segment, one holdout. You will want to do more. Don't. Lesson three converts the customers who responded well in lesson two into a structured advocate list. Consent captured properly, ask types tagged, cooldown periods set so the same six logos do not get asked for a case study, a G2 review and a webinar in the same month. ## What you need before you start Access, mostly. Seniority does not matter here, and neither does budget. **Prerequisites** That last one is the sneaky blocker. Holding back twenty percent of accounts from a campaign feels, to some VPs, like deliberately withholding value. Have the conversation in week one, not the morning you launch. The argument that works: without a holdout you cannot tell the CFO whether the program did anything, and next year's headcount request depends on that answer. [Measuring customer marketing](/guides/customer-marketing-measurement/) covers the reporting framing in more detail. If you are missing product events entirely, do lesson one anyway using support tickets and CS notes as a proxy. It is worse data. It is not useless data. ## Why three weeks and only three deliverables Because scope is what kills these programs, not ambition. I have watched four first customer marketing hires in a row build beautiful twelve stage lifecycle maps and ship nothing in their first quarter, then get folded back into demand gen in their third. The pattern is documented in [why customer marketing programs fail](/guides/why-customer-marketing-fails/), and the root cause is almost always the same: the function tried to earn credibility through planning instead of through one measured result. Three weeks is also roughly the attention window you get from a new manager before they start asking what you have been doing. Arriving at that meeting with a running campaign and a measured lift changes the conversation from "what is customer marketing" to "what should we point it at next". The tradeoff is real. A three week sprint will not give you a defensible segmentation model, a full content audit, or a health score. You will build those later, and they will be better because the trigger table already told you which moments matter. **1 campaign** The maximum number of campaigns you launch during the sprint, regardless of how many the trigger table produces ## The templates included Five files, all editable, all deliberately plain. The trigger table template is a spreadsheet with columns for event name, segment, owner, channel, timing, suppression rule and success signal. The campaign brief is a single page: hypothesis, segment definition, holdout percentage, touch sequence, and the one metric that decides whether it worked. The holdout calculator takes your segment size and baseline adoption rate and tells you the minimum detectable lift, which usually delivers a useful shock. There is also an advocate record schema for Salesforce or HubSpot, and a four question customer interview guide that gets useful answers in twenty minutes. If you want to sanity check the business case before you start, the [customer marketing ROI calculator](/calculators/customer-marketing-roi/) will model expansion and retention impact against your own ACV. ## What the sprint deliberately leaves out Customer education. Community. In app messaging design. NPS program mechanics. Renewal playbooks. All of those matter, and several of them will end up in your remit. They are excluded because each one is a quarter of work on its own, and mixing them into a three week sprint is exactly how the scope problem starts. When you are ready, [customer education programs for SaaS](/guides/saas-customer-education-program/) covers the largest of them, and [customer marketing campaign ideas](/guides/customer-marketing-campaign-ideas/) gives you the backlog to fill weeks four through twenty. There is one more honest limit. This sprint assumes a self serve or hybrid product with observable usage. If you sell six figure enterprise deals with quarterly business reviews and no product telemetry, the trigger table in lesson one will be thin and you will lean harder on CS interviews. It still works. It works less well. ## Start here Read the [customer marketing overview](/saas-customer-marketing/) if the function is new to you, then look at [SaaS customer marketing examples](/examples/saas-customer-marketing-examples/) to see what finished work looks like. After that, block three hours and open lesson one. Do not read all three lessons first. Ship lesson one's trigger table before you read lesson two, because the campaign you choose in week two should come out of the data you gather in week one, not out of a plan you made before you looked. ## Frequently asked questions ### Who is this customer marketing course for? It is built for a first customer marketing hire at a company between two and fifty million in ARR, and for generalist marketers who have just been handed retention. If you already run a mature advocacy program with a dedicated reference desk, the sprint will feel basic. If you own onboarding emails and nobody can tell you if they work, it fits. ### How long does each lesson take? Plan three to five hours per lesson plus waiting time. Lesson one is mostly interviews and data pulls, so it spreads across a week. Lesson two involves building and launching, which takes a working day if your email tool is already wired. Lesson three is CRM configuration and outreach, usually three hours plus replies trickling in over the following fortnight. ### Do I need engineering help to finish the sprint? Only if your product events are not already flowing into a tool you can query. If Amplitude, Mixpanel, PostHog or Segment is live and you have read access, you can finish without filing a ticket. If events exist only in the application database, budget one short engineering conversation to get signup, activation, invite and upgrade exposed. ### Is there a customer marketing certification at the end? No. There is no exam and no badge. What you leave with is a trigger table, a running campaign with a measured holdout, and an advocate list in the CRM, which is what a hiring manager or a CFO will actually ask to see. Certificates are easy to collect and hard to defend in a quarterly review. ### What if I do not have a holdout big enough to measure? Below roughly 300 accounts per segment, a holdout will not clear statistical noise in a month. Run the holdout anyway and report it as directional, or hold out a whole segment for a quarter instead of a slice of one. Say out loud that the read is weak. That is far better than reporting attributed opens as proof. ### How is customer marketing different from lifecycle email? Lifecycle email is a channel. Customer marketing is a function that owns adoption, expansion support, references and advocacy, and email is one of its outputs. A lifecycle marketer optimises a welcome sequence. A customer marketer decides whether the welcome sequence should exist, who owns the moment it targets, and what the company does when it fails.