Five Forces

Why workflow SaaS is not 'just growing'

Investor decks cite a $28B workflow automation TAM. Leo reminds Anita: TAM does not equal profit pool. Porter's five forces explain how industry structure shapes average returns—before Veridian's idiosyncratic advantages enter.

For Veridian, buyer power from consolidated mid-market procurement, rivalry from platform bundling, and substitution from native ERP workflows all press margins. Five forces turn buzzwords into testable structural claims.

This lesson builds a five-forces analysis for B2B workflow SaaS with Veridian-specific evidence and strategic implications—not generic lecture diagrams.

Veridian Cloud is a B2B workflow automation SaaS platform for mid-market and enterprise operations teams and the anchor company for STR 301. As of the latest reporting period, Veridian reports $95M ARR (annual recurring revenue, subscription revenue normalized to a year), 1.12 net revenue retention (NRR, revenue from existing customers including expansion minus churn), and 2,800 customers with average contract value near $34k. CEO Anita Desai, VP Strategy Leo Hartmann, and CFO Priya Nair lead industry analysis, moat assessment, and corporate scope decisions across Workflow Studio (core orchestration), Integration Hub (1,400+ certified connectors), and AI Assist (document routing and approval prediction).

You will apply Porter's industry frameworks, the resource-based view (RBV), business-level positioning, and corporate strategy tools to Veridian's real strategic tensions—not abstract case studies.

Framework overview

Five forces: (1) rivalry among existing competitors, (2) threat of new entrants, (3) threat of substitutes, (4) supplier power, (5) buyer power. Industry attractiveness rises when forces are weak; pressure rises when strong.

Rivalry in workflow automation

Rivalry is high: ServiceNow, Salesforce, Microsoft Power Automate, Zapier, Monday, and dozens of vertical SaaS tools compete for automation budgets. Differentiation is partial; switching costs moderate once integrations are live. Price competition appears in enterprise renewals—Veridian's discount depth trend is a rivalry symptom.

Growth attracts entry, increasing rivalry unless consolidation raises barriers.

Threat of entry

Cloud delivery lowered classic entry barriers, but enterprise trust barriers remain: security audits, connector reliability, compliance certifications. A startup can ship a demo; earning Fortune 500 RFP trust takes years—moderate entry threat in enterprise, higher in SMB PLG segments.

Substitutes and complements

Substitutes: manual scripts, offshore BPO, native ERP workflows, spreadsheets with macros. Complements: cloud ERP, ticketing, identity providers—Veridian's Integration Hub strategy aligns with complements to raise switching costs.

Buyer and supplier power

Buyer power rising as IT procurement standardizes three-bid processes and measures utilization. Supplier power moderate: hyperscaler hosting is commoditized, but scarce AI inference talent and premium data-labeling vendors can extract rent.

Overall: structurally competitive industry—firm advantages must earn returns, not industry tailwinds alone.

Leo facilitates executive session before 2027 plan.

Part A: Force ratings

Use table above; debate buyer power High vs Medium—Anita sides High given top-20 customer concentration at 22% ARR.

Part B: Profit pool map

Enterprise ITSM captures high ACV but high S&M; mid-market ops favors faster cycles if implementation cost controlled—fits Veridian wedge.

Part C: Strategic implication

Do not compete on pure price vs ServiceNow; invest switching costs via certified integrations and expansion modules.

Part D: Managerial read

Five forces do not pick winners—they set guardrails. Veridian must earn firm-level advantage in a high-rivalry industry.

Airlines face brutal five forces—commodity seats, powerful buyers, high rivalry. Workflow SaaS is competitive but offers stronger differentiation and switching costs than airlines. Veridian should not excuse poor execution as "industry structure" alone—yet must respect buyer power realities.

Microsoft bundles Power Automate into M365 E5 bundles at marginal incremental price.

(1) Which force shifts? (2) How does it affect Veridian win themes? (3) One response that is not price matching.

Solution

Raises rivalry and buyer substitute leverage (good-enough bundled automation).

Win themes must stress cross-ERP orchestration and compliance connectors Power Automate lacks.

Response: Publish migration-resistant integration architecture references; deepen healthcare certifications.

Key takeaways

• Five forces assess industry attractiveness before firm advantages.
• Workflow SaaS faces high rivalry and rising buyer power.
• Entry barriers are trust and integration depth, not code alone.
• Complements strategy can raise switching costs.
• Veridian needs positioning discipline in a tough structure.

1. Draft a five-forces table for an industry you know with evidence column.
2. Link each force to one Veridian metric.
3. Continue to Strategic Groups to map rival clusters.

Applying Five Forces at Veridian Cloud scale

When Veridian Cloud evaluates five forces, Leo Hartmann's strategy team starts from operating facts: $95M ARR, 1.12 NRR, 2,800 customers, and 8% annual logo churn. CEO Anita Desai, VP Strategy Leo Hartmann, and CFO Priya Nair align industry structure, five forces, and competitor analysis with quarterly business reviews and board prep. A framework that stays abstract fails Anita Desai's test: can we explain why Veridian wins deals against ServiceNow and Salesforce Flow, and what we will not do?

Consider how a 2-point improvement in win rate affects Veridian. At 34% baseline and roughly 400 qualified enterprise opportunities per year, a move to 36% yields eight additional wins. With $34k ACV and 78% gross margin, eight wins add roughly $0M in gross profit over initial contract terms before expansion. That is why five forces is not classroom vocabulary for Veridian; it is how the company avoids funding initiatives that sound strategic but do not change competitive outcomes.

The industry structure, five forces, and competitor analysis workflow at Veridian separates industry attractiveness claims from firm-specific advantage claims. Industry analysis answers whether workflow automation SaaS is structurally attractive. RBV and VRIO answer whether Veridian's connector library and CS playbooks are scarce and hard to imitate. Business-level strategy answers whether Veridian competes on cost, differentiation, or focus—and which trade-offs Anita will enforce. Corporate strategy answers build versus buy, vertical scope, and M&A. Label each slide in Leo's deck with the question it answers before numbers appear.

Extended Veridian scenario: cross-functional read

Imagine Veridian's Q3 strategy review for five forces. Sales asks whether to match a competitor's 20% list-price cut on Enterprise. Product asks whether AI Assist should ship as platform-wide or healthcare-only. Finance asks whether a tuck-in acquisition accelerates connector coverage faster than internal build. A weak industry structure, five forces, and competitor analysis answer addresses only one function. A strong answer chains frameworks: five-forces pressure on buyer power informs pricing response; VRIO on integration IP informs build versus buy; corporate scope rules inform M&A screening.

Work the arithmetic on a conservative example. Suppose Veridian's NRR falls from 1.12 to 1.06 because competitive discounting pulls expansion modules forward without adding seats. On a $95M ARR base, that 6-point NRR gap versus plan implies roughly $6M less expansion revenue over the next year if cohort behavior persists. Pair the point estimate with strategic logic: is the NRR miss industry-wide price pressure (industry effect) or a positioning mistake (firm effect)? Five Forces gives vocabulary to separate those explanations before Anita approves a hiring plan.

Stakeholder conflict is normal. Sales wants flexibility; product wants focus; finance wants payback discipline. Five Forces gives you language to negotiate with explicit trade-offs rather than slogans. If evidence is industry-level only, the decision may be ride the cycle or exit a segment—not copy a competitor's feature list. If evidence is firm-level capability gap, the decision is invest, partner, or acquire with a timeline.

Technical mechanics and checks (strategy patterns)

For five forces, Veridian analysts show reconciliations the way finance shows bridge charts. A five-forces table lists force, rating (low/medium/high), evidence, and implication for margin or growth. A VRIO row names a resource, scores V-R-I-O, and states competitive implication (parity, temporary advantage, sustained advantage). A strategic group map plots price versus breadth with Veridian, ServiceNow, Zapier, and Monday positioned explicitly. A value curve compares factors (implementation speed, connector depth, compliance, AI, TCO) with relative scores.

Use plain-language hypotheses before matrices. Example: "Buyer power rises if IT procurement mandates three-bid RFPs on renewals above $250k." Test with win-loss data and discount depth by deal size. Example: "Integration Hub is inimitable if certification requires 18-month partner co-development." Test with engineer interviews and competitor connector counts. Strategy frameworks are hypotheses until evidence fills cells.

For spreadsheet replication, write the unit of analysis first. Industry analysis uses market-year panels. Firm analysis uses Veridian fiscal year or customer cohort. Competitor analysis uses named rivals and product modules. Corporate M&A uses target-level revenue and synergy categories. Leo's team rejects slides that mix units without labeling.

Common executive questions (and disciplined answers)

Executives ask short questions that require long disciplined answers. "Are we differentiated?" maps to VRIO and value curves, not adjectives. "Should we buy them?" maps to scope, synergies, integration risk, and alternate build/partner paths. "Is the market attractive?" maps to five forces and life-cycle stage, not TAM headlines. "Why did we lose?" maps to competitor analysis and response anticipation, not anecdote from one rep.

Veridian's credible answer format for five forces is three bullets: strategic recommendation, framework evidence label (industry vs firm vs corporate), and explicit trade-off rejected. A fourth bullet states what would falsify the recommendation within two quarters. That discipline prevents strategy decks from becoming either vision poetry or spreadsheet dumps.

Practice the loop until it is habit. Diagnose performance → classify industry versus firm effects → analyze structure and rivals → audit resources → choose business-level position → decide corporate scope → plan execution and response. When the loop is complete, Veridian funds what survives skepticism.

Practice extension: self-check without peeking

Before re-reading solutions, open a blank document and complete four rows. Row one: write Veridian's strategic decision that five forces informs. Row two: name the framework primary cells you must fill (forces, VRIO rows, scope options). Row three: list one industry effect and one firm effect that could explain the same KPI miss. Row four: state the trade-off Anita should enforce if the analysis is correct. Compare your rows to the worked example. Gaps indicate what to re-read.

If you study outside B2B SaaS, substitute your company but keep numeric discipline. A manufacturer might replace NRR with share of wallet; a retailer might replace connectors with store footprint. The structural habits from STR 301 remain: separate industry from firm, name trade-offs, tie recommendations to evidence, and document what you will not do.

Connection to OMBA 102 and FIN 201

OMBA 102 (business foundations) and FIN 201 (corporate finance) unit economics gave you unit economics and capital discipline. STR 301 adds competitive logic: why some industries earn better returns, why some firms beat rivals in the same industry, and how corporate scope changes risk and return. Treat the stack as one narrative: FIN 201 asks whether a project clears hurdle rate; STR 301 asks whether the project strengthens position or merely spends cash; OMBA 102 asks how confident you should be in the forecast behind both.

When you present to Veridian's board, integrate the stack. Example: FIN 201 models a tuck-in acquisition IRR; STR 301 scores target fit on five forces post-merger and VRIO on connector IP; OMBA 102 stress-tests synergy timing. Capstone memos in Unit 6 require that integrated arc.

Deep dive: metrics Veridian reuses every quarter

ARR sums contracted recurring revenue normalized to a year. NRR divides expansion plus retained revenue by prior-year cohort revenue; values above 1.0 mean expansion outweighs churn. GRR (gross revenue retention) measures retained revenue before expansion—Veridian targets 92%. ACV averages first-year contract value per new logo. Win rate counts competitive wins divided by qualified opportunities with documented outcomes. Sales cycle measures days from qualified opportunity to signature. Logo churn counts lost customers divided by starting customers for the year.

These definitions appear boring until someone changes them silently. A definitional shift in NRR can fake a turnaround. Five Forces training includes insisting on definition footers in every strategy exhibit. When Veridian compares industry benchmarks to internal dashboards, shared definitions are the chain between Porter and proof.

For industry structure, five forces, and competitor analysis, document evidence sources and refresh cadence. CRM win-loss updates weekly; product usage for expansion scoring updates nightly; competitor intelligence from field teams batches monthly; board strategy metrics freeze quarterly. A framework exhibit without data timestamp and owner is opinion.

Walk through a reconciliation each quarter. Starting ARR plus new ARR minus churned ARR should approximate ending ARR within known timing differences. Win-rate denominators should match CRM stage definitions. Five-forces ratings should cite dated evidence, not last year's board deck recycled.

Managerial judgment prompts for Five Forces

1. If evidence supports industry headwinds only, what scope or positioning change should Veridian consider?
2. If sales requests a price match and product requests roadmap acceleration, what trade-off does five forces force?
3. Which stakeholder loses most if Veridian pursues a false differentiation story?
4. What would a smart skeptic ask about survivorship bias in competitor benchmarks?
5. What single metric movement would convince you the current strategy is wrong?

Write ninety-word answers as a memo appendix. Use Veridian numbers wherever possible. This exercise converts lesson prose into decision reflexes under time pressure.

Additional study path: compare this lesson's worked example to the practice problem. Identify one assumption that changed and explain how that change alters Anita's decision. Then preview Unit 6's board memo structure: decision ask, framework evidence, trade-offs, execution risks, and falsification triggers. Courses compound when you reuse the same company, rivals, and metrics across units.

For industry structure, five forces, and competitor analysis, also stress-test recommendations with explicit counterfactuals. If Veridian had matched ServiceNow discounting last year, modeled NRR might sit near 1.04 with services margin compressed 3 points—Leo uses such counterfactuals to show why five forces analysis is not academic. Counterfactuals must use Veridian definitions for ARR, NRR, and discount depth; otherwise debate becomes rhetorical.

Board members will ask "what breaks first?" under stress. Five Forces answers should name the first failing link in the activity system—often certification backlog before sales pipeline, or expansion attach before new-logo CAC. Naming the weak link focuses capital on the true bottleneck rather than the loudest department in the room.

When teaching five forces to cross-functional teams, assign each function one framework column to own in perpetuity: Sales owns win-loss and response anticipation; Product owns value curve and business model experiments; Finance owns profit formula and M&A guardrails; CS owns expansion attach and SLA metrics; Strategy owns five-forces refresh and VRIO audits. Shared ownership without column owners produces slides everyone applauds and nobody maintains.

Finally, compare five forces conclusions to Veridian's written trade-offs in Lesson 1. If this lesson's recommendation requires violating a named not-doing item, escalate to Anita before execution. Strategy coherence is the difference between a portfolio of smart projects and a company that wins its chosen game.