DinghyFleet
DinghyFleetStrategic direction

Investor preview · Draft

The Operating Network for Boat-Based Businesses

Build the software. Win the network. Unlock the marketplace.

Draft for founder review. Not an offer or solicitation to sell securities.

01 / 15

← → or Space to navigate · Evidence and sources open beside each slide · PDF contains the core story only

DinghyFleetStrategic direction

Investor preview · Draft

The Operating Network for Boat-Based Businesses

Build the software. Win the network. Unlock the marketplace.

Draft for founder review. Not an offer or solicitation to sell securities.

01 / 15
DinghyFleetStrategic direction

02 · Why now

Software is becoming cheaper to create. Winning business networks remains difficult.

Getting cheaper

AI-assisted development lowers the upfront cash needed to build sophisticated vertical software.

Still scarce

Trusted, recurring collaboration between independent companies — and the distribution it unlocks.

02 / 15
DinghyFleetTo validate

03 · Problem

One charter booking crosses many companies — and no shared system.

1Enquiry by email
2Sourcing via calls & chats
3Availability in separate fleet tools
4Proposals rebuilt by hand
5Client decision lost in threads
6Booking prep re-keyed

↳ Broker ↔ Operator handoff: the moment context is lost

Problem framing from founder industry experience; severity and frequency to be quantified in pilot interviews.

03 / 15
DinghyFleetBuilt · founder reported

04 · Product wedge

One shared context from enquiry to booking.

  1. 01 ●

    Enquiry

  2. 02 ●

    Request

  3. 03 ●

    Sourcing

  4. 04 ●

    Offer

  5. 05 ○

    Client decision

  6. 06 ○

    Booking & charter prep

Wedge: yacht charter broker ↔ operator workflow. Not four products at once.

● Built · founder reported◐ Hypothesis○ To validate✎ Founder input needed

04 / 15
DinghyFleetStrategic direction

05 · Free core

Free to operate. Pay for additional value.

Free core workflow

  • ✓Organizations & team
  • ✓Client and supply records
  • ✓Requests & offers
  • ✓Booking collaboration
  • ✓Baseline operator inventory
  • ✓Partner relationships

Paid only when we add value

  • ◐Premium AI & automation
  • ◐Incremental network-sourced leads
  • ◐B2B reseller distribution
  • ◐Enterprise & integrations

Fair-use resource limits may apply to the free core.

05 / 15
DinghyFleetHypothesis

06 · First network loop

The network grows only when invites turn into repeat work.

One invite is not a network effect. Only repeated, independent collaboration counts.

06 / 15
DinghyFleetStrategic direction

07 · Expansion path

Each layer is earned by the one beneath it.

  1. Gate 1 → ●

    Software

    Free operating core for brokers and operators

  2. Gate 2 → ◐

    Operating network

    Repeat cross-company workflows

  3. Gate 3–4 → ◐

    B2B distribution

    Resellers, hotels, concierge as demand channels

  4. Conditional ○

    Potential B2C marketplace

    Later, conditional, optional

The business must be viable on B2B alone. A consumer marketplace is optional upside, not the plan.

07 / 15
DinghyFleetTo validate

08 · Market

A large reference market — and an honest bottom-up still to come.

~$271b · broader context

~$8.8b

~$8.8b

Global yacht charter (2025 estimate). Closest external reference.

~$271b

Global tours, activities & attractions (2025). Broader context — not our market.

To validate

Bottom-up boat-based TAM / SAM / SOM: sizing in progress

Figures are non-additive. Sources: Grand View Research (yacht charter, as cited in internal strategy); Arival / Phocuswright 2025.

08 / 15
DinghyFleetStrategic direction

09 · Positioning

We connect to existing systems before we replace any of them.

Legacy charter fleet software

MMK / Booking Manager, NauSYS — inventory & reservations. Coexist via Connected Operator; compete where operators go native.

Experience booking systems

FareHarbor, Bókun — adjacent; relevant if we enter day-trip and ticketed segments.

B2C travel platforms

Consumer OTAs — demand channels today; potential competitors only if a marketplace emerges.

DinghyFleet

Cross-company workflow layer between brokers and operators — native or connected.

09 / 15
DinghyFleetHypothesis

10 · Monetization

We charge for new value — never a toll on existing relationships.

Automation ◐

Premium AI and workflow automation

New business ◐

Clearly incremental network-sourced leads and bookings

B2B distribution ◐

Reseller and channel distribution

Payments ○

Financial services, subject to regulation

Enterprise ◐

Integrations and larger fleets

Consumer layer ○

Possible later B2C marketplace

● Built · founder reported◐ Hypothesis○ To validate✎ Founder input needed

No universal take-rate. Revenue = blended realized platform revenue across services actually used.

10 / 15
DinghyFleetBuilt · founder reported

11 · Readiness & evidence

A working core, built capital-efficiently — traction not yet proven.

Broker Workspace ●

Exists

Org, billing, collaboration ●

Structures exist

€5–10k ●

Founder-reported cash spend to date. Excludes founder time, QA, ops and maintenance

Operator foundations ○

Partial, found in code

End-to-end reliability ○

Not yet verified

Traction metrics ✎

[Founders to add verified data]

● Built · founder reported◐ Hypothesis○ To validate✎ Founder input needed

€5–10k is founder-reported cash spend, not fully loaded economic cost. No revenue or traction is claimed.

11 / 15
DinghyFleetStrategic direction

12 · Go to market

Win one micro-market deeply before entering the next.

  1. 01 ◆

    Focused pilot

    Real brokerage + operators, Split/Trogir (candidate)

  2. 02 ◆

    Founder-led

    Warm industry conversations

  3. 03 ◐

    High-intent users

    Adoption inside live work

  4. 04 ◐

    Repeat partners

    Loops between the same firms

  5. 05 ○

    Region by region

    Repeatable playbook

● Built · founder reported◐ Hypothesis○ To validate✎ Founder input needed

12 / 15
DinghyFleetStrategic direction

13 · Metrics & gates

One North Star, four gates — progress measured by real collaboration.

MACW

Monthly Active Collaborative Workflows — authentic workflows where 2+ independent organizations take meaningful action in a month.

Current value: [verified data pending]

  1. Gate 1 · status: not yet passed

    Collaborative utility

    Two firms complete a real process

  2. Gate 2 · status: not yet passed

    Network behavior

    Repeat collaboration and partner-led adoption

  3. Gate 3 · status: not yet passed

    Economic signal

    Payment for an additional service

  4. Gate 4 · status: not yet passed

    Repeatable expansion

    Micro-market playbook works again

Targets intentionally not set in this draft. Scorecard values: [to be populated from verified data].

13 / 15
DinghyFleetFounder input needed

14 · Team

Founders who build quickly and know the people who must adopt.

Adam

Co-founder · [Role, background and relevant industry experience — founder input required]

Founder input needed

Piotr

Co-founder · [Role, background and relevant build experience — founder input required]

Founder input needed

Biographies pending. No prior outcomes, pedigrees or partnerships are claimed.

14 / 15
DinghyFleetHypothesis

15 · The ask

Capital to prove the network — not just to build more software.

~$2.5m

18–24 months · range $2–3m · via DinghyFleet Incorporated (US)

  • 40%Distribution, partnerships & industry activation
  • 30%Product, reliability & integrations
  • 15%Onboarding, customer success & ops
  • 5%Legal, compliance & finance
  • 10%Reserve

Build the software. Win the network. Unlock the marketplace.

Illustrative fundraising scenario — not final terms or budget. Not an offer to sell securities.

15 / 15

Draft for founder review. Not an offer or solicitation to sell securities.