Yes, but only if...
Voting for a 'conditional yes' in 2026
I almost took a job that would have been a disaster.
This was about four years into my marketing career. A Series B startup, decent funding, impressive leadership team. The VP of Demand Gen role was a huge step up from where I was. They wanted me to build their demand gen function from scratch.
I said yes to the interview. Full, enthusiastic, unconditional yes.
I made it through their five rounds of interviews, but then during the offer negotiation, I started asking questions some more precise questions. Turns out “building from scratch” meant I’d have zero budget for six months while they “proved out the ROI.” What does that even mean? I’d be reporting to a CEO who wanted daily metrics updates but wouldn’t commit to any specific headcount. And the “impressive leadership team” had turned over three demand gen leaders in eighteen months.
I backed out. Felt terrible about it. Worried I’d burned a bridge. This leadership team is well connected in this space. Everyone knows their names.
But backing out of a bad yes taught me something more valuable than any role could have: the power of conditional acceptance.
👋 Hi, it’s Kaylee Edmondson and welcome to Looped In, my newsletter covering demand gen and growth in B2B SaaS. Subscribe to join 2k+ readers who get Looped In delivered to their inbox every Sunday.
The Unconditional Yes Trap
We’re taught that ambitious people say yes. That growth comes from taking on more. That opportunities favor the eager.
And look, there’s some truth there. I didn’t get from marketing coordinator to VP in six years by turning down challenges.
But the marketers I see thriving right now aren’t the ones with the longest task lists. Look at any of them. I’m sure you’ve got a few top of mind right now. They all have this mastered ability for strategic, conditional acceptance.
“Yes, but only if...”
This phrase has become my filter for everything from client work to speaking opportunities to that random LinkedIn coffee chat request. And the CMOs I work with who struggle most are usually drowning in commitments they made without conditions.
One CMO I worked with recently had said yes to launching ABM, building a content engine, running a rebrand, AND expanding into two new markets. All in Q1. With the same team size and budget as the previous year.
When I asked why she’d agreed to all of it, she said “I didn’t want to seem like I wasn’t up for the challenge.”
That’s the trap. We confuse conditional acceptance with weakness.
Career Opportunities: Protecting Your Trajectory
Let me tell you about when I joined Chili Piper as Director of Demand Gen.
They approached me about building their demand function as one of the founding marketers. Zero to one build, direct report to CEO, all the sexy startup stuff.
I wanted it. Bad.
But I didn’t just say yes. I said “yes, but only if...”
I needed to report directly to the CEO, not through another layer. I needed confirmed budget for at least the first two quarters. I needed clarity on what success looked like in months 3, 6, and 12. And I needed to know that if I built something that worked, I’d have a path to build the team underneath it. Oh, and on a personal note, it was Q1 of 2020 (IYKYK) and two days before accepting the role, I’d just found out I was pregnant. So I needed those conditions to be wildly accepted as well.
All of those conditions were met. And that role became one of the most formative experiences of my career.
Compare that to a friend who took a “VP of Growth” role at a startup. She said yes immediately, excited about the title bump. Three months in, she realized the role meant demand gen, product growth, customer marketing, AND partnerships. With a team of zero. She lasted six months before burning out.
The conditions you should set for career opportunities:
Authority matching responsibility. If they want you to own outcomes, you need decision-making power. “Yes, but only if I have final say on budget allocation and team structure.”
Resources matching expectations. Ambitious goals are great, but they require fuel. “Yes, but only if we can commit to X budget and Y headcount within the first quarter.”
Clear success metrics. Vague goals lead to vague performance reviews. “Yes, but only if we align on specific KPIs and how success will be measured.”
Alignment with your 2-3 year plan. Every role should build toward where you want to be. “Yes, but only if this gives me experience in [specific area] that I need for my next move.”
The good opportunities can meet these conditions. The bad ones reveal themselves immediately.
Work Responsibilities: Guarding Your Capacity
About four months into going solo, a client asked if I could “quickly” help them with a rebrand project.
Old me would have said yes immediately. Need to keep clients happy, right?
New me said “yes, but only if we can push the demand gen strategy work to next month, or if you want to bring in additional resources for the rebrand.”
They chose to bring in a brand specialist. Project went great. I stayed focused on what I actually do best.
When I was managing a $XXM demand gen budget at Campaign Monitor, the requests were constant. “Can you hop on this customer call?” “Can DG own this launch?” “Can you scale this across two new channels?”
Every single request seemed reasonable in isolation. But unconditional yeses meant my team was scattered across a million different priorities.
I started requiring conditions for any new ask:
“Yes, but only if we can deprioritize the content calendar refresh we planned for this quarter.”
“Yes, but only if success is defined as X measurable outcome, not just ‘launch the thing.’”
Some people pushed back. Said I was being difficult. But the requests that were actually important found a way to meet the conditions. The ones that were just someone else’s problem being punted to marketing quietly went away.
The conditions you should set for work requests:
Resource reallocation. Nothing is free. “Yes, but only if we agree on what comes off the roadmap to make room.”
Defined success criteria. If you can’t measure it, you can’t manage it. “Yes, but only if we align on what done looks like before we start.”
Appropriate timeline. Urgency doesn’t mean immediately. “Yes, but only if we have realistic time to do this right, not just fast.”
Clear ownership. Someone needs to be the DRI. “Yes, but only if I have final decision-making authority OR if someone else is clearly the lead.”
These conditions force the asker to clarify what they actually need. Half the time, once conditions are stated, the request changes completely.
Personal Responsibilities: Protecting Your Energy
I get probably 15-20 LinkedIn messages a week asking to “pick my brain” about demand gen, solopreneurship, or career stuff.
I want to help people. But I learned pretty quickly that unconditional yes to all these requests was destroying my ability to do actual client work.
So I started using “yes, but only if...”
“I’d love to help! I do most of my mentoring through this newsletter, but I’m happy to do a quick async exchange if you can send me your three most specific questions first.”
About 60% of requests never follow up. Which tells me they weren’t that serious to begin with.
The 40% who do follow up? Those conversations are focused, valuable for both of us, and don’t require me to block out 30-60 minutes I don’t have.
Same thing with speaking opportunities. I love sharing what I’ve learned. But not every conference or podcast is worth the time investment.
“Yes, but only if the audience is primarily B2B SaaS marketers in demand gen or growth roles.”
“Yes, but only if I can do it remotely (since I’m balancing client work and family).”
These are my conditions that ensure mutual value. The right opportunities can meet them easily.
The conditions you should set for personal requests:
Mutual value. Your time is finite. “Yes, but only if we can make this valuable for both of us.”
Specific parameters. Vague asks lead to vague outcomes. “Yes, but only if you can send me specific questions in advance.”
Realistic time investment. Not everything needs to be a 60-minute call. “Yes, but only if we can do this async/in 15 minutes/with clear start and end time.”
Your Move
Next time someone asks you to take on a new project, consider a role, or help with something outside your core work, try this:
Pause before answering. Even if that pause is just “let me think about that and get back to you in 24 hours.”
Ask yourself what would need to be true for this to be a clear yes.
Then communicate those conditions clearly.
You’re not being difficult. You’re being strategic about where your finite time and energy go.
The right opportunities will meet your conditions. The wrong ones will filter themselves out. And you’ll end up with a career and workload built on intentional choices, not accidental obligations.
Here’s to growth.
See ya next week,
Kaylee ✌