Day in the Life of a Marketing Manager: Three Real Days

Alarm goes off. I lie in bed for exactly eight minutes because I know today is going to be long. Tomorrow I'm presenting a competitive battle card to 22 sales reps at our quarterly enablement session, and the battle card isn't done. I roll over and check Slack on my phone. There's a message from our product manager Tomoko, sent at 11:47 PM, with a link to a competitor's blog post announcing a new feature that directly overlaps with our Q2 roadmap item. Tomoko added three fire emojis. This is her way of saying "this changes things." I screenshot it and start thinking while I brush my teeth.

Coffee. I make a pour-over, which takes four minutes, and I use those four minutes to read the competitor's blog post properly. It's a feature called "unified threat dashboard." We're building something similar but calling it "consolidated risk view." Their version launches next month. Ours launches in Q3. This means the battle card needs a section I haven't written yet: how to handle the objection "but they already have this and you don't." I open the Google Doc and start a new section at the bottom.

At my desk. Open office, second floor, about 60 people on this floor. The marketing team sits near the windows, which sounds nice but means sun glare on my monitor from 2 to 4 PM every day. I put the battle card on my second monitor and start building the new section. The core argument is: their dashboard aggregates data from their own tools only, ours integrates with 14 third-party security tools. That's the differentiation. But I need to verify the number 14 because last time I checked it was 12, and engineering may have added integrations without telling marketing. This happens constantly.

Slacked Nathan on the integrations team. "How many third-party integrations does the platform support as of today?" He responds in 3 minutes: "16 in prod, 2 in beta." So it's actually 16, not 14, not 12. I update the battle card and make a mental note to set up a recurring sync with the integrations team so I'm not guessing on my own product's capabilities. This is, genuinely, one of the hardest parts of product marketing: knowing your own product. It changes faster than the documents.

Stand-up with the marketing team. Seven people on Zoom. My manager Kit runs it. He asks for updates. I mention the competitor launch and the battle card. He asks if the messaging needs to change for the Q2 campaign. I say no, the positioning is still valid, but the urgency narrative shifts. We were going to sell "consolidated risk view" as an innovation. Now it's a parity feature with differentiation on integrations. Kit nods. He trusts me to handle it but I can tell he's mentally flagging it for the CMO update on Friday.

Deep work on the battle card. This is the best stretch of my day. I have my headphones on, Spotify playing lo-fi beats, and I'm writing. The battle card is an 8-page document that our sales team uses when they're up against this competitor in a deal. It covers positioning, feature comparison, pricing comparison (what we know of their pricing, which is not public so I'm working from intelligence gathered by our reps), objection handling, and win stories. I add the "they have it first" objection section. The answer is nuanced: yes, they ship first, but their integration count is lower, their pricing is per-seat which penalizes larger teams, and three of our enterprise customers specifically chose us because of the third-party integration depth. I pull quotes from win/loss interviews I did last quarter. One quote from a CISO at a financial services company: "We looked at [competitor] but they only talked to their own data. We have CrowdStrike, Splunk, and Palo Alto. We needed everything in one view." That quote is gold. I put it in bold.

Lunch at my desk. Leftover Thai basil chicken from last night. I eat while reading the competitor's G2 reviews to see if customers are mentioning the new feature yet. They're not. It hasn't launched. But I find a 2-star review from January that says "setup took 3 weeks and we still don't have all our data sources connected." I screenshot it for the battle card. Competitive intelligence is 40% structured research and 60% reading review sites while eating lunch.

Meeting with Tomoko and our VP of Engineering, Rashid, about the Q2 launch timeline. I need to know if "consolidated risk view" is still on track for July because if it slips to August, the competitive narrative changes again. Rashid says July is "tight but doable." I've been in product marketing long enough to know that "tight but doable" means August. I plan accordingly.

Sun glare hits my monitor. I move to a conference room. Spend an hour building the slides for tomorrow's enablement session. Six slides: competitive landscape, key differentiators, objection handling, pricing comparison, win stories, and a cheat sheet they can keep at their desk. The cheat sheet is the only thing most of them will actually use. I know this. I make the cheat sheet first.

Practice run-through of the presentation. I present to my laptop in an empty conference room. It takes 18 minutes. I need it to be 25 because I want time for questions, but 18 minutes of content for a 45-minute slot is about right. Reps ask a lot of questions. Last time, one rep asked me to role-play a competitive objection live, and that turned into a 12-minute tangent that was actually the most useful part of the session.

Back at my desk. Slack has 23 unread messages. Most are not for me. Three are. One from a rep named Sheila asking if we have updated pricing for a deal she's working. I don't have it, but I know who does, so I loop in our pricing analyst. One from Kit asking me to review a blog draft by Thursday. One from Tomoko with another competitor link, this time a case study. I bookmark it for the battle card appendix.

Finish the battle card. Export to PDF. Upload to our sales enablement platform, Highspot. Send a Slack message to the sales channel: "Updated [Competitor] battle card is live in Highspot. Covers the new feature announcement. See you at enablement tomorrow." Three reps respond with thumbs up. Sheila responds with "finally." I choose not to take that personally.

Driving home. My boyfriend Nico calls and asks how my day was. I say, "I spent eight hours writing a document about why our product is better than another product." He says, "Is it?" I say, "At some things." He says, "That's the most honest marketing I've ever heard." I think about that for the rest of the drive.

Phone buzzes before my alarm. It's a Slack notification from our customer service manager, Yolanda, timestamped 6:48 AM: "We're getting calls about a promo code that doesn't work. SPRING25. Is this yours?" I sit up. SPRING25 went out in last night's email to our loyalty segment, which is about 340,000 subscribers. I open my laptop on the kitchen counter while my daughter Zoe eats Cheerios and asks me why I look worried. I tell her I'm not worried, I'm thinking. She says, "You make that face when you're worried."

Found the problem. The promo code SPRING25 is set to activate at 12:00 AM Eastern today, Thursday. But the email went out last night at 8 PM to the loyalty segment because I scheduled it for Wednesday evening, which is our highest-open-rate window for that segment. The code wasn't active yet when people opened the email. The first customers who tried to use it, probably around 8:15 PM last night, got an "invalid code" error. The code works now. But the damage is done for anyone who tried it last night, gave up, and won't try again. I check the numbers: 42,000 opens, 6,800 clicks, 890 attempted redemptions between 8 PM and midnight. Of those 890, zero converted because the code didn't work. That's 890 people who wanted to buy something and we stopped them.

I message Yolanda back with the explanation and ask her team to honor SPRING25 for anyone who calls in saying it didn't work. She agrees. Then I message my boss, Rick, our Director of Digital Marketing, with a summary: "Scheduling error on my end. Code activation time didn't align with email send time. ~890 failed redemptions. Code is working now. CS is handling call-ins. I'll send a follow-up email to the affected segment this afternoon." Rick responds: "Thanks for the quick catch. Let's talk about QA process for code timing." That's manager-speak for "we need a system so this doesn't happen again," which is fair.

At the office. Open floor plan, fluorescent lights that make everyone look slightly tired. Our marketing department is 18 people. I'm the only one who exclusively does email. I sit between Janelle, who does paid social, and an empty desk that used to belong to our SEO specialist before she left in January and hasn't been replaced. I open Salesforce Marketing Cloud, which is our ESP, and start building the follow-up email. Subject line: "Let's try that again, SPRING25 is live." I draft three versions and A/B test the first two. One says "Sorry about last night" and one says "Your 25% off is ready." I'll test on 10% of the segment and send the winner to the rest.

Weekly email performance review with Rick and Janelle. I pull up the dashboard. Week over week: open rate is 24.3% (down from 25.1%), click rate is 3.8% (up from 3.4%), revenue per email is $0.042 (up from $0.038). Rick focuses on the open rate decline. I explain that Apple's Mail Privacy Protection continues to inflate our open rate baseline, and the "decline" is actually our numbers becoming more accurate as we shift to click-based metrics. I've explained this four times. Rick nods each time like it's new information. Janelle gives me a look. She's heard this speech too.

Back to campaign building. I have three emails to build today for next week's sends: a new arrivals email for the general list, a re-engagement email for subscribers who haven't opened in 90 days, and a birthday email for the March cohort. The birthday email is my favorite because it's personal and the conversion rate is 8.2%, which is more than double our average. The copy is simple: "Happy birthday, [first name]. Here's 15% off something your pet will love." People buy things when they feel seen. That's the whole job, honestly. Making 1.2 million people feel like you're talking to them specifically.

A merchandising manager named Doug comes by my desk and asks if I can "add a quick banner" to Friday's email promoting a surplus of dog crates that aren't selling in stores. I ask how quick he needs it. He says "today if possible." I tell him the Friday email is already built, tested, and scheduled, and that adding a banner means redesigning the email template, re-testing across 8 email clients (Outlook, Gmail, Apple Mail, Yahoo, etc.), and re-scheduling. That's about 2 hours of work for a "quick banner." Doug says, "Oh, I thought you just drag and drop things." I explain that I do drag and drop things, in a tool that requires those things to be tested in 8 different rendering environments because Outlook 2019 interprets HTML like it's 2004. Doug leaves looking confused. I feel bad. But not bad enough to add the banner without testing.

Lunch in the break room. Leftover pasta. I eat while scrolling Really Good Emails, which is a site that archives well-designed email campaigns. I screenshot three that have interesting header treatments. This is professional development that looks like procrastination. I've stopped trying to explain the difference.

Build the three emails for next week. This is the craft part of the job. Choosing images, writing subject lines, setting up the dynamic content blocks so the dog owners see dog products and the cat owners see cat products. Our segmentation engine in SFMC has 14 segments based on pet type, purchase history, geography, and engagement level. Getting the right content to the right segment is the difference between $0.03 and $0.05 revenue per email, which sounds trivial until you multiply it by 1.2 million subscribers and 14 sends per week. That $0.02 difference is about $33,600 per month in incremental revenue. I know this number because Rick asked me to calculate it for a budget meeting, and now I think about it every time I build a segment.

The follow-up SPRING25 email is ready. A/B test is running on the 10% sample. "Your 25% off is ready" is winning with a 28.1% open rate versus 22.4% for "Sorry about last night." I'm not surprised. Apology subject lines perform poorly because people don't open emails to accept apologies from brands. They open emails to get deals. I schedule the winner to send at 5 PM.

Quick sync with Rick about the QA process. We agree on a new rule: all emails with promo codes must be tested with a live code redemption before scheduling. Obvious in hindsight. The best processes are.

Driving home. My wife Tamika calls from the grocery store and asks what Zoe wants for dinner. I hear Zoe in the background yelling "tacos." Tamika asks how my day was. I say, "I accidentally sent a coupon that didn't work to 340,000 people, spent the morning fixing it, then built three emails and explained to a man named Doug why email isn't drag-and-drop." She says, "Is the coupon working now?" I say yes. She says, "Then it's fine." She's right. It is fine. The 890 people who tried to use a broken code at 8 PM will never know I laid awake last night wondering if I should have double-checked. But I know.

On the T, Red Line, standing because it's Monday and everyone decided to come to the office today. I'm scrolling through our social accounts on my phone. LinkedIn: a post I put up Friday about a customer case study got 847 impressions and 12 likes. For B2B LinkedIn, that's fine. Not great. Twitter: 4 new followers, all bots or competitors. Instagram: we don't have one because construction project management software is not visual and every time I suggest starting one, my boss Terrence says, "What would we post? Photos of Gantt charts?" He's not wrong.

At the office. We're in a WeWork in the Financial District. I like it because the coffee is free and decent. I don't like it because the desk situation changes every week depending on who's in the office, and today someone is sitting at my usual spot so I'm at a desk facing a wall. I open Sprout Social, which is our social media management tool, and check the content calendar. I have 8 posts scheduled for this week across LinkedIn and Twitter. Monday and Wednesday are customer stories. Tuesday is a product tip. Thursday is an industry stat. Friday is something lighter, which for us means a construction joke or a meme about project delays. Last Friday's meme about scope creep got 2,400 impressions. That's our best-performing post in three months. It was a construction photo of a shed that someone had renovated into a multi-story building with the caption "When the client says 'just one more small change.'" I found the photo on Reddit and spent 20 minutes making sure it wasn't copyrighted.

Marketing team standup. Five of us in a huddle room. Terrence, me, our content writer Paige, our demand gen person Max, and our marketing ops analyst Keiko. Terrence asks me for social metrics from last week. I give him the numbers: 6,200 total impressions, 89 engagements, 14 link clicks. He asks if that's good. I say, "For B2B SaaS with a 4,200-person LinkedIn following and zero ad spend behind organic, yes, it's good." He says, "Can we get it higher?" I say, "With budget, yes. Without budget, marginally." This is a conversation we have every two weeks. I call it the "can you do more with nothing" meeting in my head. Paige catches my eye. She has the same meeting about blog traffic.

Today's task: turn a customer case study into social content. The case study is about a general contractor in Phoenix who used our software to reduce project delays by 23%. The case study itself is 1,800 words. I need to turn it into a LinkedIn post that's 150 to 200 words, a Twitter thread of 4 tweets, and a quote graphic for LinkedIn. The case study was written by Paige and it's good, but it's written for a landing page, not for social. Social needs a hook in the first line. Landing pages need context. Different muscles.

Writing the LinkedIn post. First line options: "A general contractor in Phoenix cut project delays by 23%." Boring. "What does 23% fewer delays look like on a $4.2M commercial build?" Better. "The foreman called it 'the first project that finished on time in three years.'" Best. I use the third one. The rest of the post summarizes the story in 180 words and ends with a link to the full case study. I spend 35 minutes on 180 words. My college roommate Angelica writes for a news outlet and produces 3,000 words a day. She thinks social media writing is easy because it's short. It's short because every word has to earn its place.

Creating the quote graphic in Canva. Our brand colors are navy and orange. I pull the foreman quote, set it in our brand font (Inter), add a subtle construction-site background image, and export it as a 1200x1200 PNG for LinkedIn. Then I resize it for Twitter. Then I realize the text is too small on mobile so I go back and increase the font size and cut three words from the quote to make it fit. This loop takes 40 minutes. Terrence once asked me why a graphic takes longer than 10 minutes. I showed him the mobile preview at the original font size. He squinted. He stopped asking.

Lunch at the WeWork kitchen. I eat a salad I brought from home and scroll through the LinkedIn feeds of our three main competitors. One of them just posted a video testimonial that has 3,800 views. I feel a small, specific envy that I think only social media managers experience: the envy of engagement metrics. I know their video probably cost $5,000 to produce and I have a $0 video budget, but the number still stings.

Product marketing sent me a screenshot of a new feature and asked me to "post about it." The screenshot shows a Gantt chart with a new color-coding system for task dependencies. I stare at it for two minutes trying to figure out how to make this interesting to humans. Task dependency color-coding is important to our customers, but it is not, by any stretch, engaging content for a social media feed where I'm competing with puppy videos and hot takes about remote work. I draft three different angles. The one I like best: "You've been squinting at your Gantt chart. We fixed that." Attached: the screenshot with a before/after comparison I'll have to make myself because product just sent one image.

Spent an hour building the before/after graphic. Took a screenshot of the old UI from our staging environment (Keiko helped me get access), placed it next to the new screenshot, added arrows and labels. It's not beautiful, but it's clear. I schedule it for Wednesday.

Community management. I reply to 4 LinkedIn comments on last week's posts. Three are genuine engagement, one is a sales pitch from someone who "noticed we're growing" and wants to sell us intent data. I hide that one. Then I spend 30 minutes engaging with our customers' posts, liking and commenting on their content. This feels small but it's how you build a community when you have no budget. Our customer Hank, the contractor from the case study, posted a photo of a project completion and I commented "Looks like it finished on time." He replied with a laughing emoji. That interaction probably generated more goodwill than any ad I could have run.

End-of-day metrics check. Today's posts are performing normally. LinkedIn post from this morning: 312 impressions, 8 likes, 2 comments, 1 share. I add it to my tracking spreadsheet. I track every post in a Google Sheet with 14 columns: date, platform, content type, topic, copy length, media type, impressions, likes, comments, shares, link clicks, engagement rate, time of post, and notes. I've been doing this for 18 months. I have 847 rows. Sometimes I look at the data and find patterns. Sometimes the data tells me nothing. This week the data says that construction memes outperform product content by 4x on engagement. I could tell Terrence this, but he'd say, "We're not a meme account." And he'd be right. But the algorithm doesn't care about brand strategy.

On the T home. My roommate Priscilla texts asking if I want Thai for dinner. I say yes. She asks about my day. I type: "I spent 8 hours trying to make a Gantt chart screenshot interesting." She sends back a crying-laughing emoji. I look out the window. Somewhere in Phoenix, a foreman finished a project on time and I turned that into 180 words and a square graphic. That's the job. Making someone else's accomplishment fit inside a blue rectangle on a screen that someone will scroll past in 1.3 seconds. If they stop, I've done my job. If they don't, I adjust the hook and try again tomorrow.