About

Suleman Manji

Sr. Services Engineer at current services organization, working across MSP systems engineering, platform automation, Microsoft 365 diagnostics, billing/runtime proof, MCP/API tooling, and memory-backed agent operations.

Current operating frame

My formal role is services engineering. The broader work is building operator systems that span MSP tickets, PSA/RMM data, Microsoft 365, billing platforms, stakeholder deliverables, repo governance, and agent runtime memory.

I care about the boundary between automation and operational reality: what live state was checked, what action is safe, what proof exists, what needs human approval, what got posted to the system of record, and what another operator can resume later.

What that looks like in practice

Ticket as control planeCWM tickets become ordered tasks, notes, schedule entries, status gates, and time-entry records rather than loose chat instructions.
Repo as operating memoryGitHub Project 4, issue hierarchy, proof comments, validation commands, and session-harvest maps keep engineering work durable.
Agent work with guardrailsPlatform CLIs, generated contracts, Qdrant/mem0 recall, and preview-first write flows make assistant work auditable.
Stakeholder-ready outputsTechnical evidence is converted into decision packets, fillable HTML, XLSX return paths, and verified PPTX decks when the audience is not an operator.

Working lanes

Safety and publication boundaries

Public writing here abstracts organization and client-adjacent work. It avoids raw ticket notes, internal hosts, private screenshots, secrets, and customer-specific implementation detail. The goal is to show the engineering pattern without turning operational evidence into public leakage. Financial-agent material is research and engineering infrastructure only; it is not investment advice or a solicitation.

Contact

Useful conversations include operational automation, MSP systems, Microsoft 365 diagnostics, agentic workflows, MCP/API tooling, and proof-oriented engineering.