ferenc.rocks/

Proof » FishFlow

FishFlow – Booking system for small fishing lake operators

2026–present · Active ALPHA

The situation

FishFlow is an active ALPHA-stage booking system for small fishing lake operators.

Many small operators still manage bookings through phone calls, messages, personal knowledge, trust, and manual coordination.

That is not necessarily a problem. These habits often exist because they match the way the business actually works.

Where the complexity lived

The difficult part is not building a calendar.

A fishing lake booking may involve fishing spots, cabins, docks, boats, combined resources, seasonal rules, half-day or overnight bookings, multi-day stays, manual confirmation, and changes made by the operator.

Not every booking should be fully automated. Some need a human check, and some rules depend on the specific lake.

The system needs more structure without automating away the judgment and flexibility the operator still needs.

What I worked on

I am building FishFlow as an active ALPHA grounded in the workflow of a real fishing lake operator.

The work so far has focused on the multi-tenant foundation, booking and resource modeling, and request-based booking logic.

I am also shaping the public booking flow and the operator-facing admin workflow through ongoing validation with a real lake operator.

Why this matters

The useful work starts with understanding the real workflow before deciding what the software should automate.

FishFlow is about turning a local, manual, trust-based booking process into a clearer web system while preserving the parts that still require human judgment.

Technical context

Laravel, Livewire, MariaDB, multi-tenant architecture, booking and resource model, request-based booking, public and operator-facing workflows, small-operator booking logic.