← Back to the growth room

BETTER TOGETHER / MSP ROUTE SCREENING

Find the unmet need.
Protect Reclaim’s advantage.

Prioritize MSPs and service partners with a verified capability gap, customer demand and committed sellers. Exclude platform-vendor targets that already advertise automatic remediation.

00Platform targets cleared

No clean capability gap established.

07Platforms excluded

Advertised automatic remediation.

01Platform held out

Halo’s automatic resolution needs scope review.

Prepared by Givonn Jones · Evidence reviewed November 6, 2026 · Leadership review

THE RECOMMENDATION

Win through a service partner
with a real gap to fill.

Qualify the MSP’s customer need, service offering and willingness to co-sell. Its installed platform is operating context; it does not establish Reclaim fit or a reason to pursue that platform vendor.

BETTER TOGETHER / HYPOTHESIS TO PROVE

The MSP owns service delivery.
Reclaim adds a verified capability.

For a qualified customer with an unresolved exposure, combine the MSP’s access and delivery ownership with a supported Reclaim action. Agree the success criteria, customer permissions and commercial model before joint execution.

First proof: accepted customer outcome and a paid joint win.
GIVONN’S NEXT ACTION

Find the first credible service partner.

Identify an MSP with a documented gap and one ICP-qualified customer. Secure a named seller and technical owner, inspect the existing tools, then build a dated mutual action plan with Stephen and Product / SE.

Advance only with supported scope and viable service economics.

PLATFORM-VENDOR SCREEN

Apply the exclusion.
Keep the evidence.

Seven reviewed vendors explicitly advertise automatic remediation. Halo promotes automatic issue resolution and remains on hold. All eight are removed from the active platform recommendations and scorecard choices.

Inspect eight screening decisions and vendor sources
Vendor statements reviewed November 6, 2026. Status reflects the targeting rule, not Reclaim readiness.
PlatformDecisionPublic evidence behind the decisionSource
NinjaOneExcludedExplicit auto-remediation feature automates detection and resolution of endpoint issues.Vendor evidence →
AteraExcludedRemote-monitoring documentation describes auto-healing scripts for hands-free remediation; its broader offer also includes Robin and Vicarius.Vendor evidence →
SuperOpsExcludedIts RMM page explicitly lists automatic remediation of endpoint issues.Vendor evidence →
N-ableExcludedN-central is described as supporting self-healing workflows that detect issues and remediate automatically.Vendor evidence →
SyncroExcludedOfficial documentation provides an Automated Remediation feature for RMM alerts and script actions.Vendor evidence →
ConnectWiseExcludedIts cybersecurity remediation offer explicitly promotes automated vulnerability remediation.Vendor evidence →
Kaseya / DattoExcludedEndpoint Compliance Remediation automatically fixes failed controls through Datto RMM and verifies the result.Vendor evidence →
Halo / HaloPSAHoldHalo AI promotes process agents that automatically resolve known issues. The boundary with security remediation is not established, so it is not an active recommendation.Vendor evidence →

No replacement platform is cleared. A lack of search results would not establish a capability gap. Reopen a target only after an explicit strategy change and customer-specific differentiation review.

ACCOUNTABLE EXECUTION

I own the path from
platform access to partner revenue.

PHASE 1

Establish a win

Givonn: select one MSP, secure a named seller, document the gap and create a dated mutual action plan.

Product / SE: validate Reclaim scope, tenant isolation, approvals, auditability, failure handling and support.

Hai + Stephen: clear terms, account roles, AE/SE capacity and success criteria.

Advance on readiness clearance and customer acceptance. Record the paid win separately.
PHASE 2

Engineer repeatability

Givonn: package the joint story, discovery guide, overlap comparison, approved workflow, pricing, onboarding and seller enablement.

MSP owner: commit the next seller, customer and delivery capacity.

Advance on a second paid win through another seller or customer, with documented contribution and repeatable economics.
PHASE 3

Scale selectively

Givonn: inspect QBRs, attribution, support load and partner-sourced demand.

Hai + Stephen: fund the strongest route and approve platform-level investment when proof justifies it.

Expand only with repeat demand, positive net contribution and funded delivery capacity.

PRESSURE-TEST BOTH SIDES

A service margin.
A revenue contribution.

Do not confuse technician capacity with cash savings or a platform listing with pipeline.

MSP service contribution

Collected service revenue less Reclaim licensing, incremental platform fees, delivery, support and allocated onboarding costs. Validate minimum commitments and the customer size needed to support the offer.

Reclaim deal contribution

Net receipts after partner share and transaction fees, less cloud, implementation, support and allocated integration costs. Compare with direct-sale economics and avoid counting a discount twice.

Set the measurement period, attribution and margin floor. Agree channel contribution as a percentage of Reclaim’s $3M 2027 total revenue goal, with $5M as the company stretch. Track ARR separately with agreed definitions. No platform revenue forecast is assumed.

The decision: authorize one evidence-led MSP play.

Givonn owns qualification. Hai approves commercial terms. Stephen validates account priority and seller capacity. Product / SE clear technical scope. Keep customer-identifying detail restricted until permission, roles and transaction protections are agreed.

Open the decision scorecard →