labs@atheron:~/industries/fisheries-aquaculture/rescue$ recover --codebase --modernise

Hatchery records rescue

Macros replaced before next season.

Many hatcheries and farms run on workbooks or databases that one person built years ago. When that person leaves, every new season is a risk. We rebuild the records as a web system, move the history across and check it, and keep the old files in use until you are ready to switch.

Start a project See the example projects

// what matters here

What is different in this industry.

Find out what it really does

We read the workbooks and macros first, so every calculation the old files make is carried across.

History checked line by line

Every season's records are moved and checked against the originals before you rely on them.

No switch mid-season

The old files stay in use until the new system is ready, and the switch is planned for a quiet time.

// example projects

Priced examples for this service.

Each one is hypothetical, labelled as such, and priced live from our rate card. Open any of them in the estimator and make it yours.

Example projectWeb app

Hatchery records rebuilt

Hypothetical. Not a client, not a result.

// The problem

A hatchery runs broodstock, egg, feed and mortality records in a set of Excel workbooks full of macros that one retired staff member wrote, and each new season risks breaking them.

// What we would build

A web system that replaces the workbooks with broodstock, spawning, incubation, feed, mortality and release records, reads water temperature from the existing monitoring system, moves every season's history across and checks it, and puts the figures the managers ask for on dashboards. Release criteria and health records follow the requirements your biologists and veterinarian set.

// What is in it

Broodstock, spawning, incubation, feed, mortality and release records
Water temperature read from your existing monitoring system
Every season's history moved from the workbooks and checked
Dashboards for survival, growth and feed by tank and by season
Reports in the formats your funders and managers ask for

// Stack

Next.js
PostgreSQL
Metabase or a custom dashboard
Monitoring system API
DigitalOcean

// estimate

Build: ≈ US$68,300 to US$104,000, delivered within 17 weeksCAD 97,300 to 148,800
Hosting: ≈ US$176 a monthCAD 250 a month
Support: ≈ US$2,500 a monthCAD 3,565 a month

Prices in your currency are estimates from today's Bank of Canada rate. All invoicing is in CAD or USD.

Timeline by milestone

Discovery: 2.9 to 3.4 weeks
Design approved: 2.9 to 5.4 weeks
Core features: 2.4 to 3.9 weeks
Full build: 1.4 to 2.4 weeks
Testing and fixes: 0.9 to 1.4 weeks
Launch: 0.9 to 1.4 weeks

Outside our hands, and added to the calendar

Access to your monitoring system's data: 1 to 4 weeks

How it is paid

Deposit 20%: CAD 19,460 to 29,760
Discovery 7.7%: CAD 7,492.10 to 11,457.60
Design approved 7.7%: CAD 7,492.10 to 11,457.60
Core features 23.3%: CAD 22,670.90 to 34,670.40
Full build 15.5%: CAD 15,081.50 to 23,064.00
Testing and fixes 7.7%: CAD 7,492.10 to 11,457.60
Launch 8.1%: CAD 7,881.30 to 12,052.80
Holdback, 30 days after launch (10%): CAD 9,730 to 14,880

Start from this example

// questions

Questions we get about this.

Can you rescue a hatchery database nobody understands any more?

Usually, yes. We start with a takeover review that works out what it does, then plan the rebuild from what we find.

Will our hatchery calculations stay the same?

Every calculation is carried across and checked against the old workbook's results before the switch.

Can staff keep using tablets in the hatchery?

Yes. The new system works in a tablet browser, and an app can be added if staff need it away from Wi-Fi.

Back to the industry: Fisheries and aquaculture About the service: Rescue and modernization

// next

Not quite your project?

Tell us what you have in mind. We will come back to you with a range and the questions that would narrow it. Or book a call and talk it through.

Start a project Book a call