Value in Research

Proposal vision for VIR

A stronger operating base for VIR's knowledge work.

VIR has built its reputation through specialist expertise, trusted client relationships, and consistent delivery of high-quality work.

This proposal is not about replacing that judgement with automation or tools. It is about strengthening how VIR captures, structures, reuses, and applies its knowledge across projects.

Documents, evidence, and project materials forming a governed operating memory
The point The goal is not to outsource thinking.

Expert judgement stays central. The system gives that judgement a better operating base.

The opportunity

Valuable project history, assumptions, evidence, methods, and commercial insight currently sit across folders, documents, and individual experience. If that information is easier to find, govern, and reuse, VIR can improve delivery quality, reduce duplicated effort, support stronger proposals, and identify new commercial opportunities.

01

Understand the work first

Do not build tools on messy or unstable information.

02

Make reuse reviewable

Prior work should come with source links, confidence, gaps, and ownership.

03

Design for adoption

Stakeholder input and ownership matter as much as the technical build.

Programme shape

Three practical areas, sequenced from foundation to commercial leverage.

Area 01

VIR Operating Memory

Turn VI's historical SharePoint project archive into usable business intelligence, while creating a future-proof way for every new project to be structured and searchable from day one.

Historical project folders becoming a structured searchable archive
Project Thesis Output Phase
SharePoint Inventory Map VI needs to see what already exists before building tools on top of the archive. Inventory and pattern summary. Phase 1
Historical Project Classifier Old folders contain useful signals, but uncertainty must stay visible. Draft catalogue with confidence, gaps, and review needs. Phase 1
Project Metadata Model VI needs one shared language for old and new project knowledge. Metadata model, data dictionary, validation rules, and source-link conventions. Phase 1
Project Registry for New Work New work should start as structured project intelligence from day one. Registry record linked to SharePoint folders, deliverables, and owners. Phase 2
Document Registration and Drift Checker Project folders need light governance so they do not drift back into chaos. Project health report and suggested cleanup actions. Phase 2

Area 02

HEOR Commercial and Delivery Workbench

What would we do differently if every HEOR consultant had an unlimited bench of research assistants, analysts, reviewers, model checkers, writers, and project coordinators?

Start with bounded internal experiments that reduce production effort, improve reviewability, and preserve expert sign-off.

HEOR evidence, assumptions, model checks, and review workflow
Experiment 1

HEOR Intake + Scope Assistant

Turn rough client requests into structured briefs, missing questions, scope risks, assumptions, exclusions, work packages, and proposal outlines.

Success signal: faster proposal drafting and cleaner sales-to-delivery handoff.
Experiment 2

Evidence Table Builder

Create draft evidence tables with citations, page references, confidence scores, reviewer status, and evidence gaps.

Guardrail: human approval required for extracted values.
Experiment 3

Assumption Register

Capture assumptions, rationale, linked evidence, approval status, sensitivity scenarios, and reusable candidates.

Success signal: fewer undocumented assumptions and easier model/report review.
Experiment 4

Model-Report QC Assistant

Flag model/report mismatches, unsupported claims, missing references, anomalies, and consistency issues before final review.

Guardrail: flags only; it must not silently change models, reports, or claims.
Experiment 5

Internal HEOR Memory

Create searchable project memory, source libraries, assumption libraries, country libraries, model registry, and similar-project suggestions.

Success signal: less searching, more reuse, faster onboarding, reduced duplication.

Area 03

CRO Growth Wedge

The strongest wedge is not an AI CRO. It is trial startup, submission, site activation, TMF/QC, and bilingual document workflow support: boring, document-heavy, auditable work where every output can be reviewed before use.

Clinical trial startup, submission, site activation, and audit-ready document workflow
01

Trial startup + submission pack copilot

Protocol-to-checklist extraction, country pack builder, approval tracker, missing-doc alerts, and bilingual cover-letter/ICF support.

02

Site feasibility + investigator intelligence CRM

Map protocol eligibility to site capability, investigator history, patient-pool questions, and startup timelines.

03

Bilingual ICF and patient-material QA

Arabic/English concordance, plain-language review, risk/benefit consistency, glossary, change log, and reviewer workflow.

04

TMF/eTMF QC and audit-readiness assistant

Map TMF folders to expected index, detect missing or inconsistent documents, and produce audit-readiness reports.

09

Proposal/SOW estimator and assumptions library

Protocol synopsis to task list, country assumptions, timelines, risk flags, fees, site count, and change-order assumptions.

10

Reusable study knowledge base

Closeout interviews, lessons learned, country/site timelines, query patterns, template library, and source-date confidence notes.

Timeline and cost

Three focused workstreams, scoped before each starts.

Indicative timelines and costs for the proposed workstreams. Final scope should be confirmed before each workstream starts.

Value in Research Commercial plan
Indicative programme range R210k-R290k
01 Operating Memory 4 weeks / R70k
02 HEOR Workbench 4-8 weeks / R70k-R150k
03 CRO Growth Wedge 4 weeks / R70k
Workstream 01

VIR Operating Memory

Timeline 4 weeks
Indicative cost R70k

SharePoint archive mapping, structured project intelligence, and a reusable foundation for new project records.

Workstream 02

HEOR Commercial and Delivery Workbench

Timeline 4-8 weeks
Indicative cost R70k-R150k

Depends on selected scope: proposal support, evidence reuse, assumption registers, QC support, or internal HEOR memory.

Workstream 03

CRO Growth Wedge

Timeline 4 weeks
Indicative cost R70k

Focused first wedge around trial startup, submission, site activation, TMF/QC, or bilingual document workflow support.

Recommended decision

Approve a focused operating-memory discovery sprint.

The next move should be deliberately narrow: map what exists, agree the metadata language, test ownership and review workflows, and identify which HEOR or CRO use cases are worth building after the foundation is credible.

Start with SharePoint inventory + metadata model
Protect Expert judgement, reviewability, and ownership
Avoid A broad tool build before the work is understood

Proposal document

Download the full pitch for review.

The PDF contains the current proposal narrative, programme areas, timeline, and indicative pricing for the VIR operating-memory discovery sprint and related workstreams.

Printed proposal pack with charts and a download symbol 03062026-PDO-Pitch.pdf Download proposal PDF

1.9 MB document for circulation and review.