What LakeOps deliberately doesn't do

Most software pages tell you what a product does. This one is the other list, because if you run a dock company the fastest way to know whether LakeOps fits is to find out what it refuses to do — and each of these is a decision, not a gap we are working on.

There is no calendar, and there will not be one

Every general field-service tool starts from a technician, a date and an address. Put a dock season into that shape and you get a 340-row plan that is fiction by the second week of May: ice-out moves three weeks year to year, a north wind closes an exposed shoreline by ten in the morning, and half your customers ring the week they arrive.

In LakeOps a job sits in a backlog attached to a stretch of shoreline. You send a boat, a crew and a set of gear at a lake and the zones they are working, and they take whatever is still open there when they arrive. When the wind turns you point them at the lee side and nothing has to be unwound, because nothing was ever assigned. That is the single biggest difference between this and the alternatives, and it is worth understanding before you decide either way — the long version is in why the March plan is gone by May.

There is no route optimisation

Optimising a route presupposes an assignment and a fixed sequence. On water the sequence is decided by whoever can see the wind, and a solved route is stale by ten on exactly the days it would have mattered. There is also no marine routing service to optimise against — a boat does not follow roads.

What the crew app does instead is rank the open work by distance and bearing from where the boat actually is, recomputed on the device as it moves, so a crew that finishes early is never guessing what is nearest.

There are no invoices, and no QuickBooks sync

No invoice objects, no invoice numbers, no accounting integration to keep alive. A job completes, prices itself from your price list, and the customer gets an email listing exactly what was done at their property — with the crew's photographs — and a link to pay. Money comes back against the job.

That is not the same as not collecting. There is an aging report, there are statements, there is an optional reminder schedule and there are optional late fees; and if you would rather bill your own way, the completed-work report exports to CSV and PDF for whoever does your books. The reasoning is in getting paid without an invoicing system.

There is no per-user pricing

You hire six people in April and keep two in July. Charging per head would be charging you for hiring, and the first time somebody is left off the app to save a seat, half your day stops being recorded. Users are unlimited on every account; you are charged for the properties you serviced in the last twelve months, because that is what the work actually is.

Some smaller ones, for completeness

• No customer portal with a login. Your customers are lake-house owners who will not maintain a password for a dock company. The link in their email is the credential and it opens one job.
• No estimates or quote documents. Work a crew spots — a fraying cable, a cracked bracket — is recorded against the piece it is on and becomes a job when somebody sells it.
• No inventory or parts system. LakeOps tracks the customer's equipment, not your stock.
• No timesheet or payroll export beyond the productivity and costing reports, which give you minutes per person per stop.

What it does do, briefly

It holds every dock section, lift, canopy and raft as its own record, pinned where it goes in the water and where it stacks for the winter; it sends boats at shorelines; it keeps working when the signal does not; and it prices and collects the work the day it is finished. If that is the shape of your business, the features pages are the long answer.