The plan

Architecture, numbers, and dates.

The technical stack, market sizing, pricing, unit economics, timeline, hiring, and risks behind the overview.

Prepared forValsoft / DockMaster
Date24 Apr 2026
Horizon18 months
01

Tech stack

Request path: DockMaster DB → agent runtime → customer channel (SMS or web). Five layers sit underneath. Each is listed below.

01

Ingestion

Change-data-capture against the DockMaster database with a webhook fallback for event-driven tables and a nightly reconciliation job as a backstop. Nothing novel here. The point is that the pipeline is boring and idempotent.

  • CDC on customers, boats, slips, service orders, parts, invoices
  • Webhooks for booking state transitions
  • Nightly full-table reconcile for drift
02

Knowledge layer

A vector index over service history, SOPs, and part fitment paired with a structured query layer for the things a language model should never guess: pricing, inventory counts, technician availability.

  • pgvector or Pinecone for unstructured (notes, manuals)
  • Postgres read replica for structured truth
  • Row-level tenant isolation from day one
03

Agent runtime

Claude with tool use, scoped to a tight set of functions: check-parts, quote-service, find-slot, book-appointment, escalate-to-human. The model plans; the tools do. Every tool call is logged and reversible.

  • Claude Sonnet 4.6 default, Opus 4.7 for complex triage
  • Prompt caching on the system & tool schemas
  • Hard guardrails on write actions (spend caps, confirmation steps)
04

Channels

Start with SMS (Twilio) and a web widget because that is where the missed call actually lives. Voice comes next once the text surface is proven.

  • Twilio SMS + a lightweight embeddable web widget
  • Vapi or Retell for voice in phase two
  • Email digest for marinas that still prefer it
05

Observability & safety

Every conversation is a trace. Every booking is a signed receipt. Marinas can audit what the agent did on their behalf, and so can we, and that is how trust gets built in year one.

  • Trace per conversation: tool calls, tokens, cost, outcome
  • Eval harness on a frozen set of real marina conversations
  • Kill switch + human handoff triggered by confidence drop
02

GTM plan

Market sizing, ICP, pricing, unit economics, 18-month timeline, hiring, and risks. Anchor date 24 Apr 2026.

Market

Market sizing

TAM$4.8BMarine + adjacent field service

U.S. boating industry direct economic impact across marinas, dealers, service centers, and adjacent field-service operators. The addressable software layer sits within this base.

NMMA 2026 Economic Impact Study
SAM$18MDockMaster installed base

1,000+ marinas worldwide currently on DockMaster. At an $18K average contract value, the BluSynq layer represents an $18M ARR ceiling inside existing relationships.

DockMaster.com / Aspire Software Integration Announcement
SOM$1.8M18-month wedge

~190 DockMaster marinas converted by end of 2027, roughly 19% penetration of the base, on par with typical add-on attach rates inside a parent portfolio.

Umbrex Research / Digital Applied 2026
ICP

Ideal customer profile

Criteria for the first ten paid marinas. Design partners must match all four.

Slip count
100 – 500 slips
Mid-size marinas represent ~50% of the U.S. market. Large enough that missed calls translate to real revenue; small enough that a single champion can sign.Grey Aspen Capital / Association of Marina Industries
Service revenue mix
≥ 20% of total
Non-boat revenue (service, parts, winterization) reached 26.2% of total revenue at benchmark operators by 2025. Pure storage yards are not the target.MarineMax Fiscal 2025
Staff hours
Closes by 5pm
Regional marinas with a front-desk gap after hours. That gap is where BluSynq earns its keep.
DockMaster tenure
≥ 2 years
Data is clean, the integration is trusted, and the CS relationship is warm.
Pricing

Pricing

Three tiers tied to conversation volume. Overage at $0.50 per conversation beyond cap. Blended ACV: ~$9.6K.

TierMonthlyIncludedFit
Starter$299/mo200 conversations / moSmall marinas, single location
Growth$799/mo1,000 conversations / moMid-size marinas, full service dept
Scale$1,799/moUnlimited + voice + analyticsMulti-location operators
Overage$0.50 / conversation beyond cap
Unit economics

Unit economics

Distribution through DockMaster CS keeps CAC small and trust pre-built. Steady-state targets below.

$9,600Blended ACVSamsara Platform / Fractional Executive Playbook
$3,100CAC (via DockMaster CS)
~72%Gross marginWePitched 2026 — AI-native SaaS adj. benchmark: 70%
4.7 monthsPayback period
115%Net revenue retention (target)WePitched Series A Benchmarks 2026 — top-tier floor: 125%
8.4×LTV / CAC at 3yr
Timeline

18-month timeline

Six quarters. Each row lists the headline objective and the KPIs the team is held to at quarter-end.

Q2 2026Apr – Jun

Design partners

Sign 8 DockMaster marinas as unpaid design partners. Ship the MVP: SMS channel, parts check, scheduling, booking. One live, audited booking per partner per week by end of quarter.

Design partners signed
8
Live bookings / wk / partner
1+
Paid customers
0
ARR
$0
Q3 2026Jul – Sep

First dollars

Convert 6 of 8 design partners to paid at Growth tier. Add 15 net-new paying marinas through DockMaster CS at renewal conversations. Ship first case study with real after-hours revenue numbers.

Paying marinas
21
Exit ARR run-rate
$202K
Avg after-hrs revenue captured / marina
$4.2K / mo
Gross margin
64%
Q4 2026Oct – Dec

Season close & voice

Ride the end-of-season service rush. Close 19 more marinas. Ship voice channel beta to Scale-tier customers. Begin discovery on adjacent vertical (Progitek RV parks, short-list of 6 portfolio cousins).

Paying marinas
40
Exit ARR run-rate
$384K
Voice beta customers
5
Adjacent verticals scoped
2
Q1 2027Jan – Mar

Off-season push

Marina off-season = sales season. Dedicated outbound to the dormant half of the DockMaster base. Close 25 more. Tighten onboarding to a one-day lift.

Paying marinas
65
Exit ARR run-rate
$624K
Onboarding time (p50)
< 1 day
NRR (cohort)
112%
Q2 2027Apr – Jun

Second vertical pilot

Season ramp + first adjacent pilot. Sign 3 RV-park design partners on the shared platform (new adapter, same agent). Cross 100 paying marinas.

Paying marinas
105
RV-park design partners
3
Exit ARR run-rate
$1.0M
Adapters in production
2
Q3 – Q4 2027Jul – Dec

Portfolio platform

Promote BluSynq to a Valsoft-level offering. RV parks paid, storage pilot live, marinas over 180. Platform becomes the integration target for any new Valsoft acquisition in field service.

Paying customers (all verticals)
205
Exit ARR run-rate
$1.8M
Verticals with paying customers
3
Gross margin
72%
Team

Hiring plan

Q2 2026Founding engineer (2), applied AI lead, product
Q3 2026+ CS / onboarding specialist, partnerships (DockMaster embed)
Q4 2026+ Second full-stack engineer, first AE
Q2 2027+ Vertical lead (RV), platform engineer, second AE
Risks

Risks and mitigations

Seasonality

Marina revenue is compressed into May – Sep. Pilot metrics could look worse in shoulder months.

MitigationLead with off-season-friendly KPIs (staff hours saved, inbound coverage) alongside after-hours revenue. Structure pricing so off-season months still generate signal.

Data quality drift

Parts catalogs and technician calendars are only as good as what the marina maintains. An agent citing stale data becomes a trust problem fast.

MitigationConfidence scoring on every tool call. Anything below threshold hands off to staff with the context pre-drafted. Weekly data health report to each operator.

DockMaster internal priorities

BluSynq depends on DockMaster introducing the product through CS. If DockMaster's roadmap shifts, distribution slows.

MitigationFormalize a co-sell agreement with revenue share before scaling. In parallel, prove the adapter pattern on a second vertical so the motion is not single-threaded.

LLM economics

Model costs could compress margin if conversation volume spikes faster than price realization.

MitigationPrompt caching on all system prompts and tool schemas. Route easy intents to smaller models. Consumption pricing ensures revenue scales with cost.

Questions, corrections, and pushback welcome. The overview frames the argument; this page is the underlying detail.

← OverviewDemo →