DinghyFleet
Product roadmap

Building the reliable path from charter request to handover.

We are making the broker journey dependable first, then connecting brokers and operators around the decisions that keep a charter moving. This roadmap shows the outcomes we are pursuing—not a fixed release calendar.

See what we’ve shipped

Last reviewed · Updated as evidence changes

Direction without false certainty.

Our priorities are organised by what we are doing now, what should follow, and what we need to prove with live charter work. Scope can change as we learn; the customer outcome is the commitment.

Now
Actively building or validating on the broker journey.
Next
The intended next outcomes once the core journey is pilot-ready.
Pilot
Questions we will answer with real charter cases before expanding.
Show outcomes for

Showing 10 of 10 outcomes

Now

Make the charter journey reliable.

We are strengthening the connected path from request to offer, booking, and collaboration—so brokers can move real work forward without losing context or guessing what is blocked.

In progressBrokers

Complete a charter journey without losing context

Move a request through offer, booking, and collaboration as one connected case instead of rebuilding the story across screens and tools.

In progressBrokers

Know exactly what is blocking a booking

Make the difference between an active option, a confirmed booking, missing inputs, and a case ready for collaboration immediately clear.

In progressBrokers

Work reliably from desk or phone

Keep the critical broker journey usable across the devices used during live charter work.

Next

Connect brokers and operators without blurring responsibility.

The next layer is a controlled handoff: both sides share the charter context, while every decision still has a clear owner and evidence.

PlannedBrokers + Operators

Create one vessel record both sides can trust

Give broker and operator shared vessel context without creating conflicting versions of the same boat.

PlannedBrokers + Operators

Hand a booking to the operator without starting over

Carry the commercial and operational context into shared collaboration while keeping ownership of every next action explicit.

PlannedBrokers + Operators

Separate submitted skipper documents from operator approval

Make it impossible to confuse a supplied licence, VHF certificate, or sailing résumé with the operator's final qualification decision.

PlannedBrokers + Operators

See whether the charter file is operationally complete

Show crew data, arrival information, extras, payments, and required documents as distinct dependencies with a clear owner.

PlannedBrokers + Operators

Confirm readiness before handover

Turn departure readiness into an explicit decision that combines operator readiness with the required client inputs.

Pilot

Prove the workflow with real charter cases.

We will use live work—not feature assumptions—to find friction, test reliability, and decide which part of the broker–operator network deserves expansion.

PlannedBrokers

Run real broker cases end to end

Support selected brokers through live charter work so the connected journey is tested under real deadlines and exceptions.

ExploringBrokers + Operators

Earn the operator-network expansion

Choose the next operator-network outcome from observed handoff friction and usage rather than an assumed feature list.

Progress you can verify.

Outcomes appear here once they are available to customers and their delivery criteria are met.

View all updates
  • A clearer client decision journey, safer organization closure and smoother offers

    This week DinghyFleet turned the customer portal into a more complete selection and handoff experience, added a controlled organization closure lifecycle, and removed friction from offer editing and loading.

    Read the update
  • Clearer pipeline insight, smarter yacht matching and faster browsing

    This week DinghyFleet made pipeline performance easier to act on, brought request context directly into offer building, and reduced friction when browsing and importing yacht inventory.

    Read the update
  • Private yacht photography, calmer previews and clearer product direction

    This week DinghyFleet strengthened how yacht photography is protected, smoothed the loading experience across client-facing pages, and made the public roadmap and community easier to reach.

    Read the update
Long-term direction

Toward an operating system for charter.

DinghyFleet’s long-term direction is a connected operating layer for charter—from commercial intent to operational completion. We will earn that expansion one validated workflow at a time, starting with the broker journey and the broker–operator handoff.

This is a strategic direction, not a delivery commitment or release timeline.

Where does your charter workflow break?

If you manage live charter cases as a broker or operator, we want to understand the handoffs, missing information, and decisions that cost you time.

Bring one real case: your role, the workflow stage, what happened, your current workaround, and the operational impact.

Opens a scheduled conversation with the product team—no feature voting, no form.