Ryan Ament
Diver. Crew Lead. Co-Founder.
Ryan didn't start out building software.
He started in the water — cleaning hulls, managing dive crews, and dealing with the same scheduling, paperwork, and invoicing headaches every operator faces.
Today, he still runs dive teams. That means DockOps isn't built from theory — it's built from what actually happens on the job.
What Ryan's lived:
- Managing dive crews and schedules
- Tracking jobs manually across boats
- Handling late-night invoicing after long days
- Dealing with inconsistent or unclear crew pay
“I didn't build DockOps to start a software company. I built it because I was tired of the admin slowing everything down.”
Mikey Curtis
Co-Founder. Builder Behind the System
Mikey is the one turning real-world problems into something that actually works.
He works side-by-side with operators — especially Ryan — to take what's happening in the field and build tools that are simple, fast, and usable without training.
What Mikey focuses on:
- Keeping everything simple and easy to use
- Removing unnecessary steps and clicks
- Making sure it works in real conditions, not just demos
“If it's confusing or slows crews down, it doesn't belong in the product.”
Why It Matters Who Builds Your Tools
Most software is built by people who have never:
- ×Run dive crews
- ×Dealt with changing schedules
- ×Stayed up late doing invoices
- ×Tracked jobs across paper and spreadsheets
DockOps is different.
It's built inside real operations — and tested there before anything is released.
If it doesn't work on the dock, it doesn't ship.