Public website
A polished public presence for the syndicate, its waters, rules and membership information.
Part of the connected Syndicate.fish product.Case study · Syndicate.fish
A syndicate website that became a proper member platform.
Syndicate.fish brings the public presence, member experience and operational needs of a fishing syndicate into one connected digital product.
The problem
Members and administrators needed more than a collection of pages.
A syndicate has public information, private member information, rules, communication and practical administration happening at the same time.
Treating those as separate website add-ons creates friction. The better answer was to think about the whole experience as one product: public when it should be public, secure when it should be private, and shaped around the people actually running it.
What we built
One platform, several jobs.
The goal was not to manufacture feature count. It was to give the syndicate a coherent foundation for the work members and administrators actually need to do.
Member experience
Secure services for members rather than pushing private information into a public website.
Part of the connected Syndicate.fish product.Profiles & vehicles
Structured member information that can support day-to-day syndicate administration.
Part of the connected Syndicate.fish product.Communication
A clearer foundation for member messaging, updates and operational information.
Part of the connected Syndicate.fish product.Admin workflows
Product thinking around the jobs the syndicate actually needs to manage, not just pages to publish.
Part of the connected Syndicate.fish product.Room to evolve
A connected platform that can take later phases without turning each new requirement into a separate tool.
Part of the connected Syndicate.fish product.The engineering underneath
The public experience is only the visible part.
A platform like this has to keep working as requirements change, member needs develop and new operational features arrive.
Bad Otter treats that as ongoing product engineering: controlled source changes, validation, considered releases and a roadmap that can continue after the first live version.
The customer gets the benefit of that discipline without having to learn our internal workflow.
Have a business with awkward workflows?
We can build around how it really operates.
You do not need to find a product that almost fits and then change the business to suit it.