Software that helps short-sea carriers allocate scarce drop-in marine biofuel across voyages, contracts, and emissions claims.

1. Series A funding plus a strategic partnership show suppliers are entering a scale-up phase where fleets must prepare for real procurement instead of abstract climate planning.
2. Expanding the Fredericia test facility means more pilot fuel will reach operators, increasing the need for disciplined allocation and documentation workflows.
3. A named first commercial-scale plant gives carriers a concrete timeline for initial adoption and forces early decisions on which routes and customers get scarce supply first.
4. The no-retrofit claim removes engine changes as the main excuse for delay, making software-enabled rollout, tracking, and claims integrity the new bottleneck.

Catalyst. Kvasir's funded test-facility expansion, planned first commercial plant, and no-retrofit claim indicate that the next blocker is operational rollout rather than engine conversion.

The product gives carriers a control tower for running their first drop-in biofuel program without adding a large fuel-ops team. It ingests bunker supply offers, vessel schedules, fuel-quality documents, and customer decarbonization commitments, then recommends where scarce low-carbon tons should be allocated for the highest operational and commercial impact. Each voyage gets an auditable evidence pack covering what fuel was lifted, where it was used, and which customer promise it supported. Over time, the platform becomes the benchmark dataset for which suppliers, corridors, and claim structures actually let marine biofuel programs scale.

What's different. Generic maritime procurement tools handle bunker purchasing, and generic ESG tools handle reporting, but neither is built for scarce first-wave alternative fuel that must be tied to specific voyages, contracts, and proof packages. This product starts with the operational edge case that appears when drop-in biofuel becomes commercially available before processes are mature. Its moat is the dataset of real allocation decisions, supplier performance, document completeness, and claim outcomes across early marine biofuel corridors.

Jobs to be done

flowchart LR
  Buyer[Short-sea carrier] --> Pain[Scarce biofuel is hard to allocate and prove]
  Pain --> Product[Voyage biofuel allocation workspace]
  Product --> Outcome[Faster low-risk marine fuel adoption]

Executive takeaways

• The wedge is credible because early marine biofuel adoption is becoming a documentation-and-allocation problem before it becomes a fleet-retrofit problem.
• The beachhead is real but narrow: Northern European short-sea carriers already face customer-funded low-emission programs and new EU proof requirements, yet the likely year-three outcome is low-single-digit millions of ARR unless the product expands into a broader multi-fuel control tower.
• Competition is adjacent rather than direct: registries, insetting brokers, assurance firms, and bunker-procurement suites each own a slice, but none owns voyage-level fuel allocation plus proof-of-claim workflow by default.
• Supply scarcity helps the wedge because DNV still shows shipping biofuel as a tiny share of global liquid biofuel consumption, which raises the value of deciding exactly which voyages and contracts receive the limited volumes.
• The main commercial risk is that carriers keep the workflow with bunker suppliers, registries, or consultants instead of buying another operating system.

Market definition

Carrier-native software that allocates scarce certified low-carbon marine fuel across voyages, customer contracts, and claims. The category sits between bunker procurement tools, book-and-claim registries, and compliance reporting systems: it decides where physical fuel should go and packages the evidence needed to defend the resulting emissions claim.

Customer and buyer

Primary users are bunker procurement managers plus sustainability or fuel-operations leads at 10-40 vessel short-sea Ro-Ro and feeder-container operators. The economic buyer is usually the Head of Bunker Procurement or COO because fuel cost, service reliability, customer commitments, and compliance risk all converge in the same workflow.

Buying triggers

• A carrier signs its first certified biofuel supply agreement or gains access to new corridor volume, forcing it to decide which voyages, customers, and claims should consume the limited fuel. [106][109][14]
• An anchor cargo customer asks for a book-and-claim or low-emission service backed by auditable Scope 3 evidence, creating a revenue-linked need for better allocation and proof. [81][82][23]
• FuelEU Maritime and EU ETS reporting deadlines expose how brittle spreadsheet-based fuel, contract, and document reconciliation is under verifier scrutiny. [1][3][16]

Willingness to pay

Willingness to pay exists when the workflow is attached to live customer revenue or expensive compliance effort. DHL signed a three-year framework with Hapag-Lloyd to use sustainable marine fuels via book and claim, MOL turned third-party fuel switches into EAC-backed services for customers, 123Carbon says its platform has already issued certificates representing more than 500,000 tCO2e avoided, and maritime software vendors still sell on a per-ship enterprise basis rather than self-serve commodity pricing. That suggests buyers will fund the tool if it clearly protects contract revenue, verifier trust, or manual headcount. [81][82][53][41]

Category dynamics

Growth signal ~63% CAGR in reported bio-blended bunker sales at Singapore and Rotterdam (2021 to Q3 2024)

Validation signals

• DHL and Hapag-Lloyd committed to a three-year sustainable-fuels and book-and-claim framework, showing customer-funded demand for auditable low-emission shipping.
• MOL and Shell demonstrated that third-party vessel fuel switches can be converted into customer-facing EACs via 123Carbon, proving the commercial value of traceable claim infrastructure.
• 123Carbon says its platform has already issued certificates representing more than 500,000 tCO2e avoided, indicating that the attribute-transfer market is moving beyond concept stage.
• DFDS and UECC both show that short-sea operators already treat low-carbon fuel as a live customer or compliance tool rather than an abstract future option.
• Kvasir’s funding round and planned first commercial plant make future corridor supply more concrete than a generic decarbonization narrative.

Regulatory & technical constraints

• From 2027, sustainable biofuel claims increasingly need a PoS or accredited PoC linked to ship IMO number, BDN, and ultimately the Union Database or equivalent evidence chain.
• Novel blends or higher biofuel ratios still require class, OEM, and operational due diligence even when the headline story is “drop-in”.
• FuelEU and EU ETS reporting through THETIS-MRV and verifier workflows creates strict timing and data-integrity requirements for any operational software layer.

Competition clusters into four camps: bunker-procurement and digital-operations suites (ZeroNorth), registry infrastructure (123Carbon and Katalist-style systems), insetting service providers (GoodShipping and carrier green products), and assurance/compliance advisors (DNV and class-linked experts). The whitespace is a carrier-native operating layer that makes the physical allocation decision first, then hands the resulting evidence to registries, verifiers, and customers.

Why incumbents do not win by default

• Registry platforms. 123Carbon and Katalist prove the market wants auditable claim transfer, but registries do not win by default because they sit after the fuel-allocation decision rather than inside the carrier workflow that decides which voyage should receive the fuel.
• Insetting service providers. GoodShipping and similar programs aggregate shipper demand and help fund low-carbon transport, but their center of gravity is commercial program management, not the internal carrier system of record for bunker allocation and evidence assembly.
• Compliance and assurance vendors. DNV and legal/compliance advisors already own methodology trust, yet they are services-first and verifier-facing; that leaves room for productized operational workflow underneath their assurance layer.
• Bunker and operations suites. ZeroNorth is closest to the budget line because it already touches bunker buying, eBDN, and emissions reporting, but it is not positioned around scarce-biofuel allocation across customer contracts and proof-of-claim packs.

Voyage Biofuel Allocation OS should start as a carrier-native control tower for scarce drop-in marine biofuel on Northern European short-sea routes, not as a broad maritime procurement suite or generic carbon registry. The first user is the head of bunker procurement or fuel-operations lead at a 10-40 vessel Ro-Ro or feeder-container operator running fixed weekly loops through ARA, Baltic, or Nordic corridors. The urgent pain begins when the carrier signs its first certified biofuel supply agreement or customer contract with an emissions commitment and must decide which voyages should consume limited volume while preserving proof for FuelEU, EU ETS, and customer claims. The product wedge is a voyage-level allocation workspace that ties supply offers, schedules, bunker documents, contracts, and evidence packs into one workflow, sold as an overlay rather than a bunker ERP replacement. Research supports the timing, because biofuel supply remains scarce, documentation requirements are growing, and customer-funded low-emission services already exist, but the likely year-three outcome is only about $2.7M SOM unless the company expands into a broader multi-fuel operating layer. The strategic choice is to win one corridor and one live program first, because supply fragmentation, claims ambiguity, and substitute solutions from registries, suppliers, and consultants make a broad launch likely to fail. The biggest disconfirming risk is that carriers leave allocation and proof workflow with bunker suppliers, registries, or services firms instead of paying for standalone software. The inputs do not provide direct evidence of standalone software budgets, measured implementation times, or real verifier rejection rates, so the first 12 months must prove paid carrier ownership of the workflow, deployment speed, and pilot-to-production conversion.

Problem

• Scarce early biofuel supply forces carriers to choose which voyages, customers, and contracts receive limited low-carbon tons, but most teams still manage the tradeoff in spreadsheets, email, and bunker notes.
• FuelEU Maritime, EU ETS, and customer book-and-claim expectations make proof-of-claim documentation operationally brittle, especially when BDNs, PoS or PoC documents, schedules, and contract terms are not reconciled in one system.

Solution

• Provide a voyage-level workspace that ingests supply commitments, vessel schedules, bunker documents, customer decarbonization commitments, and evidence requirements, then recommends where scarce biofuel should be allocated first.
• Generate an auditable evidence pack for each covered voyage and customer claim so carriers can defend emissions statements without adding a large manual back-office process.

Why we win

• The product starts at the physical allocation decision inside the carrier workflow, which registries, insetting platforms, and verifier-led services do not own by default.
• Defensibility can compound from corridor-level data on supplier reliability, document completeness, verifier acceptance, and contract outcomes across early marine biofuel programs.

Milestones

flowchart LR
  Wedge[Carrier corridor wedge] --> MVP[Voyage allocation MVP]
  MVP --> Proof[Trusted proof packs and live allocations]
  Proof --> Expansion[Multi-corridor and multi-fuel expansion]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least half of qualified target carriers must confirm that one live biofuel program is painful enough to fund a standalone pilot rather than expand spreadsheets or consultant support.
• The product must go live for a first corridor in 4-6 weeks using schedule exports, eBDN inputs, and evidence templates rather than a large ERP integration.
• At least 70% of covered voyages must produce accepted evidence packs without major manual rework after initial onboarding.
• At least 50% of paid pilots must convert to annual deployments because the workflow becomes recurring across future voyages and contracts.
• The platform must expand into additional corridors or adjacent fuel workflows fast enough to overcome a year-three SOM that is only a few million dollars on the initial wedge alone.

Open diligence questions

• Which exact workflow owner decides where scarce biofuel goes today when a carrier has one live customer commitment?
• How often do bunker suppliers, registries, or consultants already absorb this workflow well enough that a carrier does not need new software?
• Which fields in BDNs, PoS or PoC documents, lab certificates, and customer contracts most often cause verifier or customer rework?
• What annual budget line can plausibly fund the first deployment: bunker procurement, compliance, sustainability, or customer program revenue protection?
• How fast are ZeroNorth, 123Carbon, GoodShipping, or verifier-led services moving into the same carrier-native allocation workflow?

Model sanity

• Revenue engine. Base-case revenue comes from growing from 3 to 12 paid corridor programs and monetizing each at roughly $225K per program-year as customers add more vessels and second corridors.
• Must go right. Pilot-to-production conversion has to stay strong enough that the company reaches eight live programs by Q4Y2 without pulling forward a much larger sales or services team.
• Model breaks if. If pricing stalls near $200K per program-year or the ramp slips toward only 10 live programs in Y3, the downside case pushes cash slightly below zero even with the modeled raise.
• Next-round proof. The seed story becomes credible once the company reaches eight live programs across 4–6 carriers, shows second-corridor expansion, and proves clean handoffs into registry or verifier workflows.

Scenarios

Sensitivity

flowchart LR
  Leads[Founder + partner leads] --> PaidPilots
  PaidPilots --> LivePrograms
  LivePrograms --> Revenue
  Revenue --> GrossProfit
  GrossProfit --> Cash

Flags: The model assumes each paid corridor program quickly expands toward about 12.5 managed vessels and a $225K blended annual value; if customers remain near the $60K-$180K annual band for single-corridor scope, Y3 revenue undershoots materially. · The downside case turns slightly cash-negative, so hiring must remain tightly sequenced to pilot conversion and second-corridor expansion rather than calendar-based optimism. · Monthly churn is used only for LTV math while the operating model uses milestone-driven net customer adds; once renewals exist, cohort retention should replace the heuristic churn input. · Y3 revenue per FTE sits near the low end of SaaS benchmarks because implementation and proof-pack support are still meaningful parts of delivery, which limits operating leverage until workflows standardize further.

• Supply rollout slips. If commercial marine biofuel volumes arrive slower than expected, early workflow volume may be lumpy and sales cycles may stretch. Mitigation: Land with carriers and bunker suppliers on pilot planning and documentation first, then expand into live allocation as soon as corridor volumes appear.
• Operators stay on spreadsheets. Smaller carriers may resist adding another system for a program that starts with only a few voyages. Mitigation: Integrate tightly with existing voyage and ERP tools and price the product as a lightweight pilot control tower that replaces consultant and back-office effort.
• Claims standards remain fragmented. Buyers and carriers may disagree on what documentation is sufficient to support a lower-emissions shipping claim. Mitigation: Start with conservative evidence workflows tied to supplier documents and third-party lab data, then build reusable templates accepted by anchor customers.