Partner and client portal
What partnership with AiR actually delivers
Sector-by-sector value, the five commercial models, how partner-funded deployment works, and the exact route from first conversation to a live pilot.
The principle
AiR should increasingly make other organisations pay for deployment.
No partner is asked to be charitable and no partner is asked to endorse a product they have not tested. Every model below is built so that the partner's own commercial interest is the reason it works.
Sectors with a defined value case
0
Each with what they gain and what they give
Organisations mapped
0
22 tier A priority targets
Commercial models available
0
From partner-funded to grant-funded
Partner-ready portals built
0
Marque, roadside, dealer group and safety-body surfaces
Value exchange
What each sector gains, and what it gives
Partnership only holds if both sides can name their return. These are stated plainly so a partner can test them.
What they gain
Correct pressure at handover and through the ownership cycle, plus a branded driver experience that reinforces the marque rather than diluting it.
What AiR needs
Approved pressure tables, dealer estate access and a co-designed handover moment.
Sixteen marque portals already built, each with its own driver app simulation and hardware family.
What they gain
Warranty defensibility. A verified 90-day pressure record turns a disputed claim into an evidenced one, and correct inflation extends tread life measurably.
What AiR needs
Load and pressure data, warranty programme alignment, and distribution through fitting networks.
The AiR Verified Care programme and the tyre-warranty surface are fully specified.
What they gain
A working, revenue-generating amenity in place of a broken loss-leader, plus measurable dwell time and repeat visits.
What AiR needs
Site access, power and a pilot forecourt footprint.
Operator portal, unit economics and installation specification are complete and costed.
What they gain
A priced, observable safety behaviour. Verified pre-journey checks are a risk signal that no telematics provider currently supplies.
What AiR needs
Actuarial validation and a premium or excess incentive for verified drivers.
Governed data layer with consent model and residency rules already designed.
What they gain
Attributable outcomes: sessions delivered, deficits corrected, casualties avoided. Campaign reach with evidence attached.
What AiR needs
Methodology scrutiny, campaign alignment and public credibility.
The TyreSafe-facing intelligence portal is neutral by design and asks for co-design, not endorsement.
What they gain
Fewer avoidable callouts, a prevention product to offer members, and branded stations at the sites members already use.
What AiR needs
Member reach, roadside data and national brand trust.
RAC, AA and Green Flag partner surfaces are built end to end.
What they gain
Fuel and tyre savings that land straight on the P&L, plus a duty-of-care record per vehicle.
What AiR needs
Depot deployment, driver volume and hard before-and-after data.
Fleet portal with per-vehicle compliance and savings modelling.
What they gain
Emissions and road-surface benefit from an intervention that costs the public purse nothing to operate.
What AiR needs
Grant routes, standards alignment and network access.
National impact and carbon surfaces model the benefit with sourced coefficients.
What they gain
A second reason to visit the charging site, and a resilient sovereign comms and compute node on infrastructure already powered.
What AiR needs
Site estate, grid connection and co-location.
Mesh and edge-compute architecture are specified against real hardware tiers.
What they gain
A longitudinal physical-world dataset with consent and residency handled, rather than inferred telematics.
What AiR needs
Platform integration and analytics distribution.
Twelve-layer revenue architecture with the data layer governed separately from operations.
Built with the industry, not around it
Sixteen partner surfaces are already live in this platform.
Commercial
Five ways to deploy, and how each is funded
| Model | Who funds hardware | How it works | Why it fits |
|---|---|---|---|
| Partner-funded deployment | Partner buys the hardware | Partner owns the asset and the site relationship; AiR licenses the platform per node | Zero AiR capital, fastest to scale, strongest partner commitment |
| Revenue share | AiR funds the hardware | Site takes a share of session and subscription revenue | No partner capital required, slower rollout, higher AiR capital intensity |
| Co-branded programme | Shared | Partner funds hardware and brand activation, AiR funds platform and support | Best fit for OEM and roadside brands where the experience carries the marque |
| Grant or social-value funded | Third party | Public or charitable funding covers deployment in priority areas | Correct model for high-deprivation and high-casualty locations |
| Fleet depot licence | Fleet operator | Per-depot hardware plus per-vehicle software subscription | Shortest payback of any model, measured in months |
Integration
What actually gets connected
Approved pressure data
Manufacturer load and pressure tables ingested into the engine as versioned records. AiR never interpolates a value that a manufacturer has not published.
Brand layer
Colour, typography, imagery and copy of the driver app and station screen wear the partner's identity, subject to the partner's own brand approval.
Identity and accounts
Single sign-on into the partner's existing member, owner or driver account so no new credential is created.
Verified record export
Signed session records exported to warranty, claims or fleet-compliance systems in a documented schema.
Estate telemetry
Machine health, uptime, queue and utilisation surfaced to the partner's operations team through the operator portal.
Data governance
Consent captured per driver, residency enforced per region, and aggregate research outputs separated from identifiable operational data.
Onboarding
From first conversation to live pilot
Ninety days, six stages, with a decision point at each one.
Introduction
Week 1A twenty-minute demonstration of a live session, the verified record, and the numbers behind it. The product argues better than a deck.
Technical review
Weeks 2 to 3Your engineering or safety team interrogates the pressure engine, the data model and the regression results. Nothing is hidden, including known defects.
Commercial shape
Weeks 3 to 5Select the deployment model, site count and brand treatment. Heads of terms rather than a full contract at this stage.
Pilot design
Weeks 5 to 7Agree sites, success metrics and the measurement method before anything is installed, so the result cannot be argued about afterwards.
Install and instrument
Weeks 7 to 10Units installed, screens branded, estate telemetry connected to your operations view, staff briefed.
Measure and decide
Weeks 10 to 13Report against the metrics agreed in stage four: sessions, deficits corrected, dwell, revenue and driver feedback. Scale or stop on evidence.
Questions
What partners ask before committing
Next step
See the specific organisations mapped, the justification for each, and the outreach already drafted.
Open the partner directory and outreach engine