Vera's story

The company

Vera helps subscription businesses keep their customers. When someone goes to cancel, Vera catches them in the flow with a save offer such as a discount, pause, or downgrade. It also recovers failed payments before they lapse.

What makes the offers work is the network engine underneath. Any one company sees only its own churn data. Vera sees everyone’s, so its saves are already calibrated to what works. While Vera can work for any subscription business, it’s currently strongest in product-led B2B SaaS, where it has the most data.

The buyer is a growth or product leader who owns the churn number but doesn’t have anyone dedicated to it. For these customers, Vera isn’t a tool so much as the churn-reduction team they don’t have.

The people

Maya	VP Product. Started in February. Our protagonist.
Daniel	CEO and cofounder. Ran product himself until Maya arrived.
Michelle	CTO and cofounder. On the strategy squad.
Jordan	Marketing. On the strategy squad.
Marcus	Customer success. On the strategy squad.
Sofia	VP Sales. Looped in closely, not in the room.

The situation

Daniel and Michelle founded Vera after living the problem. Their last company nearly died from churn, and they hacked together an internal system to stop the bleeding, Daniel on the data and Michelle on the code. Daniel ran product himself until recently, mostly from intuition he never wrote down.

Midmarket companies came to love the product, and that love carried Vera to a $35M Series B last October on a two-part story: dominate midmarket and move upmarket into the enterprise. Seven months later, with $15M ARR and a headcount of 60 including 18 engineers, the funding story had become a slogan. The team was stretched thin trying to satisfy both sides of it at once.

Maya took the VP Product job in February and spent her first few months getting up to speed and asking lots of questions, learning the product, the customers, and the org before changing anything. By May she had enough context and trust to take on what she’d been hired for: turn that fundraising story into reality.

She went looking for the strategy and found the board decks from the fundraise. It wasn’t wrong, just thin. It was built to raise money, not to run a company, and seven months on, each team had interpreted the ambiguity its own way.

Part 1: Craft the strategy

The Sketch – Chapter 2

Start with a Strategy Sketch

Maya wasn’t going to figure this out alone, so she pulled together a small strategy squad: Michelle, Jordan from marketing, Marcus from customer success, with Sofia from sales looped in closely.

Their task: dump everything they knew onto the table, including product performance, pipeline, win/loss, support patterns, board promises, and capacity. Then split up and each sketch a whole strategy individually before comparing notes. Maya’s own first pass tried to fit it all in: win midmarket, push enterprise, and lean into the data story.

Jordan named the symptom.

“I can’t write the homepage. Are we a cancel-flow tool or a retention platform? Midmarket or enterprise? Every version I try is right for half our customers and wrong for the other half.”

But side by side, the sketches told a different story. Everyone had independently drawn the same picture: Vera wins by being the retention team its customers don’t have, and what’s hard to copy is the efficacy data across a whole network of saves. Where they differed was the approach.

Maya wrote down the shared thesis as provisional, and came away with one rough page.

Maya’s sketch

This is the sketch printed in Chapter 2. Italics are Maya’s own notes to herself, the open questions she’d chase next.

Context

• Midmarket self-serve is working—they love us, lots of room left. Enterprise stalling—deals stuck at evaluation, not seen as must-have.
• Series B raise promised both markets. We’re doing neither well.
• Data engine real and growing. Dense enough in any one segment to actually win? TBD.
• Issues:
  • Teams stretched thin (capacity)
  • Pressure to show upmarket progress
  • Sales comp plan may tilt enterprise
• A billing provider keeps circling. Trying to acquire us/integrate?

Challenge

• We’re a must-have in midmarket and nice-to-have in enterprise.
• Why? And is the gap the real problem or a symptom of something underneath? Dig in.

Value thesis (provisional)

• We win by serving subscription businesses who struggle with churn they can’t staff a team to own. They’ll choose us over building it themselves or living with it because our save offers are calibrated on network data no single company has. Hard to copy because that data compounds as more companies join.
• But who exactly? “Subscription businesses” = everyone. Sharpen.

Approach (unresolved—three ideas)

• Take cancel flow upmarket now
  • Market segment focus = company-level call. Going enterprise means real GTM investment, so need ELT alignment.
• Deepen retention platform in midmarket first, then go upmarket
  • Leaning here. Would defer the Series B promise—review data + go over with CEO.
• Keep chasing both markets at once (status quo, but not winning)

Bets (rough if/thens, if we go deep in midmarket)

• If we catch at-risk customers before the cancel flow, then we save more subs than we can on their way out the door
• If we make the network data the thing the whole product runs on, then our interventions beat anything built off one company’s data
• If we’re deeply integrated into customer workflows, then we’re infrastructure they’d hate to rip out
• Not now: enterprise-readiness (SOC2, SSO). Eventually needed, doesn’t win midmarket, and network data isn’t dense enough to win enterprise yet.

Maya walked Daniel through the sketch that afternoon, not for sign-off, but to gauge his reaction. His concern was exactly what she expected.

“The board funded upmarket.”

Now the tension was on the page instead of lurking in the background.

Distill the Context – Chapter 3

What’s Going On?

Maya’s sketch was a set of guesses, so she set out to find which were wrong. She started with the foundations: the business strategy, product vision, and previous product strategy.

That’s where the first problem surfaced. Maya went looking for the strategy docs and only found the deck from the fundraise. It wasn’t a strategy. It was a grab bag: dominate midmarket and break into enterprise, “be the AI-native retention platform,” and everything a priority. No diagnosis, no tradeoffs, no argument for why this path over that one.

That may have been enough at twenty-five people with Daniel holding the rest in his head. At sixty people, it wasn’t. Every team had quietly resolved the ambiguity its own way. Sales heard enterprise, where the big money and logos were. Engineering heard midmarket, where the product actually worked. Nobody was wrong, because it hadn’t been decided. And unmade choices never stay unmade. In a clarity vacuum, everyone comes up with their own interpretation.

The business strategy wasn’t up to Maya, but closing the clarity gap was. First she got Daniel to clarify the business objective: not logos for their own sake, but durable, fundable growth, a business strong enough to raise the next round on.

That reframed the question. “Upmarket or not” was the wrong one. The real question was sequence. Could Vera build its way to a winning enterprise position instead of trying to force one now?

Maya’s recommendation was to win midmarket first, then the enterprise. It was the same destination promised to investors, but sequenced to build something durable instead of chasing logos they couldn’t keep. Daniel pushed back, saying the board was expecting enterprise progress.

“They expect us to win,” Maya countered, “and the pipeline says we can’t win enterprise yet anyway.”

Daniel sat with it for a few days, then made the call.

What the data said

With the foundation clear, Maya turned to the current state. She went through the recent data and did a listening tour about the product, business, customers, competition, and constraints.

Product. A strong wedge, but a thin platform. The cancel flow worked, but the deeper retention layer that might win the enterprise didn’t exist yet.

Business performance. Midmarket was strong: 120% net revenue retention, short sales cycles, a high win rate. The enterprise pipeline kept stalling at evaluation. The big companies could staff their own retention teams and leaned on their own data, so Vera wasn’t a must-buy for them.

Customers. The sharpest story. The ones who loved Vera were the ones where it had become central to their retention work, not just a cancel flow they bolted on. These customers clustered in self-serve B2B SaaS, where Vera’s data was dense enough to make its interventions effective.

Competition. Less comforting. A competitor had open-sourced its cancel flows, and the billing providers already had the enterprise reach Vera wanted. One billing provider had recently contacted Daniel about a “strategic partnership” he feared could end Vera’s billing-agnostic stance, and its chance to stay independent.

Constraints. Tighter still. The round was raised on the upmarket story, the sales comp plan rewarded enterprise, and Michelle’s engineering team had capacity for platform depth or enterprise-readiness, but not both.

The surprise

One finding surprised Maya. She’d assumed the data network was Vera’s trump card: more data, better interventions, game over. But every other tool now pitched cross-company benchmarks. Having data was table stakes.

What made Vera’s interventions work wasn’t volume, it was concentration. In dense categories, efficacy patterns transferred across customers. In categories where they had sparse data, like consumer apps, Vera’s performance tanked.

So the strategy couldn’t just be about market sequencing. It had to account for category density too. The segment most tempting to chase might be exactly where Vera’s interventions were weakest.

The grounded beliefs

She finished her listening tour and met with the strategy squad to pressure-test what they believed, until each belief was grounded and defensible.

• Retention is existential for our best customers, and nobody owns it. That gap is our opening.
• Our cancel flow is a wedge, not a moat. It gets us in the door, but won’t keep us in.
• Our advantage comes from data density within a category, not raw volume. Depth beats breadth.
• Midmarket is unfinished, and we can win there. Enterprise is unproven, and the deck oversold where we are.
• The path upmarket runs through the platform, not the cancel flow. That platform doesn’t exist yet.

Frame the Challenge – Chapter 4

What Must We Solve?

With the market sequencing settled, Maya could find the real product problem.

The strategy squad dumped every challenge and opportunity onto a board, thirty-some sticky notes. A few she pulled off immediately because they were solutions in disguise: “take the flow upmarket,” “go AI-first,” “the data already wins enterprise.” For each, she asked what problem it was really solving, put that problem on the board, and let the solution go.

Then the squad clustered the notes down to about ten, then kept debating and editing until they stalled at six groups. All six looked important. And they were, six real problem areas, all worth solving.

This was the part that actually hurt. Not the analysis, but the cutting: five important problems would not get attention right now.

Maya named what was happening. This discomfort was a signal they were doing it right. Focus means cutting, not ranking. She also reminded them that “not now” wasn’t “never.” The strategy would be updated next quarter, so no cut was a forever choice. Accepting that was what let them make the cuts instead of fighting them.

So she asked the squad her favorite tiebreaker question: if we solved just one of these, which makes the rest easier?

After some discussion, the wall reorganized around a single uncomfortable truth.

The crux

That truth was the density problem Maya had surfaced earlier.

Vera’s interventions won so far because no single customer could match its cross-network data. But the market it was chasing was full of buyers who could. Large enterprises already had plenty of their own data, so Vera’s network edge, the whole reason its saves beat anyone else’s, was worth far less to them. That was why enterprise prospects kept asking why they couldn’t just do it themselves. At their scale, they mostly could.

And Vera couldn’t simply stay in midmarket, where its data edge was strong. The raise had promised the enterprise, so the one market where its edge counted least was the one market it had committed to win.

That was the crux. Critical, because Vera needed a market its current edge couldn’t win. Addressable, because Vera could choose what to build. It could earn its way upmarket on something other than the data alone.

Naming it snapped the scattered findings into place.

Bringing the stakeholders along

The diagnosis came from the strategy squad, so Michelle, Jordan, and Marcus were already aligned on it. The two stakeholders Maya needed to bring along for the ride were the ones not in the room: Daniel and Sofia.

When Maya showed Sofia, the stalled deals finally made sense to her. Her prospects liked Vera but had so much data already that Vera’s supplemented theirs instead of beating it.

Daniel was the hard one. The board still wanted upmarket now, but getting him to nod at the diagnosis, before there was any solution to fight about, opened the door to a different path. You align on the diagnosis before you can align on a response.

What got cut, and why

She also wrote down the strong candidates they’d cut, and why each lost to the crux.

• Enterprise-readiness gaps (SOC2, etc). Real, but closing them wins nothing if enterprise isn’t pulling for the product in the first place.
• The crowded retention-tools market. Symptom, not cause. Vera wasn’t losing to other tools, it was losing to homegrown workarounds and people tolerating the status quo.
• Onboarding friction. Legit problem, and solving it would make a good tool better, but not the core issue.

The challenge statement

Then Maya drafted a challenge statement, because a challenge that lives only in the room fades quickly. She drafted it eight different ways before she landed on:

Vera needs the one market where its data advantage counts least.

The statement named what was wrong and why, but not how to fix it. They’d deal with the how next.

Define the Value Thesis – Chapter 5

Why Will Customers Choose Us?

The sketch’s thesis had the right idea but wasn’t specific enough. Vera helps subscription businesses solve churn they can’t staff, using data no single company has. But “subscription businesses” is almost everyone, and a thesis that broad is a must-buy for no one.

Talking with customers helped Maya sharpen it. She asked a growth lead at a mid-sized subscription company why they used Vera, and the answer changed her thinking.

“Honestly? Nobody here owns churn. Vera is the only thing here that wakes up every morning obsessed with saving these customers—and at our size, every customer matters. We can’t out-grow the leak the way a big company might. If I had a retention team, or if we grew fast enough, I’m not sure what I’d need Vera for.”

When Maya asked customers like this to stack-rank their problems, unowned churn landed in the top three, unprompted. It hurt enough to act on.

The segments

So the bullseye wasn’t “subscription businesses.” It was the midmarket self-serve B2B SaaS company with material, unowned churn and less-than-rocketship growth. They can’t easily leave because Vera isn’t a tool they use, it’s a job they delegated. Category density narrowed it further: this only held where Vera’s data was strong.

These were Vera’s targets.

Naming who Vera was for meant naming who it wasn’t for, which was harder.

Bystanders: consumer subscriptions. The product would work, but the data was too thin to be reliably effective.

Distractions: sales-led businesses, however big. No self-serve cancel to intercept, no failed card to recover, churn run by a human CSM.

Which meant some of the big logos Sofia’s team had been chasing weren’t wins at all. They were pulling Vera toward customers who’d never love it.

The differentiation choices

The real competition wasn’t other vendors. It was build-it-yourself, and its quieter cousin, live with the churn. Maya made her ABC choices against those.

Be Amazing at	Intervention efficacy. Saves and recoveries shaped by a data network no single company could match.
Be Basic at	Table-stakes cancellation flows and dunning mechanics. Good enough not to lose deals on, not where they’d win.
Be Crappy at	Breadth. Worse than a general tool across the board, because depth in self-serve B2B SaaS was the whole point.

Anyone could build a cancel flow. What they couldn’t build was the data network that made it smart.

The defensibility

That last bit pointed at the defensibility, which had two parts.

The first was the data network effect. Every cancel and recovery made the next intervention sharper, so the more companies used Vera, the smarter it got.

The second was integration depth. The more of a customer’s retention work Vera touched, the more it hurt to leave.

The thesis

Maya drafted the value thesis:

We win by serving midmarket self-serve B2B subscription companies who struggle with material, unowned churn they can’t staff a team to fix. They’ll choose us over building it themselves, stitching together point tools, or living with it, because we’re the retention function they can’t staff, with interventions shaped by network data they can’t reproduce. This will be hard to beat on two fronts: our system gets smarter the more companies use us, and the deeper we wire into a customer’s work, the more it costs them to leave.

The statement held together, with one weak link: whether Vera could stay dense in each new category as it expanded. So she pressure-tested the thesis, running it past Daniel, Sofia, and a skeptical customer, looking for where it cracked.

Develop the Approach – Chapter 6

How Will We Make This Real?

With the thesis sharp, Maya turned to how Vera would make it real. She pushed the squad to generate real alternatives, distinct paths, not flavors of one. Three survived.

Path one — Take the cancel flow upmarket now

Fast, and it matches the fundraise story. Vera had the tool, and Sofia’s team had pipeline for it. But it went upmarket with Vera’s weakest hand: a thin wedge, aimed at the buyers least likely to need it.

Path two — Become the full retention layer midmarket runs on, then go upmarket with that

Own the whole lifecycle, not just the cancel flow. This answered path one’s problem. Vera couldn’t win upmarket as a tool whose value reduced with scale, but it could as an integrated layer across every customer touchpoint, which got harder to replicate the bigger the customer got. The network still sharpened the interventions underneath, but upmarket, the lock-in would come from the integration depth, not the data.

The catch: it deferred exactly what the board funded, and the integrated layer didn’t exist yet.

Path three — Ride upmarket on a billing provider’s distribution

Partner or get absorbed, the way Brightback went to Chargebee and ProfitWell to Paddle. Instant enterprise reach, and it could read like a fast exit the board might love.

The status quo, chasing both markets at once, wasn’t a fourth path. It was winning nothing.

The premortem

The squad ran a premortem on each: assume it failed a year out, why?

Path one died because a cancel flow is easy to copy, and the bigger the buyer, the more their own data closed the gap with Vera’s network. Vera’s edge was strongest with smaller companies that couldn’t solely rely on their own data, so going upmarket now aimed at exactly the wrong customers.

Path three died because Vera could never stay billing-agnostic inside a billing company, and the founders wanted to build a company of their own.

Path two had the subtlest risk: a competitor could plant their flag upmarket while Vera was still building depth in midmarket.

Then Maya checked against the evidence. The customers who loved Vera most were already leaning on it for more than the cancel flow, unprompted, and those accounts retained better and expanded faster than the cancel-flow-only ones. When she floated path two to operators she trusted, it was the one that made them lean in. One and three had their appeal, but neither had that pull.

So Maya chose path two. Blending the other paths, a little upmarket, a little platform, a little partnership, might have felt like consensus, but it had no focus.

A gate, not a date

The key move was how she set it up. “Enterprise next year” is a deferral, and deferrals crumble under board pressure. So she switched from a date to a gate.

Vera earns the upmarket push when, in each of three categories, it cuts total churn at least 15% over the customer’s prior baseline and three reference customers vouch it’s integrated at platform depth.

That was the version Daniel could take to the board. Not “we’re bailing on our promise,” but “here’s the gate, and here’s how you’ll know we’re through it.”

The critical assumptions

Then the squad surfaced the critical assumptions path two depended on.

1. The riskiest. An easily replicated cancel flow couldn’t win upmarket. Enterprise would only pay for a platform they’d struggle to build themselves. If a competitor won upmarket with just a flow, then path two was wrong.
2. A close second. Whether Vera’s data could get dense fast enough in each new category as it expanded.
3. A third. That the billing providers would be slow to move into retention, because a billing company, with payments at its core, couldn’t easily build the neutral, cross-company data network deep retention needs. This was the same bias that made getting absorbed by one a dead end for Vera. Their slowness would give Vera time to build depth.

These were the ones she’d track, to notice if reality invalidated them.

Naming it

Finally, Maya named the approach so it would stick. The name surfaced when she was talking the work through with Peter, one of her senior PMs, who said it back to her concisely: “So we win by becoming the thing they can’t build.”

That was the phrase she’d been circling.

Decide the Bets – Chapter 7

What Will We Do, Not Do, and Why?

Working from path two, Maya and the squad brainstormed about ten candidate bets. Some came top-down from the approach, and some came bottom-up from the teams’ discovery work. Where the two met, she paid close attention. She wrote each as an objective, not a solution, as an if/then: if we invest in theme X, then we expect outcome Y.

Then they built the strategy grid, ranking the strongest six bets in rows and assessing each against three questions: how critical it was to beating the challenge, how much it built differentiation and defensibility, and how feasible it was. After a few rounds of debate, four themes landed above the line.

The themes above the line pulled in the same direction: stop being the tool at the exit, and become the retention layer across the whole journey. Maya kept the lifecycle theme deliberately broad. It was the biggest and would likely take more than one team. The intervention engine was the network-trained brain the other three themes would all draw on.

Enlarge

Two themes went below the line. The first was a consumer-subscription expansion. Tempting, but it was exactly the breadth trap they’d already decided to avoid. The data was too thin there to be effective. The second was enterprise-readiness, the SOC2, SSO, governance and compliance work, which was deferred until Vera could push upmarket. Maya put both themes on the grid anyway, to make the tradeoffs explicit.

Then Maya checked the grid as a whole. It was mostly playing offense, and the themes reinforced each other: the lifecycle gave the engine more to learn from, the engine made the interventions sharp, the integrations made them sticky, and activation fed all of it more customers and more data.

Confident the grid made sense, Maya wrote the strategy narrative herself, making sure to name the critical assumptions and the approaches considered but not chosen, so anyone could inspect the thinking.

Aligning before the decision meeting

Maya sought alignment before the decision meeting, because the meeting shouldn’t be a reveal. She took the narrative to each key stakeholder one-on-one and walked them through the hardest calls, especially the cuts.

She mined for disagreement on the tradeoffs. It’s easy to agree to what you’re doing, harder to agree to what you’re not. So she’d ask, “what does this mean we’re not doing?” and didn’t move on until they could name what they were giving up in their own words.

Sofia was the real test. The strategy hit her hardest. She had a live ~$200K enterprise deal and had built her team’s comp plan around the upmarket direction.

She didn’t blow up. She went quiet, which was worse.

So Maya got curious. She asked Sofia what she was seeing that the strategy was missing, and then she listened. Sofia’s objection was real, and it wasn’t that the strategy was wrong. She bought the platform logic. Her worry was the cost of the change: the live deal and pipeline she’d developed this quarter, and the risk that a competitor would grab the enterprise logos while Vera built the platform.

Maya took Sofia’s concerns seriously. She didn’t pretend the cost wasn’t real. They talked through the data, and named what would prove the strategy wrong. Sofia’s concern became something they’d watch together.

After some discussion, Sofia felt understood but still wanted enterprise now. So Maya asked her to disagree and commit. Sofia did, with her reservations out in the open.

A reservation said out loud is one you can work with. A buried one comes back as drift.

Then Maya checked in with Daniel, who wanted the squad and Sofia aligned before he’d sign off. By the time the strategy reached the decision meeting, there were no surprises, including for Daniel. He signed off and they got moving.

That’s what alignment looks like when it’s a throughline, not a one-time ask.

Part 2: Live the strategy

Deploy the Strategy – Chapter 9

Place Your Bets

With the strategy approved, Maya’s focus shifted from crafting it to deploying it. The rest of the org needed to live out the strategy without her, or any of the squad, in the room.

Communicate

First, she communicated the strategy outward, in widening circles. She’d already walked the inner circle through everything. Then she rolled it out to the whole product org, tailoring the message to each audience instead of blasting out a mass email that would land differently for everyone.

She explained what Vera was not doing this cycle and why, so the consumer-expansion and enterprise-now questions wouldn’t get relitigated in two months. And she killed a couple of zombie projects, work limping along from the both-markets-at-once era that no longer connected to the strategy.

The named approach, “become the retention platform they can’t build,” was the phrase that survived every retelling, so the strategy stayed recognizable no matter who passed it on.

Operationalize

Then Maya operationalized the strategy. The four above-the-line themes became team objectives, and adding targets to the outcome metrics from the strategy grid created their key results.

She had five teams and four themes. The lifecycle theme was the broadest, so she split it across two teams. A theme could span teams, but no team carried more than one, which kept everyone focused. As she assigned OKRs to the teams, she explained the known risks of each.

Maya got the systems and reporting structures updated to match, because the system would either reinforce the strategy every week or erode it.

Verify

Last, she met with each team, and her PMs in particular, to verify the strategy landed. She didn’t assume communication had created understanding. Instead, each team taught the strategy back to her in their own words and showed what it meant for their plans.

Most had it right. But the activation team was about to pursue its onboarding metric by stripping setup down to the fastest path, and punting on the deep integrations that wire Vera into a customer’s workflow. They would hit their own number and quietly weaken the thing that made Vera hard to leave.

Maya treated this as a coaching moment for the PM on the team, and was grateful the teach-back caught it before the quarter did.

A strategy a team can teach back without you is one that survives a busy quarter.

Manage the Strategy – Chapter 10

Live Your Bets

The quarter started, and so did the thrashing. An urgent customer request one day, a competitor launch the next, three teams suddenly eyeing work that wasn’t in the strategy.

Maya’s job now was to keep the strategy alive and well in the decisions people made every day. She made three efforts in parallel through the quarter: supporting her team’s decisions, keeping the org on course, and sensing what was changing.

Support decisions

Most of the decision support work was coaching her PMs. When Peter brought her a hard decision in their 1:1, she didn’t make it for him. She coached him through the strategy until the call was clear to him, then supported him in making it.

The strategy gave Peter air cover: he could decline an urgent “sales special” by saying “that’s not aligned with the strategy,” instead of being the bad guy. Saying no is easier when backed by a documented rationale.

Her 1:1s were also where Maya hunted for insights. The moment one surfaced, she thought about who else needed to know. When Marcus’s team learned why midmarket accounts stalled in their second month, she didn’t let it sit in customer success. She pushed it to the activation team, who owned that part of the journey.

An insight that stays with one team is worth a fraction of one that travels.

Stay on course

Staying on course meant constantly beating the drum and protecting focus when it got tested. Maya kept the strategy top of mind, opening team reviews by connecting the work to the strategic theme it drove, and found new ways to tell the story so it didn’t fade. She reinforced the strategy with leadership at every opportunity, because leadership, faced with the fires of the week, is prone to strategy amnesia.

That was the easier part.

The harder part came when a consumer SaaS company showed up in the pipeline with real budget. Vera’s product would have worked for them, more or less. But the strategy squad had classified consumer companies as a bystander segment, and parked consumer expansion below the line on purpose. The data network was still too thin in consumer to be effective, and saying yes meant pulling a team off a bet they were already working on.

Six months ago, they would have taken the deal. Today, Maya pointed at the line they’d drawn and it held.

Drift doesn’t happen as one big betrayal of the strategy. It happens through twenty reasonable little exceptions nobody added up.

Sense what’s changing

Maya also continually scanned for anything that invalidated the assumptions the strategy rested on.

One came through Marcus. An account had mentioned a new save-flow bundled into their billing. Marcus recognized it as a big billing provider, Remit, quietly testing an expansion into retention, exactly what the approach had assumed billing providers would be slow to do. Maya flagged it to dig into next cycle.

The strongest signal, though, came from the person with the most reason to want a bet to fail. Sofia had wanted the upmarket push that got deferred, so now she was watching upmarket companies closely. In a leadership meeting, she flagged it. She’d been watching for the thing they said would prove the strategy wrong: a big SaaS company buying a cancel-flow-only product instead of building its own.

She hadn’t seen it. If anything, the opposite. Competitors who went upmarket with just the flow were getting built around.

The assumption was holding, surfaced by the person who’d have been first to call it if it was wrong.

Three weeks out from quarter’s end, Maya began pulling together what they’d learned: the insights, the signals, and which bets were working or not. It wasn’t a big production, just enough to feed into the next cycle, so she wouldn’t be starting from a blank page when she sat down to choose again.

Evolve the Strategy – Chapter 11

Choose Again

In week ten of the quarter, Maya started on the next cycle. She wasn’t starting cold. A quarter of signal had laid the groundwork, and she already had a sense of how it would go. She’d told the squad a week earlier that the coming cycle would ask a bit more of them.

She reviewed the strategy from the deepest layer up.

The thesis held. Midmarket companies still needed the retention team they couldn’t staff, and the data network still made Vera’s interventions hard to copy.

The challenge hadn’t changed either. Vera hadn’t cleared the upmarket gate yet, hitting the churn-reduction bar in two of three categories but short on platform reference customers.

Usually, that would have made this cycle a standard refresh. The Remit signal Marcus had flagged was what made it more.

The signal that changed things

Remit had bundled the billing-adjacent features it could ship fast, dunning and a basic cancel save flow, and it had better distribution since it was in thousands of companies’ billing stacks. The assumption that billing providers would be slow was starting to slip, and the move suggested Vera’s window to dominate the midmarket might be shrinking.

The other critical assumptions were holding. A cancel flow alone still didn’t seem viable upmarket, and the category data had remained dense as Vera grew.

So this cycle was somewhere between a refresh and a rebuild. Most bets were quickly updated, but Remit had shortened the midmarket timeframe, and that demanded a response.

Vera was already building platform depth. It was how they’d dominate the midmarket and, eventually, earn their way upmarket into a durable business. None of that changed. What changed was the time available to do it. The deep, billing-neutral data network was the one thing Remit couldn’t bundle, so widening that gap, fast, was how Vera could keep Remit’s good-enough bundle from becoming the midmarket default.

Maya put more resources behind the platform bets to accelerate them.

The cycle, not the event

Updating the strategy took a few days, rather than having to cram a quarter’s worth of thinking into a panicked sprint. Maya duplicated last cycle’s strategy doc, flagged what changed, walked the squad and stakeholders through it, and deployed the update for next quarter.

Strategy had become a cycle, not an event.

Back in the spring, Maya had gone looking for the strategy and found a deck sitting on the shelf. Now Vera’s strategy was alive. Not a document, but a practice.

Now it’s your turn

Maya’s path isn’t a template. Your context is different, your crux is different, and the right answer for Vera would be the wrong one for you.

What transfers is the sequence. Distill what’s going on. Frame what must be solved. Define why customers will choose you. Develop how you’ll make it real. Decide what you’ll do and not do. Then deploy it, manage it, and choose again.

This story is the compressed version. The book is where the method lives: every step, the traps, and what to do when it gets hard.