LIFT is a Cumbria-only ride-hailing platform extended into hyperlocal produce delivery, safeguarded school carpools, and pre-booked late-night returns for young people. Every driver is licensed by Cumbria Council. Every fare stays inside the county. Every safeguarded ride is escrow-held until the right human confirms safe arrival. This document is the complete platform overview prepared for Cumberland Council leadership.
LIFT is not another ride-hailing app. It is a Cumbrian transport platform, built by Cumbrian people, designed to keep Cumbrian money in Cumbria. The four things below are why it matters to Cumberland Council in particular.
Every driver holds a current Cumbria Council taxi or PHV licence, checked manually against the council ledger before they can take a single fare. We do not onboard drivers from outside the county. Ever.
National platforms take 25 to 30 percent of every fare and ship it to a head office a long way from here. LIFT takes 10 percent. The remaining 90 percent goes to a driver who lives in the county and spends here.
School pools require Enhanced DBS and a 2-year renewal cycle. Capacity is hard-locked at the database. Fares stay in escrow until a school agent confirms safe arrival. Safe Return wellness-escalates to the parent if a young person does not respond.
We will share anonymised journey data with the council on request, integrate licence-revocation events into our suspension flow, and host school agents on the admin dashboard at no cost. The platform is ready for production today.
Four problems have run unchecked here for too long: late-night riders stranded by an app that closed at 9pm, school runs that look like motorway queues, supermarkets shipping milk back through its own valley, and families paying four hundred pounds a month for a car that sits on the drive five days out of seven. The drivers were always here. The platform that gets out of their way was not.
Local drivers see your request the second you post it. Any of them can bid their own price and ETA. No dispatcher to call. No engaged line. No thirty-minute estimate that turns into ninety.
Carpool with neighbours within 1.5 miles, in a vehicle driven by an Enhanced-DBS-verified driver. Forty cars doing the work of eight, becomes eight. Fares held in escrow until safe arrival.
Order direct from the farm a mile from your house. The same Cumbria-licensed driver doing your taxi run can collect on the way. Money stays in the county. Fuel stays in the tank.
Use LIFT for the predictable trips (school run, weekly shop). Keep the car for what you actually need it for. Three families sharing a pool can keep around a thousand pounds a year in each household.
The Cumbria boundary is hard-coded into the database as a polygon. Any pickup or dropoff outside it is rejected at insert time, before a driver is ever notified. This is the operational footprint LIFT serves: the whole historical county, both new unitary authorities, every town and every fell.
The four streams below are built, committed to the repository, and ready for production. The eight in the next section are modelled extensions that use the same drivers, the same trust scaffolding, and the same Cumbria-only geofence. Each shipped stream has its own state machine, its own pricing model, and its own escrow profile.
Bidding model. Riders post trips, nearby drivers bid their own price and ETA, riders pick. Standard / XL / Estate / WAV / Executive. Scheduled up to 4 weeks ahead.
Drivers earn 30 to 50% more per fare versus national platforms. 10% platform feeFarms catalogue. Eggs, milk, cheese, vegetables, bread, meat. Order direct from the producer. Same driver collects from the farm and brings it to your door in your slot.
Producers paid directly, no national distributor margin. 10% platform feeCarpool to school with neighbours within 1.5 miles. Enhanced-DBS-verified drivers only. Capacity hard-locked at the database. Fares in escrow until safe arrival.
Estimated 80% reduction in solo-parent school-run cars. 10% + escrow holdPre-book a guaranteed driver on standby for a young person going out. Cutoff time, gentle prompts, one-tap I am ready. Wellness escalation if they do not respond.
Built to remove the late-night taxi gap entirely. £5 reservation + ride fareThe same driver pool, the same trust stack, the same Cumbria geofence can underwrite eight additional service streams. Each one solves a specific structural rural-transport gap the existing market does not. Phase 2 streams are partner-led (NHS, employers, refuges, schools); Phase 3 streams add seasonal and niche volume. None require core architecture changes. They ride on the same backbone.
Pre-booked recurring rides to GP appointments, hospital outpatient visits, day centres, dialysis. Uses the existing DBS-verified driver pool. WAV filtering already in the vehicle profile. Could be NHS-commissioned or paid through Cumbria Adult Social Care budgets. Partner: NHS Cumbria ICB.
Group transport from rural villages to major employers (Sellafield ~10,000 staff, BAE Barrow, NHS Cumbria Trust, council offices). School pool mechanics applied to adult commuters. Employer-subsidised. Direct fix for the rural workforce mobility gap.
Premium pre-booked tier for tourism. Hotel-to-trailhead drop-offs, end-of-walk pickups (drop me at Helvellyn, collect me at Patterdale), pub circuits, stargazing tours. Higher fares, lower volume, fills driver gaps in shoulder hours. Partner: Cumbria Tourism.
Same-day B2B parcel pickup-and-deliver for pharmacies → patients, florists → recipients, hardware shops → tradesmen. Drivers idle between fares pick up small parcels. Different commercial structure: B2B billing, recurring routes.
Partnership pathway with Cumbria refuges and domestic-abuse support services for safe, traceless moves. DBS-checked drivers trained for the specific safeguarding protocols, encrypted routing, no record on the standard ride trail. Partner: Women's Community Matters, Carlisle Refuge.
Daily luggage transfer between B&Bs for walkers and cyclists doing the Coast-to-Coast or Lake District tours. The C2C walk is a £20m/year Cumbrian tourism flow. £15 to £20 per bag, predictable daytime work for drivers, fills shoulder hours.
Surge-demand operation for Appleby Horse Fair, Keswick Mountain Festival, Lake District triathlons, weddings, funerals. Coordinated fleet for one-time peaks with pre-allocated drivers and surge-priced bidding within a per-event cap.
Vet visits, kennel transfers, grooming pickups. Particularly for elderly pet owners and households without a car. Cleaning protocol between rides, vehicle-feature tagging for pet-friendly drivers already in the vehicle profile.
There are other taxi-dispatch apps starting up around the county. They are useful and they are local. They are also not what LIFT is. The seven structural differences below are where LIFT is operationally distinct from anything else serving Cumbria today, and why those differences matter to Cumberland Council, to parents, and to drivers in particular.
Other platforms hand the trip to the nearest available driver at a fixed fare. LIFT lets every driver in range bid their own price and ETA. The rider picks by price, by speed, or by driver rating. That difference is the whole reason riders can find a driver at half past eleven on a Friday.
A typical Cumbrian taxi-firm model leaves the driver with 65 to 75% of the fare after the firm and the platform both take their cut. On LIFT, drivers are independent and keep 90% of every fare. They can stay with their existing firm if they want; LIFT has no exclusivity clause and no lock-in.
Capacity mutex, DBS gate, state machine triggers, Row-Level Security, Cumbria geofence, escrow until safe arrival. These are not features in the application; they are constraints that the application cannot bypass. The database physically rejects an out-of-county pickup, an over-capacity school pool, or a DBS-expired driver bid.
The other platforms in the county offer one stream: taxi rides. LIFT offers taxi, hyperlocal delivery, safeguarded school pools, and Safe Return today. NHS patient transport, workplace shuttles, and the tourist circuit are next on the roadmap. The same drivers, the same trust scaffolding, the same Cumbria geofence underwrite all of them.
The Cumbria boundary is a polygon in the database. Out-of-county trips are rejected at insert time. Other apps expand to the next city the moment local volume drops; LIFT is contractually and architecturally Cumbrian. It will not become a national platform.
Licence ledger integration, revocation webhook, anonymised journey data on request, free school agent admin access. Most platforms treat the council as an obstacle to be navigated around. LIFT treats the council as the partner whose blessing makes the whole thing more credible.
LIFT is privately built and self-sustaining at modest pilot volumes. No venture capital, no Series A clock, no growth pressure to expand out of the county to make a return on capital. The platform exists to be the long-term Cumbrian utility, not the next acquisition target.
Capability-by-capability comparison with the platforms typically serving the county. No competitor names; the structural differences speak for themselves.
| Capability | LIFT | What other Cumbrian apps typically offer |
|---|---|---|
| Pricing model | Driver bidding (rider picks price, ETA or rating) | Nearest-driver allocation at fixed fare |
| Driver share of fare | 90% (independent driver, no firm cut) | 65 to 75% (firm cut + platform cut) |
| Vetting depth | Cumbria licence + Enhanced DBS + 2-year renewals + manual ledger check | Council licence only |
| Payment safeguarding | Stripe escrow with manual capture on school + Safe Return | Auto-charge on completion |
| Streams supported | Taxi · Delivery · School Pools · Safe Return (+8 roadmap) | Taxi only |
| Geofence | Cumbria polygon, enforced at the database | None (will expand outside Cumbria over time) |
| Capacity safety | Database mutex: a 4-seat car cannot carry a 5th child | Application code, not enforced at DB level |
| State machine | BEFORE UPDATE triggers per domain; invalid transitions raise | Application code |
| Data sharing with council | Built-in (anonymised journey data on request) | Not offered |
| Funding model | Self-sustaining, privately built, no VC | Often VC-backed with exit timelines |
LIFT was built for independent Cumbria Council licensed drivers. It works equally well for drivers who already belong to a local firm. There is no exclusivity. There is no non-compete. There is no lock-in.
A firm can keep its own dispatch system AND let its drivers take LIFT jobs on the side. The platform fee is the same 10% either way, and the driver keeps the same 90%. A driver does not have to choose between a firm and LIFT; they can do both. Many will, particularly to fill quieter hours with the streams the firm does not handle (school pools, Safe Return, delivery).
For firms that want to bring their drivers onto LIFT as a fleet, Phase 2 includes a firm partnership tier: bulk driver onboarding with an aggregated firm dashboard, optional co-branding, and a per-driver referral payout. No firm is excluded from the platform because of a competing relationship; the goal is to have every Cumbria-licensed driver on it.
Tap a stream below to walk through its feature categories. Each card groups the primitives that make up a single user journey, with the underlying tech surface listed beneath.
The rider posts the trip. Every Cumbria-licensed driver within 5km sees it live on their phone. The one who wants the job bids. Usually under 30 seconds. The atomic accept_bid RPC makes double-assignment impossible.
The rider's first 30 seconds in the app.
Pickup, drop-off, preferences, scheduling.
From request to accepted bid in seconds.
From acceptance to drop-off.
Stripe Connect Express, 10% platform fee.
Every active ride has the same protective stack.
The same Cumbria-licensed drivers handle the hyperlocal logistics layer. The producer is paid directly. The driver collects from the farm gate and brings the order to your door in your chosen slot.
Farms catalogue and product detail.
Single-farm basket with slot selection.
Drivers in range see the order and bid.
Driver collects, transports, delivers.
Stripe pre-auth on order, capture on delivery.
Pool with neighbours within 1.5 miles. Driver is Enhanced-DBS-verified. Capacity is locked at the database level. Fares stay in escrow until the school confirms your child has arrived safely. Then 90% releases to the driver.
Profiles and registry.
PostGIS vector matching + consent quorum.
Drivers bid the total; system splits per parent.
Sequential pickup with proximity gates.
No double-booking, no over-capacity, no DBS gap.
Mid-route abort, no-shows, force cancel.
Rural Cumbria runs short on taxis after 11pm. Pre-book a guaranteed driver on standby until a cutoff you set. Your young person taps one button when they are ready. If they do not respond, you decide what happens next.
Dual-consent before any booking.
Pickup area, cutoff, max fare, auto-dispatch toggle.
Reservation fee + standby state.
Six scheduled notifications driven by cron.
Live location broadcast and ride creation.
Escalating, with one-tap actions throughout.
Drivers see taxi bids, school pool opportunities, Safe Return standby jobs, and delivery orders in one app. Onboarding is hand-vetted by LIFT before they can take a single fare.
Hand-checked against the council ledger.
5s standard, 2s during a school run, foreground service on Android.
Taxi bids, school bids, reservations, delivery orders.
Same screen pattern across taxi, delivery, school, SR.
Stripe Connect Express, instant payouts.
25 routes covering driver approvals, live rides, school pools, Safe Return wellness, payouts, family link safeguarding, audit. Mono palette, server-rendered, privacy-first throughout.
What ops watches at peak risk hours.
Two human-in-the-loop screens.
Leaflet, mono greyscale tiles, Realtime + polling fallback.
Three urgency buckets, earliest-cutoff first.
Schools, farms, products, slots, agents.
Everything provable, nothing hidden.
Every protection on the platform is enforced at the layer where it cannot be bypassed. Driver eligibility lives in the database. Capacity locks live in the database. State transitions live in the database. Application code can be wrong; the database will not let it through.
A polygon stored as a single-row geofence. Every insert of a pickup, dropoff, home, or anchor coordinate runs through is_inside_cumbria. Out-of-county trips are rejected before any driver is notified.
BEFORE UPDATE trigger on pool_memberships locks the pool row FOR UPDATE, counts approved members plus the new joiner, and raises CRITICAL_ERROR if the total exceeds the vehicle's licensed seat capacity.
Drivers cannot bid on a school pool unless drivers.dbs_verified is true AND dbs_expiry_at is in the future. Enforced both at RLS insert policy and on a separate row-level trigger.
Every domain (rides, orders, school pools, safe returns) has a BEFORE UPDATE OF state trigger that rejects any transition not in the defined diagram. Invalid transitions raise.
RLS on every table. Drivers cannot see other drivers' locations. Parents cannot see other parents' children. School agents only see their own school's pools and check-ins.
Safe Return requires a family_link with status='active'. Status can only transition to active by the young person themselves. Parent cannot self-link.
Every driver onboarding is checked by a LIFT operator against the Cumbria Council licence ledger before activation. No driver can take a single fare until manually approved.
School pool drivers submit Enhanced DBS certificate at onboarding. The admin DBS Queue tracks expiry with a 60-day warning band. Expired DBS auto-suspends pool eligibility.
School pool fares are pre-authorised on every parent card at acceptance and held with Stripe manual capture. Capture only fires when the school agent confirms the last child has arrived.
Single tap broadcasts live location to chosen trusted contacts and LIFT support, and dials 999. Confirmation modal prevents accidental triggers.
Rider and driver never see each other's personal mobile. Calls and messages route through the app. Same protection on family links.
If a ride goes off-course or stays stationary too long, the app prompts the rider and a chosen trusted contact. If they do not respond, ops gets a flag.
At cutoff the parent gets a notification with one-tap actions. At +30 and +60 minutes, escalating wellness checks fire automatically. Police welfare check is Phase 2.
Every admin action (driver suspension, force-cancel, family link revoke, manual welfare push, DBS verify) writes to admin_actions with the admin id, action, target, reason, and timestamp. Full provenance.
Young person initials in tables (never full names), full first name only on the detail screen, never photos in lists. Phone numbers are masked in admin UI.
A national platform exports 25 to 30 percent of every fare out of Cumbria. LIFT does not. The 10 percent platform fee stays at LIFT's Cumbrian operations, and the remaining 90 percent goes to a driver who spends inside the county. The projections below assume Phase 1 levels (1,000 active riders, 100 active drivers, 10 partner schools).
Modelled on 30 hours per week at the existing local fare structure, with the LIFT 10% fee instead of the 25 to 30% national fee. Direct cashflow back into Cumbrian households.
Three families sharing a daily school pool can cut their school-run fuel, parking and wear-and-tear by around a thousand pounds per household per year. School pool fares are split equally.
A 4-seat school pool absorbs the school run for 4 families. At full Phase 1 saturation (10 schools, 20 pools each), 800 cars become 200. Direct traffic and emissions reduction outside Cumbrian schools.
Average round-trip to a supermarket for a small grocery order. LIFT's hyperlocal delivery routes through the farm gate instead, eliminating the supermarket detour and the food-miles loop.
LIFT requires no funding or grant. The partnership cost to Cumberland Council is zero. The platform is privately operated and self-sustaining at 10% platform fee.
Phase 1 platform is built and committed to the repository today. Pilot launch readiness is gated only on Supabase production project provisioning, Stripe Connect activation, and EAS Build for the mobile app. ~2 weeks from go-ahead to first ride.
A three-year financial picture built on Phase 1 assumptions (10% platform fee, 90% to driver). Numbers below are deliberately conservative on volume and explicit on cost. The platform breaks even on Year 1 pilot volumes and turns a healthy operating surplus by Year 2 without external funding.
30 drivers at launch, ramping to 100 by Q4. 300 active riders ramping to 1,000. Three partner schools in Q1, ten by Q4. Three partner farms ramping to eight. £2.0m gross merchandise volume across the four streams.
| Annual GMV | £2,000,000 | Across taxi, delivery, school pools, Safe Return |
| LIFT gross (10%) | £200,000 | Application fee on every transaction |
| Stripe processing | (£50,000) | ~2.5% on GMV |
| Operations | (£120,000) | Hosting · ops · safeguarding · 2 FTE |
| Net operating surplus | £30,000 | Reinvested into Phase 2 expansion |
250 active drivers (approx 20% of the county licensed pool). 3,000 active riders. 25 partner schools. 20 partner farms. NHS Patient Transport pilot starts in Q3 (Phase 2 stream activation). £7.5m gross merchandise volume.
| Annual GMV | £7,500,000 | 4 shipped streams + NHS Patient Transport pilot |
| LIFT gross (10%) | £750,000 | Same application fee, 3.75x volume |
| Stripe processing | (£190,000) | ~2.5% on GMV |
| Operations | (£350,000) | 4 FTE + safeguarding ops 24/7 cover |
| Net operating surplus | £210,000 | Funds Phase 3 streams (workplace, tourist) |
400 active drivers (approx 30% of the county licensed pool). 6,000 active riders. 50 partner schools. 35 partner farms. Workplace shuttles + tourist circuit live (Phase 2 streams 2 and 3 activated). £14m gross merchandise volume.
| Annual GMV | £14,000,000 | 4 shipped + 3 active roadmap streams |
| LIFT gross (10%) | £1,400,000 | |
| Stripe processing | (£350,000) | |
| Operations | (£550,000) | 6 FTE + 2 safeguarding leads + ops infra |
| Net operating surplus | £500,000 | Phase 3 streams + reinvestment + reserves |
Stacked by destination: driver income (the bulk), LIFT operating revenue (10%), Stripe processing (~2.5%). Driver income is Cumbrian household income; LIFT operating revenue is spent inside the county on staff, hosting, and safeguarding.
Per-transaction breakdown for each of the four shipped streams. These are the unit economics that scale linearly with volume.
Average taxi fare across Standard and XL tiers.
4 children at £5 per child, daily morning run.
Average produce order with hyperlocal delivery fee.
Reservation captured on driver claim; ride only on dispatch.
Modelled on a driver running 25 active hours per week, 48 weeks per year, with the local fare mix. The headline difference is the platform fee (10% vs 25 to 30%).
The sum of money cycled through Cumbrian households and businesses, modelled on the Year 1 to Year 3 projections above. None of this leaves the county.
Total transaction volume cycled through the platform over the 3-year window. Of which £20.4m is direct driver income and £6m is direct producer income (delivery side).
Cumulative income paid directly to Cumbria Council-licensed drivers who live in the county. Every pound spent inside Cumbria, not in a city head office.
Cumulative direct payment to Cumbrian farms and producers via the delivery vertical. Bypasses national distributor margin entirely.
No money leaves the county. LIFT operating revenue is spent on Cumbrian staff, hosting, and safeguarding. National platforms typically export £5m+ over the same window on the same volume.
Nothing. Zero pounds. LIFT is privately built, privately operated, and self-sustaining at modest pilot volumes. The Year 1 break-even point is reached at approximately 60 active drivers and 600 active riders, which is well inside the conservative pilot scenario.
The partnership ask is purely operational: licence ledger access, revocation feeds, and school pilot introductions. There is no procurement process, no grant application, no commercial obligation on the council. The platform exists to serve Cumbria and will continue to operate inside the county whether the council chooses to partner formally or not.
LIFT can run today without any council involvement. With it, it becomes a partnership that the council can point to as a regional model: licensed, safeguarded, transparent, audited, and provably local-first. Here is the partnership we propose.
The marketing site and the admin dashboard are deployed to Vercel against stable aliases. The backend and the mobile app are committed and reproducible but require an environment to deploy into. Roughly two weeks of provisioning stands between today and first paying ride.
15 sections, mobile drawer, directional gradient hero, photo-real Lake District footage, FAQ accordion. Vercel production at the stable alias.
25 routes, zero-state rendering when Supabase env missing. Vercel production. Wire to a Supabase project to see live data.
12 migrations + 25+ edge functions checked in. Run supabase db push and supabase functions deploy per docs/DEPLOYMENT.md.
Expo SDK 52, all four streams wired. Requires EAS Build with the secrets per the runbook.
expire-safe-return, wellness-escalate, send-safe-return-prompts. Schedule every minute via pg_cron (recommended), Vercel Cron, or GH Actions.
Set STRIPE_SECRET_KEY, STRIPE_WEBHOOK_SECRET in Supabase function secrets. Register the stripe-webhook endpoint in the Stripe dashboard.
Each item below is captured as a TODO in the code with a clear stub or feature flag. Phase 1 ships the working core; Phase 2 adds the things that need partner agreements or extended engineering time.
HMG access agreement is 3 to 6 months. Phase 1 is manual cert check. Phase 2 swaps in the API on a feature flag.
Safe Return prompts use Expo Push only in Phase 1. Phase 2 adds SMS for soft_nudge and last_call when the young person device is offline.
Wellness ladder caps at +60 min in Phase 1. Phase 2 adds a +90 min police welfare option behind admin feature flag with explicit opt-in.
School pools use admin-side check-in in Phase 1. Phase 2 adds a school terminal app with QR scanning at the drop-off zone.
School pool runs are manually fired by the driver in Phase 1. Phase 2 cron iterates matched pools whose days_of_week includes today.
Stripe pre-auth requires every parent to have a saved default_payment_method. Phase 2 forces card-on-file before pool approval.
Pick up your weekly produce shop on the way home. Schema discriminator already supports this (ride_kind = combined).
Wallet balance displayed in Phase 1, top-up screen is stubbed. Phase 2 wires Stripe Checkout for top-ups.
Loyalty balance accrues per spend. Redemption catalogue and partner business APIs are Phase 2.
Optional onboarding pathway for existing Cumbrian taxi firms: bulk driver registration, aggregated firm dashboard, co-branding, per-driver referral payout. Drivers stay with their firm AND take LIFT jobs.
LIFT operates inside UK GDPR (Data Protection Act 2018) and child safeguarding frameworks. Data minimisation is a design principle: we collect only what is required to operate each stream, retain it for the legally required period, and surface it on request through Subject Access Requests. The seven cards below are the operational posture.
Ride data is processed under contract (the rider has booked a ride). Marketing communications are under consent (opt-in only). Safeguarding logs are under legitimate interest. The lawful basis for each table is documented in the data map.
Ride records: 90 days for operations, 6 years for HMRC. Driver location samples: 90 days then anonymised. Family link records: until revoked. Pool check-ins: 7 years (school safeguarding). DBS certificates: 2 years (cycle expiry). admin_actions log: 6 years.
Designated Safeguarding Lead role inside LIFT operations. Tier-1 (concern logged), Tier-2 (driver suspended pending review), Tier-3 (council and police notified). Every override and suspension is captured in admin_actions with the operator name, reason, and timestamp.
Users can request their data export (SAR) or deletion through a dedicated form. Anonymised aggregate data is retained for transport-planning even after individual deletion. Children's data is held under stricter retention rules with parent-only access.
Every driver must carry valid Hire and Reward insurance at council level (verified at onboarding). LIFT carries platform-level public liability and professional indemnity cover. The two layers are separate; LIFT does not act as the driver's insurer.
Anonymised journey-and-demand data is shared with Cumberland Council on request for transport planning. No data is sold, no data is shared with third-party advertisers, no data is exported outside the UK. Stripe, Supabase, and Expo are sub-processors under DPA agreements.
Children profiles never leave the parent + school + driver visibility scope. No marketing communications to or about children. Photos never captured in the children table. School agent check-ins are signed with the agent's profile id for full provenance.
The platform is built. The pilot phase is operational, not engineering. The timeline below assumes Cumberland Council green-lights the partnership in week zero; everything after is execution.
Create production Supabase project, run all 12 migrations + seed, deploy 25 edge functions, schedule the 3 Safe Return cron jobs. Activate Stripe Connect Express account and register the webhook. Configure EAS Build with secrets. Apply mobile app for App Store and Google Play review (review window 2 to 7 days).
Approach 5 Cumbria Council licensed drivers personally for the pilot cohort. Walk each through onboarding: licence + DBS (for those who consent to school pool eligibility) + vehicle + insurance + MOT + selfie. Manual ledger check, manual DBS review, manual Stripe Connect approval. Each driver receives a soft-launch test ride to verify the flow.
App publicly available on stores. Initial radio + local-paper coverage. Target: 100 rider signups in week 3, focused on Workington and Whitehaven postcodes. Drivers run normal taxi rides. SOS, ratings, and number masking tested live. Safeguarding lead on call 24/7 for the launch fortnight.
First produce delivery partner farm onboarded (Whinlatter Farm pre-named in seed). Driver count target: 20. Active rider count target: 300. Move from manual driver onboarding to self-service with admin approval queue. Begin DBS verification cycle for the next cohort of drivers (school pool readiness).
School pool pilot at Seaton Academy. School office staff trained on the /check-in admin view (scoped school_agent role). 2 pools running, ~8 children, 2 DBS-verified drivers. Escrow flow tested with real parent cards. Safe Return becomes available to all signed-up riders.
Whitehaven Academy and Cockermouth School added. 8 partner farms across the county. 50 drivers operational, 25 with DBS for school eligibility. Daily ride volume ~ 200. Anonymised journey data exported to council for transport-planning briefing.
Phase 1 saturation. Conversation starts with NHS Cumbria ICB on Patient Transport pilot (Phase 2 stream activation). First financial review with the council on anonymised journey patterns and safeguarding incidents (target: zero).
No platform is risk-free. The eight risks below are the ones LIFT actively monitors, with the mitigation in place today. Categorised by impact (operational, regulatory, technical, commercial).
Risk:Pilot needs 100 drivers in Year 1. Cumbria has ~1,200 licensed drivers; converting 8% requires real outreach. National platforms have larger budgets for driver-side promos.
Mitigation:10% fee (vs 25-30%) is the structural advantage. Firm partnership tier (Phase 2) lets drivers stay with their firm AND join. Manual personal onboarding for the first cohort. Bonus per-referral for drivers who bring others.
Risk:HMG access agreement for the DBS API is 3 to 6 months. School pool feature gates on DBS verification; manual verification has a ceiling.
Mitigation:Phase 1 is manual cert check via the admin DBS Queue. 2-year renewal cycle gives headroom. Council partnership can fast-track the HMG application. Phase 2 swaps API in on a feature flag with zero downtime.
Risk:Stripe approval for marketplace flows in transport sector can require manual review. Without Stripe Connect, the platform cannot pay drivers automatically.
Mitigation:Pre-application engagement with Stripe before launch. Documentation pack ready (KYB, business model, safeguarding evidence). Fallback: manual driver payouts via BACS for first 30 days while Connect activates.
Risk:Any platform handling children, vulnerable adults, and late-night young-person travel is exposed to safeguarding incidents. One serious incident can permanently damage the brand and the council relationship.
Mitigation:Database-enforced safeguarding (RLS, capacity mutex, DBS gate, state machines, geofence, escrow). Designated Safeguarding Lead with 24/7 on-call. Full admin_actions audit trail. Police liaison pre-established. Public liability + professional indemnity insurance in force.
Risk:If the partnership conversation with Cumberland Council stalls, school pool pilots and licence ledger access slow down. The pitch loses its "council-partnership-ready" advantage.
Mitigation:The platform operates independently of council partnership. Schools can pilot directly. Driver onboarding works without ledger access (manual check). Council benefits are upside, not a dependency.
Risk:School pool acceptance pre-auths every parent card. Parents without a saved default payment method break the acceptance flow.
Mitigation:Force card-on-file step in parent onboarding (Phase 2 hardening). Phase 1 ops manually contacts parents missing a card before pool acceptance. accept-school-pool-bid edge function rolls back gracefully if any pre-auth fails.
Risk:Public liability and professional indemnity premiums for ride-hailing platforms have risen in the UK. Annual policy cost may exceed initial budget.
Mitigation:Driver-side PHV insurance carries the majority of vehicular risk. Platform insurance covers IT operations and data only. Quotes secured from three providers before launch. Budget reserve of 2x annual premium in Year 1.
Risk:Other Cumbrian taxi-dispatch apps are emerging with simpler partnership models. Risk of perceived market fragmentation.
Mitigation:Multi-stream platform (4 shipped, 8 roadmap) widens the moat. Firms-welcome card and Phase 2 firm partnership tier neutralise the partnership pitch. Database-enforced safeguarding is a structural advantage that takes years to replicate.
LIFT is not a venture-backed app shipped down from a Silicon Valley head office. It is built by someone who lives in the county, knows the A595 in February, has stood on a Cumbrian doorstep at 11:30pm trying to get home, and has watched the local taxi infrastructure thin out year after year.
Cumbrian since 2005, when he moved to the county at fifteen. Twenty years on the same roads, the same villages, the same A595. The vision for LIFT began with a tragedy. After young people were lost in a bypass incident on Cumbrian roads, Micky, a father of six, looked at the safeguarding gap and asked a hard question: could a platform with DBS-gated drivers, capacity-locked school pools, escrow-held fares, and a Safe Return wellness check have changed the outcome? Every safeguarding feature in LIFT is built around the answer. The platform is not what someone parachuted in to launch. It is what a long-term resident, and a father, decided to build after watching the local taxi network thin out, the school-run queues lengthen, the late-night gap stay unsolved year after year, and a community lose young people it should not have lost.
A British inventor and serial entrepreneur. Over the last decade Micky has founded, operated, and advised multiple consumer-software ventures, raising around £25m in seed and private capital across the portfolio. His current ventures include Mickai (applied-AI tooling and bespoke agent infrastructure) and Trust Agent (trust and verification infrastructure for autonomous agents). Before software, he worked on the Sellafield nuclear site as a CE&I (Control, Electrical & Instrumentation) Commissioning Engineer for Morgan Sindall Construction & Infrastructure. That background directly informs how LIFT treats safety-critical software (state machines locked at the database, escrow holds, DBS gates, audit trails) the same way an engineer treats a commissioned system on a regulated site: signed off, traceable, and inspectable.
LIFT is the application of that operator playbook to a problem he lives with personally. Every architectural decision (the 10% fee cap, the database-enforced safeguarding stack, the four-stream commitment, the Cumbria-only geofence) is informed by what the county actually needs, not what a national platform would prefer to sell. Schools, parents, and young-person safety sit at the core of the platform alongside ride-hailing because national operators do not engage with those realities.
LIFT is privately built and operated. No external investors. No exit timeline. No out-of-county growth pressure. The platform exists to be the long-term Cumbrian transport utility, and Micky is personally on the line for every safeguarding incident, every council conversation, and every driver who needs onboarding manually.
"The drivers were always here. The platform that gets out of their way was not. LIFT is the platform we should have had ten years ago, designed by someone who has been the rider stuck without a taxi, the parent worrying about a school run, and the resident watching local pubs and shops close one by one. It is built so the money stays. It is built so the kids get home safely. It is built so the platform serves Cumbria, not the other way around."
Micky Irons · founder
The full interactive document, with the cinematic backgrounds, the live Cumbria map, the financial projections, and the safeguarding stack, in one self-contained file. Open it offline, share it across the council, print it as a PDF, or send the link with the section anchor that matters.