Resell Protection
Bring a named customer that needs backup, recovery or disaster recovery. The customer holds the Sendense licence while your team can support the design and delivery.
Qualify a protection opportunityFor MSP Resellers & Solution Partners
Start with a real customer opportunity.
Use Sendense to deliver customer protection, VMware migration and infrastructure projects. Start with a live opportunity, qualify the estate and shape the architecture, licensing and delivery plan around the customer.
What opportunity are you bringing?
Start with the customer outcome, then choose the licensing and delivery model that fits the work.
Showing Deliver a Migration Project
Deliver a Migration Project
Use Sendense for a named VMware exit, CloudStack migration or supported infrastructure-change project, with the migration and protection paths scoped around the customer.
Plan a migration opportunity
Operate an Ongoing Service
When your organisation retains and operates Sendense as part of a managed service, use the managed-service operating model rather than the customer-specific resale route.
Review the operating model
What do you need to evaluate?
Work through the customer, the estate, delivery ownership and the first reusable approach.
Name who will hold and operate Sendense.
The same organisation can use different models on different opportunities. The licence holder, operator and customer outcome determine the route.
- 1MSP Reseller Licensing
Named customer holds the licence
Use the MSP reseller and solution-partner route when the named customer holds the Sendense licence.
- 2Migration Licensing
One-time permanent workload move
Use migration-project licensing for a permanent named-workload move rather than ongoing protection.
- 3Managed-service operating model
Provider retains and operates Sendense
Use the managed-service operating model when your organisation retains and operates Sendense.
- 4Cloud Service Provider journey
Provider operates its own cloud infrastructure
A Cloud Service Provider that licences and operates Sendense follows the Cloud Service Provider customer journey.
Qualify the customer environment before you design the project.
Map the customer platform, storage path, repository, recovery target and workflow to the documented Sendense architecture.
| Dimension | Qualification question |
|---|---|
| Customer objective | Is the work backup, recovery, disaster recovery, a named migration, or a mix? |
| Source platform and version | Which source platform and version will the customer protect or move? |
| Hypervisor | Which hypervisor is in scope for the named workloads? |
| Storage path | Which primary storage path does the estate use today? |
| Repository | Where will backup and recovery data be stored, and who controls that repository? |
| Recovery destination | Where must workloads recover or land after a move? |
| Backup / DR / migration workflow | Which supported workflow must the first opportunity prove? |
| Network and connectivity | What connectivity is available between source, repository and recovery target? |
| Workload and dependency scope | Which representative workloads and dependencies belong in the first proof? |
| Operator after handoff | Who operates Sendense after delivery: the customer, the partner, or a managed-service team? |
Make ownership clear before delivery starts.
Agree who owns access, architecture, deployment, acceptance and first-line support before the first workload is protected or moved.
Customer responsibilities
Provide environment access, change control and acceptance criteria for the named workloads. Confirm who will operate Sendense after handoff.
Partner delivery responsibilities
Lead discovery, design and the agreed implementation steps. Capture test evidence and complete the operational handoff for the opportunity.
Sendense product and support path
Sendense provides the product, documentation and the support path agreed for the opportunity. Agree the support and escalation path as part of the delivery plan.
Scope the first opportunity around the customer.
Customer-specific resale uses the MSP reseller licensing route. A permanent named-workload move uses migration licensing. Retained managed operation is scoped through the managed-service route.
Quote readiness
- Named customer
- Licence holder
- Operator
- Workload and platform scope
- Protection or migration requirement
- Term or one-time project
- Repository and recovery target
- Delivery and support ownership
- Evaluation requirement
Build a reusable approach from the first opportunity.
Use the first qualified project to settle discovery, proof and handoff. Reuse that approach on the next similar customer estate.
Discover
Capture the customer trigger, estate, platforms, storage and recovery goal.
Qualify
Confirm the exact product path, commercial route and responsibilities.
Prove
Use representative workloads and acceptance criteria to test the intended workflow.
Deliver and review
Complete the customer handoff, review evidence and decide what can be reused for the next similar opportunity.
Move one live opportunity from discovery to a delivery decision.
Use this sequence to move a live opportunity from discovery to a delivery decision.
Stage 1
Name the customer and business trigger
Record who the opportunity is for and why the work is needed now.
Stage 2
Establish who will hold and operate Sendense
State the licence holder and the operator for this opportunity.
Stage 3
Inventory the platform, storage and recovery paths
Capture the source estate, storage path, repository and recovery destination.
Stage 4
Choose resale, migration or managed operation
Select the licensing and delivery route that matches the licence holder and the work.
Stage 5
Define technical and commercial success criteria
Agree what the first proof and the first commercial step must show.
Stage 6
Prove the workflow with representative workloads where needed
Run the supported backup, recovery, DR or migration workflow on a representative set.
Stage 7
Agree delivery, support, licensing and next action
Close ownership, the licensing route and the next commercial step for the customer.
Bring evidence into the customer conversation.
Use product, compatibility and named customer evidence in the customer conversation. The Quadris customer story documents a named VMware-to-CloudStack migration project. Quadris VMware to CloudStack.
Bring the customer, the estate and the delivery model.
We will use those details to map the technical path, licence holder, delivery responsibilities and next commercial step.
Partner FAQs
Who holds the licence in an MSP reseller opportunity?
The named end customer holds the Sendense licence. Your team can support design and delivery while the customer remains the licence holder.
Can a solution partner deliver a VMware or CloudStack migration?
Yes. A solution partner can deliver a named VMware exit, CloudStack migration or supported infrastructure-change project. A permanent named-workload move uses migration licensing.
What changes when the provider retains and operates Sendense?
The work becomes a managed-service operating model. Licence holder and operator are scoped for that service rather than as named-customer resale.
Is the Cloud Service Provider route the same as the MSP reseller route?
No. A Cloud Service Provider licences and operates Sendense as a customer on its own cloud infrastructure. That journey is separate from named-customer resale.
What information is needed to qualify a customer opportunity?
Name the customer, the licence holder, the operator, the platforms and storage paths, the protection or migration workflow, and who will own delivery and support.
How is the commercial model scoped?
Named-customer resale uses MSP reseller licensing. A one-time permanent workload move uses migration licensing. Retained managed operation is scoped through managed-service scoping.
What should the first opportunity prove?
It should prove environment fit, the intended backup, recovery, DR or migration workflow, recovery or test evidence where that workflow requires it, and a clear delivery and licensing next step.