Appendix E. End-to-End Cases
Use these cases as learning templates. They help you see how the same method changes for different roles.
E1. Backend Engineer for B2B SaaS
Element Example
Business problem Strengthen the team responsible for payment or transactional circuit reliability
Mandatory work Designing backend services, working with load, incidents, observability and data quality
Observable signs Mentions of distributed systems, reliability, observability, high-load, transaction processing, PostgreSQL, Kafka
Donor companies B2B SaaS, fintech infrastructure, billing, logistics platforms, marketplace core teams
Risk Profile may be strong on the stack but without production ownership
Message angle Not "we have an interesting vacancy" but "a role centred on reliability and scaling a critical circuit"
Primary evaluation criteria Facts about service ownership, incident response, performance, architectural decisions
How to apply across chapters:
1. In the brief, clarify what "senior" means: service ownership, architecture, mentoring or speed of delivery.
2. In the portrait, separate the technology language from the work actually performed.
3. In the market map, look not only at direct competitors but also at teams with similar operational load.
4. In the message, talk about the technical challenge, not a stack of technologies.
5. In the evaluation, do not judge by company name without facts about the person's role.
E2. BDM for B2B SaaS Payments
Element Example
Business problem Open or strengthen sales of a payment product in the B2B segment
Mandatory work Complex product sales, long cycle, multiple stakeholders, understanding the payment or fintech environment
| Element | Example |
|---|---|
| Observable signs | Enterprise sales, payments, acquiring, PSP, merchant services, partnership sales, quota, pipeline |
| Donor companies | Payments, fintech, banking SaaS, e-commerce infrastructure, embedded finance, B2B platforms |
| Risk | Candidate may be a strong active seller but without relevant deal complexity |
| Message angle | "A role focused on growing the payment line and complex B2B deals" |
| Primary evaluation criteria | Buyer type, average deal size, deal cycle, role in negotiations, pipeline ownership |
How to apply across chapters:
1. In the brief, clarify the ICP, deal cycle, average deal size, geography and disclosure constraints.
2. In the market map, separate direct competitors, adjacent fintech and B2B SaaS with a similar sales model.
3. In the message, do not promise compensation or seniority if it is not approved.
4. In the evaluation, separate a fancy job title from facts about pipeline ownership.
5. In the weekly update, show which pool delivers not just responses but qualified interest.
Message angle "A role focused on growing the payment line and complex
B2B deals"
Primary evaluation criteria Buyer type, average deal size, deal cycle, role in
negotiations, pipeline ownership
How to apply across chapters:
1. In the brief, clarify the ICP, deal cycle, average deal size, geography and disclosure constraints.
2. In the market map, separate direct competitors, adjacent fintech and B2B SaaS with a similar sales model.
3. In the message, do not promise compensation or seniority if it is not approved.
4. In the evaluation, separate a fancy job title from facts about pipeline ownership.
5. In the weekly update, show which pool delivers not just responses but qualified interest.
