Track 10 · Discovery & handoverLesson 06 of 12
Knowing the competing platforms
You're compared with three vendors and an internal team; know their ground.
- Lesson library · reference
- 40 min read
- 60 min hands-on
- Halden Freight
- Pro
What you'll be able to do
01- Map the alternatives an enterprise account is weighing (hyperscaler agent platforms, SaaS-native agents, agent platforms, open-source frameworks, the SI's accelerator and the internal team) and explain what each category is structurally good at.
- Compare platforms on requirement-weighted dimensions (integration surface, identity, data residency, evaluation and observability, pricing model, lock-in and exit, openness via MCP and A2A) using graded, dated evidence rather than feature lists.
- Implement a platform-fit scorecard that flags stale evidence, separates verified facts from vendor claims and tells you when a ranking is not yet a decision.
- Decide when to recommend the customer's incumbent platform, and design a coexistence pattern when the answer is "both".
- Defend a positioning in front of an SI account lead, a CISO or an internal engineering team without disparaging anyone.
Before you start
- Choosing a model you can defend: the same evidence discipline, applied to models rather than platforms.
- MCP: connecting agents to the customer's systems and Agents talking to other vendors' agents: the two protocols that decide how open a platform really is.
- Data residency and sovereignty: residency is usually the first hard filter.
- Picking the wedge use case: you compare platforms against a qualified use case, not in the abstract.
The short version
On almost every enterprise engagement you are one of several options. The customer's cloud provider has an agent service. Their CRM, ITSM and ERP vendors each ship agents inside their products. An SI partner has an accelerator. An internal team is sure it can build the thing on an open-source framework. Ecosystem literacy means you can describe each option accurately, compare them against the customer's weighted requirements with dated evidence, say plainly where an alternative is the better fit, and design for coexistence when several will run side by side. You never state a competitor feature you have not verified, and you never run the comparison on memory.
- Compare against the customer's requirements and weights, not against your platform's feature list.
- Grade and date every piece of evidence. A vendor claim is not a documented fact, and a documented fact from five months ago may no longer be true.
- Recommending the incumbent when it fits is the move that earns you the second use case.
- Most real estates end up multi-platform. Design the seams (identity, MCP tools, A2A calls, shared traces) on purpose.
- Talk about competitors the way you would want them to talk about you: factual, sourced, specific about fit.
Pro lesson
The rest of this lesson is in Pro.
The mental model, worked example, field note, failure table, exercise and self-check, with the voice tutor.
- Every stage and specialisation, in full
- Every lab and every role project
- Halden weeks 2–10, on your record
- Every drill, live in the playground
- All solutions, plus the server judge
- Lab Assistant and every Teach with AI