Latest / The Promotion Memo with Fexingo: Getting Visibility, Sponsors, and Executive Presence / How to Sell a Project Your Boss Hasn't Asked For
Transcript
- Lucas: One of the hardest things to do inside a large organization is sell a project that nobody asked for. Not something your boss hinted at in the last quarterly review, not a gap on the roadmap that everyone knows exists, but a genuine orphan idea that you believe in and that no executive has prioritized. Luna: And most people don't even try because they assume the answer is no before they start. Lucas: Exactly. But the people who do try, and succeed, tend to get noticed in a way that resumes and annual reviews can't replicate. There's a specific case I want to walk through. A senior product manager at a mid-size B2B software company — let's call the company DataStream, not its real name — she spotted a churn pattern that nobody in leadership was tracking. Luna: What was the pattern? Lucas: Customers who used fewer than three of the platform's modules in the first sixty days had a retention rate below forty percent after one year. But the company's customer success team was organized per module, so nobody saw the cross-module drop-off. The VP of Product was focused on feature velocity, the VP of Sales was focused on new logos. This problem was invisible. Luna: Right, and it's the kind of orphan insight that can live in a spreadsheet forever if nobody champions it. Lucas: She didn't go straight to the VP with a twenty-page proposal. That would have been a nonstarter. Instead, she spent two weeks pulling data that mapped the churn number to a concrete dollar figure. Roughly one point two million dollars in annualized revenue at risk. Then she identified two VPs who had adjacent pain — the VP of Customer Success was getting pressure on net retention, and the VP of Finance cared about unit economics. Luna: So she pre-sold the idea to them one-on-one before ever writing a formal pitch. That's the classic pre-selling move. Lucas: Exactly. She booked thirty-minute meetings with each, framed as 'I have some data I think you'll find useful.' In the meeting, she showed them a one-page mockup of a dashboard that would flag under-engaged accounts at day thirty, paired with a proposed intervention playbook. She didn't ask for budget yet. She asked for feedback. Luna: That's smart. It lowers the stakes, and it gives them ownership of the idea because they're helping shape it. Lucas: Exactly. The VP of Customer Success loved it and said, 'If you can build a prototype, I'll pilot it with my top ten at-risk accounts.' The VP of Finance said, 'If you can show a sixty-day pilot reduces churn by even ten percent, I'll fund the full build.' So now she had two senior sponsors, but no formal approval. Luna: And no budget to build the prototype. That's the hurdle. Lucas: Right. So she used a low-risk framing. She went to her manager, the Director of Product, and said, 'I want to carve out twenty percent of my time for two sprints to build a lightweight dashboard and a playbook. No new headcount, no vendor spend, just my existing hours redirected. At the end of two sprints, we kill it or scale it.' Luna: That's the 'low-risk experiment with a hard stop' move. Hard to say no to that. Lucas: Her manager said yes. She built the prototype. The pilot ran for sixty days with the top ten at-risk accounts. Five of those accounts increased module usage, and two renewed early. The pilot's churn rate dropped from forty percent to twenty-two percent in that cohort. That gave her the data to go back to the VP of Finance with a real business case. Luna: So now she's not asking for money based on a hunch. She has a measured outcome. Lucas: Exactly. The full business case requested one full-time data analyst and a license for a customer engagement tool — total incremental cost of about one hundred and forty thousand dollars a year. The projected impact based on the pilot was four hundred thousand dollars in retained revenue in year one. The VP of Finance approved it in a week. Luna: And then the CTO presented it at the board meeting as a company-wide initiative. She didn't even have to sell it at that level herself. Lucas: That's the key. She built enough sponsorship from below — from the VPs who had skin in the game — that her idea rose organically. The CTO heard about it from the VP of Customer Success, asked for a summary, and decided to feature it in his board deck. She got credit, but she didn't have to self-promote to the C-suite. Luna: So what's the framework you'd extract from this? Because I think a lot of listeners are thinking, 'I have an idea, but I don't have a VP of Finance in my pocket.' Lucas: There are four steps. First, map the orphan idea to an existing organizational pain point. Don't pitch the solution, pitch the problem that someone already feels. In her case, the VP of Customer Success already felt the pressure on net retention. She just gave him a clearer picture of the source. Luna: Second is the pre-sell. Don't go for a yes or no upfront. Go for 'let's explore.' Lucas: Exactly. Third, frame your request as a low-risk experiment with a defined stop condition. That makes it safe for your manager to say yes. And fourth, once you have a pilot result, build the full business case with real numbers. Then let your sponsors carry it upward. Luna: There's a risk here though. You could be seen as going rogue, stepping outside your lane, especially if you're not senior. Lucas: That's a real concern. And the protection against it is the pre-sell. If you've already got two VPs nodding along before you talk to your manager, you're not a lone cowboy. You're someone who's been asked to explore by people with authority. The key is to never surprise your direct manager. Loop them in early, even if just casually: 'I've been looking at some churn data, and it's interesting. Mind if I dig a little?' Luna: That's good. So the frame isn't 'I have a secret project,' it's 'I have a hypothesis and I'm testing it.' Lucas: Right. And one more thing — the data she used was already available. She didn't build a new data pipeline. She pulled cross-functional data that existed in different systems. That's a powerful move because it costs nothing and shows you can synthesize information. Luna: So for someone listening right now who has an orphan idea: what's the first concrete step they should take this week? Lucas: Write down the problem in one sentence. Then list who else in your organization might already be feeling that problem. Not who should care, but who already does. If you can't name at least two people, your idea might not be ready. If you can, book a fifteen-minute coffee chat with one of them to ask: 'Are you seeing anything like this?' Luna: And if they say no, you've learned something valuable too. Lucas: Exactly. You've either validated or invalidated your pain point. And that's real progress. The worst outcome isn't a no. It's never asking the question.