Strategic Thinking Frameworks for Business Leaders

Most strategic frameworks sit on a shelf. They're textbook exercises—good for MBA classes, corporate retreats, and consultants' pitch decks. But at £1m–£20m revenue, you don't have time for theatre. You need frameworks that shape decisions when you're deciding between three markets to attack, which product to kill, or whether your hire is worth the cash burn.

We've spoken to hundreds of Helm members about which frameworks actually move the needle. Not the ones that sound smart in a board meeting. The ones that change how you think.

Strategic thinking at scale isn't learning ten frameworks. It's learning which one to use when—and ruthlessly applying it to kill the noise in your head.

At £1m ARR, your job is clear: build a product customers want, acquire them efficiently, and keep them happy. You're tactical. You make decisions daily. You adjust weekly.

Frameworks at this stage are obstacles. They slow you down. Your competitive advantage is speed and adaptability. You move faster than bigger companies. You don't overthink. You learn from the market.

At £5m–£10m, the market stops forgiving speed alone. Competitors enter. Unit economics tighten. Your team goes from 10 people to 50. You can no longer know every customer. You can't attend every meeting.

This is where strategic thinking becomes non-negotiable. You need frameworks to:

• Align 50 people who now have different incentives
• Decide which 20% of effort produces 80% of results
• Say no to revenue that doesn't fit your strategy
• Build defensible advantages that competitors can't copy in 6 months
• Think 18 months ahead when execution is still 6 months behind

The frameworks we've seen work at scale aren't sexy. They don't sound impressive. But they reduce decision-making from painful committee exercises to 90 minutes of clarity.

SWOT is a starting point, not a strategy. The mistake is treating it as a box-ticking exercise—one afternoon, fill in four quadrants, and you've "done strategy."

The real power of SWOT is in the *connections*. A strength is only valuable if it addresses a real market opportunity. A weakness doesn't matter unless a competitor can exploit it.

Strengths worth owning: What do your customers buy you for—and what would it take a competitor six months to replicate? Not your team. Not your product. Your team + product + market position. If you have proprietary data, a defensible platform, or a network effect, write it down. If you're just "better at X," that's not a strength. That's current execution.

Weaknesses to address: Not "we're a small team" or "we don't have funding." Those are resources, not weaknesses. Real weaknesses are structural: geographic concentration, single-product dependency, customer concentration (if your top 3 customers are 60% of revenue, that's a weakness). Write down the ones that could hurt you if a strong competitor moved against you.

Opportunities are where you see white space. Not "there's a big market." That's not a white space. White space is: "This segment needs solution X, they'll pay premium prices, and incumbent competitors can't address it because their business model depends on the opposite customer." That's an opportunity.

Threats aren't new competitors. New competitors are constant. Threats are things that could destroy your unit economics: regulatory change, customer consolidation, new technology that inverts your pricing model.

SWOT is useful as a quarterly health check. Use it to ask: Are we still stronger in the areas where it matters? Are the threats we identified actually emerging? Have new weaknesses appeared?

Porter's Five Forces examines five pressures that determine industry profitability:

• Rivalry among competitors — How intense is competitive pressure?
• Threat of new entrants — How easy is it for someone to start competing with you?
• Bargaining power of suppliers — How much leverage do your suppliers have over costs?
• Bargaining power of customers — Can your customers easily switch to alternatives?
• Threat of substitutes — Can customers solve the same problem in a different way?

The framework was designed for mature industries. For a scale-up, it's most useful not for analyzing your current state, but for understanding the direction of pressure.

Rivalry pressure is increasing if: growth is slowing, margins are compressing, and features are commoditising. Increasing competition at your scale is a sign you've found a real market—and it's becoming crowded.

New entrant threat is rising if: barriers to entry are dropping, capital is cheaper, and tooling is democratising. An API-first product that cost £10m to build five years ago might cost £1m today. That matters for your strategy.

Customer switching power is high if: you're a point solution (easy to replace), there are five viable alternatives, and switching costs are low. This is the most dangerous position for profitability.

Supplier power is rising if: your core costs are tied to a single vendor, a platform (Apple, Google, AWS) owns your distribution, or talent is scarce in your function. Many SaaS companies are realising that AI model vendors (OpenAI, Anthropic) now hold leverage.

The power of Porter for scale-ups is recognising where you're vulnerable and strategically building defensibility:

Each of these reduces the power customers have and increases the barrier to entry for competitors.

J

obs To Be Done (JTBD) is built on a deceptively simple insight: customers don't want your product. They want the outcome your product enables.

A customer buying project management software isn't buying "collaboration tools." They're buying: "I need my distributed team to ship features without duplicating work or missing deadlines, and I need to report progress to executives without manual status calls."

That's the job. The software is just the vehicle.

Why does this matter for strategy?

Because it forces you to define what success actually looks like for your customer, which reveals:

• Who your real competitors are. You might think you compete with Asana. You actually compete against: Slack, email, Notion, Google Docs, or a spreadsheet. Any tool that helps customers accomplish the job.
• Which customer segments are underserved. The job is the same (coordinate work), but different segments accomplish it differently. Enterprise buys Jira. Startups use Notion. Designers use Figma. Same job, different tool.
• What maturity looks like. A startup's job is: "coordinate quickly without overhead." An enterprise's job is: "coordinate with auditability and governance." Same tool, two different jobs.
• Why customers churn. They don't leave because of features. They leave because your tool no longer does the job as well as an alternative. Or the job itself changed, and you didn't.

JTBD is exceptionally useful at the £5m–£15m stage, when you're deciding whether to expand into adjacent segments or double down on your core. Ask each segment: "What job are they hiring us for?" If it's the same job, you're expanding the market. If it's a different job, you're entering a new market with different competition and different pricing.

Most products fail at adjacency expansion because the founder assumes the job is the same. It's not. Email was built to solve asynchronous communication. Slack solved real-time coordination. Same function, different job, different market.

OKR stands for Objectives and Key Results. An Objective is what you're trying to accomplish. Key Results are how you'll know you did.

Example: Objective: "Become the fastest way for European mid-market to deploy infrastructure." Key Results: (1) Reduce time-to-deploy from 6 weeks to 2 weeks for top 50 customers. (2) Achieve 90%+ retention in this cohort. (3) Hit £1m ARR from this segment.

Why is this better than "grow revenue 50% this year"?

Because it tells you *what* growth you're pursuing and *how* you'll know it's working. It forces alignment. If you want to reduce deployment time from 6 weeks to 2 weeks, everyone needs to know that—not "grow revenue."

The common mistake with OKRs is treating them as detailed task lists. They're not. If your OKR is to "complete 10 projects," that's not an OKR. That's a roadmap. An OKR is the outcome you're betting on.

Bad OKR: Launch customer dashboard, integrate with Salesforce, hire 2 engineers, reduce page load time.

Good OKR: Become the only solution that seamlessly syncs with Salesforce pipeline. Key Results: (1) 70% of customers connect Salesforce account within 30 days. (2) NPS for Salesforce-connected segment rises to 65+. (3) Win 3 customers where Salesforce was the buying trigger.

The second version makes the *why* clear. You're not just launching features. You're building a specific competitive advantage.

At the Helm Forums, we've seen OKRs work best when:

OKRs are most valuable when they're used to say no. They force trade-offs. If your Q2 OKR is "reduce churn to 2%," then you're not launching that new product feature. You're allocating engineering to retention.

Wardley Mapping was developed by Simon Wardley. The core insight: everything evolves from custom-built to commoditised. Understanding where you are in that evolution determines your strategy.

A Wardley Map has two axes: Horizontal (visibility: how well customers understand the value) and Vertical (maturity: how far along the evolution from innovation to commodity).

Innovation stage: Uncertain, new, unpredictable. Your cloud provider is here. Your bleeding-edge ML model is here. Customers don't yet understand what it is.

Transitional stage: Getting clearer. Still some differentiation. Customers understand the value. This is where most scale-up products live.

Commodity stage: Fully understood, standardised, multiple vendors. Email hosting is here. Credit card processing is here. If you're competing in this stage, you're competing on price and reliability.

The strategic insight: never compete on commodity. You'll always lose. Your strategy is to identify which part of your value chain will commoditise next, and make sure you're upstream of it.

Example: If you're a security platform, APIs will commoditise. Cloud infrastructure will commoditise. But threat intelligence—the *interpretation* of what threats mean—is moving from innovation to transitional. Build there, not in cloud.

For scale-ups, Wardley is most useful when:

• You're deciding where to invest R&D. Invest upstream of commoditisation, not downstream. If your differentiator is commoditising, you need a new one in 18 months.
• You're choosing between partnerships and acquisitions. If you need a commodity piece of your stack, acquire or integrate. If you need strategic capability, build or partner closely.
• You're predicting competitive movement. When competitors move into commodity stages, they're abandoning that territory. That's where margins collapse.
• You're thinking about platform strategy. If you have leverage over a commoditising component, you can build a platform. AWS didn't invent cloud. They built the platform that made it commodity.

Blue Ocean Strategy says that most companies compete in existing markets (red oceans) where profit margins shrink and growth stalls. The alternative is to create new markets (blue oceans) where competition is irrelevant.

The distinction matters hugely at scale. At £1m, you're often entering an existing market and competing on speed and product. At £10m+, if you're still just competing on the same variables as everyone else, you're fighting a war of attrition.

Blue Ocean isn't about being unique. It's about redefining the game entirely.

Example—Project Management: When Asana launched, the market was already crowded (Basecamp, Monday, Jira). Asana's blue ocean move was: stop thinking about tools. Start thinking about "work orchestration." They repositioned their entire product around "structure work so teams run on the same rhythm." Different game. Different value. Different customers.

The shift worked because they redefined which variables mattered.

Red Ocean variables: Features, ease of use, integrations, price.

Blue Ocean variables: Work visibility, team alignment, context preservation.

For scale-ups, Blue Ocean is most relevant when you're hitting the growth ceiling in your current market. You have three options:

Blue Ocean is risky. It requires abandoning your current playbook. You'll move slower for a period. Customers will be confused. But if you succeed, you compete with no one.

The mistake founders make: confusing "we're different" with "we're a blue ocean." Difference is not enough. You need to redefine what success looks like for the entire category. That's rare.

Every framework in this article is most valuable when tested against peers. Not consultants. Not board members. Peers—other founders at your stage who've made the same decisions.

At Helm Forums, we've noticed strategic thinking improves fastest when:

• You're forced to articulate your strategy simply. In your head, it's complex. Say it to another founder and you'll spot the holes. "We're going after SMBs in healthcare because they value compliance" sounds fine until someone asks "but who actually *buys* on compliance grounds?" Then you realise the job isn't compliance. It's auditability.
• You hear how other founders solved similar decisions. You don't need a case study. You need to hear directly from a founder who faced your exact trade-off—market expansion vs. deep penetration, product-led vs. sales-led, build vs. buy—and what they learned.
• You stress-test your assumptions. Frameworks make assumptions explicit. A peer will challenge them. "You're using Porter's Five Forces? Which forces are you actually worried about? Can you name them?" That forces rigour.
• You see the same pattern repeated. One founder's story is interesting. Five founders telling the same story teaches you something. When multiple founders at your stage say "JTBD was the turning point," you pay attention.

The founder community doesn't replace frameworks. It makes them real.

Strategic thinking becomes a habit when you embed it into your cycle. Here's what works:

Most founders get frameworks wrong because they treat strategy as separate from execution. It's not. Your frameworks should directly inform your next quarter's roadmap and hiring plan. If they don't, you're not using them right.