MierVollConcept / 2026

Exploratory concept

MierVoll

Making marine fueling context portable.

Connect charter booking, vessel, authorized skipper and fleet policy to existing marina fuel transactions.

More time for what matters.

The pump stays local. The context becomes portable.

Follow the idea

01 / The human story

Some journeys should end with a memory, not paperwork.

A charter sailing trip ends. The yacht comes home. The right vessel, booking and skipper are already known. Fuel happens through the infrastructure already there. The transaction finds where it belongs.

Watch on YouTube

02 / The concept

The idea in 30 seconds.

Not another fuel app. A portable context layer between fleet operations and existing marine fuel infrastructure.

The pump stays local.
The context becomes portable.
Watch on YouTube

03 / Current product hypothesis

MVP-B — Fleet Fuel Authorization & Transaction Matching

MierVoll connects the operational context known before fueling to the real transaction that happens afterwards.

Five-step MierVoll flow: fleet context, authorization layer, portable fuel authorization context, existing marina infrastructure, and automatic transaction matching.
Exploratory architecture. The existing operator or marina infrastructure remains in place.
Five-step MierVoll flow: fleet context, authorization layer, portable fuel authorization context, existing marina infrastructure, and automatic transaction matching.

MVP-B — Fleet Fuel Authorization & Transaction Matching

01

Know who is allowed to fuel before it happens.

02

Use the infrastructure already there.

03

Match the resulting transaction automatically.

Today

Fuel happens receipt exists somebody later identifies the context.

With MierVoll

Vessel + booking + authorized person are known before fueling the transaction lands in the right context.

Why MVP-B first

Start where value can be tested.

Starts with capabilities that already exist

No pump replacement required for the MVP

Delivers value through matching and reconciliation

04 / Illustrative validation scenario

Two sites. One operator layer.

The first scaling question is not whether MierVoll can work at one marina. It is whether one partner/operator integration can work at the second location mostly through configuration.

Illustrative pilot ecosystem linking an example fuel operator, two ACI marina sites, charter fleet demand and the MierVoll context layer without implying ownership or partnership.
Illustrative hypothesis only. No partnership with INA, ACI, Angelina or Pitter is implied or assumed.
Illustrative pilot ecosystem linking an example fuel operator, two ACI marina sites, charter fleet demand and the MierVoll context layer without implying ownership or partnership.

Pilot hypothesis — two sites, one operator layer

If the hypothesis holdsSite two becomes configuration — not another integration project.

05 / Hypothesis value areas

Why this may matter.

These are areas to validate with partners—not proven outcomes.

For charter fleets

  • Fewer fuel-related exceptions
  • Vessel-level transaction matching
  • Simpler reconciliation
  • Potentially smoother return-day operations

For fuel operators

  • Reusable fleet transaction context
  • Stronger fleet relationships
  • Potential digital authorization layer

For marina groups

  • Smoother customer experience
  • Less friction during concentrated return periods
  • Improved transaction visibility

06 / Why this may fit CarPay-Diem

An adjacent orchestration problem.

CarPay-Diem works with the pattern of connecting fleet context, fuel retailers, payment and transaction flows across heterogeneous environments. MierVoll asks whether a similar principle could be useful in marine fueling—with vessel, charter and marina-specific adaptations.

AutomotiveConceptual architecture reuseMarine
VehicleVessel
DriverAuthorized skipper
FleetCharter fleet
Fuel retailerMarine fuel operator
StationMarina fuel location
Fuel card / accountFleet / operator entitlement
Transaction orchestrationMarine fuel transaction
ReconciliationVessel + booking reconciliation

“The hypothesis is not that marine fueling is the same as automotive fueling. It is that several orchestration patterns may be reusable.”

07 / Evidence boundary

What we know. What we don’t.

What current research suggests

  • Digital marina fueling exists
  • Unattended marine fueling exists
  • Charter return-day fueling friction exists
  • Multi-site marine fuel operators exist
  • Fleet authorization and payment primitives already exist

What remains unknown

  • Partner-accessible interface across two marine sites
  • Cost of second-site integration
  • Charter fleet willingness to pay
  • The economic buyer
  • Whether remote pump activation is needed

Stage 4 verdict / Start partner outreach

Next gate: partner discovery.

Partner exposes reusable interface?Technical validation
Transactions only?MVP-B / reconciliation-first
Every site bespoke?Pivot away from pump orchestration
Fleet pain weak?Stop or reposition

The decisive metric is not whether one pump can be integrated.
It is whether marina number two becomes configuration instead of another integration project.

Watch on YouTube

08 / Research behind the concept

Want the evidence behind the idea?

This overview explains how the concept changed across four validation stages—including what was disproved, what survived, and what remains unknown.

  1. Opportunity assessment
  2. Infrastructure & integration mapping
  3. Installed-base verification
  4. Partner discovery & buyer validation