Rivell on the 2024 MSP 501: Historical Rank Record

This historical record is one part of provider research, not a substitute for reviewing the proposed scope. Start with Rivell’s current company information, then compare the people, systems, responsibilities, evidence, pricing, transition plan, and contract terms that apply to the actual engagement.

What the archived publisher record establishes

The archived Channel Futures Mid-Atlantic page contains a Rivell slide that identifies Rivell, links to Rivell’s website, and lists Sewell, New Jersey. That slide records rank 326 overall, rank 49 in the Mid-Atlantic, and rank 11 in New Jersey. Each number belongs to the 2024 program and should retain that date whenever it is cited.

The official MSP 501 year archive now separates the 2026, 2025, and 2024 lists. The official current program page describes an annual report and presents 2026 as the active cycle at review time. Together, those pages make the current-versus-historical boundary clear. They do not establish a 2025 or 2026 Rivell position.

How the 2024 methodology should be read

An archived Channel Futures methodology page describes a minimum annual-revenue and managed-services-revenue threshold followed by a review of weighted annual revenue, EBITDA as a percentage of revenue, and recurring revenue as a percentage of revenue. It says overall revenue represented 50 percent of the 2024 score and was weighted toward value-added services, while recurring revenue represented 25 percent.

The same page says company revenue, profitability, and other financial data remained confidential, although Channel Futures could publish aggregate totals. That distinction matters. List-wide totals and averages describe the submitted population, not Rivell. Rivell’s appearance and rank support the dated selection result, but they do not reveal Rivell’s individual revenue, profit, recurring-revenue share, growth rate, or investment decisions.

The former Rivell article extended well beyond that evidence. It reproduced broad publisher praise, drew conclusions about operating performance and customer results, and included a quotation attributed to Rivell’s CTO that changed the company identity to a different business. Exact-phrase searches located the text only on Rivell’s own page, not in an independent source. The quotation has therefore been removed in full rather than silently corrected or reattributed.

A dated rank can still be useful as discovery evidence. It shows that a named publisher included a company in a particular program under the methodology used at that time. It should be recorded with the publisher, year, geography, position, source URL, archive capture, and review date. Keeping those fields together prevents an old number from losing its date or being presented as an active market position after the program advances to a later cycle.

Recognition evidence also belongs in a different column from operating evidence. A ranking source can document selection and placement. Current operating evidence addresses staffing, tools, service ownership, escalation, security controls, recovery tests, reporting, references, and contract performance. Procurement teams should preserve both kinds of information without allowing one to stand in for the other. That separation makes the record useful while keeping the conclusion proportionate to what the publisher actually disclosed.

How to evaluate a managed IT provider now

Define the environment and responsibility matrix

Document users, devices, identities, applications, locations, vendors, business hours, regulated data, recovery objectives, and recurring support problems. Separate routine operations from projects, consulting, cloud hosting, cybersecurity, and onsite work. Rivell’s New Jersey IT services overview, managed IT services page, IT support page, and business IT support guide help distinguish those scopes.

Test operating and risk evidence

Ask who owns monitoring, triage, escalation, patching, identity administration, endpoint coverage, vendor coordination, documentation, after-hours response, recovery testing, and executive reporting. Use the same written requirements for every provider. Rivell’s provider comparison guide, cybersecurity page, and disaster recovery page provide question sets, but a proposal still needs environment-specific answers and evidence.

Normalize proof, pricing, and transition terms

Review references that resemble the proposed environment and identify the work Rivell actually owned. Rivell’s Success Stories and testimonials provide company context; their relevance still requires direct review. Normalize recurring fees, onboarding, licensing, hardware, project work, after-hours service, exclusions, annual changes, termination assistance, and data return. The managed IT pricing guide identifies variables to put in writing.

Build a transition plan covering discovery, credentials, documentation, tool deployment, vendor handoffs, acceptance criteria, reporting, escalation contacts, and exit obligations. Rivell’s company approach and service-area information add context. To discuss a specific workload, contact Rivell with the users, systems, constraints, current providers, and decisions that need to be supported.

Before a final decision, ask each provider to return the responsibility matrix with named owners, dependencies, exclusions, evidence locations, and escalation paths. Compare the answers line by line. Record which statements are supported by a current contract, report, test result, customer reference, or public source. Where evidence is unavailable, label the item as a proposal assumption instead of treating recognition language as confirmation.

Frequently asked questions