Profile 1: The business relationship manager
In the previous article, we followed a Business Relationship Manager through a single Tuesday. By Friday she had produced one prioritized backlog, two stakeholder briefings, three escalation memos, a renegotiated SLA, and a verbal commitment that quietly reshaped Q3 priorities for forty engineers.
Decomposed through T–R–M, that single week operated simultaneously across M0, M1, M2, M3, and M4. Applying the three-parameter cost model to each layer reveals a profile that is almost the inverse of what most organizations assume when they deploy AI for this role.
| Activity | M Mode | Tokens / session | Sessions / month | Users (org) | Monthly cost index |
| Consolidating intake tickets | M0 | 3,000 – 8,000 | ~200 | 500+ | 🔴 Very high |
| Drafting status briefings | M1 | 10,000 – 25,000 | 40 | 200 | 🟠 High |
| Translating needs → requirements | M2 | 25,000 – 50,000 | 20 | 50 | 🟡 Medium |
| Alignment in steering meetings | M3 | 50,000 – 100,000 | 8 | 10 | 🟡 Medium |
| SLA renegotiation post-incident | M4 | Minimal | 2 | 5 | 🟢 Low |
| Hallway verbal commitments | M4 | Zero | — | 1 | 🟢 Negligible |
Table 2. Token economics model for the Business Relationship Manager profile. ‘Monthly cost index’ is qualitative — relative budget exposure across activity layers.