How RSVR works

From a 30-minute conversation
to operational change.

Five stages. One shared engine. Applied to AI Data Safety or Contract Operations depending on where the risk lives. Evidence-first at every step. Scoped and priced before any commitment is made.

01
30 minutes · Free

Snapshot

A focused executive conversation led by Rajnish Kohli. You describe the situation honestly. We ask clarifying questions. You leave with a clear recommendation — or confirmation that no action is needed yet.

You receive
  • Identification of the right service track
  • Assessment of whether a diagnostic is justified
  • Written recommendation within 24 hours
  • Or: clear confirmation that no action is needed yet
Cost: Free Commitment: None
02
2–4 weeks · Fixed scope

Diagnostic

A time-boxed, scoped engagement that maps the problem in detail — by team, by workflow, by data type. Produces a board-readable report and a prioritised 30/60/90-day action plan. Scoped and priced before any commitment is made.

You receive
  • Board-readable exposure or workflow diagnostic report
  • Bottleneck or risk register by category and severity
  • Prioritised 30/60/90-day action plan with named owners
  • Decision: which elements to build, and in which order
Cost: Fixed price, agreed before start Commitment: Commit after Snapshot
03
1 week · Included in diagnostic

Roadmap

Sequenced actions, named owners, decision points and dependencies — sized for SME execution speed and budget. Delivered as part of the diagnostic, not as a separate engagement.

You receive
  • Action sequence with clear dependencies
  • Named owners for each workstream
  • Budget and timeline estimate for build work
  • Decision gates before any build investment is committed
Cost: Included in diagnostic Commitment: None beyond diagnostic
04
Scoped per engagement

Build

Workflows, controls, dashboards and AI-assisted components — built, not deferred. Senior-led at every step. Software delivery where the fix requires real engineering.

You receive
  • Working workflows configured in your tools
  • Approved-tool lists, data rules, manager routines (AI governance)
  • Intake forms, triage logic, routing, playbook in-system (contract ops)
  • AI usage dashboard or contract operations dashboard
Cost: Scoped and priced before build starts Commitment: Commit after roadmap review
05
Embedded into build delivery

Adoption & Operate

Role-specific training, manager routines, exception handling guides, and a quarterly review cadence so the improvement sticks long after the engagement ends.

You receive
  • Role-specific training (not click-through compliance modules)
  • Manager enablement materials and routines
  • Quarterly review cadence to update rules as tools change
  • Handover documentation your team can own and maintain
Cost: Included in build engagement Commitment: None beyond build
Typical timeline

From Snapshot to working output — how long it takes.

AI Data Safety (WorkLex AI)
Snapshot
Diagnostic
Build (6–8 weeks)
Adopt
✓ Core controls operating within 10–12 weeks of Snapshot
Contract Operations (Contractrix AI)
Snapshot
Diagnostic
Build (4–6 weeks)
Adopt
✓ Dashboard and intake live within 8–10 weeks of Snapshot
No surprises, no open-ended retainers

Pricing transparency — what you know before you commit.

RSVR does not use open-ended monthly retainers or statement-of-work padding. Every paid engagement is scoped and priced in writing before work begins.

Stage
What you pay
What you know before paying
Snapshot
Free
No obligation. No follow-up sequence unless requested.
Diagnostic
Fixed fee, agreed upfront
Typically 2–4 weeks. Scope and price set in writing before work begins.
Build
Scoped per engagement
Scoped from the diagnostic roadmap. No open-ended retainers without your agreement.

Build engagements are scoped from the diagnostic roadmap. You approve scope, price and timeline in writing before any build work begins. There are no change-order surprises — if scope changes, we discuss and agree before proceeding.

FAQ

Questions about how RSVR works.

No. Each stage is a decision point. You can stop after the Snapshot (with a written recommendation), after the Diagnostic (with a board-readable report and action plan), or after any build phase. There are no long-term commitments and no lock-in.
Before any paid engagement begins, RSVR provides a written scope document covering: what will be delivered, how long it will take, what it will cost, what you need to provide, and what constitutes completion. You approve this before we start.
For AI Data Safety (shadow AI governance): Snapshot → Diagnostic (3 weeks) → Build (6–8 weeks). Core controls operating within 10–12 weeks of the Snapshot. For Contract Operations: Snapshot → Diagnostic (3 weeks) → Build (4–8 weeks depending on CLM configuration). Visibility dashboard typically within 6 weeks of diagnostic completion.
RSVR delivers remotely, primarily. For diagnostic workshops and key build milestones, we can attend on-site in the UK. For US, ANZ and Singapore clients, all delivery is remote with appropriate timezone alignment.
For the Snapshot: nothing beyond your time. For the Diagnostic: access to key stakeholders (GC, COO, relevant team leads) and honest answers about the current state. For the Build: access to the tools and systems we're configuring, a named internal owner per workstream, and feedback on deliverables within agreed timelines.

Start with a free 30-minute Snapshot.

No preparation needed. No documents. No obligation. A focused conversation to identify the right track — or confirm no action is needed yet.

Whatsapp