Greenbox has 200 subscribers but 8% monthly churn. Over three weeks of discovery (Jobs to Be Done, Assumption Mapping, Business Model Canvas) the team has uncovered more problems than they can fix at once. Now they need to decide what changes first.
It’s Monday morning and the office whiteboard is covered. Three weeks of discovery work have produced a wall of insights, sticky notes, canvas printouts, and scribbled questions. Maya stands in front of it with a coffee that’s gone cold.
Sam arrives early, which is unusual. He puts his bag down and opens his laptop before he takes off his jacket. “We lost three subscribers over the weekend.”
Maya turns. “Churn?”
“Not exactly. They switched. To Freshly.” Sam turns his laptop around. Freshly’s Perth launch page fills the screen: a clean hero image, the $18 price tag prominent, a “Now delivering in Perth” banner. “They went live on Friday. Three of our subscribers signed up over the weekend and cancelled with us. One of them, Louise, from the JTBD interviews, sent a message: ‘Sorry, but $18 is $18.’”
Maya stares at the screen. She knew this was coming. Dave had told her Freshly was calling farms. Charlotte’s BMC questions had forced the pricing conversation. But knowing it’s coming and seeing it on a Monday morning are different experiences.
“Seven dollars a week. Three hundred and sixty-four dollars a year. Of course people switch.”
Too much to fix
The insights are clear. A two-tier pricing model could fix the economics. A pause button would reduce churn. The value proposition needs repositioning around convenience. SEO is underinvested. The recipe cards are working but the marketing doesn’t match what customers actually care about.
Maya knows all of this. The team knows all of this. And that’s the problem.
By the time everyone arrives, Maya has written five priorities on the whiteboard, each circled in red.
- Ship the pause button (reduces churn)
- Launch two-tier pricing model (fixes unit economics)
- Reposition the value prop in all marketing
- Run a mixed-sourcing pilot
- Start SEO foundation work
Priya reads the list. “We’re five people.”
“I know.”
“That’s five initiatives for five people.”
Sam looks at the board. “Plus we still have to pack and ship two hundred boxes a week, manage farm relationships, keep the platform running, and prepare a board presentation.” He’s listing his own workload, though he doesn’t frame it that way. He has forty-three unread support emails from the weekend.
Maya puts down her marker. “I don’t know how to choose.”
Everyone has a different answer
Lee and Charlotte are on the call. The team spends thirty minutes arguing.
Tom thinks the pause button should be first: highest leverage, small engineering lift. Sam disagrees; fix the value prop messaging and you’ll acquire better-fit customers who churn less in the first place. Jas pushes for two-tier pricing because the board meeting is in three weeks. Priya wants the mixed-sourcing pilot first: you can’t pitch two-tier pricing without validating the supply chain. Maya keeps circling back to SEO.
Charlotte lets the argument run past the point where it’s productive. Then she says: “Five people, five answers. That’s not a disagreement about priorities. That’s the absence of a framework for deciding.”
Now / Next / Later
Charlotte shares her screen. Three columns.
Now is the next four weeks. High impact, high urgency. You can name the people and describe what “done” looks like.
Next is four to twelve weeks. Important but can wait, or needs more information first.
Later is beyond twelve weeks. Good ideas that aren’t ready.
“Everything can’t be Now. If it is, nothing is.”
She scores each initiative on two axes: impact on churn (the metric that matters most) and effort/risk.
Priya objects to the mixed-sourcing pilot being deferred. “We need supply chain data before we can commit to two-tier pricing.”
“You’re right,” Charlotte says. “But you don’t need a full pilot. You need three phone calls to wholesale suppliers and a week of test orders. That’s not a separate initiative; it’s part of the pricing preparation.”
The roadmap:
Q3 Theme: Fix the leaky bucket. Reduce monthly churn below 5%.
Everything the team works on this quarter should connect to that theme. When someone suggests a new initiative, the first question is: does it serve the quarterly theme?
Building the Now
Tom and Priya take the pause button. They Example Map it on Monday afternoon; twenty-five minutes produces twelve concrete examples and three red cards. They build it in six days.
Maya and Jas take the two-tier pricing model. Maya spends two days on the phone with Dave, Rachel, and their third farm partner, explaining what mixed sourcing means for local orders.
Dave is quiet for a long time. Then he asks: “Will the local box subscribers grow?”
Maya doesn’t know. She says so.
“Here’s what I need. Don’t blindside me. Give me three months’ notice if the local orders are going to drop. I can find other buyers, but I need time.”
Maya commits to it. She adds “quarterly farm partner review” to the Later column.
Jas designs the pricing page. But first, she presents something she’s been working on privately.
She’d taken the value prop repositioning – the one Maya moved from Now to Next – and done it anyway. Three evenings at home in Leederville, Moleskine open, laptop beside her. She connects her laptop to the office projector without asking anyone’s permission.
The homepage: “Dinner decided.” Mrs Patterson’s words, now a headline in Greenbox’s brand typeface. Below it, not a photo of vegetables but a photo of a family kitchen, a recipe card propped against a cutting board. The message: we deliver the moment after the decision is made.
The pricing page: “Local Box, $25/week – 100% locally sourced, seasonal produce from farms within fifty kilometres” and “Fresh Box, $20/week – a mix of local and market-fresh produce, same quality, more variety.” The mixed box isn’t framed as the cheap option. It’s framed as the variety option.
The about page: not “we source from local farms” but “we take Tuesday night off your plate.” The farm stories are still there, halfway down the page. But the lead is the job.
Maya stands in front of the projector. She reads every screen twice. “This is the first time the website matches what we actually do.”
Jas’s eyes fill. She blinks hard and looks down at her Moleskine. She’s been waiting to hear something like that since week one, when she designed the customisation interface that got thrown away, when Maya redirected the product without telling her, when she sat in her Leederville flat thinking about quitting. Her mum’s words about her grandmother: “She never grew what she thought people should eat. She grew what they actually wanted.” The napkin sketch from Mrs Patterson’s interview, with “dinner decided” underlined twice, is still in her Moleskine. It might be the most important thing she’s ever drawn.
“We can’t ship this yet,” Charlotte says, gently. “Value prop repositioning is Next, not Now. But save every one of these files.”
Sam catches Jas’s eye across the table and mouths: That was brilliant.
The board meeting
Maya presents on a Thursday afternoon. Charlotte coaches her the night before: “Don’t start with the product. Start with the problem.”
Maya starts with the churn number. She walks through the JTBD insight, the assumption mapping, the broken unit economics. Then the plan: Now/Next/Later roadmap, quarterly theme, early results (pause button already shipped, churn trending down in week one).
One investor, Angela, leans forward. “This is the first time you’ve presented something that isn’t a feature list. You’re showing me the thinking behind the choices.”
The board approves the next tranche of funding. Not because the plan is guaranteed, but because it’s coherent and evidence-based.
Angela stays on the call after the others drop off. “The fact that you were willing to present a plan that partially walks away from 100% local sourcing tells me you’re making decisions based on data, not sentiment. That’s what we needed to see.”
Four weeks later
The pause button: twenty-three subscribers used it. Nineteen resumed. Four extended but none cancelled. Monthly churn dropped from 8% to 5.5%.
The two-tier model: fourteen new subscribers chose the Fresh Box ($20), six chose Local ($25). Nobody switched from Local to Fresh: the new tier is expanding the market, not cannibalising the existing one. Sam checked five of the Fresh Box subscribers in their welcome call. Three had compared Greenbox to Freshly. The $20 price point made the comparison close enough that the recipe cards tipped the balance.
“Freshly has better technology and a lower price,” Charlotte says. “You have better curation and a clearer job-to-be-done. The question is which one matters more in six months.”
The draft
On the evening after the board call, Maya sits at the kitchen table. Nadia pours her a glass of wine.
“They said yes?”
“They said yes.”
“Then why do you look like that?”
Maya opens her email drafts. The “pausing operations” email is still there: three sentences, unsent, from the night after the BMC session. She reads it once. Then she closes the draft folder. Not deleting it. Not yet.
“I look like this because the hard part isn’t over. It’s changing shape.”
Freshly has ninety subscribers in Perth after one month. Sam tracks the number. Greenbox has two hundred and thirty-one. But Freshly’s growth rate is steeper. Dave reported that Rachel got a call from them last week. Rachel told them to get stuffed, but Rachel is one farmer.
Greenbox raises its funding. The board is satisfied. Churn is dropping. The two-tier model is expanding the market without cannibalising the existing one. The team understands the customer, not the customer they imagined at the Margaret River market, but the real one, the one who hires Greenbox so that dinner is already decided when they walk through the door.
That’s product-market fit. Not a guess. Evidence.
The team grows from five to fifteen. Two cities. New subscribers arriving faster than at any point in the company’s history. And then the problems change.
The codebase that five people understood becomes a system fifteen people need to work in. The architecture that worked at startup scale starts creaking. New developers join and don’t know why things are built the way they are. A change in the billing module breaks the delivery scheduler because nobody realised they were coupled. Tom fixes it in an hour, but the look on his face says he knows: this will happen again, and next time it might not be the billing module. It might be the substitution engine, or the allergen flags, or something that sends the wrong produce to the wrong person.
The techniques from the first two series got Greenbox here. But “here” is a different kind of problem. Not “what should we build?” but “how do we build at scale without the system collapsing under its own weight?”
Charlotte has a name for the approach: Domain-Driven Design. It starts with drawing boundaries around the parts of the system that change for different reasons.
The Greenbox story continues in Scaling the Machine. I'll be writing about a few other things in the meantime -- the next chapter lands around 9 Jun.