One end of the range needed a different answer.

CaseMargin reads a ticket thread and returns two things: a structured handoff and an escalation readiness score. It runs inside Zendesk, a Chrome side panel, the web app, or over MCP. It does not own the queue or store the ticket. It adds a layer over whatever desk a team already uses.

This works across a span: solo founder at one end, tiered managed service desk at the other. At the MSP end, that layering is the point. Brief and Escalation Score sit above an existing desk and handle what those desks leave out. At the solo founder end, the picture changes. A founder answering support through email, a chat widget, or the tools already in use is often not running a traditional helpdesk at all. A layer over nothing is nothing.

CaseMargin's own product notes record this gap. A helpdesk built for solo founders was a documented intended direction. The existing tooling could not become one. The layer and the desk are different products, and that difference is real enough to keep them separate.

Foliosio is where that thinking went. A helpdesk built for the founder who is also the support team: a unified inbox handling chat and email together, AI replies informed by product context, a public help center customers can search on their own, and analytics that show what customers keep asking about.

Both products come from the same question: how much of support time goes to reconstruction rather than resolution, and how much of that reconstruction is avoidable? At the handoff level, that is CaseMargin's problem. At the desk level, for the founder who needs the desk itself, that is Foliosio's.