Seafood processing
Thirteen spreadsheets travelling by email became one system of record
Consolidating them cost the director half a working day, and by the time management saw the numbers they described the past. Now it is one screen, updated the moment fish is landed.
A seafood processing company. Catch, processing, warehouse and shipping across two legal entities and a short, intense fishing season.
spreadsheets became one system of record
departments now working in the same system
of the director's time per consolidation, gone
dashboard, updated as fish is landed
Problem
Numbers that were already history by the time anyone saw them
Thirteen Excel files travelled by email between six departments — catch, processing, warehouse, shipping, quotas, reporting. Every hand-off was a chance to overwrite someone's version. Consolidating them into one picture cost the director half a working day, and the picture it produced described a week that had already happened. During a fishing season that lasts weeks, that is the difference between managing and reacting.
Solution 1
One system of record for products
Catch, processing, warehouse and shipping now live in one place, and it is the primary accounting tool across every department — not a reporting layer bolted onto the side. Norms, tare weights, permits and quota limits are reference data in one spot: changing a norm means editing one cell, not thirteen files.
Solution 2
One live dashboard for management
Today's catch, processing and shipments alongside several years of dynamics. Getting that picture used to mean hours of paging through multi-sheet spreadsheets; now it is one screen, and it updates the moment fish is landed.
Solution 3
A rollout staged so that people would actually use it
The staff who enter the data have low computer literacy and a season with no slack in it. So the familiar spreadsheets stayed as the front end and the new machinery went underneath — same screens, different engine. Adoption came first; the full platform migration is planned as phase two. A technically superior system that nobody enters data into is worth nothing.
Thirteen Excel files moving between six departments by email
Half a working day of the director's time spent consolidating
Management sees the numbers late
Changing a norm means editing it in several files
One system of record, one version of the truth
The picture assembles itself
One screen, updated as fish is landed
Reference data lives in one place
What changed
instead of thirteen files
Now the primary accounting tool across every department
of the director's time, freed
The consolidation work disappeared rather than moving to someone else
for the whole operation
Today's numbers next to several years of dynamics
before elegance
Familiar front end kept on purpose; platform migration is phase two
Under the hood
What this is built from
- Google Sheets kept as the front end, driven through the Sheets API
- Python service layer for consolidation, norms and quota limits
- Separate web dashboard for management
- Staged migration plan — front end swapped last, on purpose
Let’s talkabout your bottleneck
Hiring, a project, or a second opinion on an agent design — Telegram is the fastest way to reach me. I read everything myself.
mail [at] artemborisov.ru
Based in Russia (UTC+12) · open to relocation