The capability bar for riggr.co.uk
If you are a framework holder evaluating Riggr with no prior engagement, need UK-wide coverage including rural, and your hardest gate is insurance, liability, and contract fit, this page states what we commit to commercially — and what you should bring to a first conversation.
Buyer journey (mental model)
1. Positioning and proof
Riggr is a managed workforce service, not a staffing agency: we optimise for matching, mobilisation, RAMS and job-pack discipline, and audit trails — not CV forwarding. See the managed workforce one-pager.
- Proof on merit — programme types, regions, and accreditation classes (tower, MATS, reactive, PPM) as your diligence allows; we do not overclaim coverage we cannot sustain.
- Delight factors — predictability, audit-ready evidence, mobilisation speed, clear commercials, a single accountable partner, and artefacts that fit Tier 1 reporting.
2. Risk, insurance, and contract fit
Full insurance schedules and contract positions are shared under NDA and aligned to your framework language. At a high level:
- Commercial-grade pack — insurance lines and limits; typical liability positions (caps, indemnities where applicable); mapping to Tier 1 / MNO framework clauses.
- Governance — RAMS and method statements, controlled change, sign-off, and immutable handover for procurement. Governance summary · Procurement FAQ.
3. Operational credibility (UK-wide and rural)
- Honest forecasting — rural and remote constraints (access, weather, crew availability) are surfaced early; “predictability” means escalation and replanning, not silent slips.
- Mobilisation — response windows and SLA tiers are agreed per engagement; we need clear upfront data (site, scope, accreditation, access) to commit dates.
- Surge and standby — how burst and reactive cover fits alongside planned programmes.
4. Platform and evidence
The product direction is a single place to defend the programme: portfolio health (sites in flight, SLA risk, blockers) and exportable evidence — RAMS lineage, engineer certifications as-of job date, photos and sign-offs, history — for internal compliance and customer audit. Capabilities evolve with the live platform; we describe production behaviour honestly in diligence.
5. Single accountable partner
- Named engagement — a clear owner for dispatch, escalation, and customer communications (no ambiguity between “software” and “service”).
- Escalation — severity levels, response times, and ownership of rework or disputes.
6. Commercial clarity
- Engagement models — surge blocks, retained capacity, per-job; what is in and out of scope; how variations are handled.
- Invoicing — milestones tied to delivery so programme leads can see revenue and cost at risk when dispatch slips.
7. Integration with your world
- Data handover — exports and reporting cadence that drop into Tier 1 and MNO packs without re-keying.
- Pilot-friendly — bounded pilots with agreed success metrics (see below).
Who to involve on your side (stakeholder map)
Enterprise buyers move faster when the right people are in the room from the first serious call. Typical roles:
| Concern | Typical owner | Often signs |
|---|---|---|
| Programme delivery, SLAs, surge capacity | Programme / project lead, ops director | Commercial agreement (with procurement) |
| Insurance, liability, contract schedules | Procurement, legal, commercial | Full framework schedules, NDAs, liability caps |
| RAMS, site safety, audit evidence | HSEQ / H&S | Methodology and governance addenda |
| Data, access, subprocessors | IT / information security | DPAs, technical controls |
| Network / customer narrative (MNO) | Customer-facing programme office | Customer-facing reporting (often Tier 1) |
Tip: identify who can sign liability and insurance schedules early — that is the usual gate for greenfield Tier 1 deals.
Pilot scope (recommended starting point)
UK-wide strategic intent is compatible with a bounded first pilot that proves the model before scale:
- Geography — one or two adjacent regions (or a defined site list) for the first 8–12 weeks, with explicit criteria to expand UK-wide.
- Accreditation mix — agreed upfront (e.g. MATS tower, reactive standby, PPM only); instant “no” if we cannot demonstrate depth in the classes you need — state those classes in the workshop.
- Volume — a minimum number of jobs or days per month so both sides can judge schedule adherence and evidence quality.
Integration depth (year one)
Default for year one: client and ops visibility (dashboard-style views where deployed), structured exports, and a regular reporting cadence (e.g. weekly or monthly) for programme and procurement. That usually satisfies QBRs and audit without a heavy integration project.
Phase two (as needed): deeper integration with ticketing, asset, or workforce systems — scoped after the pilot when data flows and ROI are clear.
Month-one success metric (alignment)
Pick one primary metric that your internal stakeholders will defend politically; we recommend:
- Primary: SLA adherence (or agreed response / completion window) on pilot jobs, plus evidence pack completeness (RAMS lineage, certs as-of date, sign-offs) — together they prove both operational and governance value.
- Secondary: first-time fix or rework rate, schedule adherence, and cost vs prior agency baseline — tracked from the same pilot data.