Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How One Employee Got Promoted by Building a Business Case
Transcript
- Lucas: So you get a request from your boss that feels like busywork. But what if that request is actually the launchpad for the promotion you've been waiting for? Luna: That sounds like a specific story. Lucas: It is. I want to walk through how a marketing coordinator at a mid-sized logistics firm turned a routine request for a data report into a business case that got her promoted into a brand-new role. Luna: What was the request? Lucas: Her boss asked her to compile monthly marketing spend across three departments. Simple enough. But as she dug into the numbers, she realized the same data was being tracked in three different spreadsheets, none of them talking to each other. Luna: Classic data silo problem. Lucas: Exactly. Most people would have just cleaned it up and sent the report. But she started asking questions. How many hours are people spending on this duplication? What decisions are being missed because the data doesn't integrate? Luna: She went from task-doer to problem-solver. Lucas: Right. And that shift is the difference between staying in your lane and creating a new lane. So she did something smart. She interviewed people across departments — operations, finance, sales — and estimated that the company was losing about three hundred and forty thousand dollars a year in duplicated work and missed insights. Luna: That's a specific number. How'd she get to that? Lucas: She tracked time. She found that five people collectively spent about twenty hours a week reconciling data. At an average loaded cost of sixty dollars an hour, that's about sixty-two thousand dollars a year in wasted labor. Then she added the cost of poor decisions — like campaigns running on outdated lists, or missed cross-sell opportunities. She got conservative estimates from the sales team. That pushed it over three hundred thousand. Luna: So she built a bottom-up cost model. That's more credible than a top-down guess. Lucas: Exactly. Now she had a problem quantified. Next, she researched a solution. She found an analytics platform that could integrate all three data sources. Price tag: four hundred thousand dollars for a two-year license, plus implementation. Luna: So the cost of the problem is three hundred forty thousand a year. The solution costs four hundred thousand over two years? That's a twelve-month payback. Lucas: Roughly. Eighteen months if you include implementation. But here's the key — she didn't just present the numbers. She framed it as an investment, not an expense. She used the language of the CFO. Luna: What does that mean exactly? Lucas: She calculated return on investment, payback period, net present value. She showed that even with a conservative discount rate, the project had a positive NPV in under two years. She also included qualitative benefits: faster decision-making, fewer errors, better customer targeting. Luna: She did all that as a marketing coordinator? Lucas: She did. And that's the point. She took initiative beyond her scope. Now, she needed a sponsor. She scheduled a thirty-minute meeting with the VP of marketing, but she also asked if the CFO could join. That was a power move. Luna: She went straight to the decision-maker with a financial argument. Smart. Lucas: The CFO was impressed. He said it was the most well-prepared pitch he'd seen from someone below director level. The project got approved. But here's the promotion part. When it came time to implement, the company realized they needed someone to own this new capability. They created a new role: data strategy lead. She got it. Luna: She essentially designed her own promotion. Lucas: She did. And this is a repeatable pattern. Identify a measurable pain point. Quantify the cost of inaction. Research a solution. Build a business case in the language of leadership. Then present it to someone who can say yes. Luna: I love that she didn't wait for permission. She just started solving a problem. Lucas: And that's exactly the kind of behavior that gets noticed for promotion. But a lot of people worry about overstepping. They think, 'I'm not an analyst, I can't build an NPV model.' But you don't need an MBA. You just need to ask the right questions and do the math. Luna: Which brings me to a quick thought. If this episode is giving you a framework you can actually use, that's exactly why we do the show ad-free. The way to keep that going is listener support. If today was useful, you can buy me a coffee dot com slash fexingo. It's a small way to say this content matters to you. Lucas: Absolutely. And it keeps us independent. So back to the business case. One thing she did that I think is underappreciated: she anticipated objections. She knew the CFO would ask about maintenance costs, so she included a three-year total cost of ownership. Luna: She didn't just pitch the upside; she showed she'd thought about the downside. Lucas: Exactly. That builds trust. Now, here's a practical step you can take this week. Pick a recurring frustration in your work. Something that wastes time or money. Estimate the cost. Just rough numbers. Then see if you can find a solution that costs less than the problem. Luna: And if you present that to your boss, you're not complaining — you're proposing an investment. Lucas: Right. And that's how you go from task-doer to strategist. That's the promotion path. Luna: One thing I'd add: she also built relationships during her research. She interviewed people, got their buy-in, and they became advocates when the pitch happened. Lucas: Great point. The business case was technical, but the promotion was social. She had allies. Luna: So if you're listening and you're thinking about doing something similar, start small. Find one problem, quantify it, and bring a solution. You don't have to go from zero to four-hundred-thousand-dollar proposal overnight. Lucas: Exactly. Even a ten thousand dollar savings gets attention. And it builds your reputation as someone who thinks like an owner. Luna: Alright, I'm going to try this myself this week. Lucas: Let us know how it goes. And if you want more frameworks like this, we've got a whole archive. Thanks for listening, and see you next time.