The analyst team at a Tier-1 consulting firm that covers EV fleet strategy has read every published TCO study, every market report, and every fleet electrification framework. So has the Frontyx founding advisor. The difference is that he has also deployed an EV fleet operationally — managed the OEM procurement, specified the charging infrastructure, resolved the shift-pattern conflicts that published guides do not address, and built the financial case that had to survive comparison against a diesel incumbent with 14 years of demonstrated reliability. That experience changes what the analysis can see.
The advisory network that supports that operational base includes people who have made the decisions that Frontyx clients are now trying to make — not studied them. A former OEM institutional fleet director who built government fleet sales programmes from scratch. A former Head of Government Fleet Strategy who ran a national 8,000-vehicle procurement programme and directed its EV transition. A former multilateral development bank principal who structured $800M in frontier infrastructure investments. These are not affiliates. They are engaged on specific assignments where their direct experience changes the analytical output.
These are not service lines mapped to market trends. Each capability reflects a domain where the founding advisor or advisory network has operational depth — meaning direct exposure to the problems that determine whether strategies succeed or fail in implementation.
Led the deployment of a regional EV security patrol fleet from business case to operational handover. The charging infrastructure had to be redesigned mid-deployment when the standard overnight-charging model proved incompatible with the shift pattern. The final specification used opportunity charging at nine handover points — an approach not described in any published fleet deployment guide. The Fleet TCO Architecture was built to capture those variables.
Direct market engagement in West Africa, South Asia, Southeast Asia, the Middle East, and island economies — including the in-country conversations that surface the intelligence published data cannot contain. In the West Africa engagement: the 62% commercial fleet demand concentration, two active government electrification mandates, and a 12% import incentive advantage were all absent from every published source and discovered through direct engagement with government procurement officials and in-market distributors.
Advisory network provides direct access to the institutional procurement decision-making process as it actually operates. The former Head of Government Fleet Strategy in the network managed national fleet procurement — including EV transition — for a programme of 8,000+ vehicles. He knows which pre-tender actions moved a supplier from "technically considered" to "actively preferred" and why technically qualified tenders were commercially eliminated. That intelligence is not in any procurement guide.
Designed an integrated EV mobility system for a 400,000-visitor annual island destination. Three previous proposals had been rejected at the authority approval stage — not on technical grounds. The Frontyx redesign was built backwards from the authority's actual approval criteria: capital exposure limit, after-sales service commitment threshold, and resort co-investment viability. Phase 1 capital requirement reduced by 44% versus the previous proposal. Approved within one planning cycle.
Advisory network includes a former multilateral development bank principal who structured $800M+ in frontier infrastructure and transport investments across fourteen countries. Engagements in frontier markets frequently encounter the development finance question: which instruments are genuinely accessible, what regulatory conditions their availability requires, which institutional relationships in the target geography are critical. This advisor has structured those deals — not researched them.
Advisory network includes a former OEM Fleet Electrification Director who held P&L responsibility for institutional fleet sales — government, corporate, NGO — across multiple markets during an EV portfolio transition. Built the institutional sales architecture from scratch in three markets: the commercial frameworks, lifecycle service programmes, and procurement pre-qualification systems that converted the OEM from an incidental fleet supplier to a preferred institutional partner. Knows exactly why most OEM institutional strategies fail.
This is not a polished case study. It is an account of a specific operational problem that the standard model did not anticipate — and what resolving it produced.
The EV fleet vendor's infrastructure specification called for depot-based overnight charging: vehicles return at shift end, charge for six to eight hours, depart at next shift start. This is the model described in every published EV fleet deployment guide because it is the model that works for most fleet types. It did not work here.
The security operation ran 24/7 with overlapping shift structures. During peak periods, 40% of the fleet was on duty with no scheduled return. Holding sufficient spare vehicles to allow overnight charging — while maintaining coverage requirements — would have required 1.4× the planned fleet size. That capital cost made the financial case negative. The vendor had not modelled this.
The infrastructure was rebuilt around the shift pattern rather than the standard depot model. Nine handover locations received 150kW rapid chargers timed to the 25-minute shift overlap. Vehicle availability reached 97% in operational year one. TCO crossover versus diesel occurred at month 26. The original specification would not have delivered either result.
What This Changed in the Analytical FrameworkEvery fleet deployment guide assumes a charging window. Security, emergency response, and continuous-operation fleets do not have one. Rebuilding the charging architecture around shift handover — rather than depot return — is not a known best practice. It is a solution developed under operational pressure when the standard model failed. The Fleet TCO Architecture now includes shift-pattern charging variables as a mandatory input for all security and operational fleet assessments. No published framework does.
The infrastructure vendor who produced the original specification had successfully deployed EV charging infrastructure for fourteen corporate fleet operators. All fourteen used overnight depot charging. The specification failure was not incompetence — it was the application of a valid model to an operational context for which the model was not designed. That is the analytical gap that operational experience closes: knowing which published model applies to which operational context, and which operational contexts have no valid published model yet.
These are not strategic advisors retained to add credibility to a pitch. They are practitioners engaged on specific assignments where their direct experience — from the decision-making side of the process — changes the quality of the intelligence produced. Identities disclosed under NDA at engagement stage. All descriptions are accurate.
Built the institutional fleet sales architecture — commercial frameworks, lifecycle service programmes, procurement pre-qualification documentation — that converted the OEM from incidental fleet supplier to preferred institutional partner in three markets. Managed the commercial relationships with the six largest government fleet buyers in two regions. Has direct knowledge of why OEM institutional fleet strategies fail: the commercial infrastructure is designed for retail buyers and does not address the structural requirements of institutional procurement. That knowledge is applied to every Frontyx institutional channel advisory engagement.
Engaged on: OEM institutional fleet commercial structure, government buyer relationship design, EV product positioning for fleet procurement contexts, lifecycle service programme architecture.
Has evaluated and structured the investments that make frontier market entry programmes financially viable for private sector participants: the development finance instruments, the regulatory conditions their availability requires, and the institutional relationships in target geographies that determine access. The difference between a development finance instrument that is theoretically available and one that is genuinely accessible in a specific frontier market context is a distinction that requires direct knowledge of how DFIs evaluate proposals — from the inside. Every frontier market engagement where development finance is relevant draws on this network relationship.
Engaged on: frontier market financial modelling, development finance access strategy, regulatory investment environment assessment, infrastructure investment structuring in Sub-Saharan Africa and South Asia.
Did not study government fleet procurement — ran it. Over multiple procurement cycles, he managed the evaluation and selection of fleet suppliers for the largest single-agency vehicle programme in his jurisdiction. He knows the specific informal evaluation criteria that determined supplier selection outcomes: the pre-tender engagement quality that moved a supplier from technically qualified to actively preferred; the commercial flexibility on lifecycle maintenance that eliminated a technically superior competitor; the internal stakeholder at the right seniority who needed to be an active champion before the formal evaluation even began. That intelligence is applied to the Institutional Channel Map analyses Frontyx produces for OEM clients targeting government fleet contracts.
Engaged on: government fleet procurement intelligence, OEM tender positioning, pre-tender relationship sequencing, fleet electrification programme design from an institutional buyer's perspective.
Has evaluated destination infrastructure proposals from the approval side. Knows exactly what separates a technically sound proposal from one that gets approved: the capital exposure structure that the authority can commit to within its mandate, the after-sales service commitment that resort operator co-investment requires, the stakeholder alignment sequence that prevents a proposal from stalling after the technical approval stage. The Destination Mobility Architecture framework was built with her input — specifically to address the gap between what infrastructure consultants design and what tourism authorities can actually approve and fund.
Engaged on: tourism authority proposal design, destination infrastructure investment structuring, stakeholder dynamics in destination approval processes, resort operator co-investment architecture.
In the markets where Frontyx advises, the intelligence gap between published secondary data and current ground-level reality is not a marginal adjustment — it is frequently the variable that determines whether the analysis produces the right answer or a sophisticated-looking wrong one. The West Africa engagement identified three market conditions that determined the entry strategy; all three were absent from every published source. If primary intelligence is not feasible for a specific engagement question, Frontyx declines the engagement rather than produces a well-structured analysis of insufficient data.
Some market assessment requests arrive with a timescale that does not permit adequate primary intelligence gathering. In those cases, the honest answer is that the analysis will not be reliable enough to support a significant entry decision — and that extending the timeline or narrowing the scope to the questions that can be answered with available intelligence is the correct approach. That is not a comfortable commercial position. It is the correct analytical one.
The founding advisor has implemented the strategies that Frontyx now advises on. He knows the specific ways in which market entry strategies fail when they encounter the actual distribution economics, the procurement officers whose names do not appear on tender documents, and the regulatory conditions that the published framework describes differently from how they are enforced. Every Frontyx recommendation is stress-tested against those failure modes before it is delivered. This occasionally produces a recommendation to not proceed — delivered directly, in the first paragraph, not as a hedged conclusion at the end of a comprehensive market assessment.
Frontyx advises in five domains. Each domain has direct operational or advisory depth behind it. A sixth domain is not being added because adjacent market interest exists. The value of the platform model is that clients receive primary-intelligence analysis from practitioners with operational depth — not broad-coverage advisory from analysts with research depth. Maintaining domain boundaries is what makes the analysis reliable in the domains where Frontyx operates.
If the analysis does not support the client's preferred outcome, that is stated in the first paragraph — not buried in caveats at the end of a document designed to appear balanced.
Every conclusion identifies whether it rests on primary or secondary intelligence and what the specific source is. Analytical opacity is a method of avoiding accountability for unreliable findings.
The founding advisor conducts the analytical work on every engagement. There is no delegation to an associate team. The person whose operational experience is the basis for the analysis produces the output.
No referral fees, no commercial relationships with OEMs or infrastructure vendors, no conflicts between advisory independence and commercial interest. The analysis reflects the client's interest exclusively.
Engagements are scoped to the decision. A broader scope that produces a more comprehensive document but does not improve the quality of the decision is not a better engagement. It is a more expensive distraction.
45 minutes. We come prepared with relevant market context. Direct assessment of whether Frontyx is the right analytical resource. No pitch for a broader engagement than the problem requires.
Complimentary. Founder-led. No obligation.