01Executive Overview

Workforce operations,
compliance and shift
fulfilment - one platform.

Connex OS modernises how compliant logistics drivers are onboarded, matched, deployed, managed and paid. This proposal defines the MVP, the pilot workflow, the delivery plan and the commercial terms.

Single-tenant pilotUK PAYE modelEnterprise complianceAudit-ready workflows
Field-first operations
Compliant drivers, deployed and evidenced.

Prefer to comment as you read? .

The platform

Three products. One shared platform.

Driver Mobile Application

Onboard, discover, book, execute and get paid.

Client Operations Portal

Post demand, manage sites, approve timesheets.

StaffCo Direct Admin Console

Verify, allocate, resolve, invoice, evidence.

Shared Platform Infrastructure
02The Opportunity

Compliant logistics work still runs on phone calls and spreadsheets.

Fill rate leaks, payroll rework and audit exposure all trace back to the same cause: the operating model is manual, fragmented and un-evidenced. Connex OS is the operational layer that fixes it.

How it works today

  • Phone calls
  • Spreadsheets
  • Manual document checks
  • Email shift confirmations
  • Manual timesheets
  • Disconnected payroll handover
  • Manual compliance evidence retrieval

With Connex OS

  • Driver notifications
  • Structured onboarding
  • Verification workflows
  • Digital booking
  • Geofenced attendance
  • Payroll-ready data
  • Per-booking evidence ledger
03· Project Objectives

What the pilot must achieve.

Six commitments that define what MVP means for Connex OS.
O01
Digitally verified drivers

Onboard a controlled cohort of compliant drivers with a fully digital identity, RTW, licence and PAYE trail.

O02
Real client demand

Publish live shifts from a paying enterprise client under contract for the pilot.

O03
Reliable fulfilment

Match eligible drivers to eligible shifts and evidence attendance on site.

O04
Clean payroll handover

Produce a deterministic, validated payroll batch for StaffCo every cycle.

O05
Audit-ready evidence

One retrievable evidence bundle per booking within the pilot SLA.

O06
Commercial validation

Prove unit economics with real data ahead of a broader release.

04Proposed MVP Solution

Three product environments on one shared platform.

Each product surface is scoped to a role; each depends on the same shared platform so that compliance, evidence and payroll stay consistent.

Driver Mobile Application

Confirmed MVP

The driver's daily operating system - onboarding, shifts, attendance, timesheets and earnings.

Primary users
Compliant HGV / logistics drivers on PAYE.
Device
Mobile (iOS + Android via responsive PWA for pilot)
Key capabilities
  • Digital onboarding
  • Shift discovery & booking
  • Walkaround
  • Clock in / out
  • Timesheets
  • Earnings

Client Operations Portal

Confirmed MVP

Where enterprise clients post demand, run live operations and approve timesheets.

Primary users
Client site managers, ops teams and finance.
Device
Web (desktop-first, tablet-optimised)
Key capabilities
  • Site setup
  • Shift templates
  • Live operations
  • Timesheet approval
  • Invoices
  • Evidence access

StaffCo Direct Admin Console

Confirmed MVP

The operational control plane for the StaffCo team.

Primary users
StaffCo operations, compliance, finance.
Device
Web (desktop-first)
Key capabilities
  • Driver & client pipelines
  • Rate cards
  • Live board
  • Disputes
  • Payroll prep
  • Evidence

Shared Platform Infrastructure

Confirmed MVP

The horizontal capabilities every product depends on.

Primary users
All products - invisible to end users.
Device
Cloud services (AWS preferred, subject to discovery)
Key capabilities
  • Identity
  • Matching & eligibility
  • Notifications
  • Evidence bundles
  • Payroll handover
  • Audit
05Platform Architecture

A five-layer architecture - click any layer to explore.

A conventional, defensible enterprise architecture. Technology choices below reflect our current recommendation and remain subject to Phase 1 Technical Discovery.

PostgreSQL, object storage, caching and event-driven services are the current technical recommendation. Final technology choices are subject to Phase 1 Technical Discovery. AWS is the currently preferred environment; final cloud architecture is subject to discovery.

06Detailed Scope of Work

Every module, by role, with MVP status.

Use the tabs to switch between roles. Each module lists purpose, capabilities, responsible role, MVP status, dependencies and exception states where relevant.

Onboarding & Compliance

Shift Discovery & Execution

07· Shared Platform Systems

The horizontal capabilities every product depends on.

These systems are why compliance, evidence and payroll can stay consistent across the three product surfaces.
Authentication
Confirmed MVP

Identity for drivers, clients and admins.

Role-Based Access
Confirmed MVP

Least-privilege access per tenant, site and role.

Eligibility Engine
Confirmed MVP

Only present shifts a driver is actually eligible for.

Matching & Allocation
Expected MVP

Order eligible drivers by suitability for a shift.

Pricing Engine
Confirmed MVP

Apply the right rate to the right booking.

Notifications
Confirmed MVP

Reliable multi-channel messaging.

Geofencing
Confirmed MVP

Validate presence on site at clock events.

Digital Timesheets
Confirmed MVP

Structured attendance record ready for approval.

Payroll Handover
Confirmed MVP

Deterministic export to StaffCo payroll.

Invoicing
Confirmed MVP

Convert approved shifts into client invoices.

Ratings
Confirmed MVP

Structured post-shift feedback both ways.

Disputes
Confirmed MVP

Formal issue lifecycle with evidence.

Evidence Bundles
Confirmed MVP

One per booking: everything auditors need.

Consent Records
Confirmed MVP

Immutable log of consents given and withdrawn.

Audit Logging
Confirmed MVP

Who did what, when, from where.

Document Storage
Confirmed MVP

Secure storage for compliance and evidence documents.

Reporting & Observability
Expected MVP

Operational and commercial visibility.

Support
Expected MVP

Route in-app requests to the right team.

08· Integrations

The third-party services that make the pilot possible.

Every integration below has a purpose, an MVP importance and an auditable manual fallback.
IdentityRequired
Identity Provider (Onfido / Yoti / Didit)

Digital ID document capture and liveness.

Vendor status
Selection during Phase 1
Dependency
Enables digital onboarding
Manual fallback
Admin-led manual verification
Third-party cost
Per-check third-party fee, billed to client
ComplianceRequired
Home Office Right to Work

Verify share codes and record RTW status.

Vendor status
Public share-code endpoint
Dependency
Required for eligibility
Manual fallback
Manual admin verification
Third-party cost
No fee (public service)
ComplianceRequired
Licensed DVLA Reseller

Verify driving licence entitlements and endorsements.

Vendor status
Selection during Phase 1
Dependency
Required for licence eligibility
Manual fallback
Admin review of driver-supplied evidence
Third-party cost
Per-check fee
ComplianceRequired
JAUPT / Approved CPC Source

Confirm CPC status and hours.

Vendor status
Public / approved source
Dependency
Required for HGV eligibility
Manual fallback
Manual capture of Driver Qualification Card
Third-party cost
No fee / per-check where applicable
CompliancePreferred
DBS Provider

Basic / Standard checks where required by client.

Vendor status
Selection during Phase 1
Dependency
Client-driven requirement
Manual fallback
Not required for pilot cohort
Third-party cost
Per-check fee
Client onboardingRequired
Companies House

KYB and company data on client onboarding.

Vendor status
Public API
Dependency
Feeds admin-led onboarding
Manual fallback
Manual data entry
Third-party cost
No fee
CompliancePreferred
Vehicle Operator Licensing Register

Validate client operator licence where applicable.

Vendor status
Public register
Dependency
Confirms client legitimacy
Manual fallback
Manual admin check
Third-party cost
No fee
Client onboardingOptional
Credit Bureau

Assess client credit for invoicing terms.

Vendor status
Selection during Phase 1
Dependency
Commercial risk control
Manual fallback
StaffCo internal risk process
Third-party cost
Per-check fee
Client onboardingRequired
E-Signature Provider

Signed client contracts and driver declarations.

Vendor status
Selection during Phase 1
Dependency
Contract enforceability
Manual fallback
PDF + email signature
Third-party cost
Per-envelope fee
LocationRequired
Address & Postcode Service

Accurate site and driver address capture.

Vendor status
Selection during Phase 1
Dependency
Site setup and RTW address matches
Manual fallback
Free-text with admin validation
Third-party cost
Per-lookup fee
LocationRequired
Google Maps / what3words

Site geofencing, routing and place capture.

Vendor status
Standard commercial API
Dependency
Powers geofencing and site brief
Manual fallback
Manual polygon capture
Third-party cost
Usage-based fee
CommunicationsRequired
Twilio + WhatsApp Business

Reliable SMS, WhatsApp and OTP delivery.

Vendor status
Provisioned during Phase 1
Dependency
Driver reachability
Manual fallback
Email-only notifications
Third-party cost
Per-message fee
PayrollRequired
StaffCo Payroll System

PAYE payroll for verified drivers.

Vendor status
Existing StaffCo system
Dependency
Deterministic file / API handover
Manual fallback
Manual batch import
Third-party cost
No third-party fee
CommunicationsRequired
Email Provider

Transactional email at scale.

Vendor status
Selection during Phase 1
Dependency
Notifications and audit trail
Manual fallback
SMTP relay
Third-party cost
Usage-based fee
InfrastructureRequired
Cloud Storage

Encrypted storage for compliance and evidence documents.

Vendor status
AWS preferred, subject to discovery
Dependency
Backs document storage and evidence bundles
Manual fallback
N/A
Third-party cost
Consumption-based
InfrastructureRequired
Monitoring Platform

Logs, metrics, traces, error reporting.

Vendor status
Selection during Phase 1
Dependency
Operational SLA
Manual fallback
Cloud-native tooling
Third-party cost
Subscription
InfrastructurePreferred
Feature-Flag Platform

Controlled release and safe deferral of parked features.

Vendor status
Selection during Phase 1
Dependency
Governs deferred functionality
Manual fallback
Config-file flags
Third-party cost
Subscription

The final integration approach, sequencing and implementation priority will be confirmed during Phase 1 Technical Discovery. Where a service is unavailable or introduces unacceptable delivery risk, Keza Studio may recommend an auditable manual or administrative alternative for the pilot release.

09

What's in, what's out, and what's parked.

Scope Boundaries & Deferred Features

Radical honesty about scope is how the pilot ships. Everything below is decided - not undecided.

Included in MVP

Everything scoped in Sections 04–07 - the three product surfaces and the shared platform systems required to run the pilot workflow end-to-end.

Deferred capabilities
  • Multi-tenant activation
  • Fully self-service client onboarding
  • Machine-learning matching
  • Continuous live driver tracking
  • Real-time HMRC RTI
  • Automated digicard parsing
  • Voice AI agents
  • Full TMS integrations
  • Advanced driver tiering
  • Automated sub-two-hour audit exports
  • Client mobile application
  • US functionality
  • Predictive analytics
  • Public third-party API

Parked products

Parked
FlexPay

On-demand access to earned wages ahead of the normal payroll cycle.

Excluded
Wallet, on-demand disbursement, fee logic, lender / partner integrations.
Why parked
Regulatory review, partner selection and treasury design required - out of pilot scope.
Prototype
Prototype screens may be retained behind disabled feature flags for future activation.
Parked
Driver Protection

Optional insurance and protection products offered to drivers in-app.

Excluded
Underwriting, claims handling, price comparison, third-party product feeds.
Why parked
Distribution and regulatory positioning to be defined post-pilot.
Prototype
Prototype screens may be retained behind disabled feature flags.
Parked
Refer & Earn

Structured driver-to-driver referral programme with rewards.

Excluded
Reward wallet, fraud rules, cross-tenant referral, campaign management.
Why parked
Requires validated referral economics from pilot cohort data.
Prototype
Prototype screens may be retained behind disabled feature flags.

Training - a focused compliance module, not an LMS

MVP training is a focused embedded learning and compliance module. It is not a full LMS.

Included
  • · Training records
  • · Required courses
  • · Site induction
  • · Video or hosted content
  • · Duration
  • · Completion acknowledgement
  • · Completion status
  • · Renewal dates
  • · Admin assignment
  • · Compliance reporting
Excluded
  • · Full course-authoring suite
  • · SCORM ecosystem
  • · Complex exams
  • · Instructor management
  • · Certificate marketplace
  • · Detailed LMS analytics
  • · External training-provider commerce
10Delivery Strategy

The pilot-critical workflow, end-to-end.

Eleven steps take a driver from application to a fully evidenced, paid, invoiced booking. Every step below has a responsible user, inputs, actions, output, next state and a defined exception path.
Step detail
Driver Onboarding
Responsible user
Driver + Admin
Application
Driver App + Admin Console
Inputs
Personal & PAYE details, ID documents, RTW, licence, CPC
Actions
Digital capture, provider verification, admin review
Output
Verified driver account
Next state
Compliance Clearance
Potential exception
Failed check routes to admin review with reason
11Development Process

Six commercial delivery phases - executed asynchronously.

The phases describe principal commercial and delivery activities - not rigid waterfall gates. Approved work may progress asynchronously: frontend can begin on approved screens while later designs continue, and backend, frontend and QA may overlap. Detailed feature allocation and sprint sequencing are finalised after Phase 1.
P11–2 weeks
Mobilisation & Technical Discovery

Confirm architecture, integrations, environments, tenants and delivery plan.

  • Kick-off & governance
  • Technical discovery
  • Integration selection
  • Delivery plan
P22–4 weeks (overlapping)
Branding & UX/UI Design

Design the three product surfaces to a signed-off standard.

  • Design system
  • Driver, client and admin flows
  • Prototype reviews
  • Sign-off gates
P3Progressive
Frontend Development & Code-Based Prototype

Progressive build of approved screens across the three surfaces.

  • Approved-first delivery
  • Component library
  • Wired prototype
  • Iteration in-flight
P4Runs alongside frontend
Backend Development & Integration

Domain services, data model, third-party integrations and events.

  • Domain services
  • Data & migrations
  • Integrations
  • Event & audit
P52–3 weeks
QA, UAT & Bug Fixing

Systematic testing and structured client acceptance.

  • QA plan
  • Regression
  • UAT windows
  • Defect triage
P64 weeks
Launch, Monitoring & Early-Life Support

Pilot cut-over, active monitoring and hyper-care.

  • Cut-over plan
  • Runbook
  • Monitoring
  • Hyper-care support
12· Testing, Security & Compliance

The controls that make the pilot audit-ready.

Grouped by domain. Every item is a control we plan to implement or an obligation we design towards.

Data Protection

Encryption in transit

TLS 1.2+ across every client, service and integration boundary.

Encryption at rest

Managed encryption for databases, object storage and backups.

Protected document access

Signed, time-limited URLs; no public buckets.

Access

Secure OTP & password handling

Rate-limited OTP, hashed passwords, credential rotation policies.

Multi-factor authentication

Enforced for admin and client-admin roles from day one.

Least privilege

Role- and site-scoped access; production access is exceptional and logged.

Secret management

Central secret store; no secrets in code or CI logs.

Operations

Audit logging

Structured, retained audit events across privileged actions.

Rate limiting

Per-endpoint and per-tenant limits to prevent abuse.

Input validation

Schema-validated inputs across API and background workers.

Dependency scanning

Automated dependency and container scanning in CI.

Security testing

Static and dynamic scanning in CI; targeted manual testing.

Resilience

Backups & restore

Automated backups with periodic restore drills.

Incident logging

Structured incident capture and post-incident review.

Penetration testing

Subject to the commercial schedule; recommended pre-scale-out.

Regulatory

UK data residency

UK region hosting; deviations require documented approval.

Consent history

Versioned, retrievable consent records per user.

DSAR

Data-access request workflow and response tooling.

Secure deletion or anonymisation

Applied to right-to-erasure requests and retention triggers.

UK GDPR

Design and process aligned to UK GDPR obligations.

Employment

Agency Workers Regulations

Structured data supporting AWR obligations.

PAYE

Clean handover to StaffCo PAYE payroll.

Pension auto-enrolment

Declarations captured for downstream enrolment.

Sector

DVLA & DVSA

Structured evidence capture aligned to sector expectations.

Right to Work

Share-code capture, expiry tracking and audit trail.

Working-time rules

Eligibility engine surfaces working-time considerations.

Client evidence requirements

Per-booking evidence bundles retrievable within pilot SLA.

Legal and regulatory interpretation remains the responsibility of the client's legal and compliance advisers. Keza Studio implements controls and workflows as agreed and does not provide legal advice.

13· Project Management & Governance

Cadence, roles and change control.

Decisions on paper, at the right level, at the right cadence.
CadenceAttendeesFocus
Weekly Gary / Project Lead + Keza StudioDelivery, blockers, scope and budget
Fortnightly Keza Studio + StaffCo operations & complianceProduct demonstration and operational readiness
Monthly Board / executive stakeholdersMilestones, risks, spend and decisions
As required Anchor-client representativesPilot-site requirements and readiness

14Indicative Timeline

A conditional path to the October pilot launch.

The bars below are indicative. Sequencing is finalised after Phase 1.
P1Mobilisation & Technical Discovery
1–2 weeks
P2Branding & UX/UI Design
2–4 weeks (overlapping)
P3Frontend Development & Code-Based Prototype
Progressive
P4Backend Development & Integration
Runs alongside frontend
P5QA, UAT & Bug Fixing
2–3 weeks
P6Launch, Monitoring & Early-Life Support
4 weeks

The client's target pilot launch at the end of October is conditional upon prompt contract award, immediate access to the codebase and documentation, stakeholder availability, timely approvals, vendor access, stable APIs, limited review cycles and no material scope change.

15

What Connex must supply for the pilot to land on time.

Client Responsibilities & Dependencies

Delivery is a two-team sport. The commitments below are the client-side inputs the timeline depends on.

Timely decisions

Nominated decision-makers with authority to approve within agreed review cycles.

Access to codebase & docs

Immediate handover of the existing Lovable Proof of Concept and supporting documentation.

Vendor access

Introductions and account access for identity, DVLA, communications, e-signature and payroll vendors.

Pilot cohort

Nominated driver cohort and anchor-client sites available for onboarding and live shifts.

Content & policy

Client-supplied content for training, site inductions, terms of use, privacy notices and consent copy.

Data & migrations

Any legacy data required for the pilot, in an agreed format.

Stakeholder availability

StaffCo operations, compliance and finance available for the agreed governance cadence.

16

Three-month post-launch warranty; optional maintenance thereafter.

Warranty & Ongoing Support

Warranty covers reproducible defects in the agreed functionality. Anything new, changed or externally caused sits outside - with a separate optional maintenance path.

Covered
Three-month warranty

Reproducible defects in agreed functionality delivered at pilot launch.

Not covered
  • New features
  • Workflow changes
  • Third-party outages
  • Regulatory changes after acceptance
  • Unauthorised modification of the code
Optional ongoing maintenance

A separate, optional maintenance agreement can cover proactive monitoring, security patching, dependency updates, minor enhancements and continued responsive support. Scope and pricing are agreed separately at pilot acceptance based on observed operational load.

17Investment

Three payment options, one clear scope.

Prices include VAT. Third-party pass-through fees are separate. Choose the option that best fits your finance rhythm.
Before pricing

What Connex OS could return, at your scale

Your inputs

Model the impact for your operation

Tune the assumptions to your data. Numbers update live.

120 vehicles
180 drivers
8 per month
£4,200
60 per week
Your projected impact

What Connex OS unlocks for you

Projected annual saving
£240,960
Payback
1.7 mo
3-year net value
£621k
Hours reclaimed
2,184

Assumes 35% incident reduction from evidence-first workflows and a £32 blended hourly rate for reclaimed compliance admin. Platform cost approximated by fleet tier. Talk to us to model against your actuals.

Best value
Option
100% Upfront
£22,185incl. VAT

One payment at contract signature - lowest overall project cost. VAT included.

  • At contract signature£22,185
Option
50 / 50
£24,403.50incl. VAT

Two equal payments across the engagement.

  • Payment 1 - contract signature£12,201.75
  • Payment 2 - mid-engagement milestone£12,201.75
Option
Six Equal Milestones
£26,843.85incl. VAT

Six commercial milestones aligned to the delivery process.

  • Initial & mobilisation£4,473.98
  • UX/UI design£4,473.98
  • Frontend development£4,473.98
  • Backend & integrations£4,473.98
  • QA testing£4,473.98
  • UAT & completion£4,473.95
Commercial terms
  • All prices include VAT.
  • Third-party fees (identity providers, DVLA, communications, cloud, e-sign, etc.) are excluded and passed through.
  • Each staged invoice is payable within five business days unless otherwise agreed.
  • Billing milestones are commercial milestones, not rigid technical gates.
  • Workstreams may progress asynchronously - invoicing follows the agreed schedule regardless of internal sequencing.
18· Why Keza Studio

How we deliver - and why Connex chose us.

A single accountable team that has already been inside the codebase.
Enterprise craft

We build regulated, workflow-heavy products for teams who cannot afford to hand-wave the details.

Full-stack delivery

Discovery, design, frontend, backend, QA and launch - a single accountable team.

Async by default

We overlap workstreams so approved decisions become shipped software immediately.

Grounded in the codebase

We are already familiar with the existing Lovable Proof of Concept and will extend, not restart.

Governance without theatre

Weekly delivery, fortnightly product demos, monthly executive updates - decisions on paper.

Skin in the game

We commit to the October pilot conditionally and transparently, with clearly defined dependencies.

19· What Launch Unlocks

The commercial and operational value the pilot enables.

Every capability below becomes real the day the pilot goes live.
Unlock 01
Onboard a controlled driver cohort
Unlock 02
Verify drivers digitally
Unlock 03
Publish real client demand
Unlock 04
Fill shifts
Unlock 05
Record attendance
Unlock 06
Generate timesheets
Unlock 07
Complete payroll handover
Unlock 08
Generate invoices
Unlock 09
Resolve disputes with evidence
Unlock 10
Demonstrate to enterprise stakeholders
Unlock 11
Measure fill rate
Unlock 12
Collect user feedback
Unlock 13
Validate commercial assumptions
Unlock 14
Plan later releases using real data
20Closing Statement

Connex OS can become the operational layer for compliant logistics workforce.

Driver compliance, enterprise demand, live shift execution, payroll, invoicing and audit evidence - connected.

The pilot is a proving ground. Connex OS turns a fragmented, phone-and-spreadsheet operation into a defensible, evidenced and scalable platform - starting with a single anchor client, and designed from day one for the shape of the business you're building.

Schedule proposal review
Connex OS - MVP Product Design, Development & Pilot-Launch Proposal · Draft v1.0 · Prepared by Keza Studio. Confidential.