Fresh eyes wanted: help shape ProtocolDock

ProtocolDock has now moved beyond the alpha and beta stage, and I am looking for fresh testers to put the system through its paces.

The platform is live, the core systems are in place, and the next stage is about scrutiny. I want people who can use ProtocolDock with fresh eyes, test it properly, challenge the workflow, spot anything that feels awkward, and tell me what needs improving.

ProtocolDock has been built as a research-focused workspace for managing projects, protocols, documents, writing, file organisation, and research workflows in one structured environment. The aim is to reduce the mess of scattered folders, duplicated files, disconnected drafts, unclear version control, and expensive platforms that often do far more than researchers actually need.

In exchange for serious feedback, I am willing to give selected testers one year of Researcher-level access for free.

That is not a limited demo or a quick trial. It is full Researcher-level access for a year, giving testers the chance to use the platform properly across real projects, writing tasks, and research workflows. For some users, this could mean avoiding hundreds, or even thousands, of pounds in fees across other research, writing, storage, and collaboration platforms.

Who I am looking for

I am particularly interested in hearing from:

researchers managing active projects;
PhD students and postgraduate researchers;
supervisors or academics working with multiple documents and drafts;
research teams who need cleaner organisation and better workflow structure;
people who are willing to be honest, critical, and specific about what works and what does not.

What I need from testers

This is not about polite feedback or vague comments. I am looking for people who will genuinely scrutinise the system. I want to know where the workflow feels strong, where it feels unclear, where the interface needs refining, and where ProtocolDock could better support real research practice.

Useful feedback might include comments on project organisation, writing tools, file handling, document structure, version history, collaboration features, usability, onboarding, missing features, confusing labels, or anything that feels slower or more difficult than it should.

What testers get

Selected testers will receive:

one year of free Researcher-level access;
early access to new features as the platform develops;
the chance to influence the direction of ProtocolDock;
a research workspace that may replace several disconnected tools;
direct input into a platform being built around real research workflows.

ProtocolDock is already live, but this is the stage where fresh eyes matter most. The platform has passed the early alpha and beta phase, but I want it tested by people who have not been close to the build, who are not already used to its assumptions, and who can approach it like real users with real projects.

If you are a researcher, student, supervisor, or research professional who wants to try ProtocolDock properly and is willing to give honest feedback, I would like to hear from you.

Help scrutinise it, shape it, and make it better.

← All posts