CS Operations · The lifecycle

    The customer lifecycle for an MSP

    Five stages. Seven critical meetings. One rhythm that separates MSPs from MVPs. Click any stage on the bow-tie to open its playbook.

    What is CS Operations?

    The operating system behind every customer commitment.

    CS Operations is the doing side of the practice — the ceremonies, playbooks, SOPs, and agents that turn strategy into a repeatable rhythm the whole team runs on. Where CS Strategy decides what promises we make to a client, CS Operations decides how we consistently deliver them, stage by stage.

    Each of the five lifecycle stages below has its own playbook: the critical meetings that must happen, the SOPs that back them, and the agents that scale them. Together they form the bow-tie — acquisition on the left, the engagement knot in the middle, growth on the right.

    MSP vs. MVP

    MSPs sell technology. MVPs deliver business outcomes.

    The MSP side of the lifecycle is anchored in the stack — environments, tools, tickets, uptime. The MVP side is anchored in the client's business — the objectives they are trying to achieve and the outcomes we are on the hook for. Same stages, different centre of gravity.

    Consultative Sales
    MSP DefaultSold on stack, uptime, and price. Discovery centres on environments, endpoints, and tools to replace.
    MVP MoveSold on business outcomes. Discovery qualifies the client's goals, growth plan, and cost of inaction — technology follows the objective.
    Onboarding
    MSP DefaultMigrate the environment, standardise the stack, get the tickets flowing. Success = clean cutover.
    MVP MoveLand the commitments made in sales. Onboarding graduates the client into a plan tied to their business outcomes, not just a working stack.
    Engagement
    MSP DefaultReport on tickets closed, uptime, patch compliance, and tools deployed. The conversation is operational.
    MVP MoveReport on progress against the client's objectives. QBRs prove business value to the cheque-signer and land the next decisions.
    Expansion
    MSP DefaultPitch new technology when a gap appears — more licences, another tool, a security add-on.
    MVP MoveExpansion is driven by the client's roadmap and business goals. New services are proposed because they unlock an outcome, not because they exist.
    At-Risk
    MSP DefaultRisk shows up as SLA breaches, escalations, and renewal pushback. The fix is technical remediation.
    MVP MoveRisk is named against the business outcome that is slipping. The At-Risk Meeting realigns the plan to what the client is actually trying to achieve.