Marine Services: Dredging Contractor

What the Business Looked Like

A family-owned marine dredging business ran on the owner's expertise. The technology behind the business held no interest for him and the back office was not technical either, so there was no CRM, no call logging, and no structured outreach. Revenue depended on mobilizing whole waterfront communities at once, because a project only proceeds when enough neighbors commit together, and the accounting structure could not tell the owner what a job actually earned.

What Broke and What It Cost

Reaching an entire waterfront community depended on individual memory and unlogged phone calls, which is not a method that survives contact with a mobilization date.

Without a system, a resident who said yes on a phone call and a resident who was never reached looked identical. Coordination gaps in a project of that shape show up on site rather than in a report, which is the most expensive place for them to appear.

What Was Built, in Dependency Order

A CRM and phone stack stood up and operated day to day, plus a repeatable cluster-mobilization playbook: a verified contact list, a five-email sequence sent from the client's own accounts, call-priority lists ordered by open and click behavior, a certificate of insurance issued to the property owners' association, and a daily-report template delivered from the job site

1. 01CRM and phone system stood up and operated day to day
2. 02Cluster mobilization playbook, built once and cloned
3. 03Accounting integration architected against a sandbox first
4. 04Reporting, daily operations guide, and back-office ownership

What Changed

One mobilization coordinated from a single system, and a playbook the team runs on the next four communities without rebuilding it.

The roster grew send by send from 11 enrolled contacts to 15 valid email addresses plus two phone-only residents whose addresses were captured on the call because invoicing requires them. Every late arrival received the emails the cohort had already read, sent as a reply inside the existing thread so their inbox reads as one clean conversation. The property owners' association received a certificate of insurance, the scope distribution, and a daily-report commitment that became a template covering crew, equipment, work done and planned, on-track status, resident interactions, and photos, logged to the CRM timeline. That template is now recurring retainer scope for every future community project. Accounting integration was built against a sandbox with test data before production was touched, and the engagement converted to a month-to-month retainer at a figure the owner named himself.

"The client did not buy a retainer pitch. He watched the system run for six weeks and picked the number himself."