Getting Started · The Published On-Ramp

Start without switching.

You don't have to fire your MSP today. You don't have to fire them this year. Device logistics works alongside whatever you have — and when you're ready for more, the path is published, dated, and runs in parallel with your existing contract. You'll never pay for two service desks. That's in writing, below.

/ The Roadmap

The roadmap

01 · START

Device logistics, day one

Begin with the wedge: laptops in, laptops out, at published rates. This touches nothing your MSP does — no contract conflict, no displacement, no risk conversation. Pilot at $2,500 / 30 devices / 60 days, or go straight to platform access.

"Your MSP keeps doing exactly what they do today. We just run the warehouse they never wanted to build."

02 · COVER

Device Response Coverage

Add the same-day swap promise: $4/user/mo, spare pool staged, dispatch by 2:00 PM ET. Your people start experiencing what a logistics-grade SLA feels like. Still zero overlap with your MSP's scope.

03 · ASSESS

Security & zero-trust projects

Independent assessment work — zero trust, identity hardening, OT security — delivered as fixed-scope projects. Independent is the point: findings about your environment from a party with no incumbent configuration to defend. These projects stand alone whether or not you ever open Door 2.

04 · ALIGN

Bring us one date

The day your current MSP contract ends. We build the entire onboarding plan backward from that date. Your contract term isn't an obstacle to us — it's the project schedule. Some clients reach this step in months; some take two years. Both are fine. The date drives the plan, not our sales calendar.

05 · RAMP

Onboarding in parallel, transparently

With Door 2 signed, onboarding runs while your MSP is still in place: integrations stood up, knowledge captured, the AI service desk running in shadow mode against your real ticket queue — producing a measured containment report on your actual tickets before go-live. Your MSP works their contract to its last day. We build alongside, in the open.

06 · CUTOVER

Renewal date = go-live date

Nothing migrates on cutover day, because the migration already happened. The switch you flip is a billing switch, not a technical one.

/ The Rule

The no-double-billing rule

You will never pay Surya and your MSP for the same service desk in the same month. AI Service Operations billing starts the day your MSP contract ends — not the day you sign, not the day the ramp starts. The parallel onboarding period is included with commitment.

SIGN EARLY · RAMP IN PARALLEL · BILL AT CUTOVER

During the ramp you pay only for what's already running and delivering: logistics on the meter, coverage per user, assessment projects as quoted. Every line, published. Nothing overlaps your MSP's scope; nothing bills twice.

/ What We Ask

What we ask of you

  1. 01The contract end date. One date unlocks the whole plan.
  2. 02Read-only access during the ramp. Shadow mode needs to see tickets to measure containment. It reads; it doesn't touch.
  3. 03A decision at signature, not at cutover. The free ramp is the trade for commitment. We build the bridge; you commit to crossing it.

/ Start

Two ways in

Pilot

Start the pilot

$2,500 · 30 DEVICES · 60 DAYS

Align to your renewal

Bring us your renewal date →

Assessment projects quoted fixed-scope before work begins. Shadow-mode reporting uses read-only ITSM access; no changes are made to production during the ramp. If you choose not to proceed at renewal, ramp infrastructure is decommissioned and logistics continues unaffected — Door 1 never depended on Door 2.