GreenBox has 12,000 subscribers, three cities, twenty-five people, and a board that meets when Maya remembers to schedule it. For three years, that was enough. The Series B investors have a different opinion.
GreenBox’s board, until now, has consisted of three people: Maya, one investor from the seed round, and Lee in an advisory capacity. They meet quarterly – or rather, they intend to meet quarterly. In practice, Maya sends the investor a spreadsheet of subscriber numbers and revenue each month, Lee drops in when he’s in Perth, and the three of them have a conversation over coffee every few months that loosely qualifies as governance.
Nobody has ever prepared a board pack. Nobody has defined KPIs beyond the subscriber count on the dashboard. Nobody has asked whether the board’s composition is appropriate for a company preparing to raise an $8M round.
Diane Kerrigan is the one who names the problem. She’s been working with Maya for three weeks on Series B preparation, and she’s reviewed the company’s governance documents – such as they are. One shareholder agreement. One set of articles. No board charter. No committee terms of reference. No financial reporting cadence beyond “Maya emails a spreadsheet.”
“Maya,” Diane says, sitting across from her at the Fremantle office on a Tuesday morning. “Your governance is a spreadsheet and a handshake. That worked when you were five people and a dream. You’re asking investors to put eight million dollars into this company. They need to know there’s a board that can hold you accountable.”
Maya bristles. “We’ve been accountable. We’ve grown from zero to twelve thousand subscribers. We’re profitable. The numbers speak for themselves.”
“The numbers are excellent. But investors don’t just bet on numbers. They bet on the system that produces numbers. If you got hit by a bus tomorrow, who would run the next board meeting?”
Silence.
“That’s what I thought.”
The independent director
The lead investor for the Series B round requires an independent director as a condition of the term sheet. Not someone from the team. Not an advisor. Someone who represents shareholder interests – including Maya’s interests as a shareholder, but not Maya’s preferences as a founder.
Maya has never worked with an independent director. Lee explains the role over the phone: “An independent director isn’t there to tell you what to do. They’re there to ask whether you’ve thought about what you’re doing. Their job is to make sure the board is governing, not just cheerleading.”
“That sounds like Charlotte.”
Lee laughs. “Charlotte challenges you on how to scale the business. An independent director challenges you on whether the business is being governed properly. Different thing. Charlotte asks: ‘Is your engineering team structured to support three cities?’ An independent director asks: ‘If your engineering team falls apart, does the board know soon enough to do something about it?’”
The investor introduces Patricia Osei. She’s sixty, Ghanaian-Australian, a former CFO of a mid-size ASX-listed food company. She retired two years ago and now sits on four boards – two listed, two growth-stage. She’s precise in a way that feels warm rather than cold, the kind of precision that comes from decades of making numbers tell the truth.
Patricia meets Maya for lunch in Northbridge before agreeing to the role. She arrives in a tailored jacket and flat shoes, orders black coffee, and listens for twenty minutes while Maya tells the GreenBox story. The farms, the subscribers, the pivot from local-only to two-tier pricing, the three cities, the Freshly acquisition by Hartland Group.
Patricia asks three questions.
“What’s your gross margin by city?”
Maya hesitates. “Overall it’s about 42%. By city – I’d need to check.”
“What’s your customer acquisition cost?”
“About forty-five dollars. Marcus has been bringing it down through referral programmes.”
“If your delivery system went offline on a Thursday morning, how long before you’d know?”
Maya looks at her. “Sam would email us.”
Patricia nods slowly. “Those three answers tell me everything I need to know about where this company is.” She pauses. “You have a strong business with weak instrumentation. The business is real. The numbers exist. But they’re in people’s heads, not in systems. That’s what I’d want to help with.”
She agrees to join the board.
The first proper board meeting
The first formal board meeting is held in early November, in the small meeting room at the Fremantle office. It’s the room where the team held their first Event Storm three years ago. The laminated photos of sticky notes are still on the wall. Maya once told Charlotte they were “one of the smartest things a founder has ever done.” Now they’re a backdrop to a conversation about governance structures.
Present: Maya (founder and CEO), the seed-round investor, Lee (advisory), Patricia (independent director), and Diane (business scaling advisor, observing). Charlotte dials in from her home office in Perth’s northern suburbs.
Patricia opens her laptop and says: “Show me last quarter’s board pack.”
Maya looks at Diane. Diane looks at the table. There is no board pack. There has never been a board pack.
“All right,” Patricia says. She doesn’t sound surprised. “Let’s start from there.”
What goes in a board pack
A board pack is the document that the board receives before each meeting. It tells the board what happened since the last meeting, what’s happening now, and what needs the board’s attention.
Patricia walks the room through the structure she uses for growth-stage companies. It’s deliberately simple – she’s seen boards drown in hundred-page packs that nobody reads.
The five sections:
-
CEO update. One page. Narrative. What happened, what’s going well, what’s not, what needs the board’s input. “This is your chance to set the agenda,” Patricia tells Maya. “If you don’t write it, the board will spend the meeting asking random questions about whatever caught their eye in the numbers.”
-
Financial summary. Revenue, costs, cash position, burn rate, runway. Monthly trend for the last six months. Not a full P&L – that goes in an appendix for directors who want it. “The summary should fit on one page. If a board member needs to dig deeper, the detail is there. But the summary is what we discuss.”
-
Key metrics. The five numbers that tell you whether the business is healthy. Different for every company. For a subscription business like GreenBox, Patricia proposes: Monthly Recurring Revenue (MRR), churn rate, Customer Acquisition Cost (CAC), Lifetime Value (LTV), and gross margin.
-
Risk register. What could go wrong? Updated every quarter. Not a comprehensive risk management framework – five to ten risks, ranked by likelihood and impact, with a note on what’s being done about each one. “This is where the board earns its keep,” Patricia says. “The CEO sees the risks she’s managing. The board should see the risks the CEO isn’t seeing.”
-
Decisions required. Anything that needs formal board approval: funding decisions, major hires, strategic partnerships, policy changes. “If you need the board to decide something, put it here. Don’t surprise us in the meeting.”
Maya is writing notes. She’s writing fast, which Nadia would recognise as a sign that she’s both overwhelmed and engaged.
The five numbers
Patricia’s proposed key metrics generate the first real debate of the meeting.
Charlotte, on the phone, wants more. “Five numbers isn’t enough. I’d want to see deployment frequency, sprint velocity, customer satisfaction score, employee engagement –”
“That’s operations,” Patricia says. “Those are important. But they’re not board metrics. The board’s job is governance, not management. We need to know whether the business is healthy. The management team needs to know whether the operations are healthy. Those are different questions answered by different numbers.”
Charlotte pushes back. “If deployment frequency drops, it affects delivery timelines. That affects revenue. By the time it shows up in MRR, it’s three months late.”
“Then the CEO update should mention it. ‘Deployment frequency dropped this quarter. Engineering is addressing it. Here’s the plan.’ That’s narrative, not a KPI on the board dashboard.”
Diane, who has been listening, enters the conversation. “Patricia, I agree the board shouldn’t drown in numbers. But Charlotte’s right that some operational metrics are leading indicators. MRR tells you what happened. Churn rate tells you what’s about to happen. I’d want at least one forward-looking metric in the five.”
Patricia considers this. “Net Revenue Retention. NRR captures expansion revenue from existing customers minus churn. If NRR is above 100%, you’re growing even if you stop acquiring new customers. It’s the single best health metric for a subscription business.”
Maya looks up from her notes. “We’ve never calculated NRR.”
“I know. That’s why we’re here.”
Charlotte wants structured OKRs cascading from the board level down to squad level. Quarterly objectives, key results, tracked and reported. She’s seen it work at the SaaS company she scaled before GreenBox.
Diane shakes her head. “OKR cascades sound great in a slide deck. In practice, at twenty-five people, they become a reporting burden that eats the time you should spend talking to customers. Five numbers on one page. If all five are green, don’t waste the board’s time.”
They argue. Not heated – professional. Charlotte is making a structural case: without cascading metrics, how does the board know that squad-level work connects to company-level goals? Diane is making an operational case: the team is twenty-five people, not two hundred. The overhead of a full OKR cascade would consume a week per quarter in reporting alone.
Patricia listens. Then: “Charlotte is right about structure. Diane is right about simplicity. Five numbers, reviewed monthly, with a written narrative when any of them goes red. That’s your board pack. If the company grows to a hundred people, we revisit. For now, five numbers and a story.”
The seed-round investor, who has been quiet until now, nods. “I’ve been getting Maya’s spreadsheet for three years. I love Maya’s spreadsheet. But it doesn’t tell me when something’s going wrong until it’s already gone wrong. This is better.”
The subscription business dashboard
Patricia and Maya spend the next day building the first GreenBox board dashboard. Five metrics, twelve months of historical data, calculated from the numbers Tom’s system already tracks.
Monthly Recurring Revenue (MRR). The total monthly revenue from active subscribers. GreenBox’s MRR is approximately $300,000 – 12,000 subscribers at a blended average of $25/month. The trend line shows steady growth: Perth flat (mature market), Melbourne growing, Brisbane early but accelerating.
Churn rate. The percentage of subscribers who cancel each month. GreenBox’s churn is 3.8% – down from the 4% that Charlotte identified in the planning onion work. The pause-resume flow that the Perth squad built reduced involuntary churn by 40%. Voluntary churn is harder – subscribers who leave because they’ve changed their cooking habits or moved to a different service.
Customer Acquisition Cost (CAC). What it costs to acquire one new subscriber. GreenBox’s CAC is $45, which Marcus has been working to reduce through referral programmes and word-of-mouth amplification. For comparison, Freshly’s CAC was estimated at $15 before the Hartland Group acquisition – but Freshly’s model was volume-driven with lower margins. Different economics.
Lifetime Value (LTV). The total revenue a subscriber generates before churning. With a 3.8% monthly churn rate, the average subscriber stays about 26 months. At $25/month blended average, that’s an LTV of roughly $650. LTV/CAC ratio of 14:1 – well above the 3:1 benchmark that most investors look for.
Net Revenue Retention (NRR). This is the new one. Patricia helps Maya calculate it for the first time. NRR measures how much revenue you’d have from existing customers if you acquired nobody new. It accounts for upgrades (subscribers moving from $20 to $25 boxes, adding family boxes), downgrades, and cancellations. GreenBox’s NRR is 104% – meaning the company would grow 4% per year even with zero new customer acquisition. Patricia calls this “the number that makes investors lean forward.”
Maya stares at the dashboard. Five numbers. Twelve months of data. One page.
“I’ve been sending a spreadsheet with forty columns,” she says. “This tells a better story than any of them.”
“That’s the point. The spreadsheet tells you everything. The dashboard tells you what matters.”
The governance conversation
The second half of the board meeting shifts from metrics to governance itself. Patricia explains the difference between a startup board and a growth board.
A startup board is advisory and supportive. The founders are figuring things out. The board’s job is to help – open doors, share experience, ask good questions. The power sits with the founders.
A growth board is about governance and accountability. The company has reached a scale where decisions affect employees, customers, investors, and partners. The board’s job is to make sure decisions are being made well – not to make them, but to ensure the process is sound. The power is shared.
“You’re transitioning from the first to the second,” Patricia tells Maya. “That doesn’t mean the board becomes adversarial. It means the board becomes a check on the things you can’t check yourself. Your blind spots. Your biases. The risks you’re too close to see.”
Maya is quiet. This is the same pattern from the management gap conversation – she’s learning, again, that the structures she instinctively resists are the structures the company needs.
Patricia outlines three governance practices she wants to establish:
Regular board meetings. Quarterly, on fixed dates, scheduled a year in advance. Board pack distributed five business days before the meeting. “If the pack isn’t ready, the meeting is rescheduled. A board meeting without preparation is worse than no meeting at all.”
Committee structure. For now, two committees: Audit and Risk (Patricia chairs), and People and Culture (the seed-round investor chairs). The committees meet between board meetings and report to the full board. “You don’t need committees at twenty-five people. You need them at fifty. Better to build the habit now than retrofit it during a crisis.”
Board evaluation. Once a year, the board reviews its own performance. Are meetings productive? Is the right information reaching the board? Are the right questions being asked? “Boards that don’t evaluate themselves become complacent. Same principle as your sprint retros, just at a different level.”
Lee, who has been listening from his advisory seat, smiles. “She’s right. A board that doesn’t retro is like a team that doesn’t retro. The same mistakes repeat.”
The tech seed
Near the end of the meeting, Patricia returns to the question she asked Maya at lunch. “If your delivery tracking goes down on a Thursday morning, how quickly do you know?”
Tom is dialled in for the technology update. “Sam monitors the key systems. If something’s off, she emails the team.”
Patricia pauses. “That’s a person doing a system’s job. What happens when Sam is sick? What happens when Sam is on leave? What happens when you’re in eight cities and the system goes down at 3am?”
Tom doesn’t answer immediately. He’s thinking.
“In my last company,” Patricia says, “we had what the SRE team called ‘golden signals.’ Four metrics that tell you whether a system is healthy: latency, traffic, errors, and saturation. If any of those signals crosses a threshold, the system alerts the team. Not a person checking – the system itself, telling you something’s wrong.”
Tom hasn’t heard the term. He writes it down.
Charlotte, still on the phone, says quietly: “We should talk about that.”
Patricia also asks about engineering velocity. “How often do you deploy to production? How long does it take from code commit to live? How often does a deploy fail and need to be rolled back?”
Tom hesitates. “We deploy… when things are ready. Maybe twice a week? The process takes about an hour. Failures – I’d have to check the logs.”
“Those are DORA metrics,” Charlotte says. “Deployment frequency, lead time for changes, change failure rate, mean time to recovery. They’re the industry standard for measuring engineering performance.”
Tom looks interested despite himself. “We’ve never formally tracked those.”
“I know,” Charlotte says. “We should.”
Patricia nods. “I’m not asking because I understand the engineering. I’m asking because the board needs to know whether the technology platform can support the growth plan. If you’re deploying twice a week manually and you want to be in eight cities, that’s a constraint the board should understand.”
She looks at Maya. “Put it in the next CEO update. Not as a KPI – as a narrative. ‘Here’s where our engineering capability is. Here’s where it needs to be. Here’s the plan to get there.’”
The dashboard goes up
The following Monday, Maya prints the board dashboard on A3 paper and pins it next to the planning onion on the wall of the Perth office. Five numbers. One page.
MRR: $300K. Churn: 3.8%. CAC: $45. LTV: $650. NRR: 104%.
Sam looks at it. “That’s… really clear.”
“Patricia’s idea. Five numbers. When one goes red, we write a narrative.”
Tom walks past, reads the numbers, and stops. “NRR 104%. That’s actually really good.”
“I know. I didn’t even know what NRR was two weeks ago.”
Priya, on a video call from Melbourne, asks: “What’s the threshold for red?”
Maya checks her notes from the board meeting. “MRR: any month-on-month decline. Churn: above 5%. CAC: above $60. LTV: below $400. NRR: below 100%.”
“And when something goes red?”
“The board gets a written narrative. What happened, why, and what we’re doing about it.”
Priya nods. “That’s basically an ADR for the business.”
Maya hadn’t thought of it that way. But Priya is right. The board narrative serves the same purpose as an Architecture Decision Record: it captures the context, the problem, the options, and the decision. The ADR captures technical decisions. The board narrative captures business decisions. Same structure, different domain.
Patricia sends Maya an email that evening. One line: “Governance isn’t bureaucracy. It’s how you make sure the company survives beyond any single person.”
Maya reads it twice. Then she forwards it to Nadia with no comment. Nadia replies: “She sounds like your mum.”
Maya stares at the screen for a long time.
What the board pack reveals
Maya prepares the first real board pack over the following week. Five sections, as Patricia outlined. CEO update, financial summary, key metrics, risk register, decisions required.
The process of writing it is harder than she expected. Not because the information doesn’t exist – it does, scattered across spreadsheets and dashboards and Sam’s head and Tom’s memory. The hard part is synthesising it into a story that a non-operational person can understand.
The financial summary reveals something Maya hasn’t articulated: Perth is subsidising Brisbane. Brisbane’s unit economics are negative – the delivery costs in a new market with fewer subscribers are higher per box. That’s expected for a market in early growth. But the board pack makes the cross-subsidy visible in a way that Maya’s spreadsheet never did.
The risk register is where it gets uncomfortable. Patricia asked Maya to list the top five risks to the business. Maya writes them down:
- Key person dependency (Maya, Tom, Dave)
- Customer concentration (70% of revenue from Perth)
- Competitive pressure (Hartland Group/Freshly)
- Supply chain fragility (seasonal, weather-dependent)
- Technology scalability (manual deployments, limited monitoring)
She stares at the list. The first risk – key person dependency – is the one she’s been avoiding since Diane first raised it in the valuation conversation. It’s the risk that applies a 20% discount to the company’s value. It’s the risk that means the company is worth $35M instead of $44M.
And the board pack makes it impossible to ignore.
The board pack reveals something nobody wanted to see: GreenBox’s value depends on people who could leave tomorrow.