Software and web studio · St. John’s, NL · fishing first, any trade on paper
DeepGrade is two people in Newfoundland. We started on the wharf, where the software had to work with no signal, and we build the same way for every trade that still runs on paper: fitted to how the operation already works, by the people who write the code.
St. John’s harbour from the south side, looking toward the Narrows.
CREW SETTLEMENT STATEMENT
Cape Race · Snow crab · 4-day trip
Statement
2026-004127
| Crew | Share | Gross | Net |
|---|---|---|---|
| Ches Whiffen captain | 1.25 | $3,911.76 | $3,111.76 |
| Gerard Pittman mate | 1.10 | $3,442.36 | $3,442.36 |
| Wade Sheppard deckhand | 1.00 | $3,129.41 | $2,729.41 |
| Ronnie Bursey deckhand | 1.00 | $3,129.41 | $3,129.41 |
Showing 4 of 6 aboard
The wharf, the plant floor, the crew's pay and the buyer, on a coast where the signal ends at the breakwater.
A checklist done on site, a report typed up afterwards, and a client emailing to ask where it is.
Crews and equipment spread across a region, with the day's hours, logs and safety forms still on paper.
Dispatch on a whiteboard, trip sheets back on Friday, and billing that waits for the paperwork.
Counts and quality checks on paper, the true cost of a run known at month end, labels typed by hand.
Orders by phone and email that somebody keys in, and customers who cannot check stock without driving over.
Remote sites, heavy equipment, scale and load tickets, and inspections that live in a binder until the audit.
Bookings, renewals, work orders and client questions that all arrive by phone and get answered one at a time.
The deck, the dock and the cold room have no bars, which is exactly where a landing is born. Dockside is built so that capture keeps working there: records queue on the device, the list keeps reading from what the phone already holds, and the queue drains itself when you come back in range.
Send one back in range and watch the server refuse it. That half is real too, and nobody demos it.
WRITING THROUGH · 1 on device · synced 06:42 NDT
Cut the signal and keep recording. Landings queue on the device, the list keeps reading from what the phone already holds, and the queue drains itself the moment you are back in range. Sync is idempotent, so a retry never books a landing twice.
One track runs the operation: what got landed, what it graded out at, and what the crew is owed. The other puts the operation online and sells from it. Start with whichever is costing you most. They do not have to arrive together.
A one time build, plus a monthly that runs it.
Record the landing on the wharf, with no signal, and never key it again.
Know what a load graded out at, and what that is actually worth, before the shift ends.
Split the lay to the cent, and run the plant payroll off the same landings.
A flat one time build. The care plan is optional.
A site that looks like your operation and turns a visitor into a phone call.
Sell direct, take the order and the money, and keep the markup.
None of these is a shrink-wrapped product. They are the five shapes of work we have already scoped in detail, so a call starts from a real starting point instead of a blank page. If your trade is not fishing, start from your own industry page: what we would build for it, and which of that is already built and tested. If your operation needs something none of them describes, say so and we will scope it.
Email the studio and one of us answers, most days the same day. That is the whole company, which is rather the point: a studio this size can fit the work to your floor instead of to a product roadmap.
Devon Hewitt
Builds the software
Writes the code that ends up on your dock and the tested packages the math lives in. Offline first, because the wharf gave him no choice.
Jacob Skanes
Growth and partnerships
Usually your first call. Maps where the data leaks between the boat and the buyer, and keeps the build moving once it starts.
Enterprise seafood software is quote only, and you will not see a figure until you are several calls deep with somebody whose job is to work out what you can afford. Ours is on the page, in Canadian dollars.
Swipe the table for the monthly →
| Build | One time | Typical to | Monthly |
|---|---|---|---|
| DocksideOffline catch capture | $8,450 | $18,900 | $299/mo |
| GradeLineGrading and live yield | $6,950 | $14,900 | $249/mo |
| SettleCrew share and payroll | $4,950 | $9,900 | $149/mo |
| BridgeWebsite and brand | $2,450 | $5,500 | $99/mo |
| WharfOnline storefront | $4,450 | $9,900 | $149/mo |
Where you land in a range depends on your operation: how many boats or lines, what has to keep working with no signal, and what it has to talk to. We walk that once, with the two people who build it, and you leave with a quote you can hold us to.
We can build the data spine that traceability work sits on, as a scoped build, and we will describe exactly what it does and does not do. What we will not do is put a regulatory promise on a price list that a two person studio has not shipped and could not stand behind in an audit.
That sentence costs us work. It is staying on the page, because the alternative is being the vendor who said yes and found out later.
The rest of what we refuse, and what happens when a build goes wrong, is on how we work.
A package off this page, or the thing only your operation needs. Tell us where the numbers go missing between the work and the office, and we will come back with times.