Quiz: Market Strategy and Startup Approaches¶
Test your understanding of the three startup strategies, beachhead workflow selection signals, domain-specific workflow systems, go-to-market motions, and the competitive moats that make context-graph businesses defensible.
1. Which set names the three startup strategies the chapter analyzes?¶
- Open source, freemium, enterprise tier
- Direct sales, channel partner, online self-serve
- Full System Replacement, Module Replacement, and New System Creation
- Vertical SaaS, horizontal SaaS, platform play
Show Answer
The correct answer is C. The chapter names exactly these three strategies and contrasts their risk/reward profiles. The other options describe unrelated business-model dimensions.
Concept Tested: Startup Competitive Analysis
2. According to the chapter, in what narrow condition does Full System Replacement make strategic sense?¶
- When the incumbent's core architecture makes it impossible for them to add the missing capability without a complete rewrite (e.g., no temporal model in the schema, no event-oriented APIs) — making a purpose-built replacement structurally rather than just feature-wise superior
- When the incumbent has weak marketing
- When the customer has no IT department
- When the startup has more salespeople than the incumbent
Show Answer
The correct answer is A. The chapter is explicit that structural impossibility (not marketing, staffing, or feature gaps) is the criterion. The other options misstate the rationale.
Concept Tested: Full System Replacement Strategy
3. Module Replacement creates a window rather than a moat unless the startup does what?¶
- Patents the module's user interface
- Uses the deployment window to accumulate enough proprietary decision traces that the resulting model cannot be replicated even if the incumbent ships a competing feature — i.e., the context graph's accumulation dynamic becomes the actual moat
- Stops shipping any improvements
- Lowers the price below cost
Show Answer
The correct answer is B. The chapter explicitly says module replacement is defensible only if the startup uses the window to accumulate irreplaceable proprietary context. The other options misstate the defense.
Concept Tested: Module Replacement Strategy
4. Which combination best describes an exception-heavy workflow — the first signal of a strong beachhead?¶
- A workflow whose standard process covers most cases and where exceptions are rare
- A workflow where the standard process covers only a minority of cases; most actual work involves exception handling, edge cases, or deviations — often accompanied by an informal shared knowledge base capturing "how we handle the weird cases"
- A workflow that runs without human input
- A workflow performed entirely by a single person
Show Answer
The correct answer is B. The chapter defines exception-heavy precisely this way, including the informal-KB tell. The other options describe non-exception-heavy patterns.
Concept Tested: Exception-Heavy Workflow
5. A startup is evaluating four candidate workflows for a beachhead. Workflow A scores 3 on exception-heavy, 3 on high-headcount, 3 on glue-function. Workflow B scores 1/1/1. Workflow C scores 2/2/2. Workflow D scores 3/1/1. According to the chapter's checklist, which is the strongest candidate and what does the chapter say about workflows that cannot score above 5?¶
- Workflow A (score 9) is the strongest. Candidates that cannot score above 5 may indicate the market is not ready for context graph technology in that functional area, or the wrong area is being examined
- Workflow B (score 3) is the strongest because it is smallest
- Workflow D (score 5) is the strongest because exception-heavy alone is enough
- All four are equally strong because every workflow benefits equally
Show Answer
The correct answer is A. The chapter's beachhead checklist scores each dimension 1-3 and explicitly recommends totals above 5; sub-5 totals indicate looking elsewhere. The other options misuse the scoring rule.
Concept Tested: High-Headcount
6. The chapter highlights "glue function" workers as particularly valuable beachhead targets. Which combination best captures why?¶
- They are the cheapest employees to replace
- They already know what context is needed (tacit knowledge from manual integration work) and tend to become enthusiastic champions when the work that exhausts them is systematized — but caution: they may also resist systematization if it threatens organizational power derived from being the only one who knows how
- They have the largest budgets
- They have the smallest data sets
Show Answer
The correct answer is B. The chapter captures both the upside (tacit knowledge + champion potential) and the political caution. The other options misstate the rationale.
Concept Tested: Glue Function
7. A finance team is evaluating context-graph beachheads. Which workflow does the chapter highlight as a strong fit because it combines exception-heavy work, high compliance requirements, and cross-system synthesis?¶
- Printing monthly reports
- Updating the office cafeteria menu
- Migrating to a new color palette in dashboards
- The revenue exception workflow — quarterly and month-end close generate large volumes of revenue-recognition exceptions, each requiring research, policy lookup, and precedent check
Show Answer
The correct answer is D. The chapter cites the revenue exception workflow as exactly this kind of fit. The other options are not the workflows the chapter highlights.
Concept Tested: Finance Workflow AI System
8. Among the three context graph go-to-market motions, which would be most defensible for a startup targeting mid-market insurance claims processing?¶
- A proof-first sales motion (60-90 day POC on a single beachhead claims workflow with written success criteria and a sponsor with budget authority), followed by champion-driven expansion to adjacent claims workflows, supported by integration partnerships with the iPaaS platforms common in insurance — combined to accumulate decision traces faster than any competing startup can replicate
- Cold outbound only, with no proof of concept
- Open-source release with no paid tier
- Wait for the incumbent to acquire the startup
Show Answer
The correct answer is A. The chapter's go-to-market analysis prescribes exactly this combination of proof-first POC, champion-driven expansion, and integration partnerships. The other options ignore the chapter's structural recommendations.
Concept Tested: Go-To-Market Strategy
9. The chapter argues that a context graph startup's primary defense against incumbent system vendors who eventually ship competing AI features is what?¶
- Speed of data accumulation and depth of customer integration — once 18 months of decision traces have accumulated, the incumbent's competing feature has to convince the customer to start over from scratch, which is a very hard sell
- Filing patents on the graph schema
- Lower pricing than the incumbent
- Heavier marketing spend than the incumbent
Show Answer
The correct answer is A. The chapter is explicit that proprietary decision-trace accumulation is the durable defense against incumbents. The other options describe defenses the chapter does not recommend.
Concept Tested: Competitive Moat
10. Which set of characteristics does the chapter use to define the "Context Graph Startup" archetype?¶
- Cheap, fast, flexible, scalable, profitable
- Lean, agile, growth-hacking, viral, monetized
- Decision-first data modeling, write-path obsession, accumulation as strategy, compliance as a feature (not a cost), and domain depth as a moat
- Mobile-first, AI-first, cloud-first, security-first, design-first
Show Answer
The correct answer is C. The chapter names exactly these five archetype characteristics and explains how they reinforce each other. The other options are generic startup buzzword sets.
Concept Tested: Context Graph Startup