Greenbox has 12,000 subscribers, twenty-five people, three cities, and a product backlog with 340 items. The board has priorities. Marcus has priorities. Three key customers have priorities. Maya has said yes to all of them, and the engineering team is drowning.
Maya is a yes person. She always has been. It’s one of the things that made Greenbox work in the early days. When Dave mentioned his surplus zucchini, Maya said yes. When a customer asked about corporate boxes, Maya said yes. When the Melbourne farmers’ market invited Greenbox to set up a stall, Maya said yes before checking whether they had the logistics to support it.
At five people and 200 subscribers, saying yes to everything was a strategy. Every yes was an experiment. Most of them failed, but the ones that succeeded, the recipe cards, the corporate pilot, the Thursday delivery window, became the product. Maya’s willingness to try things was Greenbox’s competitive advantage.
At twenty-five people and 12,000 subscribers, saying yes to everything is a crisis.
The board meeting
The quarterly board meeting is on a Thursday afternoon in late January. The room is the same one where the team held their first Event Storm, the laminated photos are still on the wall, though now they share space with the quarterly theme board and Patricia’s KPI dashboard. The board has grown: Maya, the seed investor, the Cerulean Ventures partner from the Series B, and Patricia Osei as independent director.
Charlotte is there for the operational review. Diane dials in from Sydney. Marcus presents the commercial update.
The meeting is productive. Revenue up 12% quarter over quarter. Churn at 4% and falling. The Sydney acquisition is bedding in, slowly, painfully, but the subscriber count is growing. Marcus’s B2B pipeline has six active opportunities. The numbers are solid.
Then Patricia asks a question. It’s the kind of question that sounds simple and isn’t.
“What are we not doing this quarter?”
Maya opens her mouth. Closes it.
The seed investor looks up from his notes. The Cerulean partner shifts in her chair. Charlotte, who has been reviewing the sprint data on her laptop, stops typing.
“I can tell you what we are doing,” Maya says. “The loyalty programme. The corporate gifting portal. The API integration for FreshOffice. The Sydney team onboarding. The –”
Patricia holds up a hand. “I didn’t ask what you’re doing. I asked what you’re not doing. Every company has more opportunities than capacity. A healthy company knows which opportunities it’s choosing not to pursue. Can you tell me which opportunities Greenbox has deliberately said no to?”
Silence. Not because the room is hostile. Because the answer is genuinely: none. Maya hasn’t said no to anything. She’s said yes to everything and assumed the team would figure it out.
“We haven’t said no to anything,” Maya admits.
Patricia nods. She writes something in her notebook. She doesn’t push. That’s Patricia’s style, she asks the question, hears the answer, and trusts it to do its work. The question sits in Maya’s chest for the rest of the meeting like a stone.
The three commitments
After the board meeting, Charlotte asks Maya to walk her through the current commitments. They sit in the kitchen, because the meeting rooms are all booked, a sign of how much the company has grown. Charlotte has a notebook. Maya has her phone, scrolling through Slack messages, emails, and a note she made on the flight back from Sydney.
Commitment one: the loyalty programme. The board’s idea. The seed investor raised it two quarters ago, a points-based system where subscribers earn rewards for tenure, referrals, and engagement. The theory: reduce churn by giving long-term subscribers tangible benefits. The investor has data from another portfolio company where a loyalty programme reduced churn by 1.5 percentage points. At Greenbox’s scale, 1.5 points of churn reduction is worth roughly $540K in annual retained revenue.
Maya said yes at the board meeting where it was raised. She said yes because the numbers made sense and because saying no to a board member feels like saying no to the people who funded your company.
Commitment two: the corporate gifting portal. Marcus’s priority. Three B2B prospects, a law firm, a tech company, and a property group, want to buy Greenbox subscriptions as corporate gifts for clients. Combined annual value: $120K. But they need a portal: branded landing pages, bulk ordering, recipient management, custom messaging. Marcus estimates six weeks of engineering time for one squad.
Maya said yes because Marcus was excited, the revenue was real, and the commercial function she’d fought to build was finally generating pipeline. Saying no to Marcus’s first big deal felt like undermining the hire.
Commitment three: the FreshOffice API integration. A large corporate customer, 400 subscriptions, wants to integrate Greenbox into their internal ordering system. Custom API endpoints, SSO authentication, automated onboarding for new employees. The customer is paying $108K per year and has hinted that the contract renewal depends on the integration.
Maya said yes because losing a $108K customer would be the largest single churn event in Greenbox’s history. The customer’s account manager. Sam, flagged it as urgent. Maya agreed without checking whether the engineering team had capacity.
Charlotte writes the three commitments on the whiteboard. Under each one, she writes the estimated engineering effort.
| Commitment | Effort | Value |
|---|---|---|
| Loyalty programme | 1 squad, 10 weeks | ~$540K retained revenue/year |
| Corporate gifting portal | 1 squad, 6 weeks | ~$120K new revenue/year |
| FreshOffice API integration | 1 squad, 8 weeks | ~$108K retained revenue/year |
“How many squads do you have?” Charlotte asks.
“Three.”
“And how many of those squads are available for new work this quarter?”
Maya pauses. One squad is finishing the Sydney migration, that’s committed through February. One squad is on operational maintenance and the seasonal availability rules update that the Adelaide launch needs. That leaves one squad.
“One.”
“One squad. Three commitments. Total effort: twenty-four weeks. The quarter has thirteen weeks. You’ve committed to roughly twice what you can deliver.”
Maya stares at the whiteboard. She knows the maths. She’s known it for weeks. She’s been hoping that something would give, that one project would be smaller than estimated, that the Sydney squad would free up early, that Tom would find a way to parallelise.
“What happens if we try to do all three?” Charlotte asks.
“We do all three badly.”
“What happens if we do all three badly?”
Maya doesn’t answer, because the answer is the thing she’s most afraid of. If the loyalty programme is half-built, the board loses confidence. If the gifting portal is late, Marcus loses his first major deal and the commercial function looks like a failed experiment. If the FreshOffice integration isn’t delivered, a $108K customer leaves and the churn metrics spike in the quarterly report. Doing all three badly is worse than doing none of them.
Tom’s chart
Tom has been tracking the problem from the engineering side. He’s built a capacity model, nothing fancy, just a spreadsheet that maps squad availability against committed work. He brings it to the Monday leadership meeting.
“This is the current state,” he says, turning his laptop so Maya, Sam, Marcus, and Charlotte can see.
The chart shows three swimlanes, one per squad. Each swimlane is filled with coloured blocks representing committed work. The blocks extend past the end of the quarter. Way past.
“If we start all three commitments now and work on them simultaneously, the first one ships in late April. The last one ships in mid-June. That’s five months from now.”
Marcus leans forward. “The gifting prospects won’t wait five months. They’ll go to a competitor.”
“I know,” Tom says. “But if we focus one squad on one commitment, it ships in six to ten weeks. The question is which one.”
Sam adds: “FreshOffice told me last week that if the integration isn’t in progress by March, they’re evaluating alternatives. That’s not a threat. That’s their procurement timeline. Their IT team has a roadmap and we’re either on it or we’re not.”
The room is tense. Not angry, nobody is pointing fingers. But the weight of three commitments that can’t all be honoured is pressing on everyone. Marcus is thinking about the B2B pipeline he’s been building for three months. Sam is thinking about a customer she’s been managing for two years. Tom is thinking about the engineering team, already stretched, being asked to context-switch across three projects simultaneously.
Maya is thinking about the board meeting. Patricia’s question. What are we not doing?
Lee’s question
Maya calls Lee that evening. She hasn’t called him in months, since the discovery cadence was established and the team was running smoothly, Lee stepped back to an occasional advisory role. But tonight she needs someone outside the building.
Lee picks up on the third ring. She can hear his garden in the background, the hose running, the sound of a dog somewhere nearby.
“I’ve said yes to three things and we can do one,” Maya says without preamble.
Lee turns off the hose. “Tell me about all three.”
She talks for ten minutes. The loyalty programme, the gifting portal, the API integration. The board pressure, the sales pressure, the customer pressure. Lee listens the way he always has, completely, without interrupting, without planning his response.
When she finishes, he asks: “If Greenbox could only be great at one thing this quarter, what would it be?”
“That’s not how it works. We have commitments to the board, to Marcus, to FreshOffice –”
“I know you have commitments. I’m asking a different question. Not what you owe people. What would make Greenbox stronger? If you could only do one thing well between now and April, what thing would make the biggest difference to the company a year from now?”
Maya is quiet for a long time. She can hear Lee’s dog drinking water from a bowl.
“The loyalty programme,” she says. “Churn is the thing that compounds. Every subscriber we keep is revenue we don’t have to replace. The gifting portal is new revenue, which is important, but keeping existing subscribers is cheaper than finding new ones. And FreshOffice is one customer, even if they’re a big one.”
“So you have your answer.”
“But I can’t say no to the board on the gifting portal, they’re expecting Marcus to –”
“You just told me the loyalty programme is more important than the gifting portal. The board wants Greenbox to grow. If reducing churn grows the company more than a gifting portal, the board wants the loyalty programme. They just don’t know it yet.”
Framing
Charlotte coaches Maya on the conversation. Not the decision. Maya has made the decision. The framing.
“You’re not saying no to growth,” Charlotte says. They’re in the kitchen again, Tuesday afternoon, the espresso machine hissing. “You’re saying yes to the growth that compounds. The loyalty programme reduces churn. Reduced churn means the revenue from every new subscriber Marcus brings in is worth more, because they stay longer. The loyalty programme makes Marcus’s future work more valuable, not less.”
“And FreshOffice?”
“That’s a ‘not now.’ You’re not saying no to the integration. You’re saying: we’ll build it in Q2, when the Sydney squad frees up. In the meantime, offer them a manual workaround. Sam’s team can handle bulk onboarding manually for one quarter. It’s not elegant, but it keeps the customer.”
“They might leave anyway.”
“They might. But a customer who leaves because you were honest about timing is a customer you can win back. A customer who leaves because you delivered a half-finished integration is a customer who tells everyone your platform is unreliable.”
Maya nods. She’s heard Charlotte frame things before, during the Business Model Canvas work, during the management restructure. Charlotte’s skill isn’t in making decisions. It’s in making the decision feel like what it is: a strategic choice, not a failure.
“And Marcus?”
Charlotte pauses. “That one is harder. Marcus has been building pipeline for three months. Telling him the gifting portal is delayed feels like pulling the rug out from under his first major initiative. You need to tell him yourself, face to face, and you need to be clear about why.”
The conversation with Marcus
Maya asks Marcus to walk with her. It’s a thing she does when a conversation matters, she’d rather be moving than sitting across a desk. They walk along the waterfront near the Fremantle office, the Indian Ocean flat and impossibly blue.
“The gifting portal is delayed,” Maya says. “Not cancelled. Delayed to Q2.”
Marcus is quiet for a few steps. She can see his jaw working.
“The three prospects –”
“I know. I’m sorry. We have one squad available and the loyalty programme is the highest-impact use of that capacity this quarter.”
“The loyalty programme.” Marcus says it flat, tasting the words. “The thing the board wants.”
“The thing that reduces churn. Every point of churn we prevent makes your future deals more valuable. The subscribers you bring in next quarter will stay longer because we built this now.”
Marcus stops walking. He’s looking at the water. He’s been in sales for a decade. He’s had deals pulled before. He knows the feeling, the pipeline that was real yesterday and theoretical today.
“Can I at least tell the prospects Q2? Give them a timeline?”
“Yes. Absolutely. And if you need engineering time for a demo environment or a mockup to keep them warm, we can find a few days. But the full build is Q2.”
Marcus nods slowly. “Okay.” He turns and starts walking again. “I don’t love it. But I understand it. I’ve worked at companies that said yes to everything. They shipped nothing. At least you’re making a choice.”
He pauses. “Most founders can’t do this, you know. Say no to revenue. It’s a muscle most people don’t have.”
“I’m building it,” Maya says. “Ask me again next quarter and maybe I won’t need Charlotte to coach me through it first.”
Marcus almost smiles. Almost.
The board
The harder conversation is with the board. Maya schedules a special session, thirty minutes, focused agenda, one topic. She sends a pre-read the day before, which is something Patricia taught her: never surprise the board in the meeting.
The pre-read is one page. It shows the three commitments, the capacity, and the recommendation: focus on the loyalty programme in Q1, defer the gifting portal to Q2, offer FreshOffice a manual workaround and build the integration in Q2.
The board call starts at 4 PM. Maya presents the one-pager. She walks through the logic: churn reduction compounds, one thing done well beats three things done poorly, the team has capacity for one.
The seed investor speaks first. “I was the one who pushed for the loyalty programme, so obviously I’m biased. But I want to ask, what happens to the gifting revenue if we delay?”
Marcus, who Maya invited to present the commercial impact, responds: “Two of the three prospects will wait. One might not. Worst case, we lose $42K in annual revenue. That’s real. But it’s a fraction of the $540K in retained revenue the loyalty programme protects.”
The Cerulean partner asks: “What’s the risk if we try to do all three?”
Tom, also on the call, shares the capacity chart. “If we do all three, the earliest any of them ships is late April. The last one ships in June. We’d be context-switching across three projects for five months. Engineering velocity drops by roughly 30% when a squad juggles three priorities versus one. I’ve measured it over the past two quarters.”
Patricia’s question is the one Maya has been bracing for. “Maya, this is the first time you’ve come to the board and said no to something. Why now?”
Maya takes a breath. “Because you asked me what we’re not doing, and I couldn’t answer. That scared me. A company that can’t say what it’s not doing is a company that doesn’t have a strategy. It just has a list.”
The room, the virtual room, voices on a call, goes quiet. Not the uncomfortable quiet of the first board meeting when Angela asked how many people reported to Maya. A different kind of quiet. Consideration.
Patricia says: “Good.”
The seed investor says: “Agreed. Focus on churn.”
The Cerulean partner says: “I’d like to see the Q2 plan for the gifting portal and the API integration. But Q1 is clear.”
The call ends twelve minutes early. Maya stares at the screen for a moment. She expected pushback. She expected to defend the decision. Instead, the board was relieved. They’d been watching Maya say yes to everything for three years. They wanted someone to prioritise. They just didn’t want to be the ones to choose.
The backlog
With the decision made, Tom and Priya do something that’s been needed for months. They audit the product backlog.
340 items, the same feature factory backlog that had been growing unchecked. Some from the Event Storm in Year 1. Some from customer interviews. Some from Marcus’s commercial requirements. Some from engineers who noticed something wrong and filed a ticket instead of fixing it. 340 items, most of them undifferentiated, many of them outdated, some of them contradictory.
Tom and Priya spend a Wednesday afternoon with Charlotte going through them. The filter is simple: does this item serve the Q1 priority (loyalty programme and churn reduction), the Q2 pipeline (gifting portal, FreshOffice integration), or ongoing operational health? If none of those, it goes to a “parking lot”, not deleted, but explicitly deprioritised.
By the end of the afternoon, the backlog has 40 items. Forty. Each one tagged with a clear outcome: what will be different for subscribers or the business when this ships.
Tom photographs the whiteboard. 340 items crossed out, 40 remaining, each with a coloured dot indicating which quarter it belongs to.
“I feel like I’ve lost weight,” Priya says.
“You have,” Charlotte replies. “Decision debt is real. Every uncommitted item in a backlog is a decision you haven’t made. Three hundred open decisions is a cognitive load that slows everything down, even if nobody is actively working on any of them. Forty decisions is manageable. Your squad leads can hold forty items in their heads. They couldn’t hold three hundred.”
Sam and FreshOffice
Sam calls the FreshOffice account manager on Thursday morning. She’s prepared. Charlotte helped her structure the conversation: acknowledge the commitment, be honest about the timeline, offer the interim solution, be specific about Q2.
“The API integration is moving to Q2,” Sam says. “I know that’s not what you wanted to hear. Here’s what we can offer right now: my team will handle bulk onboarding manually. You send us a CSV of new employees on the first of each month, and we’ll have them set up within 48 hours. It’s not automated. It’s not elegant. But it means your team gets the same outcome while we build the proper integration.”
The FreshOffice account manager is quiet for a moment. “That’s actually fine for now. Our IT team was planning the integration for May anyway. As long as we have a date for the API, the manual process works.”
Sam feels the tension drain from her shoulders. She’d been carrying this conversation for two weeks, imagining the worst. The worst didn’t happen. Honesty and a concrete interim solution were enough.
“You could have told them that two weeks ago,” Charlotte says when Sam reports back.
“I know. I was scared they’d leave.”
“The fear of saying no is almost always worse than actually saying no. Customers want clarity. They can plan around ‘Q2.’ They can’t plan around silence.”
What saying no teaches
The quarter unfolds. One squad, one priority. The loyalty programme ships in eight weeks, two weeks ahead of the original estimate, because a team focused on one thing moves faster than a team juggling three.
The programme is simple: subscribers earn points for tenure (one point per week), referrals (fifty points per successful referral), and feedback (five points for completing a post-delivery survey). Points convert to discounts on future boxes. The mechanics aren’t revolutionary. But the implementation is clean, well-tested, and integrated into the existing subscription lifecycle, because the squad had time to do it properly instead of rushing.
By the end of the quarter, early data shows a 0.8 percentage point reduction in monthly churn among subscribers who’ve engaged with the loyalty programme. That’s not the full 1.5 points the investor projected. But it’s real, it’s measurable, and it’s compounding every month.
Marcus, meanwhile, keeps his three gifting prospects warm with monthly check-ins and a demo environment that Tom’s squad built in two days. Two of the three confirm they’ll sign when the portal launches in Q2. The third goes to a competitor. Marcus is philosophical about it. “One out of three isn’t bad. And the two that stayed are the bigger accounts.”
FreshOffice renews their contract on the existing terms, with the API integration written into the Q2 roadmap. Sam’s manual onboarding process works well enough that the customer’s IT team actually asks if they can keep using CSV uploads alongside the API. “Some things don’t need to be automated,” Sam tells Tom, who pretends not to hear.
The muscle
Saying no is not a personality trait. Maya used to think it was, that some people are naturally decisive and others naturally accommodating, and she was the latter. Charlotte reframed it: saying no is a skill. Like any skill, it’s uncomfortable at first and gets easier with practice.
The discomfort doesn’t go away entirely. Maya still feels the pull to say yes when someone presents an opportunity. The farmer who wants Greenbox to carry dairy products. The event company that wants a partnership for corporate catering. The engineering team member who pitches a mobile app. Each one is a good idea. Each one is a yes that would dilute the focus.
Maya’s filter, the one she keeps coming back to, is Lee’s question: If Greenbox could only be great at one thing this quarter, what would it be?
Not: what should we do? Not: what can we do? What should we be great at? The question forces a ranking. And a ranking forces a choice. And a choice means some things get done and other things don’t.
The board, at the next quarterly meeting, asks the same question Patricia asked. “What are we not doing this quarter?”
This time, Maya answers without hesitating.