Rose Kozar

The through-line

Rose Kozar's fixed idea is that value has to be articulated, not assumed. Asked what founders should know before starting a company, she goes straight past product and market to the ability to explain worth: "no one cares about your software," and even the best platform solving real pain points "doesn't really matter" if you can't say exactly why and how it helps a customer make more money or make their life easier [1]. The corollary, and the part she says founders miss, is that the articulation work is mostly someone else's job. "You need to be able to coach your clients and your customers to be able to speak effectively to the value they're getting out of your platform, which will pay dividends across future sales motions, recurring revenue" [1]. Churn, in her reading, is largely a failure to reinforce value from day one [1].

Everything else follows from that: post-sales as the majority of the work rather than the tail of it, the quarterly business review as the machine for producing and rehearsing the value story, and a refusal to treat a signed contract as protection.

On why the contract is the beginning, not the end

Kozar treats the moment of signature as roughly the first third of a customer journey, not the halfway point [1]. She attributes the blind spot to a mix of causes: the first few sales are so hard and so exciting that it is mentally easier to declare victory and move on, and founders who have never bought enterprise software themselves may not realise that for the buyer signing is where things actually start [1]. Her own standard is deliberately extreme: "I would consider the sales process not done until you have a really evangelical champion at every client" [1]. She is sympathetic about why the discipline slips, noting how hard it is to be a founder or one of the first ten to twenty people, and that many people have never seen what a genuinely good post-sales process looks like, even as exposure has made good sales processes widely understood [1].

She extends the point past the contract entirely. Master service agreements and statements of work are, in her experience, "pieces of paper" [1]. Nobody is realistically taking a large enterprise customer to court, and a seed or Series A company will simply be bled dry in the attempt [1]. An entire C-suite can turn over, budgets can be cut, a black swan event can arrive and vendors simply stop being paid [1]. Her conclusion is blunt: "you are constantly in a sales process" [1], and large enterprises, particularly public companies, will put every vendor on the line and behave outside the letter of the contract when conditions demand it [1].

On what a QBR is and why the ask is not an imposition

A quarterly business review, in her definition, is time set aside every quarter with key stakeholders at the client to walk through what happened last quarter, what value was generated together, and what value can be generated going forward [1]. She acknowledges directly that it is a real investment of time on both sides and that this is precisely what puts people off asking for it [1]. Her fix is to reframe the request in sales terms: if you have a powerful solution to someone's problem, "it is a favor in some ways to sit down with a QBR for them" [1]. She calls herself obsessed with them and treats the arrangement as a win-win, adding a duty argument on top: with a six-figure enterprise license, "it's your duty to make sure that the client is getting all the value they have out of the platform," and failing to ensure that value is negligence toward someone you sold a promise to [1].

There is a second, softer benefit she keeps returning to. In a post-COVID and largely remote world, a QBR is sometimes the only occasion on which a client's own teams assemble [1]. Groups that work adjacently but not closely get a quarter's worth of strategic conversation they would otherwise never schedule, and internal dynamics get hashed out in the room while the vendor serves as the forcing function [1]. She also values the intelligence that only proximity produces: hallway and bathroom-corridor exchanges about what someone meant by a comment, or why a particular stakeholder was so interested, "you can't replicate some of that on a Zoom meeting" [1].

On sizing the effort to the deal

She puts the threshold for a full-scale QBR at roughly $200,000 to $250,000, the level at which she considers it the vendor's responsibility to run one [1]. Below that, she argues for scaled-back versions rather than nothing: many of the tactical components can be partly automated, and a monthly or quarterly email, increasingly assisted by AI tools, at least puts an explanation of value into the customer's hands even without a full day on site [1]. She also cautions against reading current contract value as final. A $50,000 license can become a million-dollar ACV as new features and modules arrive, so the account you deprioritise on price today may be the one you most need a champion inside tomorrow [1].

On format, she is testing rather than asserting. Her team recently made a rule that for the next two quarters they will push to hold QBRs in person or not at all, as an experiment [1]. Her honest position is that remote QBRs still have value because the conversations still happen, but that in person is "so much more powerful" [1].

On arming the champion

Her single test for whether a QBR worked is a hypothetical: if your champion ran into the CFO in an elevator tomorrow and was asked whether the platform could be cut from the budget, what would they say [1]? The goal is that everyone leaves the meeting enthusiastic and holding a clean sound bite [1]. She observes that an excited user, a director who understands the purchase rationale, and a C-suite sponsor who can slot it into an AI strategy still mostly cannot produce a succinct must-have argument on the spot, and that this matters more, not less, in an uncertain economic period [1]. The burden sits with the vendor because the champion has a bajillion other things going on and is not thinking about your ROI [1]. Her framing is train-the-trainer: you invest in sales enablement for your own AEs, so apply the same thinking to the customer so they have the sound bites ready [1].

She offers a reframe for people uncomfortable pushing their own value: if the platform helps someone get promoted, the customer gets value, their career develops, and you have created a lifelong champion who is emotionally tied to your success because they know you are tied to theirs, including when they move to another organisation [1]. Pressing your value, in that light, is showing off the excellent work the users are doing [1].

On who to put in the room

She recommends keeping two lists, a wish list of attendees and a realistic one [1]. Always ask whether the check signer will attend, and depending on price point and seniority, whether their boss will too, because "they're not going to come without the ask" and the worst answer is no [1]. A no is itself an opening: have someone senior on your side follow up afterwards with a note saying sorry we missed you, here are three core slides, which she does routinely to stay in a target executive's mind space [1]. Beyond that she wants the main user, the internal champion, ops or IT support for the platform, and a core representative from each key stakeholder group, with care taken over when user spotlights happen and how long each person is asked to stay so that nobody's time is wasted [1].

Her hot take is to invite a detractor. She would rather hear the objection in the room than discover it later, and reports converting sceptics into some of her biggest advocates by letting them watch colleagues describe the value the platform has added and see it come to life [1]. She flags this as a judgement call: your mileage may vary, and the risk should be sized honestly [1]. The optimal preparation state, she says, is that clients co-present or largely own the material themselves, and as her team elevates client stakeholders they increasingly take over the conversation [1].

On how post-sales teams should think

Kozar draws a line between where post-sales sits organisationally and how it should be trained. Her own function is not in the sales organisation, but she still believes sales training on a regular cadence for a post-sales team is essential and widely skipped [1]. Being sales-minded makes the team more efficient rather than less, because it teaches them to identify the highest-leverage use of their time [1]. She pairs this with the discipline of being clear-eyed about what is service revenue and what is platform revenue [1].

Takeaways

• Treat the signature as the first third of the journey, not the finish line, and consider the sales process incomplete until you have an evangelical champion at every client [1].
• "No one cares about your software": the differentiator is being able to articulate exactly how it makes a customer money or makes their life easier, and coaching them to say it themselves [1].
• Reframe the QBR ask as a favour to the client rather than an imposition, and treat ensuring realised value on a six-figure license as a duty [1].
• Judge a QBR by the elevator test: if the CFO asked your champion tomorrow whether the platform could be cut, would they have a crisp one-liner ready [1]?
• Run full-scale QBRs from roughly $200,000 to $250,000, and below that use scaled-back or partly automated monthly and quarterly value updates rather than nothing [1].
• Always ask the check signer to attend, and when they decline, have someone senior send the three core slides as a follow-up [1].
• Invite a detractor into the room: hearing objections early beats discovering them late, and sceptics convert when they watch colleagues describe the value [1].
• Contracts are pieces of paper, since you will not sue a large enterprise as an early-stage company, so assume you are permanently in a sales process [1].