theonline.mba
← Back to ENT 403

ENT 403 · Unit 2 of 6

Positioning, Messaging and Category Design

Startup Go-to-Market and Founder-Led Sales

Start unit · 4 lessons →

Learning objectives

  • Run a repeatable founder-led sales motion
  • Apply "Positioning, Messaging and Category Design" to a real venture decision
  • Contribute to your Founder sales playbook deliverable

Unit overview

#LessonCore idea
1Understanding Positioning, Messaging and Category DesignCore frameworks for this unit
2How Positioning, Messaging and Category Design Works in PracticeCore frameworks for this unit
3Evaluating Trade-offs in Positioning, Messaging and Category DesignCore frameworks for this unit
4Positioning, Messaging and Category Design: Case Analysis and RecommendationsCore frameworks for this unit

Complete all four lessons, then finish unit assessments on this page.

Unit assessment

Complete each section below. Score 80%+ on the quiz to finish this unit's assessment.

50% applied project30% case work20% knowledge checks

Exercises

Apply what you learned in this unit with structured practice.

ExerciseApplied practice: Positioning, Messaging and Category Design45 min
Complete a focused practice exercise on **Positioning, Messaging and Category Design**. 1. Choose a real company, product, or situation you know. 2. Apply one core framework from this unit to analyze it. 3. Write your analysis in 300–500 words with a clear recommendation. 4. Cite at least one credible source.

Deliverable

300–500 word analysis document saved to your portfolio under ENT 403.

Rubric

  • • Framework applied correctly (not just named)
  • • Specific evidence from a real example
  • • Clear recommendation with tradeoffs acknowledged
  • • Professional writing with source citation
ExerciseDrill: Positioning, Messaging and Category Design30 min
Work through the practice problems in the unit lesson without looking at notes. Then check your work against the lesson and write a short reflection: - What you got right - One mistake you caught - One concept to review before the next unit

Deliverable

Problem solutions + 150-word reflection in your ENT 403 workbook.

Rubric

  • • Attempted all practice items before checking answers
  • • Honest reflection on errors
  • • Identifies a specific review action

Case analysis

Analyze a case using frameworks from this unit.

CaseCase analysis: Positioning, Messaging and Category Design60 min
Analyze a real business case through the lens of **Positioning, Messaging and Category Design**. Choose a public company event, HBR-style case, or documented decision. **Deliverable structure:** 1. Situation summary (150 words) 2. Analysis using this unit's frameworks (400 words) 3. Recommendation (150 words) 4. Risks and what would change your mind

Deliverable

2-page case write-up in your portfolio.

Rubric

  • • Case facts are accurate and sourced
  • • Analysis uses unit frameworks explicitly
  • • Recommendation is justified with tradeoffs
  • • Risks are specific, not generic

Knowledge quiz

Check your understanding before marking the unit complete.

1. RelayOps positions against PagerDuty using a "coexist and fix routing" frame rather than rip-and-replace. Why is coexistence often stronger in Series B SaaS?

2. In RelayOps's positioning canvas, "for Series B SaaS teams drowning in misrouted pages" is which component?

3. RelayOps tests beachhead landing copy at 4.2% conversion vs 1.1% generic "incident management." What does this demonstrate?

4. RelayOps compares positioning strategies where coexistence emphasis yields higher win rate at similar ACV. Which trade-off is most likely when choosing "incident command layer" category design vs "PagerDuty killer"?

5. A RelayOps AE uses the message map: headline (MTTA), proof (pilot KPI), objection (PagerDuty coexistence). A prospect asks "why not just fix PagerDuty rules?" Best response type:

6. RelayOps outbound projects 7,143 targets × 4.4% reply × 14% meeting rate ≈ 44 opps, then 23% win ≈ 10 logos. Which error would inflate this forecast?

7. Which is a common positioning mistake in early B2B SaaS?

8. RelayOps case analysis requires every sales deck slide to map to: segment, struggling moment, wedge, proof, or objection handler. An investor asks if positioning is "real." Best evidence:

Next unit: Founder-Led Sales and Pipeline Creation →