An agent layer for the data DockMaster already collects.

BluSynq sits on top of DockMaster and lets its existing operational records, inventory, schedules, and service history, answer customers directly, instead of only the back office.

In context

Prepared by Rowan McDonald

Where the data stops.

DockMaster captures the operational record. Today, it terminates at the back office.

Boat raised on a marina service lift — A typical marina service yard. Every lift, part, and technician here is already tracked in DockMaster.

DockMaster customers have years of structured operational data — inventory levels, service history, equipment profiles, parts lead times, technician schedules. Today, that data only serves staff. It does not reach the customer.

Operational data flow, today

The diagram is the working assumption we’re here to discuss. The customer-facing edge is the part we’re proposing to close.

What we’re building.

Operational data, surfaced to the customer

BluSynq reads from DockMaster's existing inventory, scheduling, and customer records. When a customer calls or texts, the agent already has their boat, service history, required parts, current stock, and lead times. Staff is in the loop only when escalation is warranted.

Example

A customer texts at 9pm asking about winterization for their 2019 Yamaha 150. BluSynq checks parts inventory, confirms the impeller kit is in stock, finds an available technician slot, and proposes the appointment before a staff member sees the message.

Conversations feed back as structured signal

Every handled interaction produces a structured signal: what customers are requesting, which parts are causing delays, where stock and demand diverge. That signal flows back into DockMaster's inventory and scheduling guidance.

Example

Over 30 days: 14 Mercury-engine customers request the same service; 6 are delayed by a back-ordered part. The reorder threshold for that SKU is flagged for review.

One architecture across portfolio verticals

The same agent infrastructure, vertical-specific configuration, operational data integration, and signal feedback, is templated and re-deployed across other field-service companies in the Valsoft portfolio. Marina is the first instance, not the only one.

Example

A car-rental portfolio company reuses the same architecture: fleet availability stands in for parts inventory, vehicle service history for boat records. Same platform, new adapter.

Portfolio adapter map

MarinaPilot

Field ServiceQ3

Car RentalNext

Equipment ServiceQ2

Travel & LeisureLater

Shared BluSynq platform

Distribution.

Built on existing Valsoft distribution and customer relationships.

Valsoft portfolio · representative

Land— Existing DockMaster base

DockMaster already has an installed base of marina operators. BluSynq is positioned as a capability on top of data they already pay to collect, not a separate AI product. Introduction happens through CS at renewal or via a dedicated outreach to current accounts.

Prove— Design partner program

First ~10 DockMaster customers onboarded as design partners with a 30–60 day activation window. The goal is concrete numbers: after-hours revenue captured, staff hours saved, appointments booked without human handling. Those numbers become the reference for everything that follows.

Price— Consumption-based

Pricing tied to conversations handled or appointments booked, not seats. Aligned with how marinas already think about cost per outcome. Low friction to start, scales with usage.

StarterUp to 200 convos / mo

GrowthUp to 1,000 / mo

ScaleUnlimited + analytics

Expand— Portfolio rollout

The marina playbook becomes the template. Valsoft introduces BluSynq at the operating-company level across other field-service verticals. Each new vertical adds an adapter on top of the shared platform. Distribution flows through existing Valsoft relationships rather than a new sales motion.

Month 1–2Design Partners

Month 3–4Marina Rollout

Month 6First Adjacent Vertical

Month 12Portfolio-Wide Platform

Prototype

Walkthrough.

A short prototype showing how a service booking would move through the system. Rehearsed sequence, not a live integration.

Customer names, part numbers, and timings are illustrative.