Operational Command Layer / Client Lifecycle

Control every customer journey from first lead to live monitoring.

A CRM-enforced lifecycle that turns sales, delivery, migration, approval, and production cutover into one governed operating system.

WISPGate’s Client Lifecycle connects Growth, Delivery, Onboarding, CSM, Support, Technical Operations, Finance, and the client through xGate CRM. It is designed to replace scattered Trello follow-ups, informal WhatsApp memory, and disconnected delivery handoffs with visible operational control.

Explore Lifecycle View Pipelines
13
Lifecycle stages
3
CRM pipelines
4
Client approval gates
2-way
Team + client notifications
Lifecycle Command Center
Sales → Delivery → Migration → Approval → Monitoring
xGate CRM
Lifecycle Core
Growth Pipeline
Delivery Pipeline
Onboarding Pipeline
Monitoring Layer
Licensing Control
Growth

Lead-to-subscription control

Every prospect is sourced, verified, followed up, demonstrated, negotiated, and converted through visible stages.

Delivery

Order and license discipline

Commercial commitment turns into order form, license activation, installation, delivery, and CRM adjustment.

Migration

Questionnaire-driven onboarding

The migration plan is based on real data, questionnaire answers, dry-runs, validation, and approval.

Approval

No blind go-live

Production cutover only happens after client approval, readiness validation, and accountable handover.

Complete WISPGate Client Lifecycle

Every customer moves through a visible journey from lead to monitoring. The orange stages are client-dependent gates where WISPGate cannot proceed alone.

Client Gates Pipelines Automation
Lifecycle Diagram / End-to-End

One operational path from first contact to production confidence.

This diagram follows the WISPGate website architecture language: modular blocks, clear directional flow, and highlighted control gates.

Lead → Monitoring
LeadICP + source EngagementPain qualified Demo1-month demo NegotiationScope + terms SubscriptionClient request InstallationEnvironment OrderLegal + scope DeliveryInstance ready QuestionnaireMigration facts MigrationValidate + dry-run ApprovalClient sign-off CutoverGo-live MonitoringHypercare
01

Lead

Potential customer enters CRM with source, ICP fit, country, segment, and owner.

02

Engagement

Pain, urgency, current system, network type, and decision path are qualified.

03

Demo

The client sees WISPGate, usually through a guided demo or 1-month free demo.

04

Negotiation

Commercial terms, setup scope, migration support, and integration needs are aligned.

05

Subscription

Client requests/accepts subscription, triggering formal handoff to Delivery.

06

Installation

Environment, license, base configuration, access, and technical setup begin.

07

Order Submission

Client submits formal order data, legal acceptance, plan, and delivery scope.

08

Delivery

Instance is prepared and delivered with credentials and required instructions.

09

Questionnaire

Client completes scoping questionnaire for migration, billing, data, and network risks.

10

Migration

Data collection, validation, staging, dry-run, and parallel testing are executed.

11

Client Approval

Client confirms staging/dry-run results and authorizes production cutover.

12

Production Cutover

WISPGate becomes live for operational usage, billing, workflows, and users.

13

Monitoring

Hypercare, CSM follow-up, support ownership, and operational reports stabilize the account.

Client Gates / Control Points

The four stages where WISPGate cannot move alone.

These gates require customer action. They prove WISPGate has a governed delivery methodology, not an improvised onboarding process.

Client Action Required
Gate 01

Subscription Request

Commercial commitment. Growth triggers customer record, subscription plan, delivery handoff, and internal notifications.

Gate 02

Order Submission

Formal order, scope, legal acceptance, subscription data, commercial details, and delivery requirements.

Gate 03

Questionnaire

The client provides operational truth: billing model, network setup, current platform, data quality, and migration constraints.

Gate 04

Client Approval

Formal sign-off after staging and dry-run validation. No production cutover should happen without this.

Subscription RequestClient commits Order SubmissionLegal + commercial data QuestionnaireMigration truth Client ApprovalGo-live permission

Hard rule

These gates must have CRM status, owner, due date, reminders, meeting notes, customer notification history, and proof of completion. Otherwise, the workflow only looks organized while still operating like chaos.

Three CRM pipelines powering the lifecycle

Each pipeline owns a different phase of the customer journey and hands the customer forward through governed gates.

Pipeline 01

Growth Pipeline

Manages the prospect’s sales journey from sourced lead to subscription request.

  1. Sourced
  2. Verified
  3. Outreach Sent
  4. Follow up 1
  5. Follow up 2
  6. Follow up 3
  7. Engaged
  8. Demo Conducted (1-Month Free Demo)
  9. Negotiation
  10. Subscription Request
  11. Subscribed
  12. Closed-WON / Closed-LOST
Pipeline 02

Delivery Pipeline

Manages delivery from license activation to installation, order submission, and CRM adjustment.

  1. License Activation (1-Month Free Promo)
  2. Requirement Review
  3. Installation
  4. Order Submission
  5. Delivery
  6. CRM Adjustment (Contact/Org + CSM board)
  7. Closed-WON / Closed-LOST
Pipeline 03

Onboarding Pipeline

Manages migration from questionnaire to roadmap, staging, approval, cutover, and hypercare.

  1. Questionnaire
  2. Roadmap
  3. Assignment
  4. Data Collection
  5. Validation
  6. Staging (Dry-Run)
  7. Parallel Testing
  8. Client Approval
  9. License Activation
  10. Production Cutover
  11. Hypercare
  12. Closed-WON / Closed-LOST
Pipeline Handoff Diagram

Growth sells it. Delivery installs it. Onboarding makes it safe to go live.

The key is handoff control. Every pipeline must pass structured context to the next team.

CRM Control Path
Growth PipelineLead → Demo → NegotiationOwner: Growth Subscription GateCustomer commitsHandoff starts Delivery PipelineInstall → Order → DeliverOwner: Delivery Onboarding PipelineQuestionnaire → MigrationOwner: CSM / Migration
Lifecycle Control Lanes

Five operational lanes make the lifecycle understandable.

This section gives the page more visual structure and explains how WISPGate coordinates commercial, legal, technical, migration, and success work.

Control Model
01

Commercial Lane

Lead, engagement, demo, negotiation, subscription request, closed-won/lost.

02

Legal / Order Lane

Order submission, legal acceptance, subscription terms, plan confirmation.

03

Technical Lane

License activation, installation, instance delivery, environment readiness.

04

Migration Lane

Questionnaire, roadmap, assignment, data collection, validation, dry-run.

05

Success Lane

Client approval, production cutover, hypercare, monitoring, CSM follow-up.

Stakeholder Map

Every stage has internal and client-side visibility.

The lifecycle must show both parties where the project stands, what has been done, and what action is required next.

Team + Client

WISPGate Team

Growth, Finance, Delivery, Technical Ops, Support, CSM, Migration, and Management receive stage-based tasks and alerts.

Client Team

Client owners receive Email/SMS updates, meeting outputs, required-action notices, questionnaires, approvals, and cutover alerts.

xGate CRM

The central record of stage, owner, evidence, notifications, license state, instance status, and customer environment control.

Automation Layer / Notifications

Every stage generates action, visibility, and proof.

xGate CRM is essentially WISPGate with networking modules removed and Licensing added. It uses the same operational philosophy: every state change should trigger the right action.

Email / SMS / Tasks / Logs
01Stage ChangeCRM stage changes from Growth, Delivery, or Onboarding pipeline.
02Rule TriggerAutomation detects required notification, task, report, or manual approval.
03Internal AlertResponsible department receives ownership and next action.
04Client NoticeCustomer receives Email/SMS update or required-action request.
05Evidence LogMeeting notes, action history, and done activities are recorded.
06Next GateCRM blocks or allows progression based on required input.
CRM StageStatus updated AutomationRule evaluates Team AlertOwner assigned Client NoticeEmail / SMS
Connected Assets

Lifecycle depends on these systems

  • WISPGate Biggest Pain: Migration
  • WISPGate Scoping Questionnaire
  • WISPGate Order Form
  • WISPGate Legal Stack / Legal acceptance
  • CRM Operations module replacing Trello over time
  • Licensing module for customer instance and environment control
Failure Warning

Where the lifecycle will break

The system fails if staff treat stages as decoration instead of operational control. Every stage needs an owner, required fields, notification trigger, SLA, evidence, and next action.

PARTNER PROGRAM

Partner With WISPGate

OFFER CLAIM

Claim Your WISPGate Offer

Complete the form below and a WISPGate representative will contact you regarding your selected offer.

Selected Offer: No offer selected
✓

Success

Your request has been submitted successfully.