GreenBox knows what it’s worth – and the discounts that reduce that number. The biggest gap is commercial: the company has 12,000 subscribers and no sales function. Maya hires a sales lead. He speaks a language nobody else in the building understands.
Marcus Holt arrives at the GreenBox Perth office on a Monday morning in late November carrying a laptop bag, a reusable coffee cup, and the slightly over-groomed energy of someone who’s spent the last decade in Melbourne B2B SaaS. He’s 35, clean-shaven, wearing a button-down shirt that’s slightly too formal for a startup where the CEO wears running shoes. He moved to Perth from Melbourne three months ago – lifestyle decision, he tells people. The surf, the pace, the way the sun hits the coast at six in the morning. He doesn’t mention the burnout that preceded the move, or the three months of doing nothing that followed it, or the phone call from a recruiter that described a role at “a produce box company that’s growing fast and doesn’t know how to sell.”
Marcus knows how to sell. He’s done it for seven years at two SaaS companies – one acquired, one still running. He’s built pipelines, managed CRMs, run discovery calls, and closed enterprise deals. He’s never sold produce boxes. He’s never worked at a company this small. He’s never been in a room where the vocabulary is “bounded contexts” and “Example Mapping” rather than “pipeline velocity” and “qualified leads.”
Maya hired him after three interviews, a reference check with his former VP of Sales, and a conversation with Diane. Diane’s assessment: “He’s good. He’ll clash with your engineering culture. That’s the point.”
The first day
Marcus spends his first morning in orientation. Sam walks him through the product – the box tiers, the subscription flow, the delivery cadence. Jas shows him the customer experience – the website, the onboarding emails, the recipe cards that were born from the JTBD insight about weeknight dinner stress. Tom gives him a technical overview – the architecture, the bounded contexts, the substitution engine.
Marcus listens carefully. He asks good questions. “What’s the average revenue per subscriber per year?” ($1,250.) “What’s the churn rate?” (About 4% monthly, down from 6% after the pause flow improvement.) “What’s the current acquisition channel?” (Word of mouth, referrals, the Saturday market stall.) “What’s the B2B pipeline?” (Three pilot customers in Melbourne, one of which doubled their order.)
Then he asks a question nobody has a good answer for: “Who are the next thousand subscribers and how do we reach them?”
Sam: “They find us. Through friends, social media, the market.”
“That’s not a channel. That’s hope.”
The room goes a little cold. Sam, who has been running GreenBox’s informal marketing since the beginning – the social posts, the email newsletters, the Saturday market stall – feels the comment like a slap. She doesn’t say anything. She doesn’t need to. Her expression says it.
Marcus catches it. He softens. “I’m sorry, that came out wrong. What you’ve built is remarkable. Twelve thousand subscribers through word of mouth is extraordinary. Most companies I’ve worked with would kill for that organic traction. What I mean is: you’ve taken word of mouth as far as it can go. To get to 25,000, then 50,000, you need structured acquisition. Not instead of word of mouth. On top of it.”
Sam nods. The correction helps. But the discomfort remains. Marcus speaks a different language, and it lands differently in a company that has spent two years building a culture around collaboration, discovery, and letting the product speak for itself.
Two languages
Over the first week, the language gap becomes a recurring friction. Marcus uses words the engineering team doesn’t use. “Pipeline velocity.” “Qualified leads.” “Objection handling.” “Sales cadence.” “Conversion funnel.” “Discovery call.”
Tom, sitting across the open-plan office, overhears Marcus on a call with a potential B2B client. Marcus is smooth, structured, deliberate. He asks questions, pauses, acknowledges the prospect’s concerns, and guides the conversation toward a trial. It’s clearly skilled work. Tom finds it deeply uncomfortable.
“We don’t sell,” Tom says to Priya during a code review. “People come to us because the product is good.”
Priya glances at him. “That’s not a strategy. That’s luck. Didn’t Marcus say exactly that?”
“I don’t trust salespeople.”
“You didn’t trust workshops either.”
Tom doesn’t have a response to that. He returns to the code review. But the comment sits with him for the rest of the day.
The engineering team’s suspicion isn’t about Marcus personally. It’s about what his presence represents. For two years, GreenBox has grown through the quality of the product and the strength of the customer relationships. The team built something good, and people found it. That feels pure. Adding a sales function feels like an admission that the product isn’t enough on its own. And if the product isn’t enough, what have they been building?
Jas articulates it most clearly over lunch with Charlotte. “Marcus is nice. He’s clearly good at what he does. But everything he says makes me feel like what we’ve built doesn’t matter unless someone can sell it. Like the product is necessary but not sufficient. That bothers me.”
Charlotte puts her fork down. “It is necessary but not sufficient. At twelve thousand subscribers, word of mouth works. At fifty thousand, it doesn’t. The product is the foundation. Sales is the amplifier. One doesn’t diminish the other.”
“Then why does it feel like it does?”
“Because the engineering culture treats making something good as the whole job. And in the early days, it was. But a company isn’t just a product. It’s a product plus the ability to find customers, serve them, and grow. You’ve been doing the first two. Marcus does the third.”
What Marcus wants
Within his first week, Marcus produces a document. It’s a two-page “Commercial Readiness Assessment” – a term that makes the engineering team wince – and it lists what he needs to do his job.
-
A CRM. “I need somewhere to track prospects, conversations, and pipeline stage. Right now, the B2B leads are in Sam’s email inbox and Maya’s head.”
-
A sales deck. “When I talk to a potential B2B client, I need to show them what GreenBox is, who uses it, and why they should care. We don’t have that.”
-
Case studies. “The Melbourne B2B pilot is a success story. The office that doubled their order, the team that fights over Wednesday lunch boxes. I need to write those up and use them.”
-
Pricing tiers for B2B. “Consumer is $20-$25 per week. What’s the B2B pricing? Volume discounts? Custom branding? Minimum orders? Nobody has defined this.”
-
A customer dashboard. “I need to see subscriber growth by region, churn by cohort, and acquisition source. Right now, that data exists in three different databases and nobody has built a view that combines them.”
Tom reads the document and his first instinct is resistance. A CRM. A sales deck. Case studies. This is corporate. This is everything GreenBox decided not to be.
But then he reads item five again. Subscriber growth by region, churn by cohort, acquisition source. Three different databases. Tom knows this is true. The subscriber data is in the main application database. The churn data is in a separate analytics pipeline that Priya built six months ago. The acquisition source data – such as it is – lives in Sam’s spreadsheets and Maya’s memory. There’s no single view.
Marcus isn’t wrong about needing the data. He’s not even wrong about how it should be structured. The request is reasonable. It’s the framing – “Commercial Readiness Assessment” – that makes the engineering team’s skin crawl.
Diane mediates
The tension comes to a head on Thursday of Marcus’s first week. The leadership meeting – Maya, Tom, Sam, Jas, Charlotte, and now Marcus – is discussing quarterly priorities. Marcus presents his pipeline targets for Q1: fifteen B2B prospects, five trials, two signed customers. He outlines the assets he needs to get there.
Tom pushes back. “We have a product roadmap. We have quarterly themes. We have a discovery cadence that tells us what customers need. Now we’re adding a sales pipeline with its own targets and its own asset requests? We’re going to spend engineering time building a sales deck and a CRM integration?”
Marcus, to his credit, doesn’t get defensive. “I’m not asking engineering to build a CRM. I’ll use an off-the-shelf tool. I am asking for help with the customer dashboard, because the data is locked in systems only your team can access. And I’m asking for case studies, which is mostly Sam and Jas’s territory – customer stories told well.”
“But the pipeline targets,” Tom says. “Fifteen prospects. Five trials. Those numbers come from you, not from the quarterly themes. Are they connected to the Impact Map? To the planning onion?”
It’s a fair question. Marcus doesn’t know what the Impact Map is. He’s been at GreenBox for four days.
Diane, who has been listening, steps in. “Tom, you’re right that Marcus’s targets should connect to the strategic framework. Marcus, you need to understand how GreenBox plans – the quarterly themes, the Impact Map, the discovery cadence. But let me ask a question that cuts through the process debate.”
She looks around the table. “Can GreenBox grow to 50,000 subscribers on word of mouth alone?”
Nobody answers, because the answer is obvious. No.
“Then the commercial function isn’t optional. It’s not a nice-to-have. It’s the thing that’s been missing since the beginning. Maya has been the sales function – every partnership, every B2B conversation, every farmer relationship runs through her. That’s why key person dependency is the biggest valuation discount. Marcus isn’t replacing the product. He’s replacing Maya-as-the-only-person-who-can-sell.”
Charlotte adds: “And Marcus isn’t wrong about needing structure. Tom isn’t wrong about connecting to the strategic framework. Both things are true. The question is how to integrate them, not which one wins.”
Diane nods. “Marcus, your pipeline targets are a hypothesis. Just like the quarterly themes. ‘We believe that fifteen B2B prospects will yield five trials and two customers.’ That’s testable. You run Q1, measure the results, and adjust. Charlotte, can you help Marcus connect his targets to the Impact Map?”
Charlotte can. And the temperature in the room drops three degrees.
The language bridge
The integration starts the following Tuesday. Marcus sits in on a customer interview.
Every Tuesday morning, a GreenBox team member interviews a subscriber or prospect. It’s the Continuous Discovery cadence that Charlotte established months ago – a weekly habit of talking to one customer, synthesising the insight, and feeding it into the product roadmap. This week, Jas is interviewing a Melbourne subscriber who’s been with GreenBox for eight months.
Marcus watches from the corner of the room, taking notes. Jas runs the interview using the JTBD framework – not the academic version, but the practical approach the team has refined over two years. She asks about the subscriber’s life, not the product. What was happening when she signed up? What was she struggling with? What does the box replace in her routine?
The subscriber – a woman named Claire, mid-thirties, two kids, husband who works late – tells a story that Marcus has never heard in a sales call. “I was spending Sunday nights planning meals for the week. Making a shopping list. Going to Coles on Monday morning. Standing in the produce section trying to figure out what’s in season and what the kids will eat and what I can cook in thirty minutes after work. The box just… removed all of that. I don’t plan any more. I open the box on Thursday, look at what’s inside, and the recipe card tells me what to do. It’s like having a friend who’s a good cook and already did the shopping.”
Jas asks the follow-up that the team has learned to ask: “If GreenBox disappeared tomorrow, what would you do?”
Claire thinks about it. “Go back to Coles. And hate it.”
After the interview, Marcus is quiet for a long time. The team is debriefing – Jas is writing up the key insights on the whiteboard, Charlotte is mapping them to the current quarterly themes, Sam is flagging an operations insight about delivery timing.
“This is the best sales research I’ve ever seen,” Marcus says.
Everyone turns to look at him.
“I’m serious. At my last company, we spent $200K a year on market research. Customer surveys, focus groups, competitive analysis. We never got insight this deep. You do it every Tuesday for free. Most sales teams would kill for this kind of customer understanding.”
Charlotte and Diane exchange a look across the room. It’s a small look – half-second, no words. But it carries something important. The discovery practices and the sales function aren’t separate things. They’re the same muscle applied to different stages of the customer relationship.
Marcus continues, thinking aloud. “The interview Jas just did – she identified the customer’s job to be done, the struggling moment, the emotional context, and the competitive alternative. That’s a consultative sales discovery call. The only difference is that Jas is doing it with an existing customer to understand the product, and I’d do it with a prospect to understand the opportunity. Same structure. Same questions. Different stage.”
Jas looks at Charlotte. “Is that true?”
Charlotte nods. “Consultative selling – the good kind, not the hard-close kind – is literally built on customer understanding. You already know how to understand what customers need. Marcus just needs to help you do it before they’re customers.”
Consultative selling
Marcus spends the next two weeks learning the GreenBox discovery techniques and mapping them to the sales methodology he knows. The overlap is larger than anyone expected.
JTBD maps to sales discovery. When Marcus talks to a B2B prospect – say, an office manager interested in corporate produce boxes – the first conversation isn’t about GreenBox’s product. It’s about the prospect’s world. What are they struggling with? What have they tried? What does success look like? These are the same questions the team asks in JTBD interviews. Marcus has been trained to do this, but the terminology is different: he calls it “discovery call” or “needs analysis.” The team calls it “JTBD interview.” Same conversation, different label.
Example Mapping maps to objection handling. When a prospect raises a concern – “What about allergens?” “Can you handle dietary restrictions?” “What if we need to change the order size week to week?” – the answer is a specific example. “Here’s how we handle allergens for a Melbourne client with three employees who have nut allergies. The decision table automatically excludes all nut-containing produce and substitutes…” The Examples and Rules from Example Mapping sessions are exactly the concrete answers that address prospect objections.
Assumption Mapping maps to deal qualification. Before investing time in a prospect, Marcus needs to assess: is this a real opportunity? The assumptions that matter in sales are different from product assumptions, but the technique is the same. “We assume this company has budget for employee perks.” “We assume the office manager has authority to sign a supplier contract.” “We assume there’s a kitchen or breakroom where boxes can be delivered.” Each assumption can be validated or invalidated early, before Marcus spends weeks nurturing a deal that was never going to close.
Marcus builds a one-page mapping document that he shares with the team:
| Discovery technique | Sales equivalent | When it’s used |
|---|---|---|
| JTBD interview | Discovery call / needs analysis | First conversation with a prospect |
| Example Mapping | Objection handling with concrete examples | Mid-pipeline, addressing concerns |
| Assumption Mapping | Deal qualification | Early pipeline, assessing fit |
| Impact Mapping | Account planning | Post-close, expanding the relationship |
Tom reads the mapping document and says nothing for a while. Then: “I hate that this makes sense.”
Priya laughs. It’s the first time the engineering team has laughed about the sales function. The tension breaks, slightly.
The pipeline
Marcus starts building pipeline. He’s methodical about it – the SaaS discipline serves him well, even though the product is different. He targets three segments:
B2B corporate wellness. Office produce boxes for companies that want healthy perks for employees. This is the segment the Melbourne pilot proved. Marcus’s pitch: “Your employees fight over the Wednesday lunch boxes. That’s employer brand. That’s retention. That’s a perk that costs less than a gym membership and is more visible.”
B2B hospitality. Restaurants and cafes that want guaranteed local produce deliveries. This is new territory – Dave and the farm network are the key differentiator. Marcus’s pitch: “We connect you directly with thirty-one farms within a hundred kilometres. Not wholesale market produce that’s been in a truck for three days. Farm to kitchen, picked yesterday.”
Consumer expansion. Not outbound cold-calling, but structured referral programmes and partnership channels. Marcus designs a “box for a friend” programme where existing subscribers can gift a trial box. He partners with local gyms and wellness studios for cross-promotion.
Within two weeks, Marcus has fifteen B2B prospects in various stages. Three are warm – an accounting firm in Perth CBD, a co-working space in Fremantle, and a restaurant group in Melbourne that Dave’s network connected him to. The restaurant group conversation started because Marcus asked Dave who in the supply chain might want direct farm relationships beyond what GreenBox already provides. Dave made one phone call. The restaurant group returned the call the same day.
Marcus is learning something the team already knows: the farm relationships are the moat. Any company can deliver produce boxes. Nobody else has Dave’s network, the trust that comes from two years of partnership, and the farm matching codified in decision tables. When Marcus talks to a B2B prospect, the farm relationships are the thing that makes their eyes widen. Not the technology. Not the subscription model. The fact that GreenBox knows which farm grew the tomatoes in the box, and the farmer knows the customer’s name.
The customer dashboard
Marcus’s request for a customer dashboard becomes a real conversation. Tom initially resists – it’s engineering time spent on an internal tool, not the product. But when he looks at what Marcus needs, he realises it’s the same data the product team needs for quarterly planning.
“Subscriber growth by region, churn by cohort, acquisition source,” Tom reads aloud. “We need all three of those for the quarterly theme review. Charlotte asks for them every quarter and someone spends a day pulling them from three databases into a spreadsheet.”
Sam adds: “And I need churn by cohort for the board reporting. I’ve been doing it manually.”
Jas: “And I need acquisition source for the B2B pricing analysis.”
Tom looks at the list. Four people need the same data. The data exists in three databases. Nobody has built the view that combines them.
“This isn’t a sales tool,” Tom says. “This is a company tool that sales happens to need.”
He adds it to the engineering backlog. It’s not the top priority – the retention work from the quarterly theme comes first – but it’s real work that serves multiple functions. Charlotte classifies it as Complicated: the rules are knowable, the data exists, it needs analysis to combine properly. An Example Mapping session. Probably two sprints of work.
Marcus watches Tom add it to the backlog. He doesn’t push for urgency. He’s learning the GreenBox rhythm: propose, discuss, prioritise, build. Not “I need this yesterday.” Not “sales trumps engineering.” Just: “here’s what I need, here’s why, let’s figure out when.”
It’s a small moment, but it matters. The sales function is integrating with the engineering culture, not overriding it.
The bridge moment
The real integration happens on a Tuesday three weeks after Marcus joins.
It’s the weekly customer interview. This time, Jas is interviewing a prospect – a woman who runs catering for a mid-sized architecture firm in Perth. She heard about GreenBox from a friend whose family subscribes. She’s interested in corporate boxes but has questions.
Marcus asks if he can observe. Jas agrees. Charlotte suggests something different: “Marcus, why don’t you co-interview? Jas leads the JTBD questions. You lead the commercial questions. Let’s see how they fit together.”
The interview is revelatory. Jas opens with the JTBD structure: “Tell me about the last time you arranged food for the office. What was that like?” The catering manager describes the frustration – cold pizza delivered late, limp salads from a chain, employees who skip the provided lunch and go to the food court instead. “I’m spending $2,000 a month on food nobody wants to eat.”
Then Marcus picks up the thread, naturally, without a handoff: “What would good look like? If we could solve the lunch problem perfectly, what would your team experience?” The catering manager lights up. She describes what she wants: fresh, interesting, arrives on time, accommodates the three vegans, the person with the nut allergy, and the partner who won’t eat anything green. She wants to stop thinking about office food. She wants it decided.
Jas and Marcus exchange a glance. Decided. The word that came out of the JTBD interviews two years ago. The word Jas sketched on a napkin and turned into the “dinner decided” tagline. The same job, in a different context. Not “weeknight dinner decided” but “office lunch decided.”
After the interview, Marcus turns to the team. “That woman is going to become a customer. Not because I sold her anything. Because Jas asked the right question and the answer told us exactly what to build. The product sells itself when the discovery is good.”
Diane, who’s been sitting in the back of the room, says: “That’s the sentence I’ve been waiting three weeks to hear.”
Charlotte adds: “The discovery practices aren’t just for product. They’re for sales, for partnerships, for board conversations. Understanding before building applies everywhere.”
“That’s a nice insight, Charlotte,” Diane says. “What does the customer see?”
Charlotte pauses. It’s a gentle challenge. Diane’s question – her signature question – is a reminder that frameworks and insights matter only when they translate to something a customer experiences.
“What the customer sees,” Charlotte says, “is a company that understood her problem before asking for her money. That’s consultative selling. That’s JTBD. That’s the same thing with different names.”
Diane smiles. “Now we’re talking.”
The tension that remains
Marcus is generating pipeline. The team is adjusting to having a sales function. The language gap is narrowing – the engineering team has stopped wincing at “pipeline velocity” and Marcus has started using “discovery” instead of “needs analysis.” The cultural integration isn’t complete, but it’s moving.
But there’s a deeper tension that Marcus surfaces in his second week. He’s reviewing the board deck with Diane and notices something.
“The reporting is all product metrics,” he says. “Subscriber count, churn rate, delivery accuracy, throughput. There’s nothing about commercial metrics. No pipeline report, no acquisition cost by channel, no conversion funnel, no forecast.”
Diane nods. “Maya reports what she knows. She knows the product. She doesn’t know the commercial side because there hasn’t been one.”
“And the board accepts that?”
“The board accepted it when GreenBox was a product story. It’s becoming a company story. Company stories need different metrics.”
Marcus starts building a commercial dashboard. Pipeline by stage. Prospects by segment. Conversion rates. Forecast revenue from B2B. He presents it at the next leadership meeting and Maya stares at it for a long time. It’s data she’s never seen before – not because it didn’t exist, but because nobody was collecting it.
“How many prospects are in the pipeline?” Maya asks.
“Fifteen. Three warm, eight in discovery, four in early research.”
“And the forecast?”
“If we close two of the three warm prospects this quarter, that’s approximately $180K in annual B2B revenue. Small, but proof of concept.”
Maya looks at Charlotte. “We’ve been running a product company. We need to be running a business.”
Charlotte nods. “That’s what Series B investors will expect. Not just product metrics. Business metrics. Revenue forecast. Pipeline. Acquisition cost. Customer lifetime value by segment. The story changes from ‘we built something good’ to ‘we built something good and we know how to grow it.’”
Tom, listening, adds something that surprises everyone: “The customer dashboard I’m building – it should include Marcus’s commercial data. One view. Product and commercial. Not two separate dashboards for two separate cultures. One company, one set of numbers.”
Marcus looks at Tom. It’s the first time Tom has volunteered to build something for the sales function. It’s a small thing. A design decision about a dashboard. But it’s the moment when the engineering team stops treating sales as an invader and starts treating it as a function.
Diane catches Charlotte’s eye. They’re both thinking the same thing. It took three weeks. That’s fast, by the standards of companies going through this transition.
The road ahead
Marcus is three weeks in and the pipeline is real. The B2B prospects are moving. The consumer referral programme is generating signups. The customer interviews are informing both the product roadmap and the sales approach. The two cultures – engineering and commercial – are learning to speak the same language, slowly, unevenly, but genuinely.
But the board wants more. The quarterly review is approaching and the board wants to see structured reporting – not just product metrics, not just commercial metrics, but an integrated view of the business. KPIs for each function. Financial forecasts. A board pack that tells a coherent story.
Maya’s spreadsheet isn’t enough any more. The Saturday morning dashboard update that Priya runs isn’t enough. GreenBox needs governance – not the bureaucratic kind, but the kind that lets a board make informed decisions and gives investors confidence that the company is professionally managed.
“You have the product muscle,” Diane tells Maya at the end of the week. “You’re building the commercial muscle. What you’re missing is the governance muscle. The board doesn’t want to micromanage. They want to know that when they ask a question, someone can answer it with data, not a guess.”
Maya knows she’s right. The informal, founder-led, everyone-reports-to-Maya era is over. The management layer is in place. The sales function is growing. The next step is the thing that makes it all visible to the outside world: structured governance, professional reporting, and a board that can do its job.
That’s the conversation nobody wants to have (coming 24 November).