Engagement collateral

Pilot first. Waves next. Paid in stages.

Trustholm programs are consulting-led: you tell us what must move, we prove the pattern on a pilot, then migrate in gated waves with partial payments tied to delivery — not a single leap of faith.

Print or save as PDF for steering committees. Full fillable forms live in the engagement pack under docs/commercial/engagement/.

Multistage shape

Stage 1EvaluateWorkshops, IA, risk, pilot pick
Stage 2PilotOne family, exit criteria, go/no-go
Stage 3WavesBatched cutovers with acceptance
Stage 4HypercareFloor support + handover
Stage 5RetainerOptional ongoing counsel

What a pilot looks like

A pilot is a time-boxed migration of one agreed record family into SharePoint Online. It is not a free full-estate trial.

ElementTypical
Duration2–6 weeks
ScopeOne record type / tightly bounded set
WorkConnect → map → dry-run → live → views → champion coaching
ExitFindable records, provenance present, no LVT surprises on default views
OutcomeGo / go-with-conditions / revise / stop — before estate spend

What a multistage project looks like

After pilot acceptance, the estate moves in waves (by record type, business unit, status, or year). Each wave has a scope lock, dry-run, live import, UAT, and sign-off before the next wave starts.

Wave gateWhy it exists
Scope lockNo silent expansion mid-flight
Dry-runCounts, path risk, mapping gaps
Live + checkpointsRestartable, auditable progress
AcceptanceBusiness + ICT confirm operability
Change requestVolume or ACL surprises get priced, not absorbed

Multistage costing & partial payments

Fees are proposal-specific. Cash follows delivery gates so the agency proves the pattern before the majority of spend.

Typical payment pattern

StageShapePartial invoices (illustrative)
EvaluationFixed50% kickoff · 50% on report
PilotFixed after eval40% access confirmed · 30% dry-run · 30% acceptance
Each waveFixed or capped T&M35% start · 35% live complete · 30% acceptance
HypercareFixed50% start · 50% handover complete

Illustrative only — your SoW annex sets amounts, PO lines (E1, P1, W1.1…), GST, and pause rights for overdue invoices.

Worked cashflow idea

On a mid-complexity program, cumulative billings after pilot acceptance are often around a third of the committed program total — enough to prove SharePoint operability before wave spend.

What consultation usually covers (beyond bulk load)

Tick these in evaluation — packaged as Core migrate · Labels & retention · Permissions · Search & enablement · Capture/integrations · Decommission.

BandTopics
CorePurview labelling & retention · Information architecture · Views/columns · Permissions redesign · Search · Training & change
Common add-onsEmail/capture · Scanning · Case/container emulation · Legal holds · Audit packs · LOB integrations
Often deferredTRIM decommission · Destroyed/sentenced scope · Residency/guests · On-prem hybrid

Workshop form: engagement pack item 14 · App Welcome checklist · CLI consult

Forms we ask customers to complete

These tell Trustholm what you need migrated, under what constraints, and who decides.

  1. Customer migration intake — drivers, in/out of scope, sequencing preference, success measures
  2. Technical environment worksheet — TRIM/CM SQL, document store, agent host, M365 tenant
  3. Record type inventory — volumes, owners, pilot shortlist, wave draft
  4. Security, retention & compliance — ACLs, holds, disposal, markings
  5. Stakeholders & RACI — sponsors, decision rights, cadence
  6. Consultation scope & add-ons — labelling, IA, permissions, search, capture, decommission

During delivery we also use pilot definition, acceptance/sign-off, change requests, and hypercare handover checklists.

Ask

Start with a fixed-fee evaluation. We send the intake pack, run workshops, and only then price pilot and waves properly.

Request the intake pack Limits briefing Sales leave-behind